From: Arun Sharma <arun.sharma@intel.com>
To: Ion Badulescu <lists@cs.columbia.edu>
Cc: autofs@linux.kernel.org, nfs@lists.sourceforge.net
Subject: Re: [NFS] VFS: Busy inodes after unmount on 2 way SMP
Date: Mon, 15 Sep 2003 14:42:30 -0700 [thread overview]
Message-ID: <3F663246.7010806@intel.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0309122013380.9830-100000@moisil.badula.org>
Ion Badulescu wrote:
> On Fri, 12 Sep 2003, Arun Sharma wrote:
>
>
>>Ion Badulescu wrote:
>>
>>>I don't know if it's the same issue, but I've seen it many many times
>>>while testing amd's autofs functionality. It occurs when a non-empty
>>>autofs filesystem is unmounted, e.g. if it has some leftover
>>>subdirectories from previous mounts. Therefore I'd say it's quite
>>>clearly an autofs issue, at least in my case.
>>
>>Do you have a case that can deterministically reproduce the issue ?
>
>
> Oh yeah, easily. Kill the automounter while some things are mounted,
> unmount everything by hand but do not rmdir the mountpoints. When you
> unmount the autofs filesystem itself, you will get the self destruct
> message.
>
Thanks. This reproduces the problem I'm chasing very well. I think this is clearly an unacceptable kernel bug.
-Arun
Sep 15 13:58:57 arun-desktop kernel: VFS: Busy inodes after unmount. Self-destruct in 5 seconds. Have a nice day...
<snip>
Sep 15 14:00:00 arun-desktop kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000004
Sep 15 14:00:00 arun-desktop kernel: printing eip:
Sep 15 14:00:00 arun-desktop kernel: c015c738
Sep 15 14:00:00 arun-desktop kernel: *pde = 00000000
Sep 15 14:00:00 arun-desktop kernel: Oops: 0000
Sep 15 14:00:00 arun-desktop kernel: ide-cd cdrom emu10k1 ac97_codec sound soundcore nfs lockd sunrpc parport_pc lp parport autofs iptable_filter ip_tables
e100 keybdev mousedev hid input usb-uhc
Sep 15 14:00:00 arun-desktop kernel: CPU: 0
Sep 15 14:00:00 arun-desktop kernel: EIP: 0060:[<c015c738>] Not tainted
Sep 15 14:00:00 arun-desktop kernel: EFLAGS: 00010246
Sep 15 14:00:00 arun-desktop kernel:
Sep 15 14:00:00 arun-desktop kernel: EIP is at destroy_inode [kernel] 0x28 (2.4.20-8)
Sep 15 14:00:00 arun-desktop kernel: eax: 00000000 ebx: cee44c80 ecx: 00000000 edx: cee44c80
Sep 15 14:00:00 arun-desktop kernel: esi: cb32ee00 edi: cee44c80 ebp: 000003c6 esp: cff87f84
Sep 15 14:00:01 arun-desktop kernel: ds: 0068 es: 0068 ss: 0068
Sep 15 14:00:01 arun-desktop kernel: Process kswapd (pid: 5, stackpage=cff87000)
Sep 15 14:00:01 arun-desktop kernel: Stack: cee44c80 cb32ee00 cb32ee18 c015b563 cee44c80 cb0ff180 cff86000 00000000
Sep 15 14:00:01 arun-desktop kernel: 000001d0 00000000 c015b904 0000057c c013cd5b 00000006 000001d0 cff86000
Sep 15 14:00:01 arun-desktop kernel: cff86000 00000000 cff86305 00000000 c013d023 000001d0 00000002 000001d0
Sep 15 14:00:01 arun-desktop kernel: Call Trace: [<c015b563>] prune_dcache [kernel] 0xc3 (0xcff87f90))
Sep 15 14:00:01 arun-desktop kernel: [<c015b904>] shrink_dcache_memory [kernel] 0x24 (0xcff87fac))
Sep 15 14:00:01 arun-desktop kernel: [<c013cd5b>] do_try_to_free_pages_kswapd [kernel] 0x1b (0xcff87fb4))
Sep 15 14:00:01 arun-desktop kernel: [<c013d023>] kswapd [kernel] 0x83 (0xcff87fd4))
Sep 15 14:00:01 arun-desktop kernel: [<c013cfa0>] kswapd [kernel] 0x0 (0xcff87fe4))
Sep 15 14:00:01 arun-desktop kernel: [<c010742d>] kernel_thread_helper [kernel] 0x5 (0xcff87ff0))
next prev parent reply other threads:[~2003-09-15 21:42 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-12 0:11 VFS: Busy inodes after unmount on 2 way SMP Arun Sharma
2003-09-12 1:05 ` H. Peter Anvin
2003-09-12 14:23 ` Ryan Go
2003-09-12 17:57 ` Arun Sharma
2003-09-12 20:51 ` H. Peter Anvin
2003-09-12 23:33 ` Ion Badulescu
2003-09-13 0:08 ` Arun Sharma
2003-09-13 0:16 ` Ion Badulescu
2003-09-13 0:16 ` Ion Badulescu
2003-09-15 21:42 ` Arun Sharma [this message]
2003-09-15 22:25 ` Re: [NFS] " H. Peter Anvin
2003-09-15 22:34 ` Arun Sharma
2003-09-15 23:42 ` Ion Badulescu
2003-09-16 1:34 ` [autofs] " Matt C
2003-09-16 1:34 ` Matt C
2003-09-19 2:57 ` Frank Cusack
2003-09-16 20:37 ` Re: [NFS] " Arun Sharma
2003-09-16 20:54 ` H. Peter Anvin
2003-09-17 0:28 ` Ian Kent
2003-09-17 2:05 ` Arun Sharma
2003-09-17 2:28 ` H. Peter Anvin
2003-09-17 4:56 ` Ian Kent
2003-09-17 4:52 ` Ian Kent
2003-09-17 17:47 ` Arun Sharma
2003-09-17 20:41 ` H. Peter Anvin
2003-09-17 21:00 ` Olaf Hering
2003-09-18 0:31 ` Ian Kent
2003-09-18 5:04 ` Olaf Hering
2003-09-18 5:52 ` Re: [autofs] " Trond Myklebust
2003-09-18 8:26 ` Olaf Kirch
2003-09-19 23:36 ` [NFS] " Olaf Hering
2003-09-25 23:17 ` Re: [autofs] " Matt C
2003-09-25 23:17 ` Matt C
2003-09-26 0:24 ` Trond Myklebust
2003-09-26 0:24 ` Trond Myklebust
2003-09-26 18:31 ` [NFS] " Ion Badulescu
2003-09-26 22:29 ` Re: [autofs] " Trond Myklebust
2003-09-27 16:55 ` Olaf Kirch
2003-09-28 23:16 ` Steve Fosdick
2003-09-29 12:07 ` Ion Badulescu
2003-09-29 17:22 ` Trond Myklebust
2003-09-30 12:50 ` Olaf Kirch
2003-09-30 13:31 ` Trond Myklebust
2003-09-29 3:27 ` Frank Cusack
2003-09-18 2:26 ` [NFS] " Ion Badulescu
2003-09-18 2:54 ` H. Peter Anvin
2003-09-29 12:19 ` Ion Badulescu
2003-09-30 12:24 ` Ian Kent
2003-09-30 12:51 ` Mike Waychison
2003-10-01 12:56 ` Ian Kent
2003-09-30 13:12 ` Ion Badulescu
2003-09-30 16:44 ` Ian Kent
2003-09-17 13:14 ` Ryan Go
-- strict thread matches above, loose matches on Subject: below --
2003-09-12 23:58 [NFS] " Ion Badulescu
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=3F663246.7010806@intel.com \
--to=arun.sharma@intel.com \
--cc=autofs@linux.kernel.org \
--cc=lists@cs.columbia.edu \
--cc=nfs@lists.sourceforge.net \
/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.