Hi!
> > > 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.
> >
> > Timer only wakes up xfssyncd thread, right? That's okay, as that
> > thread will be stopped.
>
> But we call sync() before kernel threads are frozen. What happens if xfssyncd
> gets woken up by the timer after the sync() and before we freeze it?
xfssyncd writes some data to disk, but that is okay (no important data
could be generated in the meantime) and then it is frozen. As we take
system snapshot after the freeze, it is okay, because image is
consistent.
I do not see a problem.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
