Kernel 2.5.71 cannot unmount nfs

Kernel 2.5.71 cannot unmount nfs

[Seifert Guido, gse]

[-- Attachment #1: Type: text/plain, Size: 398 bytes --]


Sorry for the incomplete and unprofessional bugreport, I don't have more
info. 
I tried Kernel 2.5.71. Everything seems to work fine until I shut down
or try to 
unmount a mountend nfs filesystem. For several minutes nothing happens, 
then I get something what looks like a backtrace from the nfs related
code 
section. Unfortunately there is nothing in the log files afterwards. 
G. 


[-- Attachment #2: InterScan_SafeStamp.txt --]
[-- Type: text/plain, Size: 242 bytes --]

****** Message from InterScan E-Mail VirusWall NT ******

** No virus found in attached file noname.htm

E-mail is virus checked, Pentapharm Group, Switzerland, Support@pentapharm.com
*****************     End of message     ***************

Re: Kernel 2.5.71 cannot unmount nfs

[Alex Riesen]

Seifert Guido, gse, Mon, Jun 16, 2003 10:22:08 +0200:
> Sorry for the incomplete and unprofessional bugreport, I don't have more
> info. 
> I tried Kernel 2.5.71. Everything seems to work fine until I shut down
> or try to unmount a mountend nfs filesystem. For several minutes
> nothing happens, then I get something what looks like a backtrace from
> the nfs related code section. Unfortunately there is nothing in the
> log files afterwards. 

See the patch at http://bugme.osdl.org/show_bug.cgi?id=805

Re: Kernel 2.5.71 cannot unmount nfs

[Dipankar Sarma]

On Mon, Jun 16, 2003 at 08:23:48AM +0000, Seifert Guido, gse wrote:
> 
> Sorry for the incomplete and unprofessional bugreport, I don't have more
> info. 
> I tried Kernel 2.5.71. Everything seems to work fine until I shut down
> or try to 
> unmount a mountend nfs filesystem. For several minutes nothing happens, 
> then I get something what looks like a backtrace from the nfs related
> code 
> section. Unfortunately there is nothing in the log files afterwards. 
> G. 

Does this patch fix your problem ?

http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.5/2.5.71/2.5.71-mm1/broken-out/rpc-depopulate-fix.patch

Thanks
Dipankar

Re: Kernel 2.5.71 cannot unmount nfs

[John M Flinchbaugh]

[-- Attachment #1: Type: text/plain, Size: 463 bytes --]

On Mon, Jun 16, 2003 at 02:27:27PM +0530, Dipankar Sarma wrote:
> Does this patch fix your problem ?
> http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.5/2.5.71/2.5.71-mm1/broken-out/rpc-depopulate-fix.patch

it's working beautifully for ME now.  thanks.
-- 
____________________}John Flinchbaugh{______________________
| glynis@hjsoft.com         http://www.hjsoft.com/~glynis/ |
~~Powered by Linux: Reboots are for hardware upgrades only~~

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: Kernel 2.5.71 cannot unmount nfs

[Martin Diehl]

On Mon, 16 Jun 2003, Seifert Guido, gse wrote:

> 
> Sorry for the incomplete and unprofessional bugreport, I don't have more
> info.  I tried Kernel 2.5.71. Everything seems to work fine until I shut
> down or try to unmount a mountend nfs filesystem. For several minutes
> nothing happens, then I get something what looks like a backtrace from
> the nfs related code section. Unfortunately there is nothing in the log
> files afterwards.  G.

If the backtrace looks similar to this one:

Pid: 6820, comm:               umount
EIP: 0060:[<c01bbfb9>] CPU: 0
EIP is at atomic_dec_and_lock+0x99/0x9b
 EFLAGS: 00000246    Not tainted
EAX: 00000000 EBX: c387a48c ECX: ddf35348 EDX: ddf35348
ESI: c03173a0 EDI: c387a48c EBP: c387a4a8 DS: 007b ES: 007b
CR0: 8005003b CR2: 40018000 CR3: 03040000 CR4: 00000010
Call Trace:
 [<c0170d3c>] dput+0x1c/0x280
 [<c0170d22>] dput+0x2/0x280
 [<cc8d02ac>] rpc_depopulate+0x16c/0x190 [sunrpc]
 [<cc8d078e>] rpc_rmdir+0x5e/0x90 [sunrpc]
 [<cc8f6ce0>] nfs_sops+0x0/0x60 [nfs]
 [<cc8c02fb>] rpc_destroy_client+0x4b/0x70 [sunrpc]
 [<cc8e3767>] nfs_put_super+0x17/0x40 [nfs]
 [<c015f34a>] generic_shutdown_super+0xda/0x210
 [<cc8f6e00>] nfs_fs_type+0x0/0x20 [nfs]
 [<c016009f>] kill_anon_super+0xf/0x80
 [<cc8e5b51>] nfs_kill_super+0x11/0x20 [nfs]
 [<c015f030>] deactivate_super+0x80/0x110
 [<c01771f7>] __mntput+0x17/0x30
 [<c0166f48>] path_release+0x28/0x30
 [<c0177b4b>] sys_umount+0x7b/0x90
 [<c0177b6b>] sys_oldumount+0xb/0x10
 [<c01093b7>] syscall_call+0x7/0xb


... then you'll probably need the following patch:

<http://marc.theaimsgroup.com/?l=linux-kernel&m=105566442521995&w=2>

HTH
Martin