From: Peter Staubach <staubach@redhat.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Neil Brown <neilb@suse.de>, NFS List <nfs@lists.sourceforge.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Trond Myklebust <trond.myklebust@fys.uio.no>
Subject: Re: [NFS] [PATCH] NFS server does not update mtime on setattr request
Date: Wed, 07 Jun 2006 12:56:18 -0400 [thread overview]
Message-ID: <44870532.2010902@redhat.com> (raw)
In-Reply-To: <20060607160334.GB22335@fieldses.org>
[-- Attachment #1: Type: text/plain, Size: 1148 bytes --]
J. Bruce Fields wrote:
>On Wed, Jun 07, 2006 at 11:50:31AM -0400, Peter Staubach wrote:
>
>
>>The Red Hat BZ number is 193621.
>>
>>
>
>"You are not authorized to access bug #193621", it tells me....
>
>
>
Hmm. That ones seems to be restricted for some reason. I think that
this happens when we get escalated bugzillas from customers.
>>The description is that when zero length files are copied, even over
>>an existing zero length file, the mtime on the target file does not
>>change.
>>
>>
>
>Is the server-side patch sufficient on its own?
>
>
The server side patch isn't quite sufficient on its own. A RHEL-4 patch
is also required for the client side. I could construct the RHEL-4 patch
so that it alone would be sufficient to address the particular problem
that that customer is having, but that isn't the entire situation.
Non-Linux clients would still have a problem with the current upstream
Linux server. For example, in my testing, a Solaris 10 client mounting
an FC-5 server fails. When running the attached script, the mtime on
the file, bar, should change by about 1 minute, 3 times.
Thanx...
ps
[-- Attachment #2: repo --]
[-- Type: text/plain, Size: 265 bytes --]
#!/bin/sh
rm -f foo bar
set -x
touch foo
cp foo bar
stat --format="%n %y" foo bar
sleep 60
cp foo bar
stat --format="%n %y" foo bar
sleep 60
cp foo bar
stat --format="%n %y" foo bar
sleep 60
rm foo
touch foo
cp foo bar
stat --format="%n %y" foo bar
next prev parent reply other threads:[~2006-06-07 16:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-06 18:05 [PATCH] NFS server does not update mtime on setattr request Peter Staubach
2006-06-07 5:38 ` Trond Myklebust
2006-06-07 14:44 ` Peter Staubach
2006-06-07 15:17 ` [NFS] " J. Bruce Fields
2006-06-07 15:26 ` Peter Staubach
2006-06-07 15:39 ` Trond Myklebust
2006-06-07 15:44 ` Peter Staubach
2006-06-07 17:17 ` Trond Myklebust
2006-06-07 17:41 ` Peter Staubach
2006-06-07 15:42 ` J. Bruce Fields
2006-06-07 15:50 ` Peter Staubach
2006-06-07 16:03 ` J. Bruce Fields
2006-06-07 16:56 ` Peter Staubach [this message]
2006-06-09 0:40 ` Neil Brown
2006-06-09 13:10 ` Peter Staubach
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=44870532.2010902@redhat.com \
--to=staubach@redhat.com \
--cc=bfields@fieldses.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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