Bug 154491 - [smbfs] smb_co_lock: recursive lock for object 1
Summary: [smbfs] smb_co_lock: recursive lock for object 1
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 8.1-PRERELEASE
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-03 16:10 UTC by marek.bedy
Modified: 2017-12-31 22:32 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description marek.bedy 2011-02-03 16:10:14 UTC 
I have problem with mounting cifs network share (it is windows cifs share):

file /etc/nsmb.conf: 

[FILESERVER]
addr=172.16.2.37

[FILESERVER:SNIPS]
password=xxxxxx
cowner=mbe


/usr/sbin/mount_smbfs -I 172.16.2.37 -W DOMAIN.SK //snips@fileserver/snips-tftpd /tftpd/fs

mount_smbfs: unable to open connection: syserr = No such file or directory

in dmesg is log: smb_co_lock: recursive lock for object 1
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2011-02-04 19:33:13 UTC 
Responsible Changed
From-To: freebsd-bugs->freebsd-fs

reclassify and assign.
Comment 2 jo 2011-11-24 15:08:38 UTC 
Same thing on

FreeBSD XXX 9.0-PRERELEASE FreeBSD 9.0-PRERELEASE #0 r227793: Mon Nov 21
20:19:04 GMT 2011     root@XXX:/usr/obj/usr/src/sys/GENERIC  amd64
Comment 3 jo 2011-11-24 17:43:54 UTC 
Trying to unload smbfs.ko after these messages leaves the machine in some
sort of zombie state. Ping to it works, but everything else is dead, no io,
no keyboard input on console, numlock is dead.

This is on 9-stable, r227793, x64.
Comment 4 Eitan Adler freebsd_committer freebsd_triage 2017-12-31 07:59:42 UTC 
For bugs matching the following criteria:

Status: In Progress Changed: (is less than) 2014-06-01

Reset to default assignee and clear in-progress tags.

Mail being skipped