public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Vlad Glagolev <stealth@sourcemage.org>
To: Roger Heflin <rogerheflin@gmail.com>
Cc: Steve Cousins <steve.cousins@maine.edu>,
	linux-nfs@vger.kernel.org, linux-raid@vger.kernel.org
Subject: Re: NFS and /dev/mdXpY
Date: Wed, 21 Apr 2010 21:32:01 +0400	[thread overview]
Message-ID: <20100421213201.67a4a7a2.stealth@sourcemage.org> (raw)
In-Reply-To: <q2zd3da20d01004211009jccd81479v83e2ef4b6d5db7bf@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2339 bytes --]

On Wed, 21 Apr 2010 12:09:20 -0500
Roger Heflin <rogerheflin@gmail.com> wrote:

> On Wed, Apr 21, 2010 at 11:48 AM, Vlad Glagolev <stealth@sourcemage.org> wrote:
> > Thanks for reply, Steve!
> >
> > parameters are pretty trivial, (rw,insecure) for exports, and defaults while mounting via ``mount host:/path /path'' command.
> >
> > Yes. That sounds interesting, since XFS works fine with there partitions.
> > Also, I must say it's WD20EARS drives (with 4kb sector size, though parted says it's 512b).
> >
> > I also tried another NFS daemon implementation (cvs version, not .22) -- unfsd (unfs3).
> > It mounts ok, but when I try to write any file to the server -- I get the same error (Stale NFS file handle).
> >
> > And on the server side in dmesg I see this:
> >
> > --
> > NFS: server 172.17.2.2 error: fileid changed
> > fsid 0:f: expected fileid 0x2033, got 0xb6d1e05fa150ce09
> > NFS: server 172.17.2.2 error: fileid changed
> > fsid 0:f: expected fileid 0x2033, got 0x26550b0132c0b1
> > NFS: server 172.17.2.2 error: fileid changed
> > fsid 0:f: expected fileid 0x2033, got 0x8202a60053000020
> > NFS: server 172.17.2.2 error: fileid changed
> > fsid 0:f: expected fileid 0x2033, got 0xe542f93ebc8fe157
> > NFS: server 172.17.2.2 error: fileid changed
> > fsid 0:f: expected fileid 0x2033, got 0xc00cd74ea904301
> > --
> >
> > looks like NFS protocol doesn't like something in partitioned software RAID.
> >
> 
> 
> Try manually setting the fsid=something in the exports file and
> reexport and remount on the target system, if there was a fsid
> collision of some sort then nfs would be hitting the wrong fs...
> 
> NFS generates the fsid automatically based on the devices major minor,
> and it is possible there is something odd about the major minor
> numbers that make them not unique...and collide with someone else
> major minor.

BAH! How simple!

Thank you very much, Roger!

I've just added fsid=1 (yes, only these few chars) to exports, and it worked! Unbelievable, really :)
Of course I've checked it on OpenBSD and Linux under both nfsd and unfsd. Works flawlessly.

Thanks a lot again.

But it seems to be a bug, right? If so, patches welcome.. I'll test it with great pleasure.

-- 
Dont wait to die to find paradise...
--
Cheerz,
Vlad "Stealth" Glagolev

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2010-04-21 17:33 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 [this message]
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
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=20100421213201.67a4a7a2.stealth@sourcemage.org \
    --to=stealth@sourcemage.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=rogerheflin@gmail.com \
    --cc=steve.cousins@maine.edu \
    /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