From: "Wim Colgate" Subject: NFS_UNSTABLE vs. FILE and DATA sync. Date: Mon, 6 Aug 2007 09:02:08 -0700 Message-ID: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0319697139==" To: Return-path: Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92] helo=mail.sourceforge.net) by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43) id 1II53h-0001l5-Eh for nfs@lists.sourceforge.net; Mon, 06 Aug 2007 09:03:54 -0700 Received: from webmailrdm.xensource.com ([66.228.214.202]) by mail.sourceforge.net with esmtp (Exim 4.44) id 1II53l-0005Jr-B7 for nfs@lists.sourceforge.net; Mon, 06 Aug 2007 09:03:57 -0700 List-Id: "Discussion of NFS under Linux development, interoperability, and testing." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: nfs-bounces@lists.sourceforge.net Errors-To: nfs-bounces@lists.sourceforge.net This is a multi-part message in MIME format. --===============0319697139== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C7D843.64A63736" This is a multi-part message in MIME format. ------_=_NextPart_001_01C7D843.64A63736 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, =20 My last question was a bit too nebulous, and didn't really expect an answer. Learning my lesson, I have a specific question. =20 If I have a soft mount, and open a file with O_DIRECT and O_SYNC, should I ever expect a callback (nfs_writeback_done) with a successful task->tk_status (i.e >=3D 0) with the committed state (resp->verf->committed) set to NFS_UNSTABLE?=20 =20 A secondary question: if the above is expected, does this occur because someone is caching the write and is there a mechanism to disable this effect? =20 Regards, =20 Wim ------_=_NextPart_001_01C7D843.64A63736 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi,

 

My last question was a bit too nebulous, and = didn’t really expect an answer. Learning my lesson, I have a specific = question.

 

If I have a soft mount, and open a file with O_DIRECT = and O_SYNC, should I ever expect a callback (nfs_writeback_done) with a = successful task->tk_status (i.e >=3D 0) with the committed state = (resp->verf->committed) set to NFS_UNSTABLE?

 

A secondary question: if the above is expected, does = this occur because someone is caching the write and is there a mechanism to = disable this effect?

 

Regards,

 

Wim

------_=_NextPart_001_01C7D843.64A63736-- --===============0319697139== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ --===============0319697139== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs --===============0319697139==--