From: "J. Bruce Fields" <bfields@fieldses.org>
To: Phy Prabab <phyprabab@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Issues with knfsd + solaris clients
Date: Wed, 28 Mar 2007 13:23:10 -0400 [thread overview]
Message-ID: <20070328172310.GC21221@fieldses.org> (raw)
In-Reply-To: <2fe399760703271334j1fe56c9ctc83e1310620d7728@mail.gmail.com>
On Tue, Mar 27, 2007 at 01:34:21PM -0700, Phy Prabab wrote:
> Here is a little bit more information on my issue with slowlaris and
Could you just use their name? It's a little distracting otherwise.
> knfs 2.6.21-rc4/5 (actually appears in 2.4.20.x). Running this from
> the client (x.org source code):
> >ls -l xc/lib/Xmu/Xct.h
> -rw-rw-r-- 1 phy bdf 0 2006-01-09 06:59 xc/lib/Xmu/Xct.h
> >file xc/lib/Xmu/Xct.h
> xc/lib/Xmu/Xct.h: cannot read: Is a directory
> >rm -rf xc/lib/Xmu/Xct.h
> rm: cannot remove `xc/lib/Xmu/Xct.h': Not owner
> >uname -a
> SunOS mm3 5.10 Generic_118855-14 i86pc i386 i86pc Solaris
> >chmod 777 xc/lib/Xmu/Xct.h
> >rm -rf xc/lib/Xmu/Xct.h
> rm: cannot remove `xc/lib/Xmu/Xct.h': Not owner
> >
>
> I would think the file would not be directory and if I tried to remove
> it, I should be able as owner and permissions are correct. This is on
> a solaris 10 on intel, but I also see this problem on solaris 8, 9 and
> 10 on sparc. Again, AIX5303 and 04 and all linux clients (2.4.x,
> 2.6.x) seem to be fine.
Would it be possible to get a trace showing what the rpc traffic during
the above test? You could run something like
tcpdump -s0 -wTMP host my-client.example.com
and then post a copy of TMP someplace. Or look at it yourself in
wireshark--what you're looking for is how the server replied to the
rpc's generated by the commands above, and whether the server's replies
were consistent.
--b.
prev parent reply other threads:[~2007-03-28 17:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-27 20:34 Phy Prabab
2007-03-28 17:23 ` J. Bruce Fields [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=20070328172310.GC21221@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phyprabab@gmail.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
all inboxes | Powered by JetHome®