Trond, ----- Original Message ----- > From: "Brian Hawley" <bhawley@xxxxxxxxxxx> > To: "Ric Wheeler" <rwheeler@xxxxxxxxxx>, "Brian Hawley" <bhawley@xxxxxxxxxxx>, "Trond Myklebust" > <trond.myklebust@xxxxxxxxxxxxxxx> > Cc: "Andrew Martin" <amartin@xxxxxxxxxxx>, "Jim Rees" <rees@xxxxxxxxx>, "Brown Neil" <neilb@xxxxxxx>, > linux-nfs-owner@xxxxxxxxxxxxxxx, linux-nfs@xxxxxxxxxxxxxxx > Sent: Thursday, March 6, 2014 1:38:15 PM > Subject: Re: Optimal NFS mount options to safely allow interrupts and timeouts on newer kernels > > > I agree completely that the write() returning only means it's in the page > cache. > > I agree completely that fsync() result is the only way to know your data is > safe. > > Neither of those is what I, or the original poster (and what other posters in > the past) on this subject are disputing or concerned about. > > The issue is, the write() call (in my case - read() in the original posters > case) does NOT return. Is it possible with the "sync" mount option (or via another method) to force all writes to fsync and fail immediately if they do not succeed? In other words skip the cache? In some applications I'd rather pass the error back up to the application right away for it to handle (even if the error is caused by network turbulence) rather than risk getting into this situation where writes block forever. Thanks, Andrew -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
