* [gentoo-user] Can a forced volume check be interrupted? @ 2011-04-12 17:31 Grant 2011-04-12 17:50 ` BRM 2011-04-12 19:52 ` Paul Hartman 0 siblings, 2 replies; 12+ messages in thread From: Grant @ 2011-04-12 17:31 UTC (permalink / raw To: Gentoo mailing list Sometimes the ext3 forced volume check at boot triggers at an inopportune time. Is there a way to skip it and let it run at the next boot? - Grant ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [gentoo-user] Can a forced volume check be interrupted? 2011-04-12 17:31 [gentoo-user] Can a forced volume check be interrupted? Grant @ 2011-04-12 17:50 ` BRM 2011-04-12 17:58 ` felix 2011-04-12 19:52 ` Paul Hartman 1 sibling, 1 reply; 12+ messages in thread From: BRM @ 2011-04-12 17:50 UTC (permalink / raw To: gentoo-user Probably, but why would you want to? it fixes any errors, and makes the file system relatively clean again so that things function well - and things don't get lost. If you skip it, you risk data corruption on disk. If you know it's going to run, then you can do one of two things: 1) I believe there is an option to ignore it entirely 2) If you use Interactive mode then you can skip that step. Both of those, however, require that you know (or assume) its going to run fsck. Ben ----- Original Message ---- > From: Grant <emailgrant@gmail.com> > To: Gentoo mailing list <gentoo-user@lists.gentoo.org> > Sent: Tue, April 12, 2011 1:31:31 PM > Subject: [gentoo-user] Can a forced volume check be interrupted? > > Sometimes the ext3 forced volume check at boot triggers at an > inopportune time. Is there a way to skip it and let it run at the > next boot? > > - Grant > > ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [gentoo-user] Can a forced volume check be interrupted? 2011-04-12 17:50 ` BRM @ 2011-04-12 17:58 ` felix 2011-04-12 18:02 ` Grant 0 siblings, 1 reply; 12+ messages in thread From: felix @ 2011-04-12 17:58 UTC (permalink / raw To: gentoo-user On Tue, Apr 12, 2011 at 10:50:56AM -0700, BRM wrote: > Probably, but why would you want to? it fixes any errors, and makes the file > system relatively clean again so that things function well - and things don't > get lost. > If you skip it, you risk data corruption on disk. That misses the point. I have rebooted sometimes just for a quick change, possibly to try a different kernel, and intending to reboot several times. Then whoops! it starts a long fsck scan, not to repair damage, but just because some counter went to zero. What a waste. It's like insisting on an oil change exactly every 3000 miles. No, sorry, I will wait until it is convenient for *me*, not the odometer. So his question is, once the fsck has started, can he ^C to bomb it off, or do anything else to skip what has started? -- ... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._. Felix Finch: scarecrow repairman & rocket surgeon / felix@crowfix.com GPG = E987 4493 C860 246C 3B1E 6477 7838 76E9 182E 8151 ITAR license #4933 I've found a solution to Fermat's Last Theorem but I see I've run out of room o ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [gentoo-user] Can a forced volume check be interrupted? 2011-04-12 17:58 ` felix @ 2011-04-12 18:02 ` Grant 2011-04-12 18:21 ` BRM 0 siblings, 1 reply; 12+ messages in thread From: Grant @ 2011-04-12 18:02 UTC (permalink / raw To: gentoo-user >> Probably, but why would you want to? it fixes any errors, and makes the file >> system relatively clean again so that things function well - and things don't >> get lost. >> If you skip it, you risk data corruption on disk. > > That misses the point. I have rebooted sometimes just for a quick > change, possibly to try a different kernel, and intending to reboot > several times. Then whoops! it starts a long fsck scan, not to repair > damage, but just because some counter went to zero. What a waste. > > It's like insisting on an oil change exactly every 3000 miles. No, > sorry, I will wait until it is convenient for *me*, not the odometer. > > So his question is, once the fsck has started, can he ^C to bomb it > off, or do anything else to skip what has started? Exactly. I couldn't get it to stop with ^C or i or I. - Grant ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [gentoo-user] Can a forced volume check be interrupted? 2011-04-12 18:02 ` Grant @ 2011-04-12 18:21 ` BRM 2011-04-12 19:29 ` Grant 0 siblings, 1 reply; 12+ messages in thread From: BRM @ 2011-04-12 18:21 UTC (permalink / raw To: gentoo-user ----- Original Message ---- > From: Grant <emailgrant@gmail.com> > >> Probably, but why would you want to? it fixes any errors, and makes the >file > >> system relatively clean again so that things function well - and things >don't > >> get lost. > >> If you skip it, you risk data corruption on disk. > > > > That misses the point. I have rebooted sometimes just for a quick > > change, possibly to try a different kernel, and intending to reboot > > several times. Then whoops! it starts a long fsck scan, not to repair > > damage, but just because some counter went to zero. What a waste. > > > > It's like insisting on an oil change exactly every 3000 miles. No, > > sorry, I will wait until it is convenient for *me*, not the odometer. > > > > So his question is, once the fsck has started, can he ^C to bomb it > > off, or do anything else to skip what has started? > > Exactly. I couldn't get it to stop with ^C or i or I. > No. You can't. Nor do you want to at that point. Once it has started it really should run until completion otherwise you really risk data corruption. If you want to stop it, you have to prevent it from starting in the first place. Ben ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [gentoo-user] Can a forced volume check be interrupted? 2011-04-12 18:21 ` BRM @ 2011-04-12 19:29 ` Grant 2011-04-12 19:44 ` BRM 0 siblings, 1 reply; 12+ messages in thread From: Grant @ 2011-04-12 19:29 UTC (permalink / raw To: gentoo-user >> >> Probably, but why would you want to? it fixes any errors, and makes the >>file >> >> system relatively clean again so that things function well - and things >>don't >> >> get lost. >> >> If you skip it, you risk data corruption on disk. >> > >> > That misses the point. I have rebooted sometimes just for a quick >> > change, possibly to try a different kernel, and intending to reboot >> > several times. Then whoops! it starts a long fsck scan, not to repair >> > damage, but just because some counter went to zero. What a waste. >> > >> > It's like insisting on an oil change exactly every 3000 miles. No, >> > sorry, I will wait until it is convenient for *me*, not the odometer. >> > >> > So his question is, once the fsck has started, can he ^C to bomb it >> > off, or do anything else to skip what has started? >> >> Exactly. I couldn't get it to stop with ^C or i or I. >> > > No. You can't. Nor do you want to at that point. > Once it has started it really should run until completion otherwise you really > risk data corruption. > If you want to stop it, you have to prevent it from starting in the first place. Yeah, that can really be a drag. Last night my Gentoo HTPC checked the 2TB drive for 2 hours when I rebooted after a movie we were watching froze. - Grant ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [gentoo-user] Can a forced volume check be interrupted? 2011-04-12 19:29 ` Grant @ 2011-04-12 19:44 ` BRM 0 siblings, 0 replies; 12+ messages in thread From: BRM @ 2011-04-12 19:44 UTC (permalink / raw To: gentoo-user ----- Original Message ---- > From: Grant <emailgrant@gmail.com> > To: gentoo-user@lists.gentoo.org > Sent: Tue, April 12, 2011 3:29:35 PM > Subject: Re: [gentoo-user] Can a forced volume check be interrupted? > > >> >> Probably, but why would you want to? it fixes any errors, and makes the > >>file > >> >> system relatively clean again so that things function well - and things > >>don't > >> >> get lost. > >> >> If you skip it, you risk data corruption on disk. > >> > > >> > That misses the point. I have rebooted sometimes just for a quick > >> > change, possibly to try a different kernel, and intending to reboot > >> > several times. Then whoops! it starts a long fsck scan, not to repair > >> > damage, but just because some counter went to zero. What a waste. > >> > > >> > It's like insisting on an oil change exactly every 3000 miles. No, > >> > sorry, I will wait until it is convenient for *me*, not the odometer. > >> > > >> > So his question is, once the fsck has started, can he ^C to bomb it > >> > off, or do anything else to skip what has started? > >> > >> Exactly. I couldn't get it to stop with ^C or i or I. > >> > > > > No. You can't. Nor do you want to at that point. > > Once it has started it really should run until completion otherwise you >really > > risk data corruption. > > If you want to stop it, you have to prevent it from starting in the first >place. > > Yeah, that can really be a drag. Last night my Gentoo HTPC checked > the 2TB drive for 2 hours when I rebooted after a movie we were > watching froze. > As I said, if you are anticipating such a situation - or like the situation you are in - you can use the interactive boot or other methods to keep it from running to start with. That is your best bet, and your safest. Ben ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [gentoo-user] Can a forced volume check be interrupted? 2011-04-12 17:31 [gentoo-user] Can a forced volume check be interrupted? Grant 2011-04-12 17:50 ` BRM @ 2011-04-12 19:52 ` Paul Hartman 2011-04-12 19:53 ` Paul Hartman 2011-04-13 0:45 ` [gentoo-user] " Bill Kenworthy 1 sibling, 2 replies; 12+ messages in thread From: Paul Hartman @ 2011-04-12 19:52 UTC (permalink / raw To: gentoo-user On Tue, Apr 12, 2011 at 12:31 PM, Grant <emailgrant@gmail.com> wrote: > Sometimes the ext3 forced volume check at boot triggers at an > inopportune time. Is there a way to skip it and let it run at the > next boot? Not once it has started, but there are some ways to avoid it running in the first place: Add "fastboot" to your kernel commandline to make it bypass the auto-fsck. A grub entry for "skip fsck" might be handy. Edit /etc/fstab to prevent the auto-fsck from ever running by changing the last field to 0. If it's an ext[123] you can use tune2fs -i 0 to set the auto-check interval to never. ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [gentoo-user] Can a forced volume check be interrupted? 2011-04-12 19:52 ` Paul Hartman @ 2011-04-12 19:53 ` Paul Hartman 2011-04-12 21:31 ` [gentoo-user] " Hartmut Figge 2011-04-13 0:45 ` [gentoo-user] " Bill Kenworthy 1 sibling, 1 reply; 12+ messages in thread From: Paul Hartman @ 2011-04-12 19:53 UTC (permalink / raw To: gentoo-user On Tue, Apr 12, 2011 at 2:52 PM, Paul Hartman <paul.hartman+gentoo@gmail.com> wrote: > If it's an ext[123] you can use tune2fs -i 0 to set the auto-check > interval to never. oops, I of course meant 234 not 123 :) ^ permalink raw reply [flat|nested] 12+ messages in thread
* [gentoo-user] Re: Can a forced volume check be interrupted? 2011-04-12 19:53 ` Paul Hartman @ 2011-04-12 21:31 ` Hartmut Figge 0 siblings, 0 replies; 12+ messages in thread From: Hartmut Figge @ 2011-04-12 21:31 UTC (permalink / raw To: gentoo-user Paul Hartman: > On Tue, Apr 12, 2011 at 2:52 PM, Paul Hartman >> If it's an ext[123] you can use tune2fs -i 0 to set the auto-check >> interval to never. > > oops, I of course meant 234 not 123 :) ;) But i prefer setting the interval to 1000 with 'tune2fs -c'. | It is strongly recommended that either -c (mount-count-depen- | dent) or -i (time-dependent) checking be enabled to force peri- | odic full e2fsck(8) checking of the filesystem. Hartmut -- Usenet-ABC-Wiki http://www.usenet-abc.de/wiki/ Von Usern fuer User :-) ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [gentoo-user] Can a forced volume check be interrupted? 2011-04-12 19:52 ` Paul Hartman 2011-04-12 19:53 ` Paul Hartman @ 2011-04-13 0:45 ` Bill Kenworthy 2011-04-13 6:08 ` Mick 1 sibling, 1 reply; 12+ messages in thread From: Bill Kenworthy @ 2011-04-13 0:45 UTC (permalink / raw To: gentoo-user On Tue, 2011-04-12 at 14:52 -0500, Paul Hartman wrote: > On Tue, Apr 12, 2011 at 12:31 PM, Grant <emailgrant@gmail.com> wrote: > > Sometimes the ext3 forced volume check at boot triggers at an > > inopportune time. Is there a way to skip it and let it run at the > > next boot? > > Not once it has started, but there are some ways to avoid it running > in the first place: > > Add "fastboot" to your kernel commandline to make it bypass the > auto-fsck. A grub entry for "skip fsck" might be handy. > > Edit /etc/fstab to prevent the auto-fsck from ever running by changing > the last field to 0. > > If it's an ext[123] you can use tune2fs -i 0 to set the auto-check > interval to never. > Thats one reason I have been looking at btrfs - online fsck. Has been solid even on unexpected crashes (I am setting up remote power on/off and pressed the wrong button - more than once :) I actually had some minor corruption on reiserfs, but btrfs was fine and could be checked online anyway in a lot less time than reiserfsck took. BillK ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [gentoo-user] Can a forced volume check be interrupted? 2011-04-13 0:45 ` [gentoo-user] " Bill Kenworthy @ 2011-04-13 6:08 ` Mick 0 siblings, 0 replies; 12+ messages in thread From: Mick @ 2011-04-13 6:08 UTC (permalink / raw To: gentoo-user [-- Attachment #1: Type: Text/Plain, Size: 1287 bytes --] On Wednesday 13 April 2011 01:45:43 Bill Kenworthy wrote: > On Tue, 2011-04-12 at 14:52 -0500, Paul Hartman wrote: > > On Tue, Apr 12, 2011 at 12:31 PM, Grant <emailgrant@gmail.com> wrote: > > > Sometimes the ext3 forced volume check at boot triggers at an > > > inopportune time. Is there a way to skip it and let it run at the > > > next boot? > > > > Not once it has started, but there are some ways to avoid it running > > in the first place: > > > > Add "fastboot" to your kernel commandline to make it bypass the > > auto-fsck. A grub entry for "skip fsck" might be handy. > > > > Edit /etc/fstab to prevent the auto-fsck from ever running by changing > > the last field to 0. > > > > If it's an ext[123] you can use tune2fs -i 0 to set the auto-check > > interval to never. > > Thats one reason I have been looking at btrfs - online fsck. Has been > solid even on unexpected crashes (I am setting up remote power on/off > and pressed the wrong button - more than once :) I actually had some > minor corruption on reiserfs, but btrfs was fine and could be checked > online anyway in a lot less time than reiserfsck took. ext4 takes only a second if not less at boot time - depending on the size of the partition of course. -- Regards, Mick [-- Attachment #2: This is a digitally signed message part. --] [-- Type: application/pgp-signature, Size: 198 bytes --] ^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2011-04-13 6:09 UTC | newest] Thread overview: 12+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2011-04-12 17:31 [gentoo-user] Can a forced volume check be interrupted? Grant 2011-04-12 17:50 ` BRM 2011-04-12 17:58 ` felix 2011-04-12 18:02 ` Grant 2011-04-12 18:21 ` BRM 2011-04-12 19:29 ` Grant 2011-04-12 19:44 ` BRM 2011-04-12 19:52 ` Paul Hartman 2011-04-12 19:53 ` Paul Hartman 2011-04-12 21:31 ` [gentoo-user] " Hartmut Figge 2011-04-13 0:45 ` [gentoo-user] " Bill Kenworthy 2011-04-13 6:08 ` Mick
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox