Re: NFS and /dev/mdXpY

[Vlad Glagolev <stealth@sourcemage.org>]

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

Hmm, more testing.. It works only with tiny files flawlessly on OpenBSD (client).

If a filesize is around 50 mibs, then it just freezes and eats cpu with nfsrcvl call.

On Linux I don't see such problem. Even big files are transfered with good enough speed.

On Wed, 21 Apr 2010 21:32:01 +0400
Vlad Glagolev <stealth@sourcemage.org> wrote:

> 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


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

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