-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 reassign 773267 e2fsprogs thanks
On 12/16/2014 3:36 AM, martin f krafft wrote: > Package: util-linux Version: 2.25.2-3 Severity: wishlist File: > /sbin/fsck Tags: upstream > > In the context of #773035, I am looking for a way to figure out > whether a reboot *now* would be likely to cause lengthy fsck > routine checks, e.g. due to the maximal mount count or days since > last check being reached on ext-filesystems. > > I'd like to avoid parsing debug2fs or tune2fs output and comparing > numbers or timestamps in the text output, like > /usr/lib/update-notifier/update-motd-fsck-at-reboot seems to be > doing on Ubuntu. > > Instead, I'd really like to just ask fsck. > > fsck -A -t ext2,ext3,ext4,… -N > > is already very helpful showing me which filesystem-specific > commands it would run, but each of those is run unconditionally on > the filesystem and determines by itself whether a check is needed. The mount count fsck is specific to ext2 ( for that matter, it is at this point, a silly anachronism that many people disable.. iirc it is disabled by default these days on ubuntu ) so there is no reason to generalize it to fsck. I'm reassigning to e2fsprogs so they can consider adding something to e2fsck but my guess is they will say to just use tune2fs. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (MingW32) iQEcBAEBAgAGBQJUkD9QAAoJENRVrw2cjl5RfYQIAKSh8ys5NInZZukS2M9TCuhC VldRdW+xse1xyIwp4RbhFQ/yuhTvdo9fDBXsG+eDKLKD/gTwRjDPd0XZQjZB9fyv dz357+iLG4RCY0P7UI9j3j+G38DRtWUR8wR4HnglcCaBUHUirXbZ5LPosklHXLLE NMR5f/oOSRVYN1F8h5K7JdKVaiMujVAbGsckWa+gU4/QySJ4TSR3gn/0wm6891cS sl8W0KG7vjSsRAaExdIAmgdZwOsjW+5jZ2bGTzYl+aAUb5iLgE/F9EZikc4W2uaG qPe3+klny4dkuZGpEZuOU35w/r6njBiIbqe0U9VsACkmZ5Kg8nShKPyvWoUznBM= =dA03 -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
