Skip to contentSkip to conversation

problems with smbfs on 2.4.18 kernel (ppc)

DISCUSSION Bastien Nocera 4 participants 8 messages Mar 1, 2002 – May 3, 2002

lore
Share & tools
lore
#0 lore raw

Hi,

I'm having some problems with smbfs on ppc.
The attached file contains all the details. Am I doing something wrong ?

Hope you can help.

Cheers

Signature · 2 lines
/Bastien Nocera
http://hadess.net

# System details

dozo:~# uname -a
Linux dozo 2.4.18-ben0-xfs-o1-preempt #2 Wed Feb 27 07:50:49 GMT 2002 ppc unknown
dozo:~# smbclient | grep -i version
Version 2.2.3a-1 for Debian
dozo:~# smbmount | grep -i version
Version 2.2.3a-1 for Debian
dozo:~# export USER=hadess

# There is a Backup1 share on kara

dozo:~# smbclient -L kara 
added interface ip=192.168.1.2 bcast=192.168.1.255 nmask=255.255.255.0
Password: 
Domain=[IDORU] OS=[Unix] Server=[Samba 2.2.2]
	Sharename      Type      Comment
	---------      ----      -------
	Backup1        Disk      
	Backup2        Disk      
	IPC$           IPC       IPC Service (Samba 2.2.2 running on OSX)
	ADMIN$         Disk      IPC Service (Samba 2.2.2 running on OSX)
	hadess         Disk      Home directory of hadess
	Server               Comment
	---------            -------
	KARA                 Samba 2.2.2 running on OSX
	Workgroup            Master
	---------            -------
	IDORU                KARA

# I have a similar line in my fstab, different password obviously

dozo:~# grep backup /etc/fstab 
//kara/Backup1	/mnt/backup/	smbfs	user,username=hadess,password=XXX 0 0

# Mounting works

dozo:~# mount /mnt/backup/
dozo:~# mount
/dev/hda10 on / type xfs (rw,noatime)
proc on /proc type proc (rw)
none on /proc/bus/usb type usbdevfs (rw)
/dev/hda12 on /home type xfs (rw,noatime)
/dev/hda14 on /opt type xfs (rw,noatime)
/dev/cdrom on /cdrom type iso9660 (ro,noexec,nosuid,nodev,user=hadess)
//kara/Backup1 on /mnt/backup type smbfs (0)

# The mount point kind of disappeared...

dozo:~# ls /mnt/backup
ls: /mnt/backup: No such file or directory

# Well, it seemed to be there though

dozo:~# umount /mnt/backup 
dozo:~# mount
/dev/hda10 on / type xfs (rw,noatime)
proc on /proc type proc (rw)
none on /proc/bus/usb type usbdevfs (rw)
/dev/hda12 on /home type xfs (rw,noatime)
/dev/hda14 on /opt type xfs (rw,noatime)
/dev/cdrom on /cdrom type iso9660 (ro,noexec,nosuid,nodev,user=hadess)
#1 lore raw
Quoted 4 lines · Bastien Nocera

Hi,

I'm having some problems with smbfs on ppc.
The attached file contains all the details. Am I doing something wrong ?

Has smbfs worked for you with previous versions? A patch was added late to 2.4.18 and it has caused a lot of crashes for people. I don't think it is related, but since you mention 2.4.18 ...

mount only prints the contents of /etc/mtab. What does /proc/mounts say? Do you have any kernel messages? (dmesg).

The entry in mtab is written by smbmnt and one way to get this would be if the mount fails, but after smbmnt has written and then for some reason it fails to cleanup.

/Urban

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

#3 lore raw
In reply to Bastien Nocera
Quoted 6 lines
Quoted 4 lines

Has smbfs worked for you with previous versions? A patch was added late to 2.4.18 and it has caused a lot of crashes for people. I don't think it is related, but since you mention 2.4.18 ...

I never tried the previous versions of it.

Yes, smbfs used to work with recent version.

Ben.

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

#2 lore raw
In reply to Urban Widmark
Quoted 9 lines · Urban Widmark
Quoted 2 lines · Bastien Nocera

I'm having some problems with smbfs on ppc.
The attached file contains all the details. Am I doing something wrong?

Has smbfs worked for you with previous versions? A patch was added late to 2.4.18 and it has caused a lot of crashes for people. I don't think it is related, but since you mention 2.4.18 ...

I never tried the previous versions of it.

Quoted 2 lines

mount only prints the contents of /etc/mtab. What does /proc/mounts say? Do you have any kernel messages? (dmesg).

$ cat /proc/mounts  | grep smb
//kara/Backup1 /mnt/backup smbfs rw,file_mode=0755,dir_mode=0755 0 0

It seems to be mounted. dmesg says:
smbfs: Unrecognized mount option noexec

Quoted 3 lines

The entry in mtab is written by smbmnt and one way to get this would be if the mount fails, but after smbmnt has written and then for some reason it fails to cleanup.

smb definetaly works, as I can browse it with the smb gnome-vfs module, as well as smbclient. I'm failing to see why the /mnt/backup directory just "disappears from there".

$ file /mnt/backup
/mnt/backup: can't stat `/mnt/backup' (No such file or directory).

This is weird. Do you have any more things I could try ?

Cheers

--
/Bastien Nocera
http://hadess.net

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

#5 lore raw
Quoted 7 lines · Bastien Nocera
Quoted 4 lines · Urban Widmark

