From: Brian Henning <brian@strutmasters.com>
To: linux-kernel@vger.kernel.org
Subject: smbfs in 2.6.8 SMP kernel
Date: Mon, 17 Jan 2005 10:08:24 -0500 [thread overview]
Message-ID: <41EBD4E8.70905@strutmasters.com> (raw)
Hello,
I've just rebuilt my 2.6.8 kernel to enable SMP for my dual Xeons.
Everything seems to work great, except now smbfs is broken. If I boot
the non-SMP kernel, smbfs works perfectly; however, if I boot the SMP
kernel, most file creations/modifications in smbfs-mounted directories
hang for a long time and end with errors such as the following example:
/home/me/smb/mounted/dir: $ touch testfile
touch: setting times of `testfile': Input/output error
/home/me/smb/mounted/dir: $ rm testfile
/home/me/smb/mounted/dir: $ echo "Hello, Dave." | cat > testfile
/home/me/smb/mounted/dir: $ cat testfile
Hello, Dave.
/home/me/smb/mounted/dir: $ echo "I'm scared, Dave." | cat > testfile
bash: testfile: Input/output error
/home/me/smb/mounted/dir: $ cat testfile
/home/me/smb/mounted/dir: $ ls -l testfile
-rwxr--r-- 1 me root 0 2005-01-17 09:50 testfile
Now that I am aware of the problem, I know to avoid triggering it, but
imagine my dismay when, after attempting to save an edited file, I found
that its size had been reduced to zero!
I'm a kernel-building newbie, so I'm sure my problem is due to me
overlooking something. I tried building smbfs into the kernel, but that
made no difference. I'd be ever thankful if someone would point me in
the right direction, as I would certainly enjoy fully using my
processors while also being able to use smbfs.
Other potentially pertinent data:
Distro: Debian Sarge
Kernel Version: 2.6.8 custom
Arch: Xeon-HT/EMT (x2)
Thanks in advance!
Regards,
~Brian
next reply other threads:[~2005-01-17 15:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-17 15:08 Brian Henning [this message]
[not found] ` <Pine.LNX.4.61.0501171633140.20155@jjulnx.backbone.dif.dk>
2005-01-17 18:13 ` smbfs in 2.6.8 SMP kernel Brian Henning
2005-01-17 18:49 ` Jesper Juhl
2005-01-17 20:41 ` Alan Cox
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=41EBD4E8.70905@strutmasters.com \
--to=brian@strutmasters.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