1 |
On Wednesday 13 April 2011 01:45:43 Bill Kenworthy wrote: |
2 |
> On Tue, 2011-04-12 at 14:52 -0500, Paul Hartman wrote: |
3 |
> > On Tue, Apr 12, 2011 at 12:31 PM, Grant <emailgrant@×××××.com> wrote: |
4 |
> > > Sometimes the ext3 forced volume check at boot triggers at an |
5 |
> > > inopportune time. Is there a way to skip it and let it run at the |
6 |
> > > next boot? |
7 |
> > |
8 |
> > Not once it has started, but there are some ways to avoid it running |
9 |
> > in the first place: |
10 |
> > |
11 |
> > Add "fastboot" to your kernel commandline to make it bypass the |
12 |
> > auto-fsck. A grub entry for "skip fsck" might be handy. |
13 |
> > |
14 |
> > Edit /etc/fstab to prevent the auto-fsck from ever running by changing |
15 |
> > the last field to 0. |
16 |
> > |
17 |
> > If it's an ext[123] you can use tune2fs -i 0 to set the auto-check |
18 |
> > interval to never. |
19 |
> |
20 |
> Thats one reason I have been looking at btrfs - online fsck. Has been |
21 |
> solid even on unexpected crashes (I am setting up remote power on/off |
22 |
> and pressed the wrong button - more than once :) I actually had some |
23 |
> minor corruption on reiserfs, but btrfs was fine and could be checked |
24 |
> online anyway in a lot less time than reiserfsck took. |
25 |
|
26 |
ext4 takes only a second if not less at boot time - depending on the size of |
27 |
the partition of course. |
28 |
-- |
29 |
Regards, |
30 |
Mick |