public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Stuart Rowan <strr-debian@decisionsoft.co.uk>
To: xfs@oss.sgi.com
Subject: 2.6.24.3 nfs server on xfs keeps producing nfsd: non-standard errno: -117
Date: Mon, 17 Mar 2008 23:27:26 +0000	[thread overview]
Message-ID: <47DEFE5E.4030703@decisionsoft.co.uk> (raw)

Hi,

Firstly thanks for the great filesystem and apologies if this ends up being 
NFS rather than XFS being weird! I'm not subscribed so please do keep me CC'd.

I have *millions* of lines of (>200k per minute according to syslog):
nfsd: non-standard errno: -117
being sent out of dmesg

Now errno 117 is
#define EUCLEAN         117     /* Structure needs cleaning */
which seems to be only used from a quick grep by XFS and JFFS and smbfs.


My nfs server export two locations
/home
/home/archive
both of these are XFS partitions, hence my suspicion that the -117 is 
coming from XFS.

xfs_repair -n says the filesystems are clean
xfs_repair has been run multiple times to completion on the filesystems, 
all is fine.

The XFS partitions are lvm volumes as follows
data/home 900G
data/archive 400G
The volume group, data, is sda3
sda3 is a 6 drive 3ware 9550SXU-8LP RAID10 array

The NFS server is currently in use (indeed the message only starts once 
clients connect) and works absolutely fine.

How do I find out what (if anything) is wrong with my filesystem / 
appropriately silence this message?

Many thanks,
Stu.

             reply	other threads:[~2008-03-17 23:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-17 23:27 Stuart Rowan [this message]
2008-03-18  0:28 ` 2.6.24.3 nfs server on xfs keeps producing nfsd: non-standard errno: -117 Timothy Shimmin
2008-03-18  1:07   ` Stuart Rowan
2008-03-18 13:49   ` Stuart Rowan
2008-03-20  1:09     ` Timothy Shimmin
2008-03-20  8:25       ` XFS internal error xfs_itobp at line 360 of file fs/xfs/xfs_inode.c. (was Re: 2.6.24.3 nfs server on xfs keeps producing nfsd: non-standard errno: -117) Stuart Rowan

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=47DEFE5E.4030703@decisionsoft.co.uk \
    --to=strr-debian@decisionsoft.co.uk \
    --cc=xfs@oss.sgi.com \
    /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