From: Olaf Titz <Olaf.Titz@inka.de>
To: Neil Brown <neilb@suse.de>
Cc: Olaf Titz <olaf@bigred.inka.de>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.19: OOPS in cat /proc/fs/nfs/exports
Date: Tue, 05 Dec 2006 23:32:08 +0100 [thread overview]
Message-ID: <E1Gripc-0004KC-00@bigred.inka.de> (raw)
In-Reply-To: <17780.62607.544405.181452@cse.unsw.edu.au>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> There is a place where a failed kstrdup could lead to this, but that
> is rather unlikely and wouldn't be as reproducible as this seems to
> be.
> If you boot up and then immediately shutdown does this error trigger,
> it does it have to be up for a while?
It happens right after booting.
I've since disabled the NFS server on that box, and just tried to
manually start it, and it gives me this:
# /usr/sbin/exportfs -r
bigred:/video/rec: Cannot allocate memory
That is the first and only export:
# cat /etc/exports
# /etc/exports: the access control list for filesystems which may be
exported
# to NFS clients. See exports(5).
/video/rec bigred(rw,sync)
strace on exportfs shows this:nfsservctl(0x3, 0xbf875824, 0) =
- -1 ENOMEM
After that, /proc/fs/nfs/export exists and gives the Oops, while
/proc/fs/nfsd/export doesn't exist.
I don't think however this box is particularly short on memory:
MemTotal: 248704 kB
MemFree: 102780 kB
Buffers: 20520 kB
Cached: 50692 kB
SwapCached: 0 kB
Active: 81712 kB
Inactive: 25160 kB
SwapTotal: 0 kB
SwapFree: 0 kB
Dirty: 1516 kB
Writeback: 0 kB
AnonPages: 35672 kB
Mapped: 13104 kB
Slab: 6960 kB
SReclaimable: 3104 kB
SUnreclaim: 3856 kB
PageTables: 692 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
CommitLimit: 124352 kB
Committed_AS: 124528 kB
VmallocTotal: 786136 kB
VmallocUsed: 7568 kB
VmallocChunk: 778508 kB
(this is right after booting, DVB drivers loaded and VDR running.)
Will try your patch tomorrow.
Olaf
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFdfNoGPw4gdAdiZ0RAjDdAJ4yPltxWuJe21yB9nc2zBooLWJ2TwCaAg1I
tNsnDshD1gVpW/FYJ5P9J28=
=1zag
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2006-12-05 22:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-04 19:14 2.6.19: OOPS in cat /proc/fs/nfs/exports Olaf Titz
2006-12-05 4:24 ` Neil Brown
2006-12-05 22:32 ` Olaf Titz [this message]
2006-12-06 22:58 ` Olaf Titz
2006-12-07 1:38 ` Neil Brown
2006-12-10 22:04 ` Olaf Titz
2006-12-10 22:36 ` Neil Brown
2006-12-19 21:23 ` Olaf Titz
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=E1Gripc-0004KC-00@bigred.inka.de \
--to=olaf.titz@inka.de \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=olaf@bigred.inka.de \
/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