Bug 103200
Summary: | Intermittent hangup (stall) on smbfs mount | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | ben mohilef <benm> |
Component: | mount | Assignee: | Bernhard Rosenkraenzer <bero> |
Status: | CLOSED DUPLICATE | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 9 | CC: | astrand |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-02-21 18:58:17 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
ben mohilef
2003-08-27 17:47:24 UTC
On my system, the mount command *always* stalls, if I use filesystem type "smbfs". However, if I use "-t smb", I have no problems at all. pam_mount uses "-t smbfs", which is quite a problem for me. So, which one is more correct, "smbfs" or "smb"? Update: It actually doesn't matter if you use "smb" or "smbfs"; the problem exists in both cases. I've narrowed the problem down to the smbmount program. The parent process gets stuck in: futex(0x4212f1c8, FUTEX_WAIT, -2, NULL... A child process later does kill on the parent process, but since the parent process is waiting for the futex, the process does not die. I have no idea *why*, though. The code looks OK. Inserting sleep(1) basically anywhere in the code solves the problem. My guess is that this is a NPTL/futex problem. Here's a work-around: 1) Create /sbin/mount.smbfs_no_nptl with this content: #!/bin/sh export LD_ASSUME_KERNEL=2.4.1 exec smbmount "$@" 2) Mount with "-t smbfs_no_nptl". *** This bug has been marked as a duplicate of 97743 *** Changed to 'CLOSED' state since 'RESOLVED' has been deprecated. |