Date: Thu, 2 Jul 2015 01:44:35 +0200 From: Ahmed Kamal <email.ahmedkamal@googlemail.com> To: Rick Macklem <rmacklem@uoguelph.ca> Cc: freebsd-fs@freebsd.org Subject: Re: Linux NFSv4 clients are getting (bad sequence-id error!) Message-ID: <CANzjMX7xKBvnzJhQhB_ZrUnyE2m_FJXXy4fm_RFnuZfBDyDm2A@mail.gmail.com> In-Reply-To: <684628776.2772174.1435793776748.JavaMail.zimbra@uoguelph.ca> References: <CANzjMX45QaC8yZx2nHPAohJRvQjmUOHuhMQWP9nX%2BsrJs707Hg@mail.gmail.com> <684628776.2772174.1435793776748.JavaMail.zimbra@uoguelph.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks a lot Rick .. Actually I did reboot the nas box after setting the below in /etc/sysctl.conf (just to clean things up) vfs.nfsd.tcphighwater=61000 vfs.nfsd.tcpcachetimeout=300 Since clients are rhel5 only, they don't seem to support v4.1, only v4.0 .. So this one is not an option for now. The good news, is that after raising tcphighwater, these messages (nfsd server cache flooded, try increasing vfs.nfsd.tcphighwater) have completely stopped appearing in freebsd dmesg The not so great news is, after updating sysctl and rebooting the nas box, I still saw a few (NFS: v4 server nas returned a bad sequence-id error!) lines in logs. Users have already left, so I don't know how bad is it .. Could you share more info on what this error means? RedHat seems to think the client can skip-by-1 and choose larger IDs and that would be totally fine ? Also how serious is this error, would it cause NFS session stall like that ? On Thu, Jul 2, 2015 at 1:36 AM, Rick Macklem <rmacklem@uoguelph.ca> wrote: > Ahmed Kamal wrote: > > Hi all, > > > > I'm a refugee from linux land. I just set up my first freebsd 10.1 zfs > box, > > sharing /home over nfs. Since every home directory is its own zfs > dataset, > > I chose to use nfsv4 to enable recursively sharing/mounting any directory > > under /home (I understand nfs4 is a must in this scenario!) > > > > I'm able to mount form linux (rhel5 latest kernel) successfully. Users > are > > working fine. However every now and then a user screams that his session > is > > frozen. Usually the processes are stuck in nfs_wait or rpc_* state. I > tried > > using a much newer linux kernel (3.2 however it still faced the same > > problem). The errors in Linux log files are mostly: > > Jul 1 17:41:47 mammoth kernel: NFS: v4 server nas returned a *bad > > sequence-id error*! > > Jul 1 17:52:32 mammoth kernel: nfs4_reclaim_locks: unhandled error -11. > > Zeroing state > > Jul 1 17:52:32 mammoth kernel: nfs4_reclaim_open_state: Lock reclaim > > failed! > > > Btw, a client should only do "reclaim" operations after the server has > replied with NFS4ERR_STALE_CLIENTID or NFS4ERR_STALE_STATEID. I am pretty > certain that the FreeBSD NFSv4 server only generates these replies after > it has rebooted, so assuming the server didn't reboot, I have no idea why > the client would attempt these and am not surprised they failed. > > I'm guessing that the DRC constipation somehow caused the Linux client > to go into recovery mode? > > rick > > > My search led me to (https://access.redhat.com/solutions/1328073) a > > detailed analysis of the issue, which you can read over here > > https://dl.dropboxusercontent.com/u/51939288/nfs4-bad-seq.pdf .. NetApp > > confirmed this was a bug for them (I'm wondering if this is still in > > FreeBSD?!) > > > > PS: Right before sending this, I saw dmesg on the freebsd box advising > > increasing vfs.nfsd.tcphighwater .. So I up'ed that to 64000. I also > up'ed > > the number of nfs server threads (-t) from 10 to 60 (we're roughly 40 > linux > > machines) > > > > Any advice is most appreciated! > > > > Thanks > > _______________________________________________ > > freebsd-fs@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANzjMX7xKBvnzJhQhB_ZrUnyE2m_FJXXy4fm_RFnuZfBDyDm2A>