Re: fsck on boot...revisited

2013-09-20 Thread Andrei POPESCU
On Vi, 26 iul 13, 13:51:39, Bob Proulx wrote: > > For the larger majority of users the current default setting of > FSCKFIX=no is a problem because it will result in a system that won't > boot without a human on the console to manually answer yes to the fsck > questions. On a desktop you are ther

Re: fsck on boot...revisited

2013-07-29 Thread Dan Ritter
On Thu, Jul 25, 2013 at 10:09:00AM -0500, Tim Nelson wrote: > - Original Message - > > On Thu, Jul 25, 2013 at 09:28:56AM -0500, Tim Nelson wrote: > > > I have an interesting use case where a Debian Lenny server runs > > > headless, and is at the mercy of poor power conditions > > > (enviro

Re: fsck on boot...revisited

2013-07-26 Thread green
Bob Proulx wrote at 2013-07-26 14:51 -0500: > I always set FSCKFIX=yes in /etc/default/rcS and think that is the > best default. I agree with Bob's comments about this, in general, and have just now gone and set FSCKFIX=yes on a particular server because it would be better for it to boot with a pa

Re: fsck on boot...revisited

2013-07-26 Thread Dom
On 26/07/13 20:06, Ralf Mardorf wrote: On Fri, 2013-07-26 at 19:01 +0100, Dom wrote: On 26/07/13 17:53, Ralf Mardorf wrote: On Fri, 2013-07-26 at 11:54 -0400, Stefan Monnier wrote: The system in question is running from an SSD, which I assume changes your assumptions quite a bit. With a tradit

Re: fsck on boot...revisited

2013-07-26 Thread Bob Proulx
Roger Leigh wrote: > green wrote: > > Tim Nelson wrote: > > > On occasion, we find that a filesystem error is bad enough that > > > instead of auto{matically|magically} fixing the issue and continuing > > > to boot, the system hangs, needing a root password entered for a > > > manual fsck to be run

Re: fsck on boot...revisited

2013-07-26 Thread Ralf Mardorf
On Fri, 2013-07-26 at 19:01 +0100, Dom wrote: > On 26/07/13 17:53, Ralf Mardorf wrote: > > On Fri, 2013-07-26 at 11:54 -0400, Stefan Monnier wrote: > >>> The system in question is running from an SSD, which I assume changes your > >>> assumptions quite a bit. With a traditional HDDs, the loss of po

Re: fsck on boot...revisited

2013-07-26 Thread Dom
On 26/07/13 17:53, Ralf Mardorf wrote: On Fri, 2013-07-26 at 11:54 -0400, Stefan Monnier wrote: The system in question is running from an SSD, which I assume changes your assumptions quite a bit. With a traditional HDDs, the loss of power causes a head crash, etc which does in turn lessen the li

Re: fsck on boot...revisited

2013-07-26 Thread Ralf Mardorf
On Fri, 2013-07-26 at 11:54 -0400, Stefan Monnier wrote: > > The system in question is running from an SSD, which I assume changes your > > assumptions quite a bit. With a traditional HDDs, the loss of power > > causes a head crash, etc which does in turn lessen the life of the drive. > > Actually

Re: fsck on boot...revisited

2013-07-26 Thread Stefan Monnier
> The system in question is running from an SSD, which I assume changes your > assumptions quite a bit. With a traditional HDDs, the loss of power > causes a head crash, etc which does in turn lessen the life of the drive. Actually, I fail to see why a power outage would have any negative effect o

Re: fsck on boot...revisited

2013-07-26 Thread Dan Ritter
On Thu, Jul 25, 2013 at 09:28:56AM -0500, Tim Nelson wrote: > I have an interesting use case where a Debian Lenny server runs headless, and > is at the mercy of poor power conditions (environmental monitoring at a > remote storage building). We used to have issues with the server not coming > up

Re: fsck on boot...revisited

2013-07-25 Thread Roger Leigh
On Thu, Jul 25, 2013 at 03:17:10PM -0500, green wrote: > Tim Nelson wrote at 2013-07-25 09:28 -0500: > > On occasion, we find that a filesystem error is bad enough that > > instead of auto{matically|magically} fixing the issue and continuing > > to boot, the system hangs, needing a root password en

Re: fsck on boot...revisited

2013-07-25 Thread green
Tim Nelson wrote at 2013-07-25 09:28 -0500: > On occasion, we find that a filesystem error is bad enough that > instead of auto{matically|magically} fixing the issue and continuing > to boot, the system hangs, needing a root password entered for a > manual fsck to be run. > > My question is thus:

Re: fsck on boot...revisited

2013-07-25 Thread Tim Nelson
- Original Message - > Hi Tim, > > > Back to the original question(s), how can I make this the most > > robust > > system (not of all time, but in this use case scenario), both in > > data > > integrity and ability to fully boot? > > I'd set up a system that boots from a read only file sy

Re: fsck on boot...revisited

2013-07-25 Thread Simon Rettberg
Hi Tim, Back to the original question(s), how can I make this the most robust system (not of all time, but in this use case scenario), both in data integrity and ability to fully boot? I'd set up a system that boots from a read only file system that is all set up to run the services you n

Re: fsck on boot...revisited

2013-07-25 Thread Tim Nelson
- Original Message - > On Thu, Jul 25, 2013 at 10:33:56AM -0500, Tim Nelson wrote: > > - Original Message - > > > > Does the 'FSCKFIX' option within /etc/default/rcS do what I > > > > need? > > > > > > Yes, but your disks will continue to degrade. One morning you > > > will wake up

Re: fsck on boot...revisited

2013-07-25 Thread Tim Nelson
- Original Message - > On Thu, Jul 25, 2013 at 10:09:00AM -0500, Tim Nelson wrote: > > - Original Message - > > > On Thu, Jul 25, 2013 at 09:28:56AM -0500, Tim Nelson wrote: > > > > I have an interesting use case where a Debian Lenny server runs > > > > headless, and is at the mercy

Re: fsck on boot...revisited

2013-07-25 Thread Tim Nelson
- Original Message - > On Thu, Jul 25, 2013 at 09:28:56AM -0500, Tim Nelson wrote: > > I have an interesting use case where a Debian Lenny server runs > > headless, and is at the mercy of poor power conditions > > (environmental monitoring at a remote storage building). We used > > to have

fsck on boot...revisited

2013-07-25 Thread Tim Nelson
I have an interesting use case where a Debian Lenny server runs headless, and is at the mercy of poor power conditions (environmental monitoring at a remote storage building). We used to have issues with the server not coming up after several reboots, but we gave it a bandaid by forcing an fsck