On Tuesday, 17 October 2006 22:17, Luca Tettamanti wrote:
> On 10/17/06, Rafael J. Wysocki <[EMAIL PROTECTED]> wrote:
> > On Tuesday, 17 October 2006 17:26, Carl-Daniel Hailfinger wrote:
> > > My last power failure during suspend-to-disk caused a journal replay
> > > which took a few minutes on reboot.
> >
> > AFAICT, sys_sync doesn't prevent journal replies from happening on failure.
> > It only causes data to be written to the storage, metadata are different
> > story.
>
> Are you sure? sys_sync() causes the writeback of all dirty inodes, it
> won't prevent the replay since the FS is still marked as "dirty", but
> it will speed up the recovery (->sync_fs() will also trigger a journal
> commit).
Oh, yes, and that's why we _do_ call sys_sync().
Greetings,
Rafael
--
You never change things by fighting the existing reality.
R. Buckminster Fuller
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Suspend-devel mailing list
Suspend-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/suspend-devel
