Hello,
I earlier this week upgraded from woody to sarge on a machine that does a
nightly backup to another machine via a samba share. Since then I have had
some issues with accessing that share with I believe are a result of the
upgrade. I upgraded the kernel at the same time to 2.4.27-1-686 #1 via
apt-get, which might(??) be the source of the problem.
I am looking for some advice as to how to proceed with further
troubleshooting. Did I need to compile 2.4.27 from source?
Here is how I mount the share in fstab. I should move the user/pass to a
credentials file, but one thing at a time (this works):
/etc/fstab:
//wardrobe/backup /backup smbfs
defaults,fmask=644,dmask=755,password=***,user=*** 0 0
Once the share is mounted I am able to list directories, create and modify
small files (touch, echo, etc). I don't get any errors and things look
like they are working fine.
However, when I try to copy a 200 MB file is when I get into trouble.
Error on the command line:
aslan:/backup/test# cp wardrobe.tar.gz.1 wardrobe.tar.gz_test123
cp: writing `wardrobe.tar.gz_test123': Input/output error
Errors from syslog:
Sep 10 07:53:06 aslan kernel: smb_get_length: Invalid NBT packet, code=39
Sep 10 07:53:06 aslan kernel: smb_request: result -5, setting invalid
Sep 10 07:53:06 aslan kernel: smb_writepage_sync: failed write,
wsize=4096, result=-5
Sep 10 07:53:09 aslan kernel: smb_retry: successful, new pid=28697,
generation=2
Sep 10 07:53:09 aslan kernel: smb_get_length: recv error = 5
Sep 10 07:53:09 aslan kernel: smb_request: result -5, setting invalid
Sep 10 07:53:32 aslan kernel: smb_retry: successful, new pid=28697,
generation=3
Cat /proc/filesystems
nodev rootfs
nodev bdev
nodev proc
nodev sockfs
nodev tmpfs
nodev shm
nodev pipefs
cramfs
nodev ramfs
nodev devfs
nodev devpts
ext3
nodev smbfs
I have done a pretty complete Google search and a search of the archives
and not found anything that has helped. Anyone out there have any
suggestions?
Thanks,
Sam
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
