[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Skipping fsck during boot with systemd?



On Thu, Dec 11, 2014 at 06:16:05PM +0900, Joel Rees wrote:
> 2014/12/11 3:48 "Brian" <ad44@cityscape.co.uk>:
> >
> > On Wed 10 Dec 2014 at 19:23:07 +0300, tv.debian@googlemail.com wrote:
> >
> > > On 10/12/2014 14:04, Andrei POPESCU wrote:
> > > >
> > > >Of course, there's also the option of completely disabling automatic
> > > >fsck (there are several ways to do this), as I understand is the default
> > > >for new enough filesystems. This would make more sense for me on systems
> > > >with bad power (you'd still get the "bad shutdown" check).
> > >
> > > Yes, disabling and doing manual checks from time to time is a
> > > possibility, but you'd have to convince all users to hand their
> > > gears to an admin outside of business hours. The said admin (who
> > > might just bee a teacher in fact) might not be happy with the idea
> > > of a week-end spent at fsck'ing the world out of the compulab, just
> > > because of systemd. With the conditions I mentioned earlier running
> > > a fsck regularly is a good thing, just not being able to interrupt
> > > it in case of emergency isn't.
> >
> > Ever since Wheezy automatic fsck has been disabled on new installs. [...]
> 
> Odd. The last time I booted my wheezy-by-install system, it did an automatic
> fsck.
> 
> I did nothing in particular to enable that.
> 
> I think you are reading things into the documentation that you want to be
> there.

No, Brian is correct. It's a simple thing to check (up-to-date Wheezy):

$ truncate -s 1G 1.raw
$ /sbin/mkfs.ext4 1.raw
mke2fs 1.42.5 (29-Jul-2012)
1.raw is not a block special device.
Proceed anyway? (y,n) y
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
65536 inodes, 262144 blocks
13107 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=268435456
8 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376

Allocating group tables: done
Writing inode tables: done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: done

$ /sbin/tune2fs -l 1.raw
...
Filesystem created:       Thu Dec 11 13:47:00 2014
Last mount time:          n/a
Last write time:          Thu Dec 11 13:47:00 2014
Mount count:              0
Maximum mount count:      -1
Last checked:             Thu Dec 11 13:47:00 2014
Check interval:           0 (<none>)
...

Reco


Reply to: