From: Chris Penney <cpenney@gmail.com>
To: nfs@lists.sourceforge.net
Subject: Kernel Oops
Date: Mon, 25 Apr 2005 12:31:19 -0400 [thread overview]
Message-ID: <111aefd05042509317c139b02@mail.gmail.com> (raw)
I have a 2.6.11.5 NFS server that serves a directory /s that had light
to moderate activity. I had another file server mounted as /nicfs7
and was doing a local rsync (moving some data) from /s/path to
/nicfs7/path when (for some unknown reason) it hung. I hit ctrl-c and
then kill -9'ed the two remaining rsync processes. I then unmounted
/nicfs7 (which seemed ok right after). I then saw what I pasted in
below in messages.
At this point NFS service seems ok; however, one of the nfsd threads
is missing. I specify to start 128 and only 127 are running. Is a
missing nfsd a problem? It's no clear to me why an nfsd did in the
first place either when I was using nfs client -> local disk.
Chris
Apr 25 10:51:31 nicfs2 kernel: nfs_statfs: statfs error =3D 512
Apr 25 10:53:18 nicfs2 kernel: VFS: Busy inodes after unmount.
Self-destruct in 5 seconds. Have a nice day...
Apr 25 10:54:40 nicfs2 kernel: Unable to handle kernel paging request
at virtual address 00200038
printing eip:
c01786b0
*pde =3D 00000000
Oops: 0000 [#1]
SMP
Modules linked in: nls_utf8 af_packet usbhid nfsd exportfs ipv6
ohci_hcd e1000 i2c_piix4 sworks_agp agpgart i2c_core evdev usbcore jfs
dm_round_robin dm_multipath dm_mod ext3 jbd qla2300 qla2xxx
scsi_transport_fc ips sd_mod scsi_mod
CPU: 1
EIP: 0060:[<c01786b0>] Not tainted VLI
EFLAGS: 00010202 (2.6.11.5)
EIP is at clear_inode+0x70/0x150
eax: f5759200 ebx: d8dca3bc ecx: f5759200 edx: 00200034
esi: d8dca4e8 edi: da2bd918 ebp: 00000005 esp: dff8bec8
ds: 007b es: 007b ss: 0068
Process kswapd0 (pid: 185, threadinfo=3Ddff8a000 task=3Ddffeea60)
Stack: f5759200 d8dca3bc f5759200 c0179780 d8dca3bc da2bd910 c0179813 d8dca=
3bc
c0176c06 00000000 00000080 00000000 dfffea20 c0177004 c014a5cc 0007b=
700
00000000 0007876d 00000001 00000000 000000d0 00000020 c0393780 00000=
002
Call Trace:
[<c0179780>] generic_forget_inode+0xf0/0x110
[<c0179813>] iput+0x53/0x70
[<c0176c06>] prune_dcache+0x176/0x1a0
[<c0177004>] shrink_dcache_memory+0x14/0x40
[<c014a5cc>] shrink_slab+0x11c/0x170
[<c014b9bd>] balance_pgdat+0x24d/0x3a0
[<c014bbec>] kswapd+0xdc/0x140
[<c0134b60>] autoremove_wake_function+0x0/0x50
[<c0103f92>] ret_from_fork+0x6/0x14
[<c0134b60>] autoremove_wake_function+0x0/0x50
[<c014bb10>] kswapd+0x0/0x140
[<c0102345>] kernel_thread_helper+0x5/0x10
Code: 01 00 00 a8 08 0f 85 83 00 00 00 f6 83 34 01 00 00 20 0f 85 a3
00 00 00 8b 83 a0 00 00 00 85 c0 89 c1 74 47 8b 50 28 85 d2 74 20 <8b>
52 04 85 d2 74 19 31 d2 8b b4 93 00 01 00 00 85 f6 0f 85 b1
Apr 25 10:54:40 nicfs2 kernel: <1>Unable to handle kernel paging
request at virtual address 5d3e324d
printing eip:
c01797dd
*pde =3D 00000000
Oops: 0000 [#2]
SMP
Modules linked in: nls_utf8 af_packet usbhid nfsd exportfs ipv6
ohci_hcd e1000 i2c_piix4 sworks_agp agpgart i2c_core evdev usbcore jfs
dm_round_robin dm_multipath dm_mod ext3 jbd qla2300 qla2xxx
scsi_transport_fc ips sd_mod scsi_mod
CPU: 0
EIP: 0060:[<c01797dd>] Not tainted VLI
EFLAGS: 00010206 (2.6.11.5)
EIP is at iput+0x1d/0x70
eax: 5d3e3239 ebx: f134e1cc ecx: c01b2ba0 edx: f134e1cc
esi: e1e4276c edi: e1e42774 ebp: 00000080 esp: f5c23cf0
ds: 007b es: 007b ss: 0068
Process nfsd (pid: 4052, threadinfo=3Df5c22000 task=3Df63d9020)
Stack: f134e1cc c0176c06 00000000 00000080 00000000 dfffea20 c0177004 c014a=
5cc
000f3c00 00000000 00078889 00000002 00000000 000001d2 00000040 00000=
00c
f5c23da8 c0395ca0 00000000 c014b6b4 00078888 00000000 000001d2 00000=
020
Call Trace:
[<c0176c06>] prune_dcache+0x176/0x1a0
[<c0177004>] shrink_dcache_memory+0x14/0x40
[<c014a5cc>] shrink_slab+0x11c/0x170
[<c014b6b4>] try_to_free_pages+0xc4/0x180
[<c014461f>] __alloc_pages+0x1bf/0x3b0
[<c0146aa7>] __do_page_cache_readahead+0x107/0x150
[<c0146c62>] blockable_page_cache_readahead+0x22/0x60
[<c0146d95>] page_cache_readahead+0xf5/0x2a0
[<c0140375>] do_generic_mapping_read+0x355/0x510
[<f8a62a67>] jfs_open+0x17/0xa0 [jfs]
[<c0140a7b>] generic_file_sendfile+0x6b/0x90
[<f8b64f00>] nfsd_read_actor+0x0/0x100 [nfsd]
[<f8b65262>] nfsd_read+0x262/0x360 [nfsd]
[<f8b64f00>] nfsd_read_actor+0x0/0x100 [nfsd]
[<f8b6c2c5>] nfsd3_proc_read+0xd5/0x170 [nfsd]
[<f8b6dfc0>] nfs3svc_decode_readargs+0x0/0x190 [nfsd]
[<f8b61696>] nfsd_dispatch+0x136/0x200 [nfsd]
[<c0322587>] svc_authenticate+0x87/0xe0
[<c031fae9>] svc_process+0x409/0x620
[<f8b613d6>] nfsd+0x196/0x320 [nfsd]
[<f8b61240>] nfsd+0x0/0x320 [nfsd]
[<c0102345>] kernel_thread_helper+0x5/0x10
Code: fe ff ff 8d 74 26 00 8d bc 27 00 00 00 00 53 85 c0 89 c3 74 4c
83 bb 2c 01 00 00 20 8b 80 a0 00 00 00 8b 40 24 74 3c 85 c0 74 07 <8b>
50 14 85 d2 75 3c 8d 43 24 ba 6c 6e 39 c0 e8 5f 8a 08 00 85
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2005-04-25 16:31 UTC|newest]
Thread overview: 97+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-25 16:31 Chris Penney [this message]
2005-04-25 17:47 ` Kernel Oops Dan Stromberg
-- strict thread matches above, loose matches on Subject: below --
2023-03-31 14:23 kernel oops Olga Kornievskaia
2023-03-31 14:25 ` Chuck Lever III
2023-04-04 14:24 ` Olga Kornievskaia
2023-04-04 14:31 ` Chuck Lever III
2023-04-04 14:44 ` Olga Kornievskaia
2023-04-04 14:54 ` Chuck Lever III
2023-04-04 16:15 ` Olga Kornievskaia
2023-04-04 17:28 ` Chuck Lever III
2023-04-04 19:11 ` Olga Kornievskaia
2023-04-04 19:14 ` Chuck Lever III
2023-04-04 19:26 ` Olga Kornievskaia
2023-04-04 19:30 ` Chuck Lever III
2017-07-24 21:16 Kernel oops Jason Gunthorpe
[not found] ` <20170724211606.GA1705-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-07-27 11:46 ` Matan Barak
[not found] ` <CAAKD3BAdB2aRk3WGdbeDYof6dUfkEwhQf27cG0FWe5DRuQ15NQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-07-27 12:54 ` Matan Barak
[not found] ` <CAAKD3BDFrTMMgX0nErD50rp2je=HC9zeaYWHDKf0mqQwc5fM9g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-07-27 20:44 ` Jason Gunthorpe
[not found] ` <20170727204437.GA16986-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-07-30 10:25 ` Leon Romanovsky
[not found] ` <20170730102514.GQ13672-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-07-31 3:52 ` Jason Gunthorpe
[not found] ` <20170731035208.GA30615-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-07-31 5:39 ` Leon Romanovsky
[not found] ` <20170731053901.GR13672-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-07-31 7:12 ` Leon Romanovsky
2013-08-30 3:13 Barclay Jameson
2012-07-07 12:54 Kernel Oops RuanZhijie
2012-07-04 11:04 RuanZhijie
2008-07-23 12:52 kernel oops Andrei Popa
2008-07-23 17:11 ` Vegard Nossum
2008-08-18 16:33 ` Vegard Nossum
2008-08-18 16:39 ` Greg KH
[not found] <e8eb01770803120245x7690e6a9te8ad04296aa3fc4d@mail.gmail.com>
2008-03-12 9:49 ` Zbynek Drlik
2008-03-12 10:33 ` Al Viro
2008-03-12 13:12 ` Zbynek Drlik
2008-02-05 12:57 Andrej Hocevar
2008-02-06 17:55 ` Len Brown
2006-10-27 8:59 Kernel Oops Joël Cuissinat
2006-10-27 17:30 ` Russell Cattelan
2006-09-12 10:21 Marcin Prączko
2006-09-13 3:43 ` Andrew Morton
2005-10-15 1:03 Marc Perkel
2005-10-15 1:21 ` Randy.Dunlap
2005-10-15 1:43 ` Marc Perkel
2005-10-15 1:52 ` Randy.Dunlap
2005-01-08 12:47 kernel oops ierdnah
2005-01-03 21:10 Kernel oops Marat BN
2005-01-05 10:13 ` Andrew Morton
2004-10-17 12:02 kernel oops Thomas Bleher
2004-10-17 12:59 ` Erich Schubert
2004-10-18 21:09 ` Thomas Bleher
2004-06-11 7:27 Kernel oops tmp
2004-05-24 20:19 tmp
2004-05-16 12:08 Kernel OOPS tmp
2004-05-16 23:27 ` Andrew Morton
2004-05-17 0:33 ` tmp
2004-03-09 22:13 Kernel oops Philipp Baer
2004-03-09 23:11 ` Andrew Morton
2004-03-12 7:46 ` Philipp Baer
2004-02-08 11:05 Kernel Oops Mathieu LESNIAK
2004-02-08 16:35 ` Greg KH
2004-02-09 7:06 ` Mathieu LESNIAK
2003-11-28 23:15 Kernel oops Ville Jutvik
2003-11-28 5:45 Anderson Levi
2003-08-09 12:39 kernel oops Jean-Yves LENHOF
2003-08-09 20:37 ` Jean-Yves LENHOF
2003-08-09 9:28 Jean-Yves LENHOF
2003-07-18 19:44 Kernel OOPS Robert Scussel
2003-07-18 21:31 ` Alan Cox
2003-07-07 12:53 kernel oops Anders Karlsson
2003-07-07 13:14 ` Alan Cox
2003-07-07 13:32 ` Anders Karlsson
2003-07-07 13:37 ` Alan Cox
2003-07-07 13:56 ` Anders Karlsson
2003-07-08 9:39 ` Marcelo Tosatti
[not found] ` <200307072009.50677.bernd-schubert@web.de>
2003-07-08 5:13 ` Anders Karlsson
2003-05-31 1:32 Nadeem Riaz
2003-03-26 15:52 Steve Terrell
2003-02-03 1:18 Kernel Oops Daniel Espinoza
2003-02-03 3:23 ` vishwas
2002-08-09 5:25 sanket rathi
2002-06-23 19:39 Dirk Schmidt
2002-06-10 8:46 kernel oops Robert Litwiniec
2002-02-26 18:26 Suporte RedeBonja
2002-02-27 13:35 ` Erik Mouw
2001-11-26 19:59 Tracy R Reed
2001-11-26 19:27 ` Stephen Smalley
2001-11-13 13:23 Kernel oops Anthony
2001-11-14 6:02 ` Thiago Rondon
2001-10-08 12:59 kernel oops Terry Kendal
2001-09-27 9:49 kewl
2001-06-01 15:13 Kernel oops David Harris
2001-06-01 15:12 David Harris
2001-04-19 18:32 kernel oops Ronald Bultje
2001-04-19 19:04 ` Alan Cox
2001-04-19 19:08 ` Ronald Bultje
2001-02-19 14:44 Kernel Oops Alberto Bertogli
2000-12-10 0:53 Bastien Nocera
2000-12-10 1:13 ` Bastien Nocera
2000-05-17 17:10 Kernel oops Patrick Higgins
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=111aefd05042509317c139b02@mail.gmail.com \
--to=cpenney@gmail.com \
--cc=nfs@lists.sourceforge.net \
--cc=penney@msu.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.