From: "Jose R. Santos" <jrsantos@austin.ibm.com>
To: "Jose R. Santos" <jrsantos@austin.ibm.com>
Cc: nfs@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [NFS] Problems with NFS while running SpecSFS with JFS filesystem and 2.6 kernel.
Date: Thu, 11 Dec 2003 09:13:31 -0600 [thread overview]
Message-ID: <20031211151331.GA7920@dbz.austin.ibm.com> (raw)
In-Reply-To: <20031210144011.GE708@dbz.austin.ibm.com> (from jrsantos@austin.ibm.com on Wed, Dec 10, 2003 at 08:40:11 -0600)
On 12/10/03 08:40:11, Jose R. Santos wrote:
> >>>Dec 9 14:48:04 onus kernel: nfsd: LOOKUP(3) 20: 01000001 00420051 00000002 0000a17e 00009083 00000000 file_en.46340
> >>>Dec 9 14:48:04 onus kernel: nfsd: LOOKUP(3) 20: 01000001 00420051 00000002 0000a17e 00009083 00000000 file_en.46410
I'm looking at the NFSd code and I think I'm getting a little confuse
and since I'm not a NFS expert, I don't know if something like the above
two lines is OK or not.
Can someone impose a bit of wisdom on me. :)
-JRS
next prev parent reply other threads:[~2003-12-11 15:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-10 14:40 Jose R. Santos
2003-12-11 15:13 ` Jose R. Santos [this message]
2003-12-15 14:21 ` [NFS] " Jose R. Santos
2003-12-17 20:11 ` [PATCH] " Dave Kleikamp
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=20031211151331.GA7920@dbz.austin.ibm.com \
--to=jrsantos@austin.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
/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
Powered by JetHome