From: "Jeff V. Merkey" <jmerkey@soleranetworks.com>
To: linux-kernel@vger.kernel.org
Subject: SMBFS Locking Issues with Advanced Server 2000/2003 [kernel 2.6.14]
Date: Tue, 14 Feb 2006 11:25:58 -0700 [thread overview]
Message-ID: <43F220B6.1080406@soleranetworks.com> (raw)
Attached errors. Intermittent errors occur when VNC viewer is installed
and running from a remote server which is also mapped
with smbfs. Problem can be recreated by executing perl commands
remotely against source code stored on a Windows 2000/2003
Advanced Server. There are no other applications locking the code. The
first error occurs when running Perl and Perl hangs remotely
and the process never returns. After hitting control C to break out of
Perl, SMBFS leaves the files locked remotely and they cannot be deleted
until the volume is unmounted. Unmounting and remounting clears the
problem, but this is dirty and should recover more gracefully.
Mount also reports erroneously when this occurs that the volume is
mounted twice, which it is not the case -- the volume was only mounted
once.
Perl command:
perl -pi -e "s/interface/interfaceIndex/g" *[ch]
erroneous mount info:
/dev/sda3 on / type ext3 (rw)
none on /proc type proc (rw)
none on /sys type sysfs (rw)
none on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/sda1 on /boot type ext3 (rw)
none on /dev/shm type tmpfs (rw)
/dev/sda4 on /pfs type dsfs (rw)
//192.168.2.27/dsfs on /win type smbfs (0)
//192.168.2.27/dsfs on /win type smbfs (0)
Error returned after perl croaks:
[root@predator dsarchive]#
[root@predator dsarchive]# rm -rf 01-14-06-final/
rm: cannot remove `01-14-06-final//utils/dscapture.c': Text file busy
rm: cannot remove `01-14-06-final//utils/dsinput.c': Text file busy
[root@predator dsarchive]#
[root@predator dsarchive]#
[root@predator dsarchive]#
Jeff
reply other threads:[~2006-02-14 17:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=43F220B6.1080406@soleranetworks.com \
--to=jmerkey@soleranetworks.com \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome