Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*O

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*O_SYNC\s+behavior\?\s*$/: 5 ]

Total 5 documents matching your query.

1. O_SYNC behavior? (score: 1): Author: Ray Van Dolson <rvandolson@xxxxxxxx>; Date: Mon, 26 Apr 2010 15:56:28 -0700; End-user question: NFS client accessing an NFS export on an XFS based filesystem via "sync" (O_SYNC) mode. Will write confirmation be sent back from the NFS server when the data is written to the xfs; /archives/xfs/2010-04/msg00351.html (6,479 bytes)
2. Re: O_SYNC behavior? (score: 1): Author: Nathan Scott <nathans@xxxxxxxxxx>; Date: Tue, 27 Apr 2010 09:25:43 +1000 (EST); Data is never written to the journal. cheers. -- Nathan; /archives/xfs/2010-04/msg00352.html (6,526 bytes)
3. Re: O_SYNC behavior? (score: 1): Author: Matthias Schniedermeyer <ms@xxxxxxx>; Date: Tue, 27 Apr 2010 11:32:50 +0200; I don't think that answers the intented question. I guess the correct answer is: It depends on the server-side configuration. An "async" export gets the "done"-answer immediatly. An "sync" export (on; /archives/xfs/2010-04/msg00359.html (8,573 bytes)
4. Re: O_SYNC behavior? (score: 1): Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>; Date: Tue, 27 Apr 2010 10:12:05 -0400; The client side (that is mount-side) sync means implying O_SYNC for all I/O - no need for that. And sync exports are the default for every sane server.; /archives/xfs/2010-04/msg00360.html (8,763 bytes)
5. Re: O_SYNC behavior? (score: 1): Author: Ray Van Dolson <rvandolson@xxxxxxxx>; Date: Tue, 27 Apr 2010 08:35:04 -0700; Thanks guys. I was asking this from the perspective of a ZFS type setup with its intent log (ZIL) on SSD's or some battery backed NVRAM. In this setup, with sync mode NFS, acknowledgement is sent to; /archives/xfs/2010-04/msg00363.html (9,418 bytes)

Current List: 1 - 5
Page: [1]