From: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
To: Ken Moffat <zarniwhoop@ntlworld.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: nfs3 problem with -rc{2,3}
Date: Mon, 18 Jun 2012 13:42:37 +0000 [thread overview]
Message-ID: <1340026956.2451.9.camel@lade.trondhjem.org> (raw)
In-Reply-To: <20120617200700.GA15348@milliways>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 2392 bytes --]
On Sun, 2012-06-17 at 21:07 +0100, Ken Moffat wrote:
> I'm seeing problems writing to shared directories mounted as nfs3.
> Wondering if anyone else is seeing similar problems ?
>
> I noticed this last week with -rc2 (my first new kernel since
> 3.4.0), but haven't managed to find a minimal test case to replicate
> it.
>
> The first problem was with firefox - I use it to download tarballs
> and patches to a shared /sources. The first download worked, maybe
> also another, but some time later one stalled and firefox stopped
> refreshing its window. Looked as if it successfully created
> packagename.tar.gz.part, but with an empty packagename.tar.gz.
>
> I killed firefox, then I used wget to download to a local filesystem
> and then tried to cp it to the shared /sources - cp hung indefinitely,
> apparently after completing the transfer.
>
> At this time I tried to run a script *in* /sources which hung
> trying to rm a file [ worked fine when I killed it, ssh'd to the
> server, and ran it locally ].
>
> I've also got regular backup scripts which wrap rsync writes to a
> different writable directory on the server. These stall with -rc2
> and -rc3, and get killed by SIGINT when I eventually reboot or shut
> down.
>
> I tried using only the rsync command and playing with just an rsync
> of a single file in a directory, but that doesn't provoke the
> problem. I've also tried various attempts to cp or move a file
> to the shared directory, but again without problems. It seems that
> things are fine until something provokes the problem, then all
> updates stall. This makes it a bit hard to get a reliable and
> simple testcase.
>
> I suppose I'll have to start to bisect using the backup script as
> my test case (booted rc2 earlier, did nothing except ssh and allow
> fcron to run it - it stalled. built rc3, booted that, fcron tried
> to run the incomplete backup, again it has stalled).
>
> Config from rc2 attached, any suggestions are welcome.
Is this a problem with the client or with the server, and have you tried
seeing if the fixes that were merged into -rc3 help?
Cheers
Trond
--
Trond Myklebust
Linux NFS client maintainer
NetApp
Trond.Myklebust@netapp.com
www.netapp.com
ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
next prev parent reply other threads:[~2012-06-18 13:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-17 20:07 Ken Moffat
2012-06-18 1:11 ` Ken Moffat
2012-06-18 13:42 ` Myklebust, Trond [this message]
2012-06-18 13:45 ` Myklebust, Trond
2012-06-18 14:18 ` Ken Moffat
2012-06-18 14:53 ` Myklebust, Trond
2012-06-18 16:00 ` Ken Moffat
2012-06-18 20:05 ` Ken Moffat
2012-06-18 20:11 ` Myklebust, Trond
2012-06-18 23:38 ` Ken Moffat
2012-06-18 23:44 ` Ken Moffat
2012-06-18 21:53 ` Ken Moffat
2012-06-18 22:03 ` Myklebust, Trond
2012-06-18 22:10 ` Ken Moffat
2012-06-19 1:06 ` nfs3 problem with -rc{2,3} : blame Ken Moffat
2012-06-19 16:20 ` Myklebust, Trond
2012-06-19 16:23 ` Myklebust, Trond
2012-06-19 16:55 ` Ken Moffat
2012-06-19 17:46 ` Myklebust, Trond
2012-06-19 19:35 ` Ken Moffat
2012-06-19 22:44 ` Myklebust, Trond
2012-06-19 23:31 ` Ken Moffat
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=1340026956.2451.9.camel@lade.trondhjem.org \
--to=trond.myklebust@netapp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zarniwhoop@ntlworld.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®