From: "J. Bruce Fields" <bfields@fieldses.org>
To: Nikola Ciprich <extmaillist-Jp3n8lUXroTtwjQa/ONI9g@public.gmane.org>
Cc: linux NFS list <linux-nfs@vger.kernel.org>,
nikola.ciprich-Jp3n8lUXroTtwjQa/ONI9g@public.gmane.org,
mzik-Jp3n8lUXroTtwjQa/ONI9g@public.gmane.org
Subject: Re: 2.6.32.16 - NFS still having trouble (nfsd: peername failed (err 107)!)
Date: Tue, 20 Jul 2010 16:23:53 -0400 [thread overview]
Message-ID: <20100720202353.GA11367@fieldses.org> (raw)
In-Reply-To: <20100714110020.GB10153-K8br+RTdgN68z6Q06MQEFCF40CQGThNF@public.gmane.org>
On Wed, Jul 14, 2010 at 01:00:20PM +0200, Nikola Ciprich wrote:
> Hi,
>
> I just updated one of my NFS boxes to 2.6.32.16, but NFS is still not in
> top condition.
Sorry, I'm missing some history: was NFS doing OK in some previous
kernel version, or has this always been a problem?
> Clients are hanging during copying, and following messages
> are appearing in dmesg:
>
...
>
> machine is x86_64, what is certainly important to note is that
> NFS share sits on top of (large) dm-crypted ext4 volume.
> Could somebody please help me to track the source of problems?
Hangs appear to be in ext4, and my first impulse would be to blame
dm-crypt and/or ext4; have you asked them?
--b.
>
> Thanks a lot in advance...
>
> with best regards
>
> nikola ciprich
>
>
> --
> -------------------------------------
> Ing. Nikola CIPRICH
> LinuxBox.cz, s.r.o.
> 28. rijna 168, 709 01 Ostrava
>
> tel.: +420 596 603 142
> fax: +420 596 621 273
> mobil: +420 777 093 799
> www.linuxbox.cz
>
> mobil servis: +420 737 238 656
> email servis: servis-Jp3n8lUXroTtwjQa/ONI9g@public.gmane.org
> -------------------------------------
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-07-20 20:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-14 11:00 2.6.32.16 - NFS still having trouble (nfsd: peername failed (err 107)!) Nikola Ciprich
[not found] ` <20100714110020.GB10153-K8br+RTdgN68z6Q06MQEFCF40CQGThNF@public.gmane.org>
2010-07-20 20:23 ` J. Bruce Fields [this message]
2010-07-22 11:03 ` Nikola Ciprich
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=20100720202353.GA11367@fieldses.org \
--to=bfields@fieldses.org \
--cc=extmaillist-Jp3n8lUXroTtwjQa/ONI9g@public.gmane.org \
--cc=linux-nfs@vger.kernel.org \
--cc=mzik-Jp3n8lUXroTtwjQa/ONI9g@public.gmane.org \
--cc=nikola.ciprich-Jp3n8lUXroTtwjQa/ONI9g@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).