Has smbfs worked for you with previous versions? A patch was added late to 2.4.18 and it has caused a lot of crashes for people. I don't think it is related, but since you mention 2.4.18 ...

I never tried the previous versions of it.

Maybe you should.

Quoted 5 lines
$ cat /proc/mounts  | grep smb
//kara/Backup1 /mnt/backup smbfs rw,file_mode=0755,dir_mode=0755 0 0

It seems to be mounted. dmesg says:
smbfs: Unrecognized mount option noexec

Does it make any difference if you mount it like:
mount -t smbfs -o username=...,password=... //kara/Backup1 /mnt/backup

(should stop the "Unrecognized mount option" error)

Quoted 7 lines
Quoted 3 lines

The entry in mtab is written by smbmnt and one way to get this would be if the mount fails, but after smbmnt has written and then for some reason it fails to cleanup.

smb definetaly works, as I can browse it with the smb gnome-vfs module, as well as smbclient. I'm failing to see why the /mnt/backup directory just "disappears from there".

It can disappear if the request for attributes on that directory fails. Try getting a network trace with ethereal and see what the response to the QUERY_PATH_INFORMATION request is.

/Urban

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

#4 lore raw
In reply to [email protected]
Quoted 1 line · On Mon, Mar 04, 2002 at 10:03:41PM +0100, [email protected] wrote:

Yes, smbfs used to work with recent version.

I've mounted SMB filesystems exported via Samba (on an x86 Linux box) since upgrading to 2.4.18 with this iBook, so I can say that it Works for Me(TM).

--

Derrik Pates      |   Sysadmin, Douglas School   |    #linuxOS on EFnet
[email protected] |     District (dsdk12.net)    |    #linuxOS on OPN

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

#6 lore raw
In reply to Urban Widmark

Hello,

I'm quite ashamed of the time it took me to gather the info, been busy...

Quoted 16 lines · Urban Widmark
Quoted 7 lines · Bastien Nocera
Quoted 4 lines · Urban Widmark

Has smbfs worked for you with previous versions? A patch was added late to 2.4.18 and it has caused a lot of crashes for people. I don't think it is related, but since you mention 2.4.18 ...

I never tried the previous versions of it.

Maybe you should.

Quoted 3 lines
$ cat /proc/mounts  | grep smb
//kara/Backup1 /mnt/backup smbfs rw,file_mode=0755,dir_mode=0755 0 0
Quoted 7 lines
Quoted 2 lines

It seems to be mounted. dmesg says:
smbfs: Unrecognized mount option noexec

Does it make any difference if you mount it like:
mount -t smbfs -o username=...,password=... //kara/Backup1 /mnt/backup

(should stop the "Unrecognized mount option" error)

It did, the error doesn't appear anymore

Quoted 11 lines
Quoted 7 lines
Quoted 3 lines

The entry in mtab is written by smbmnt and one way to get this would be if the mount fails, but after smbmnt has written and then for some reason it fails to cleanup.

smb definetaly works, as I can browse it with the smb gnome-vfs module, as well as smbclient. I'm failing to see why the /mnt/backup directory just "disappears from there".

It can disappear if the request for attributes on that directory fails. Try getting a network trace with ethereal and see what the response to the QUERY_PATH_INFORMATION request is.

I'm seeing this in ethereal:
from laptop to SMB server: Transaction2 Request QUERY_PATH_INFORMATION,
Path: \
from SMB server back to laptop: Transaction2 Response QUERY_PATH_INFORMATION, Error: Directory not found

However, smbclient seems to find it:

smbclient //kara/backup1 -U hadess
added interface ip=192.168.1.2 bcast=192.168.1.255 nmask=255.255.255.0 Password:
Domain=[IDORU] OS=[Unix] Server=[Samba 2.2.2]
smb: \> ls
mp3s D 0 Wed Apr 3 06:38:08
2002

I'm running out of things to test...

Cheers

--
/Bastien Nocera
http://hadess.net

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

#7 lore raw

Dammit,

I feel stupid now. The SAMBA version I grabbed off some MacOS X site came with a borked smb.conf. There was a rule to veto some files only used by MacOS X (resource forks). Here was the rule:

veto files = .*/Temporary Items/Desktop */TheFindByContentFolder/TheVolumeSettingsFolder/Network */

And the last bit actually vetoed all the directories, beginning with the one at the bottom of the share. I still don't understand why smbclient and the smb gnome-vfs method actually worked just fine with this share.

Urban, is this actually a bug ? I'll take this off linuxppc-dev now.

Cheers

On Wed, 2002-05-01 at 16:49, Bastien Nocera wrote:
<snip>

Quoted 8 lines

I'm seeing this in ethereal:
from laptop to SMB server: Transaction2 Request QUERY_PATH_INFORMATION,
Path: \
from SMB server back to laptop: Transaction2 Response QUERY_PATH_INFORMATION, Error: Directory not found

However, smbclient seems to find it:

Quoted 7 lines

smbclient //kara/backup1 -U hadess
added interface ip=192.168.1.2 bcast=192.168.1.255 nmask=255.255.255.0 Password:
Domain=[IDORU] OS=[Unix] Server=[Samba 2.2.2]
smb: \> ls
mp3s D 0 Wed Apr 3 06:38:08
2002

--
/Bastien Nocera
http://hadess.net

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/