public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Vlad Glagolev <stealth-L+UJwxqiw56VyaH7bEyXVA@public.gmane.org>,
	linux-nfs@vger.kernel.org, linux-raid@vger.kernel.org
Subject: Re: NFS and /dev/mdXpY
Date: Thu, 22 Apr 2010 15:47:30 -0400	[thread overview]
Message-ID: <1271965650.593.21.camel@localhost.localdomain> (raw)
In-Reply-To: <20100422193236.GA10302@fieldses.org>

On Thu, 2010-04-22 at 15:32 -0400, J. Bruce Fields wrote: 
> On Thu, Apr 22, 2010 at 10:53:10PM +0400, Vlad Glagolev wrote:
> > On Thu, 22 Apr 2010 14:25:43 -0400
> > "J. Bruce Fields" <bfields@fieldses.org> wrote:
> > 
> > > On Sat, Apr 17, 2010 at 07:57:47PM +0400, Vlad Glagolev wrote:
> > > > Well, hello there,
> > > > 
> > > > Posted it on linux-kernel ML also, and post it here, for more specific analysis.
> > > > 
> > > > I faced this problem today while trying to mount some NFS share on OpenBSD box.
> > > > I mounted it successfully without any visible errors, but I wasn't able to cd there, the printed error was:
> > > > 
> > > > ksh: cd: /storage - Stale NFS file handle
> > > > 
> > > > Apropos, the partition is 5.5 TB. I tried another one on my box and it was mounted successfully. It was possible to manage files there too. Its size is ~3GB.
> > > > That's why the first time I thought about some size limitations of OpenBSD/Linux/NFS.
> > > > 
> > > > While talking on #openbsd @ freenode, I discovered this via tcpdump on both sides:
> > > > 
> > > > http://pastebin.ca/1864713
> > > > 
> > > > Googling for 3 hours didn't help at all, some posts had similiar issue but either with no answer at all or without any full description.
> > > > 
> > > > Then I started to experiment with another Linux box to kill the possible different variants.
> > > > 
> > > > On another box I also have nfs-utils 1.1.6 and kernel 2.6.32. Mounting that big partition was unsuccessful, it got just stuck. On tcpdump I've seen this:
> > > 
> > > I'm a bit confused.  What kernel and nfs-utils version is running on the
> > > problematic Linux server?
> > 
> > same. nfs-utils 1.1.6 and kernel 2.6.32.
> 
> Huh.  That should be new enough for it to be using uuid's.  I wonder why
> it isn't?

What are the contents of /dev/disk/by-uuid?


  reply	other threads:[~2010-04-22 19:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-17 15:57 NFS and /dev/mdXpY Vlad Glagolev
2010-04-21 16:39 ` Steve Cousins
2010-04-21 16:48   ` Vlad Glagolev
2010-04-21 17:09     ` Roger Heflin
2010-04-21 17:32       ` Vlad Glagolev
2010-04-21 18:26         ` Vlad Glagolev
2010-04-21 19:08           ` Vlad Glagolev
2010-04-22  1:20           ` Roger Heflin
     [not found] ` <20100417195747.5fae8834.stealth-L+UJwxqiw56VyaH7bEyXVA@public.gmane.org>
2010-04-22 18:25   ` J. Bruce Fields
2010-04-22 18:53     ` Vlad Glagolev
2010-04-22 19:32       ` J. Bruce Fields
2010-04-22 19:47         ` Trond Myklebust [this message]
2010-04-22 19:51           ` Vlad Glagolev
2010-04-22 19:56             ` Trond Myklebust
2010-04-22 20:07               ` Vlad Glagolev

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=1271965650.593.21.camel@localhost.localdomain \
    --to=trond.myklebust@fys.uio.no \
    --cc=bfields@fieldses.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=stealth-L+UJwxqiw56VyaH7bEyXVA@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