Re: XFS vs. swsusp

[Nathan Scott]

On Mon, Jul 31, 2006 at 11:59:33PM +0200, Pavel Machek wrote:
> Hi!

Hi there,

> Rafael has patches to add bdev freezing to swsusp. I'd like to know if
> they are neccessary (and why).
> 
> 1) Is sync() enough to guarantee that all the data written before sync
> actually reach the platters?
> 
> (Or is it that data only reach the journal? OTOH that would be okay, too).

It ensures file data reaches its final resting place, and that
metadata changes have been logged.  It does not necessarily
ensure that metadata changes have reached their final resting
place (which can be done during log recovery if need be).

A freeze is one way to ensure all metadata will be written out
(and not just to the log, I mean), unmount is another (d'uh),
and remount,ro is a third.

> 2) If we stop all the user proceses and all the kernel threads, is
> that enough to prevent XFS from writing to disk?

Yes, I believe so (if all user processes and kernel threads are
stopped, who else would be left to initiate I/O?).  There is a
timer driven wakeup done on the per-fs xfssyncd kernel threads,
which do background metadata writeout and will write to the log
periodically... but if those processes are all stopped too, you
should be OK.

cheers.

-- 
Nathan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/