On Tue, Dec 16, 2014 at 10:15:45PM +0100, martin f krafft wrote:
>
> A bit of context: I am intending to analyse the answer to this
> question as part of the admin's call to /sbin/reboot, so we can
> assume a clean shutdown indeed.
I'm not sure I understand why this would be useful. Suppose the
answer is "e2fsck is going to check all of the disks and it's going to
take two hours to check your RAID array". Is that going to make a
difference to the sysadmin in terms of deciding whether or not to
continue?
And note that if I add this to e2fsck, the calling program is still
going to have to parse /etc/fstab and call e2fsck with some magic
option which will do this check. I'm just not sure how generally
useful this will be, and it's not clear to me that it's worth the
effort.
If I did do this, it would probaby be as a standalone program in
contrib, and I'm not sure I would package it, simply because I'm not
yet convinced how many users would use it, and maintaining it as yet
another binary in /usr/bin, and another man page, if it's highly
specialized and only one or two users would find it useful, doesn't
seem to me to be a good trade off --- espceially since we've already
changed the default due to too many users kvetching and whining about
the boot-time check.
(Me, I use LVM snapshots and checks that don't require that I do a
rebooot; this also means I can do them much more frequently. The
e2croncheck ***really*** is a the right way to go.)
- Ted
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
