Re: [gentoo-user] Can a forced volume check be interrupted?
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 emailgr...@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 signature.asc Description: This is a digitally signed message part.
[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
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. 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 emailgr...@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
Re: [gentoo-user] Can a forced volume check be interrupted?
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 / fe...@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
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. - Grant
Re: [gentoo-user] Can a forced volume check be interrupted?
- Original Message From: Grant emailgr...@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
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. - Grant
Re: [gentoo-user] Can a forced volume check be interrupted?
- Original Message From: Grant emailgr...@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
Re: [gentoo-user] Can a forced volume check be interrupted?
On Tue, Apr 12, 2011 at 12:31 PM, Grant emailgr...@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.
Re: [gentoo-user] Can a forced volume check be interrupted?
On Tue, Apr 12, 2011 at 2:52 PM, Paul Hartman paul.hartman+gen...@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 :)
Re: [gentoo-user] Can a forced volume check be interrupted?
On Tue, 2011-04-12 at 14:52 -0500, Paul Hartman wrote: On Tue, Apr 12, 2011 at 12:31 PM, Grant emailgr...@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
