[Lustre-devel] Flush on file close

Andrew Perepechko Andrew.Perepechko at Sun.COM
Mon Apr 19 11:30:46 PDT 2010

Some applications expect non-zero errno on close() for any errors that may 
happen during flushing dirty cached data/metadata even though linux manual 
page for close(2) suggests that fsync(2) should be used prior to close(2) in 
order to detect problems like those.

Since syncing may degrade performance to a large extent, what do you think is 
the best/most convenient/least intrusive way to switch to that behaviour? 
Should it be a mount option for the client or anything else?


More information about the lustre-devel mailing list