Hi,
martin f krafft:
> There are two problems here:
>
3. Spurious errors may be reported if fsck happens to run across an
inconsistent state.
--
-- Matthias Urlichs
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas..
On Tue, Dec 16, 2014 at 09:41:30AM +0100, martin f krafft wrote:
> also sprach gustavo panizzo (gfa) [2014-12-16 03:29
> +0100]:
> > you can take a look what ubuntu does, on
> > /usr/lib/update-notifier/update-motd-fsck-at-reboot
> >
> > basically it runs dumpe2fs and parse the max mount count an
also sprach gustavo panizzo (gfa) [2014-12-16 03:29 +0100]:
> you can take a look what ubuntu does, on
> /usr/lib/update-notifier/update-motd-fsck-at-reboot
>
> basically it runs dumpe2fs and parse the max mount count and fsck
> interval time, it compares it to how many mounts and how long
> since
On 12/13/2014 09:56 PM, martin f krafft wrote:
Holger had the idea to add to molly-guard a check that would require
the sysadmin to manually ack a reboot if fsck would be expected to
run. I like it.
me too :D
Instead of parsing df -t output, invoking tune2fs -l and doing
a whole bunch of g
also sprach h...@shaw.ca [2014-12-14 05:07 +0100]:
> There's an option for that:
>
> fsck -N -T
>
> (don't show Title at startup)
This shows the fsck calls for all devices, not only those that would
need a routine check. -T makes no difference, other than omitting
the first line (version).
--
There's an option for that:
fsck -N -T
(don't show Title at startup)
On 13/12/14 07:27 AM, Scott Schaefer wrote:
On 12/13/2014 08:56 AM, martin f krafft wrote:
Holger had the idea to add to molly-guard a check that would require
the sysadmin to manually ack a reboot if fsck would be expected
also sprach Scott Schaefer [2014-12-13 16:27
+0100]:
> ... but then lists the fs-specific fscks that it would run ..
>
> [/sbin/fsck.xfs (1) -- /] fsck.xfs /dev/md0
> [/sbin/fsck.ext3 (1) -- /boot] fsck.ext3 /dev/sda1
Yeah, for all filesystems. It leaves it up to fsck.xfs and fsck.ext3
to decid
On 12/13/2014 10:27 AM, Scott Schaefer wrote:
On 12/13/2014 08:56 AM, martin f krafft wrote:
Holger had the idea to add to molly-guard a check that would require
the sysadmin to manually ack a reboot if fsck would be expected to
run. I like it.
Instead of parsing df -t output, invoking tune2fs
On 12/13/2014 08:56 AM, martin f krafft wrote:
Holger had the idea to add to molly-guard a check that would require
the sysadmin to manually ack a reboot if fsck would be expected to
run. I like it.
Instead of parsing df -t output, invoking tune2fs -l and doing
a whole bunch of grep magic, I won
Holger had the idea to add to molly-guard a check that would require
the sysadmin to manually ack a reboot if fsck would be expected to
run. I like it.
Instead of parsing df -t output, invoking tune2fs -l and doing
a whole bunch of grep magic, I wonder if there's a smarter way to
find out if fsck
10 matches
Mail list logo
