From: Chen Gang <gang.chen@asianux.com>
To: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
Cc: Jeff Layton <jlayton@redhat.com>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [Bug fix] nfs-client: fix nfs_inode_attrs_need_update for async read_done comes during truncating to smaller size
Date: Mon, 15 Oct 2012 13:39:04 +0800 [thread overview]
Message-ID: <507BA178.7030002@asianux.com> (raw)
In-Reply-To: <507B968A.9090104@asianux.com>
于 2012年10月15日 12:52, Chen Gang 写道:
>> Now, what are the conditions of your test setup? The above bug report is
>> > meaningless unless it includes a description of what is being exported
>> > by the server (including a proper listing of the contents
>> > of /etc/exports and /proc/mounts). It should also include a description
>> > of the NFS client mount options (see /proc/mounts on the client).
for exportfs command line is:
rsh -n $RHOST "/usr/sbin/exportfs -i -o no_root_squash,rw *:$TESTDIR"
$RHOST is dhcp122.asianux.net (10.1.0.122, not need input password)
$TESTDIR just the mount dir.
> they are below, if you need additional information, please tell me again.
>
--
Chen Gang
Asianux Corporation
next prev parent reply other threads:[~2012-10-15 5:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-15 2:12 [Bug fix] nfs-client: fix nfs_inode_attrs_need_update for async read_done comes during truncating to smaller size Chen Gang
2012-10-15 4:27 ` Myklebust, Trond
2012-10-15 4:27 ` Myklebust, Trond
2012-10-15 4:52 ` Chen Gang
2012-10-15 5:39 ` Chen Gang [this message]
2012-10-15 12:32 ` Myklebust, Trond
2012-10-15 12:32 ` Myklebust, Trond
2012-10-16 1:37 ` Chen Gang
2012-10-16 2:51 ` Myklebust, Trond
2012-10-16 2:51 ` Myklebust, Trond
2012-10-16 4:13 ` Chen Gang
2012-10-16 10:33 ` Jeff Layton
2012-10-16 11:44 ` Chen Gang
2012-10-16 12:13 ` Jeff Layton
2012-10-17 1:37 ` Chen Gang
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=507BA178.7030002@asianux.com \
--to=gang.chen@asianux.com \
--cc=Trond.Myklebust@netapp.com \
--cc=jlayton@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.