From: Herbert Poetzl <herbert@13thfloor.at>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: nfsd: non-standard errno: 925302784
Date: Thu, 10 Feb 2011 05:28:40 +0100 [thread overview]
Message-ID: <20110210042840.GF11496@MAIL.13thfloor.at> (raw)
Hi Trond!
I'm seeing _a_lot_ of those messages on one of my
test servers (probably caused by a client doing an
rsync -aX to an nfs mount), so I added a rate limit
and a stack trace which results in those traces:
(0x37270000 looks strange for an errno)
Any ideas how to fix that properly?
Thanks in Advance,
Herbert
[89066.666981] nfsd: non-standard errno: 925302784
[89066.666984] Pid: 5233, comm: nfsd Tainted: G A 2.6.38-rc3 #8
[89066.666986] Call Trace:
[89066.666994] [<ffffffffa02cb118>] ? nfserrno+0x68/0x80 [nfsd]
[89066.666999] [<ffffffffa02dcb77>] ? nfsd4_decode_fattr+0x537/0x9c0 [nfsd]
[89066.667005] [<ffffffffa02dd034>] ? nfsd4_decode_setattr+0x34/0x40 [nfsd]
[89066.667010] [<ffffffffa02dc102>] ? nfs4svc_decode_compoundargs+0x2c2/0x3c0 [nfsd]
[89066.667014] [<ffffffffa02c936f>] ? nfsd_dispatch+0x7f/0x240 [nfsd]
[89066.667025] [<ffffffffa01beb49>] ? svc_process+0x479/0x7a0 [sunrpc]
[89066.667029] [<ffffffffa02c9a20>] ? nfsd+0x0/0x140 [nfsd]
[89066.667033] [<ffffffffa02c9acf>] ? nfsd+0xaf/0x140 [nfsd]
[89066.667037] [<ffffffff810672c6>] ? kthread+0x96/0xa0
[89066.667040] [<ffffffff810038d4>] ? kernel_thread_helper+0x4/0x10
[89066.667042] [<ffffffff81067230>] ? kthread+0x0/0xa0
[89066.667044] [<ffffffff810038d0>] ? kernel_thread_helper+0x0/0x10
[89066.669233] nfsd: non-standard errno: 925302784
[89066.669237] Pid: 5233, comm: nfsd Tainted: G A 2.6.38-rc3 #8
[89066.669238] Call Trace:
[89066.669248] [<ffffffffa02cb118>] ? nfserrno+0x68/0x80 [nfsd]
[89066.669253] [<ffffffffa02dcb77>] ? nfsd4_decode_fattr+0x537/0x9c0 [nfsd]
[89066.669258] [<ffffffffa02dd034>] ? nfsd4_decode_setattr+0x34/0x40 [nfsd]
[89066.669264] [<ffffffffa02dc102>] ? nfs4svc_decode_compoundargs+0x2c2/0x3c0 [nfsd]
[89066.669268] [<ffffffffa02c936f>] ? nfsd_dispatch+0x7f/0x240 [nfsd]
[89066.669280] [<ffffffffa01beb49>] ? svc_process+0x479/0x7a0 [sunrpc]
[89066.669284] [<ffffffffa02c9a20>] ? nfsd+0x0/0x140 [nfsd]
[89066.669288] [<ffffffffa02c9acf>] ? nfsd+0xaf/0x140 [nfsd]
[89066.669291] [<ffffffff810672c6>] ? kthread+0x96/0xa0
[89066.669294] [<ffffffff810038d4>] ? kernel_thread_helper+0x4/0x10
[89066.669297] [<ffffffff81067230>] ? kthread+0x0/0xa0
[89066.669299] [<ffffffff810038d0>] ? kernel_thread_helper+0x0/0x10
next reply other threads:[~2011-02-10 4:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-10 4:28 Herbert Poetzl [this message]
[not found] ` <20110210195520.1b91a1f9@notabene.brown>
[not found] ` <20110216131252.631edb67@notabene.brown>
2011-02-16 23:34 ` J.Bruce Fields
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=20110210042840.GF11496@MAIL.13thfloor.at \
--to=herbert@13thfloor.at \
--cc=Trond.Myklebust@netapp.com \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome