On (20/12/04 14:59), Gonzalo Sainz-Trápaga wrote: > Hi, I posted this message on debian-testing and someone recommmended > posting here instead. The original message follows. Since samba 2.2 > went EOL lately, I upgraded Samba on the server to samba 3.0 from > backports.org after writing this message, with the same results. Any > pointers would be greatly appreciated. > > -------------------------------------------------------------------- > > Hi, > > I don't really know if this is the right list to post this problem since > it doesn't actually concern the testing distribution. Still, my problem > came up after a sid upgrade on my setup, so I guess it involves "testing > Debian" :) > > In my setup I have a home server running Woody (pastrami) and a client > (ciabatta - my desktop machine) running sid. I used to mount my WWW root > on the server as ~/www-remote on the desktop machine using "mount -t > smbfs" (via fstab), in order to allow for easy updates on the website. > > Some time ago, i started getting this message when trying to mount the > SMB share on the sid machine: > > [EMAIL PROTECTED]:~# mount /home/gomo/www-remote/ > mount: wrong fs type, bad option, bad superblock on //pastrami/gomoxweb, > missing codepage, or too many mounted file systems > > With this on dmesg: > > smbfs: mount_data version 1029990773 is not supported > > The entry on fstab looks like this: > //pastrami/gomoxweb /home/gomo/www-remote smbfs > defaults,uid=1000,username=gomo,password=XXXXXX > > I haven't touched neither fstab on the client or smb.conf on the server, > so I guess the problem comes from some incompatibility that appeared a > bit after the samba 3.0 upload into sid (the initial upgrade to 3.0 > didn't create any issues). > > The installed versions are: > > [EMAIL PROTECTED]:~# dpkg -l *smb* *samba* | grep ii > ii libsmbclient 3.0.9-1 > ii smbclient 3.0.8-2 > ii samba 3.0.8-2 > ii samba-common 3.0.8-2 > > pastrami:/home/gomo# dpkg -l *smb* *samba* | grep ii > ii smbclient 2.2.3a-14.1 > ii samba 2.2.3a-14.1 > ii samba-common 2.2.3a-14.1 > > The server runs custom-built vanilla Linux 2.4.27 and the client has > 2.6.9. > > Any help or suggestions would be greatly appreciated. > Thanks in advance, Hi Gonzalo
I'm not sure I can be much help but have had similar problems. Briefly, I am running samba 2.2.3a-14.1 on woody servers with windows and debian clients. Until recently I unsed nfs on my sid workstation to access shares on the servers. However, separately I've installed Xandros, Mepis, ubuntu and sarge on a test PC and found that smb4k is automatically installed on the first three OSs and seemed to work pretty well. In the pursuit of simplicity I thought I'd try smb4k on my sid workstation but after a couple of days of trying to get it to play nicely (sometimes it worked, sometimes it didn't) I decided to go with smbclient and mount at boot time using fstab. Again it seemed to work for a while and then I would find I could write to files. Owing to work pressures I've reverted to nfs for my workstation but would like to get all clients talking smb in due course. I'm happy to try some stuff if anyone can offer suggestions. One suggestion I would make is that you use credentials in your fstab entry rather than putting your plain text password in fstab which is world readable. I can't remember the exact wording but it was something like --credentials=pw_file_name; fstab then looks to that hidden file (rw by user only) for the password. pw_file_name contains just: username:passwd Regards Clive -- www.clivemenzies.co.uk ... ...strategies for business -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
