From: "Steve French" <smfrench@gmail.com>
To: simo <idra@samba.org>
Cc: "Jeff Layton" <jlayton@redhat.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-cifs-client@lists.samba.org,
"Guenter Kukkukk" <linux@kukkukk.com>
Subject: Re: [linux-cifs-client] Re: set last write time = fsync ?
Date: Sat, 15 Mar 2008 10:35:02 -0500 [thread overview]
Message-ID: <524f69650803150835x37c661e1jd9e0af532f3b6c5@mail.gmail.com> (raw)
In-Reply-To: <1205592719.9351.30.camel@localhost.localdomain>
On Sat, Mar 15, 2008 at 9:51 AM, simo <idra@samba.org> wrote:
>
> On Fri, 2008-03-14 at 11:16 -0500, Steve French wrote:
> > Access is usually checked on open right ... so once a file is open
> > even if the file becomes read-only, the writes, even cached writes
> > continue.
>
> Is this true even in the case you loose the connection with the server
> and need to re-establish it ?
>
> Simo Sorce
> Samba Team GPL Compliance Officer <simo@samba.org>
> Senior Software Engineer at Red Hat Inc. <ssorce@redhat.com>
If you lose the connection with the server, the eventual reconnection could
fail (changed password, deleted user) or reopen could fail (ACL on
the file changed) but there isn't much we can do about that except
aggressively flush write data (for write behind data) and do whole file
caching on the client (for read ahead data) which hurt performance
even worse - but cifs does have a mount option to write through
(forcedirectio) rather than cache writes if desired.
--
Thanks,
Steve
prev parent reply other threads:[~2008-03-15 15:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <524f69650803122054t7b0f8285kd564271f8340378e@mail.gmail.com>
[not found] ` <20080313071046.1a9350a9@tleilax.poochiereds.net>
2008-03-14 2:32 ` set last write time = fsync ? Steve French
2008-03-14 10:40 ` Jeff Layton
2008-03-14 16:16 ` Steve French
2008-03-14 16:55 ` Jeff Layton
2008-03-14 19:19 ` Steve French
2008-03-14 20:35 ` Jeff Layton
2008-03-14 21:38 ` Steve French
2008-03-14 23:19 ` Jeff Layton
2008-03-15 14:51 ` simo
2008-03-15 15:35 ` Steve French [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=524f69650803150835x37c661e1jd9e0af532f3b6c5@mail.gmail.com \
--to=smfrench@gmail.com \
--cc=idra@samba.org \
--cc=jlayton@redhat.com \
--cc=linux-cifs-client@lists.samba.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux@kukkukk.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).