On 11/11/13 08:52, Ivan Lezhnjov IV wrote:

On Nov 11, 2013, at 5:43 AM, Stan Hoeppner [off-list ref]
wrote:

quoted

quoted

What about filesystem state? Does it matter if a filesystem is
mounted when check is run?

I'm not an EXT user.  See "man e2fsck".

With XFS you can check while mounted using "xfs_repair -n
[device]", but no repairs will be performed, you simply get a
report.  To repair a damaged XFS filesystem use the same command
sans "-n" on the unmounted filesystem.  xfs_repair will abort if
the filesystem is mounted, and "-n" is not specified.  xfs_repair
is not to be automated via script/cron.  It is only to be run
if/when errors are encountered, usually after a crash, power loss,
controller failure, etc.

Oh, I meant 'check' as in

echo check > /sys/block/$DEVICE/md/sync_action

In general, you can happily do a raid check while the system is in use
(i.e., the filesystem is mounted).  Of course, if you are using the
system heavily then things will slow down, but it will all work fine.
Raid is designed for maximal uptime - you don't have to stop arrays or
umount filesystems for raid maintenance.

You can also run raid check simultaneously with e2fsck.

But you can't run e2fsck very well while it is mounted.  You /can/ run
it in read-only mode, and if nothing writes to the filesystem (including
touching access times) then it will work.  But in general you will get
false error messages when inconsistencies are found as structures are
written during the check.  (Other tricks include re-mounting as
read-only, and doing an lvm snapshot of the volume then fsck'ing that.)

That, and I also read on my distro's wiki that 'check' will pick up
where it was interrupted automatically in those cases when a system
is rebooted before 'check' is complete. Well, apparently it does not
work that way because I was only some 4% into 'check' yesterday
evening, and after resume from sleep mdstat does not show that
'check' is running. So, does the distro's wiki contain erroneous
information?

I can't say anything about that other than general points about "sleep"
being a half-way house between rebooting and running.  It does not
surprise me that you get issues with things not restarting after a sleep
and wakeup.

As far as I understand your posts, you have a laptop that you use as a
normal machine and also as a server.  Presumably you are connected to
mains power rather than a battery.  Why not just let the thing run
overnight?  It's a laptop - it's low power already.  As long as things
like the display turn off (and perhaps the disks too, after some period
without use), the power used will be tiny.  So keep it turned on, or
turn it off - then you don't have any sleep problems.

I don't think you mentioned what distro you are using (I might have
missed it), which makes it difficult to guess what the "distro's wiki" says.