NetBSD Problem Report #31317

From juan@xtrarom.org  Thu Sep 15 05:54:52 2005
Return-Path: <juan@xtrarom.org>
Received: from Nocturno.xtrarom.org (unknown [84.77.255.188])
	by narn.netbsd.org (Postfix) with ESMTP id F1E0A63B878
	for <gnats-bugs@gnats.NetBSD.org>; Thu, 15 Sep 2005 05:54:51 +0000 (UTC)
Message-Id: <20050915055442.6A331C90A@Nocturno.xtrarom.org>
Date: Thu, 15 Sep 2005 07:54:42 +0200 (CEST)
From: juan@xtrarom.org
Reply-To: juan@xtrarom.org
To: gnats-bugs@netbsd.org
Subject: Cannot stop read/writes from/to smbfs shares
X-Send-Pr-Version: 3.95

>Number:         31317
>Category:       kern
>Synopsis:       Cannot stop read/writes from/to smbfs shares
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    kern-bug-people
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Sep 15 05:55:00 +0000 2005
>Closed-Date:    Sat Apr 04 16:11:54 +0000 2020
>Last-Modified:  Sat Apr 04 16:11:54 +0000 2020
>Originator:     Juan RP
>Release:        NetBSD 3.99.8
>Organization:
Possibly maybe
>Environment:
System: NetBSD Nocturno 3.99.8 NetBSD 3.99.8 (Nocturno) #126: Thu Sep 15 06:59:08 CEST 2005 juan@Nocturno:/home/juan/build/obj/sys/arch/i386/compile/Nocturno i386
Architecture: i386
Machine: i386
>Description:

	$ cp foo /smbfs_mounted_dir
	^C^C^C [the process cannot be stopped]

	$ cp /smbfs_mounted_dir/foo .
	^C^C^C [the process cannot be stopped]

That sucks if the files are large enough, because you'll have to wait
until the process finishes... ewww.

>How-To-Repeat:
>Fix:
	Yes please!

>Release-Note:

>Audit-Trail:

State-Changed-From-To: open->analyzed
State-Changed-By: pooka@narn.netbsd.org
State-Changed-When: Sun, 20 Jan 2008 16:48:44 +0200
State-Changed-Why:
this is part of larger problem that results because of cp(1) using mmap.
Use e.g. pax -rw to workaround


From: "Martin S. Weber" <phaeton@droog.sdf-eu.org>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: kern/31317
Date: Thu, 14 May 2009 15:54:24 -0400

 This is still a problem btw. (I'm just suffering from it. Process cp
 is stuck in smbwrq and unkillable by whatever means). This is a windows
 file server (dunno version, not my kingdom) and an r/w smbfs mount on
 a 5.0 rc3. Sadly I cannot gcore the cp process because it'll react
 on nothing. suppose I'll be also unable to umount that share ...
 Couldn't mount_smbfs state it's "experimental" or document known
 bugs in a BUGS section (given this PR is in "analyzed" for 16 months)?

 -M

From: "Martin S. Weber" <phaeton@droog.sdf-eu.org>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: kern/31317
Date: Thu, 14 May 2009 15:59:08 -0400

 On Thu, May 14, 2009 at 03:54:24PM -0400, Martin S. Weber wrote:
 > (...) suppose I'll be also unable to umount that share ...

 umount -f did unmount the share, at which point gcore could produce
 the core which was sitting in a call to write from copy_file (yes,
 after mmap)

 0x0804a753 <copy_file+1183>:    add    $0xc,%esp
 0x0804a756 <copy_file+1186>:    push   %ebx
 0x0804a757 <copy_file+1187>:    pushl  0xffffff14(%ebp)
 0x0804a75d <copy_file+1193>:    push   %edi
 0x0804a75e <copy_file+1194>:    call   0x8048cc0 <write@plt>

 waiting on smbwrq in write.

 -M

State-Changed-From-To: analyzed->closed
State-Changed-By: jdolecek@NetBSD.org
State-Changed-When: Sat, 04 Apr 2020 16:11:54 +0000
State-Changed-Why:
Obsolete, SMBFS/nsmb was removed from the tree. Thanks for report.


>Unformatted:

Home	PR Database Search