Re: [Samba] Files over 4GB not listing properly. Cannot get CIFSworking.
Am Dienstag, 6. Mai 2008 schrieb Matt Boyle: Put this in the wrong thread, sorry! UPDATE: I've realized that this seems to be an issue with the compiler flags used to build samba. I've realized that i need to define _LARGEFILE_SOURCE, _LARGEFILE64_SOURCE, and _FILE_OFFSET_BITS=64. I've done this, but still have no luck reading files larger than 4GB. Anyone have suggestions? Thanks, Matt Hi guys, I'm attempting to move large files (4GB) from a PowerPC-based embedded system running a 2.4 kernel architecture to an PC running a 2.6 kernel. I've got samba compiled, installed, and running on the embedded box. I also have the directories from the PPC system mounted and accessible from the PC. I have two problems: larger file sizes do not list correctly, and large files transferred from the embedded box to the PC are not complete; IE they're dropping data along the way. I'm familiar with the 2GB file size limit on samba, and have mounted the PC side using the lfs flag. Problem 1: Incorrect listing Here's a list of the directory from the embedded box: -r--r--r-- 1 root root 52646396 Jan 5 06:46 file1.ch10 -r--r--r-- 1 root root 60755936 Jan 5 06:46 file2.ch10 -r--r--r-- 1 root root 47606684 Jan 5 06:46 file3.ch10 -r--r--r-- 1 root root 4920604376 Jan 5 05:51 file4.ch10 Here's that same listing, but of the samba mount of that directory on the PC: -r-xr-xr-x 1 root root 52646396 Jan 5 2007 file1.ch10 -r-xr-xr-x 1 root root 60755936 Jan 5 2007 file2.ch10 -r-xr-xr-x 1 root root 47606684 Jan 5 2007 file3.ch10 -r-xr-xr-x 1 root root 625637080 Jan 5 2007 file4.ch10 As you can see, files 1-3 list fine, but file4 is showing way short. I'm guessing this might be some sort of overflow condition, any ideas? Problem 2: Loss of data during transfer of large files. When I try to transfer file4, i only get 41 or so of the total file size. This is the more pressing issue. Also, I cannot mount the samba share using CIFS. I use the line mount -t smbfs //server/share/ path/to/local/ -o user=u,pass=p,lfs to mount with SMBFS, and it works correctly, just doesn't display the large files. However, when using the following: mount -t smbfs //server/share/ path/to/local/ -o user=u,pass=p,lfs I guess, that's a typo above, so smbfs should read cifs ? I get Mount error 5= Input/output error You can do the following on your local PC running a 2.6 kernel to track this down a bit more when using the cifs kernel module: 1. 'modinfo cifs' (to query some cifs version and kernel info) 2. 'modprobe cifs' (to make sure the module is loaded) 3. 'echo 3 /proc/fs/cifs/cifsFYI' (to make cifs more chatty) 4. 'logger HERE-ALL-NEW-STUFF-NOW-=' 5. In a separate console, use 'tail -f /var/log/messages' to fetch cifs' msgs 6. use 'mount.cifs //server/share /path/to/local --verbose -o user=u,pass=p' (the option lfs is _not_ needed here, not a valid cifs option) (Usually) there should be cifs debug messages in the 4.) tail -f ... console. All new entries start at the string HERE-ALL-NEW-STUFF-NOW-= Please send all output from the above steps 1.) 2.) 5.) and 6.) Cheers, Günter Note that some of the cmds above need root privs. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] XP share not listed in Linneighborhood
Am Mittwoch, 30. April 2008 schrieb Larry Alkoff: I am unable to find my Windows XP share (winpro) in Linneighborhood which runs on my desktop Kubuntu Linux box. When I try to mount that Windows XP share I get the error message: 2139: session request to WINPRO failed (Not listening on called name) 2139: session request to *SMBSERVER failed (Not listening on called name) SMB connection failed smbmt: Error: winpro _not_ mounted. The command line I'm using to mount Winpro is: smbmount //winpro/lba /mnt/winpro -o guest,uid=lba This line _used_ to work before I had a malfuntion on the winpro box and had to Repair XP. Repair is similiar to a fresh install except many (but not all) settings are kept. Both winpro and the Kubuntu box are on the same workgroup and subnet with fixed IP. Why is the winpro machine not listening on called name ? I've been working on this a couple of days and suspect something in the Windows XP configuration but haven't made any headway. Larry Are you sure, that you named that winxp box winpro? Inside a windows cmdline window, use nbtstat -n to view the registered netbios names. Also have a look whether the workgroup matches. Btw - using 'smbclient -L winpro -Uusername%password' is an easier way to check for availability of that remote box. Also 'smbtree' can help to diagnose that problem. Cheers, Günter -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] XP share not listed in Linneighborhood
Am Mittwoch, 30. April 2008 schrieb Larry Alkoff: Guenter Kukkukk wrote: Am Mittwoch, 30. April 2008 schrieb Larry Alkoff: I am unable to find my Windows XP share (winpro) in Linneighborhood which runs on my desktop Kubuntu Linux box. When I try to mount that Windows XP share I get the error message: 2139: session request to WINPRO failed (Not listening on called name) 2139: session request to *SMBSERVER failed (Not listening on called name) SMB connection failed smbmt: Error: winpro _not_ mounted. The command line I'm using to mount Winpro is: smbmount //winpro/lba /mnt/winpro -o guest,uid=lba This line _used_ to work before I had a malfuntion on the winpro box and had to Repair XP. Repair is similiar to a fresh install except many (but not all) settings are kept. Both winpro and the Kubuntu box are on the same workgroup and subnet with fixed IP. Why is the winpro machine not listening on called name ? I've been working on this a couple of days and suspect something in the Windows XP configuration but haven't made any headway. Larry Are you sure, that you named that winxp box winpro? Inside a windows cmdline window, use nbtstat -n to view the registered netbios names. Also have a look whether the workgroup matches. Btw - using 'smbclient -L winpro -Uusername%password' is an easier way to check for availability of that remote box. Also 'smbtree' can help to diagnose that problem. Cheers, Günter Thanks very much for your reply Günter. Clicking on Control Panel System Properties shows 'Full computer name' winpro and Workgroup LANET as expected. nbstat -n from winpro command prompt gives an error message Failed to access NBT driver smbtree gives a full screen of shares from other computers but nothing from winpro. The shares list other windows 98 computers. smbclient -L winpro -Uusername%password gives a '' prompt that I can't do anything with except to re-enter my password. I then get session request to WINPRO failed (Not listening on called name) session request to *SMBSERVER failed (Not listening on called name) smbclient -L winpro -Uusername session request to WINPRO failed (Not listening on called name) session request to *SMBSERVER failed (Not listening on called name) Some notes: My username and password is the same on both machines. The WXP computer has Service Pack 1 and 2. I can connect to shares on other machines from winpro. Larry Have you enabled NetBIOS over tcp/ip in the tcp/ip settings of your network interface? I think, it's placed in the WINS tab dialog page. Cheers, Günter -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] XP share not listed in Linneighborhood
Am Mittwoch, 30. April 2008 schrieb Larry Alkoff: Guenter Kukkukk wrote: Am Mittwoch, 30. April 2008 schrieb Larry Alkoff: Guenter Kukkukk wrote: Am Mittwoch, 30. April 2008 schrieb Larry Alkoff: I am unable to find my Windows XP share (winpro) in Linneighborhood which runs on my desktop Kubuntu Linux box. When I try to mount that Windows XP share I get the error message: 2139: session request to WINPRO failed (Not listening on called name) 2139: session request to *SMBSERVER failed (Not listening on called name) SMB connection failed smbmt: Error: winpro _not_ mounted. The command line I'm using to mount Winpro is: smbmount //winpro/lba /mnt/winpro -o guest,uid=lba This line _used_ to work before I had a malfuntion on the winpro box and had to Repair XP. Repair is similiar to a fresh install except many (but not all) settings are kept. Both winpro and the Kubuntu box are on the same workgroup and subnet with fixed IP. Why is the winpro machine not listening on called name ? I've been working on this a couple of days and suspect something in the Windows XP configuration but haven't made any headway. Larry Are you sure, that you named that winxp box winpro? Inside a windows cmdline window, use nbtstat -n to view the registered netbios names. Also have a look whether the workgroup matches. Btw - using 'smbclient -L winpro -Uusername%password' is an easier way to check for availability of that remote box. Also 'smbtree' can help to diagnose that problem. Cheers, Günter Thanks very much for your reply Günter. Clicking on Control Panel System Properties shows 'Full computer name' winpro and Workgroup LANET as expected. nbstat -n from winpro command prompt gives an error message Failed to access NBT driver smbtree gives a full screen of shares from other computers but nothing from winpro. The shares list other windows 98 computers. smbclient -L winpro -Uusername%password gives a '' prompt that I can't do anything with except to re-enter my password. I then get session request to WINPRO failed (Not listening on called name) session request to *SMBSERVER failed (Not listening on called name) smbclient -L winpro -Uusername session request to WINPRO failed (Not listening on called name) session request to *SMBSERVER failed (Not listening on called name) Some notes: My username and password is the same on both machines. The WXP computer has Service Pack 1 and 2. I can connect to shares on other machines from winpro. Larry Have you enabled NetBIOS over tcp/ip in the tcp/ip settings of your network interface? I think, it's placed in the WINS tab dialog page. Cheers, Günter Just looked again Günter. Yes, NetBIOS over tcp/ip is checked. Also iptables on the Linux machine is wide open (all policies ACCEPT). The entire internal LAN is behind a router/firewall of course. Larry Then i don't understand the result from one of your recent posts: nbstat -n from winpro command prompt gives an error message Failed to access NBT driver Btw - it should read nbtstat -n (sorry, my fault) Cheers, Günter -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] XP share not listed in Linneighborhood
Am Mittwoch, 30. April 2008 schrieb Larry Alkoff: Guenter Kukkukk wrote: Am Mittwoch, 30. April 2008 schrieb Larry Alkoff: Guenter Kukkukk wrote: Am Mittwoch, 30. April 2008 schrieb Larry Alkoff: Guenter Kukkukk wrote: Am Mittwoch, 30. April 2008 schrieb Larry Alkoff: I am unable to find my Windows XP share (winpro) in Linneighborhood which runs on my desktop Kubuntu Linux box. When I try to mount that Windows XP share I get the error message: 2139: session request to WINPRO failed (Not listening on called name) 2139: session request to *SMBSERVER failed (Not listening on called name) SMB connection failed smbmt: Error: winpro _not_ mounted. The command line I'm using to mount Winpro is: smbmount //winpro/lba /mnt/winpro -o guest,uid=lba This line _used_ to work before I had a malfuntion on the winpro box and had to Repair XP. Repair is similiar to a fresh install except many (but not all) settings are kept. Both winpro and the Kubuntu box are on the same workgroup and subnet with fixed IP. Why is the winpro machine not listening on called name ? I've been working on this a couple of days and suspect something in the Windows XP configuration but haven't made any headway. Larry Are you sure, that you named that winxp box winpro? Inside a windows cmdline window, use nbtstat -n to view the registered netbios names. Also have a look whether the workgroup matches. Btw - using 'smbclient -L winpro -Uusername%password' is an easier way to check for availability of that remote box. Also 'smbtree' can help to diagnose that problem. Cheers, Günter Thanks very much for your reply Günter. Clicking on Control Panel System Properties shows 'Full computer name' winpro and Workgroup LANET as expected. nbstat -n from winpro command prompt gives an error message Failed to access NBT driver smbtree gives a full screen of shares from other computers but nothing from winpro. The shares list other windows 98 computers. smbclient -L winpro -Uusername%password gives a '' prompt that I can't do anything with except to re-enter my password. I then get session request to WINPRO failed (Not listening on called name) session request to *SMBSERVER failed (Not listening on called name) smbclient -L winpro -Uusername session request to WINPRO failed (Not listening on called name) session request to *SMBSERVER failed (Not listening on called name) Some notes: My username and password is the same on both machines. The WXP computer has Service Pack 1 and 2. I can connect to shares on other machines from winpro. Larry Have you enabled NetBIOS over tcp/ip in the tcp/ip settings of your network interface? I think, it's placed in the WINS tab dialog page. Cheers, Günter Just looked again Günter. Yes, NetBIOS over tcp/ip is checked. Also iptables on the Linux machine is wide open (all policies ACCEPT). The entire internal LAN is behind a router/firewall of course. Larry Then i don't understand the result from one of your recent posts: nbstat -n from winpro command prompt gives an error message Failed to access NBT driver Btw - it should read nbtstat -n (sorry, my fault) Cheers, Günter Sorry Günter but I made a mistake with nbtstat -n. On winpro there was an old copy of nbtstat in a directory from Windows 98 but on my path. I renamed _that_ nbtstat and then which nbtstat found the real nbtstat in \windows\system32. -- The result of nbtstat -n Local Area Connection 3: Node IpAddress: [10.22.44.11] Scope Id: [] NetBIOS Local Name Table Name Type Status - WINPRO 00 UNIQUE Registered LANET 00 GROUP Registered LANET 1E GROUP Registered Local Area Connection 4: Node IpAddress: [0.0.0.0] Scope Id: [] No names in cache --- What does this result show for my problem? Larry Have a look here how netbios names are registered and what kind of resource type is used - the 00 or 1E in your output. http://technet2.microsoft.com/windowsserver/en/library/691e1e3f-0ac1-45a2-b19a-cf7ef25ade4b1033.mspx?mfr=true Your windows box has not registered the name WINPRO20, so it seems to me, that the peer/server service is not running ... Btw, 'nmblookup -S winpro' (done on your samba box) should also list the registered names. Inside a windows cmdline console, does 'net share' list your exports? 'net statistics server' should also list some info. Cheers, Günter -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] XP share not listed in Linneighborhood
Am Mittwoch, 30. April 2008 schrieb Larry Alkoff: Guenter Kukkukk wrote: Am Mittwoch, 30. April 2008 schrieb Larry Alkoff: Guenter Kukkukk wrote: Am Mittwoch, 30. April 2008 schrieb Larry Alkoff: Guenter Kukkukk wrote: Am Mittwoch, 30. April 2008 schrieb Larry Alkoff: Guenter Kukkukk wrote: Am Mittwoch, 30. April 2008 schrieb Larry Alkoff: I am unable to find my Windows XP share (winpro) in Linneighborhood which runs on my desktop Kubuntu Linux box. When I try to mount that Windows XP share I get the error message: 2139: session request to WINPRO failed (Not listening on called name) 2139: session request to *SMBSERVER failed (Not listening on called name) SMB connection failed smbmt: Error: winpro _not_ mounted. The command line I'm using to mount Winpro is: smbmount //winpro/lba /mnt/winpro -o guest,uid=lba This line _used_ to work before I had a malfuntion on the winpro box and had to Repair XP. Repair is similiar to a fresh install except many (but not all) settings are kept. Both winpro and the Kubuntu box are on the same workgroup and subnet with fixed IP. Why is the winpro machine not listening on called name ? I've been working on this a couple of days and suspect something in the Windows XP configuration but haven't made any headway. Larry Are you sure, that you named that winxp box winpro? Inside a windows cmdline window, use nbtstat -n to view the registered netbios names. Also have a look whether the workgroup matches. Btw - using 'smbclient -L winpro -Uusername%password' is an easier way to check for availability of that remote box. Also 'smbtree' can help to diagnose that problem. Cheers, Günter Thanks very much for your reply Günter. Clicking on Control Panel System Properties shows 'Full computer name' winpro and Workgroup LANET as expected. nbstat -n from winpro command prompt gives an error message Failed to access NBT driver smbtree gives a full screen of shares from other computers but nothing from winpro. The shares list other windows 98 computers. smbclient -L winpro -Uusername%password gives a '' prompt that I can't do anything with except to re-enter my password. I then get session request to WINPRO failed (Not listening on called name) session request to *SMBSERVER failed (Not listening on called name) smbclient -L winpro -Uusername session request to WINPRO failed (Not listening on called name) session request to *SMBSERVER failed (Not listening on called name) Some notes: My username and password is the same on both machines. The WXP computer has Service Pack 1 and 2. I can connect to shares on other machines from winpro. Larry Have you enabled NetBIOS over tcp/ip in the tcp/ip settings of your network interface? I think, it's placed in the WINS tab dialog page. Cheers, Günter Just looked again Günter. Yes, NetBIOS over tcp/ip is checked. Also iptables on the Linux machine is wide open (all policies ACCEPT). The entire internal LAN is behind a router/firewall of course. Larry Then i don't understand the result from one of your recent posts: nbstat -n from winpro command prompt gives an error message Failed to access NBT driver Btw - it should read nbtstat -n (sorry, my fault) Cheers, Günter Sorry Günter but I made a mistake with nbtstat -n. On winpro there was an old copy of nbtstat in a directory from Windows 98 but on my path. I renamed _that_ nbtstat and then which nbtstat found the real nbtstat in \windows\system32. -- The result of nbtstat -n Local Area Connection 3: Node IpAddress: [10.22.44.11] Scope Id: [] NetBIOS Local Name Table Name Type Status - WINPRO 00 UNIQUE Registered LANET 00 GROUP Registered LANET 1E GROUP Registered Local Area Connection 4: Node IpAddress: [0.0.0.0] Scope Id: [] No names in cache --- What does this result show for my problem? Larry Have a look here how netbios names are registered and what kind of resource type is used - the 00 or 1E in your output. http://technet2.microsoft.com/windowsserver/en/library/691e1e3f-0ac1-45a2-b19a-cf7ef25ade4b1033.mspx?mfr=true Your windows box has not registered the name WINPRO20, so it seems to me, that the peer/server service is not running ... Btw, 'nmblookup -S winpro' (done on your samba box) should also list the registered names. Inside a windows cmdline console, does 'net share' list your exports? 'net statistics server' should also list some info. Cheers, Günter Hello Günter I'm not sure what to make
Re: [Samba] File locks?
Am Donnerstag, 10. April 2008 schrieb Jim Young: Hi Jim, Thanks for the info. I am using the smbfs debian package, but mount tells me that type is cifs //nsh/jyoung on /mnt/uni type cifs (rw,mand) I have updated my fstab: //nsh/jyoung/mnt/unicifs credentials=/myfolder/credentials,gid=jyoung,uid=jyoung,auto,rw 0 0 and remounted, same problem. Thanks, Jim On your local system. what's the outcome of 'modinfo cifs' ? Btw - recent debian/ubuntu packages ship versions of the smb/cifs userland helpers smbmount and smbumount, which are no longer mounting smbfs when specified. Instead they mount cifs vfs behind the scenes. Both are (usually) also called indirectly by the mount/umount programs. Technically spoken, 'mount -t smbfs ...' is (ususally) calling /sbin/mount.smbfs which formerly mounted smbfs - but now cifs vfs instead. Cheers, Günter On 10/04/2008, Jeremy Allison [EMAIL PROTECTED] wrote: On Thu, Apr 10, 2008 at 10:12:54AM -0600, Jim Young wrote: Hello, Recently, the following problem started happening with a particular samba server: If i have a file open for reading (say, a pdf in xpdf) and then try to write to it (say, through recompiling a latex document) it complains that it cannot open the file for writing. this seems like a file lock issue but I am unsure where it is happening. My previous usage should be perfectly safe since xpdf should only open for reading. This problem does not happen locally or when I connect to a different samba server (a windows machine). I can also ssh into the remote server, port xpdf , and my local process can write to the file. It is the samba connection that is making the lock. I am running Debian Unstable, using smbclient/smbfs 3.0.28a-1 to connect to a samba server (unix backend) on my university network. Server: Samba3.0.10-1.4E I mount the smb share in my fstab as follows: //myserver/jyoung/mnt/unismbfs credentials=credsfile,gid=jyoung,uid=jyoung,auto,rw smbfs is going out of support soon. You should be using cifsfs instead. Jeremy. -- James Young, B.Sc. Ph.D. Student Interactions laboratory, Department of Computer Science, University of Calgary 2500 University Drive NW, Calgary, Alberta, Canada, T2N 1N4 Phone: +1.403.210.9502 E-mail: [EMAIL PROTECTED] URL: http://pages.cpsc.ucalgary.ca/~jyoung/ -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] RE: Mount error 13
Am Mittwoch, 26. März 2008 schrieb Tosh, Michael J: More information on my problem: (with text this time) linuxserver:/var/log # date;mount -v -t cifs //server/share /mnt/share -o credentials=.cifs_creds Wed Mar 26 12:03:38 EST 2008 parsing options: rw,credentials=.cifs_creds Domain W2K3ADDOMAIN mount.cifs kernel mount options unc=//server\share,ip=10.x.x.x,user=remoteuser,domain=W2K3ADDOMAIN,pass= remotepass,ver=1,rw,credentials=/root/.cifs_creds mount error 13 = Permission denied Refer to the mount.cifs(8) manual page (e.g.man mount.cifs) linuxserver:/var/log # grep Mar 26 12:03 messages warn messages:Mar 26 12:03:08 proto2 kernel: CIFS: Unknown mount option credentials messages:Mar 26 12:03:08 proto2 kernel: CIFS VFS: cifs_mount failed w/return code = -13 messages:Mar 26 12:03:39 proto2 kernel: CIFS: Unknown mount option credentials messages:Mar 26 12:03:39 proto2 kernel: CIFS VFS: cifs_mount failed w/return code = -13 warn:Mar 26 12:03:08 proto2 kernel: CIFS: Unknown mount option credentials warn:Mar 26 12:03:08 proto2 kernel: CIFS VFS: cifs_mount failed w/return code = -13 warn:Mar 26 12:03:39 proto2 kernel: CIFS: Unknown mount option credentials warn:Mar 26 12:03:39 proto2 kernel: CIFS VFS: cifs_mount failed w/return code = -13 # smbclient -V Version 3.0.28-0.1.95-1624-SUSE-SLES9 _ From: Tosh, Michael J Sent: Wednesday, March 26, 2008 11:36 AM To: 'samba@lists.samba.org' Subject:Mount error 13 I am trying to connect a SLES9 server to a share on a Windows 2003 domain. # mount -t cifs //server/share /mnt/share -o credentials=.cifs_creds mount error 13 = Permission denied Refer to the mount.cifs(8) manual page (e.g.man mount.cifs) #cat .cifs_creds username=remoteuser password=remotepass domain=W2K3ADDOMAIN On the domain controller, I see: Successful Network Logon: User Name: remoteuser Domain: W2K3ADDOMAIN Logon ID: (0x0,0x20544132) Logon Type: 3 Logon Process: NtLmSsp Authentication Package: NTLM Workstation Name: \\10.x.x.x (IP of linux box) Logon GUID: - Caller User Name: - Caller Domain: - Caller Logon ID:- Caller Process ID: - Transited Services: - Source Network Address: 10.x.x.x (IP of linux box) Source Port:0 Then immediately after I see: User Logoff: User Name: remoteuser Domain: W2K3ADDOMAIN Logon ID: (0x0,0x20544132) Logon Type: 3 You need to install the cifs userland helpers mount.cifs and umount.cifs, part of the samba client package (distro dependent). The credentials file - and other stuff - is parsed in userland, before being passed to the cifs kernel module. Cheers, Günter -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] [Samba to samba transfert] Timestamp problem
Am Donnerstag, 28. Februar 2008 schrieb Hervé Richard: Ross Smith wrote: I don't have a lot of experience of Samba, but under windows that's exactly what I'd expect to see if you copied a bunch of files. To retain timestamps under windows you generally need to use a backup program and not a copy one. However, since you're using Nautilus, are you actually using Samba to do the copy? I'm wondering if you would be better just avoiding Samba and using Linux / Unix file transfer tools. A quick google has brought up cp --preserve=timestamps so I would imagine there are ways to do this. Using nautilus was easy and more flexible to make transfer but at the end it took more time according to the timestamps problem :-/ Yep I used scp -pr to copy and preserving timestamps. So in résumé scp is an alternative / workaround but not a solution to the problem. What about a little patch in the future? ;-) Thanks for your answer. Hervé It has already been mentioned, that a normal file copy does not preserve time stamps! Inside a console, (assuming file test is present), try stat test cp test /tmp stat /tmp/test As can be seen, no time stamps are preserved! But stat test cp -p test /tmp stat /tmp/test does preserve them. Note, that the '-p' option is not available on all *nixes. So nautilus would need a configuration option (or similar) to allow what you want. It's not a samba problem at all. Cheers, Günter -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Re: cifs verses smbfs for Linux clients
Am Dienstag, 19. Februar 2008 schrieb Guenter Kukkukk: Am Dienstag, 19. Februar 2008 schrieb Michael Lueck: /bin/mount -t cifs -o credentials=/home/mdlueck/.smbcredentials,uid=mdlueck,gid=mdlueck //ldslnx01/data /mnt/ldslnx01/data/ And received this type of error: mount: wrong fs type, bad option, bad superblock on //ldslnx01/data, missing codepage or other error In some cases useful info is found in syslog - try dmesg | tail or so What kind of smb server is running //ldslnx01/data ? Cheers, Guenter This kind of error is reported, when the userland cifs helpers mount.cifs (and umount.cifs) are not installed - or the symlinks are not set. Cheers, Guenter -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Re: cifs verses smbfs for Linux clients
Am Dienstag, 19. Februar 2008 schrieb Michael Lueck: simo wrote: There is no interdependency at all, when compiling samba you can choose to build either or both helpers, it is a packaging choice. Most distributions are slowly killing smbfs and stopping building the smbmount helper in the samba packages. I unmounted all cifs connections, then I purged the smbfs package off of my Ubuntu 7.04 desktop. I tried mounting connections: /bin/mount -t cifs -o credentials=/home/mdlueck/.smbcredentials,uid=mdlueck,gid=mdlueck //ldslnx01/data /mnt/ldslnx01/data/ And received this type of error: mount: wrong fs type, bad option, bad superblock on //ldslnx01/data, missing codepage or other error In some cases useful info is found in syslog - try dmesg | tail or so Thus, the dependency I was referring to. I do not like to be one to argue. (shrug) Thanks, -- Michael Lueck Lueck Data Systems http://www.lueckdatasystems.com/ What kind of smb server is running //ldslnx01/data ? Cheers, Guenter -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba + LDAP
Am Freitag, 12. Oktober 2007 06:58 schrieb John H Terpstra: On Thursday 11 October 2007 22:57, Daniel L. Miller wrote: Are the IDEALX tools necessary for complete integration with LDAP? Or is the built-in support sufficiently advanced now? Daniel Daniel, What function do you believe the IDEALX tools serve? Why do you think these scripts are needed? What makes you think that built-in support might be the right (or best) solution? Have you read the Samba documentation? Specifically, is there anything in the Samba3-HOWTO or in Samba3-ByExample that would lead you to believe that there is any attempt to supercede the necessity for the IDEALX tools (or an alternative set of scripts that is external to Samba itself)? What does complete integration with LDAP mean to you? You are not the first person to ask questions like these. It would help me to write more useful documentation if I could better understand what is behind the questions. In case you do not know of the books Samba3-HOWTO and Samba3-byExample they can be obtained from: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf http://www.samba.org/samba/docs/Samba3-ByExample.pdf The IDEALX tools are a means of creating and managing UNIX user and group accounts in the LDAP directory. Samba can then create and manage the Windows (SambaSAM) account information that is necessary to support Windows network activities. As a network administrator, I want total control over how UNIX accounts are managed in my LDAP directory and I would not want this done by Samba - particularly if that removes my ability to control how this is done. Your mileage may vary, but I suspect most UNIX administrators who manage Samba would not want to lose control of the UNIX part of the directory. For example, if Samba had total control over all Windows networking (Samba) accounts, and the Windows network administrator deletes a user account, but the users also has vital UNIX files, how should the deletion of the UNIX account information be handled? By keeping the LDAP administration scripts that impact the UNIX account management separate from the Windows (Samba) account part, the administrator can exercise greater control over. - Just my $0.02 worth. Cheers, John T. Hi John, there is ongoing work to avoid (some) external scripts http://wiki.samba.org/index.php/Ldapsam_Editposix Cheers, Guenter -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] samba 3.0.26a-1 / Debian/Lenny sendfile(?) performance problems
Am Samstag, 29. September 2007 20:00 schrieb Justin Piszcz: Package: samba Version: 3.0.26a-1 Kernel: 2.6.22 samba 3.0.26a-1 performance 900 KiB/s, but FTP = 30-90 MiB/s Let me start out by saing this is an oddball problem: SAMBA: LINUX - WINDOWS = 900 KiB/s (varies between 100 - 900 KiB/s) WINDOWS - LINUX = 30-90 MiB/s (always) FTP: Either direction, 30-90 MiB/s (always) I do not see any nasty errors in the logs even with verbose = 5. Any ideas here? I am not using any special options. # cat /etc/samba/smb.conf [global] log level = 5 workgroup = WORKGROUP server string = %h - Pentium IV 3.4GHZ security = user encrypt passwords = true [user] comment = user path= /home/user writable= yes valid users = user create mask = 644 -- Here, FTP for pulling files from Linux. ftp mget * 200 TYPE is now 8-bit binary 200 PORT command successful 150-Connecting to port 1255 150 715924.0 kbytes to download 226-File successfully transferred 226 13.687 seconds (measured here), 51.08 Mbytes per second ftp: 733106176 bytes received in 13.69Seconds 53562.23Kbytes/sec. 200 PORT command successful 150-Connecting to port 1256 150 716272.0 kbytes to download 226-File successfully transferred 226 13.032 seconds (measured here), 53.67 Mbytes per second ftp: 733462528 bytes received in 13.05Seconds 56216.95Kbytes/sec. 200 PORT command successful 150-Connecting to port 1257 150 713200.0 kbytes to download 226-File successfully transferred 226 12.869 seconds (measured here), 54.12 Mbytes per second ftp: 730316800 bytes received in 12.88Seconds 56723.63Kbytes/sec. Here, FTP for pushing files to Linux. ftp mput 1 2 3 200 PORT command successful 150 Connecting to port 1263 226-File successfully transferred 226 12.802 seconds (measured here), 54.61 Mbytes per second ftp: 733106176 bytes sent in 12.80Seconds 57287.35Kbytes/sec. 200 PORT command successful 150 Connecting to port 1264 226-File successfully transferred 226 12.949 seconds (measured here), 54.02 Mbytes per second ftp: 733462528 bytes sent in 12.95Seconds 56624.92Kbytes/sec. 200 PORT command successful 150 Connecting to port 1265 226-File successfully transferred 226 15.400 seconds (measured here), 45.23 Mbytes per second ftp: 730316800 bytes sent in 15.38Seconds 47500.28Kbytes/sec. But (all I can offer is packet dumps/traces or bandwidth measurements): Incoming: Outgoing: Curr: 0.00 MByte/s Curr: 0.07 MByte/s Avg: 0.00 MByte/s Avg: 0.07 MByte/s Min: 0.00 MByte/s Min: 0.07 MByte/s Max: 0.00 MByte/s Max: 0.07 MByte/s Ttl: 1898.08 MByte Ttl: 2954.92 MByte LOCAL - REMOTE TXBPS RXBPS TOTALBPS (IP) PORT PROTO (IP) PORT TX RX TOTAL linuxbox - p4w.internal.lan 546k/s 4.74k/s 551k/s 192.168.0.1 445TCP 192.168.0.212596.88m106k 6.99m Why do I get such poor performance when trying to retrieve a file off the Linux box? This is a very strange problem. Linux: $ netstat -i Kernel Interface table Iface MTU Met RX-OK RX-ERR RX-DRP RX-OVRTX-OK TX-ERR TX-DRP TX-OVR Flg eth0 1500 0 14049682 0 0 0 11354070 0 0 0 BMRU lo16436 0 45335 0 0 045335 0 0 0 LRU Windows: netstat -s IPv4 Statistics Packets Received = 5053597 Received Header Errors = 0 Received Address Errors= 19 Datagrams Forwarded= 0 Unknown Protocols Received = 0 Received Packets Discarded = 2 Received Packets Delivered = 5053595 Output Requests= 3655144 Routing Discards = 0 Discarded Output Packets = 0 Output Packet No Route = 0 Reassembly Required= 0 Reassembly Successful = 0 Reassembly Failures= 0 Datagrams Successfully Fragmented = 0 Datagrams Failing Fragmentation= 3 Fragments Created = 0 ICMPv4 Statistics ReceivedSent Messages 47 24 Errors0 0 Destination Unreachable 25 2 Time Exceeded 0 0 Parameter Problems0 0 Source Quenches 0 0 Redirects 0 0 Echos 0 22 Echo Replies 22 0 Timestamps0 0 Timestamp Replies 0 0 Address Masks 0 0 Address
Re: [Samba] OS/2 Warp 4 Access Issues
Am Donnerstag, 5. Juli 2007 22:38 schrieb Michael Powell: OK, here are the versions: OS/2 Warp 4.50 Debian Etch Samba 3.0.24-6etch4 linux kernel 2.6.18 I actually started having problems before upgrading to etch. Then, I was on a 2.4 kernel, and had upgraded to what was then the latest security fix for samba for the debian stable version previous to etch. I was hoping that upgrading to etch might fix the problem, but it did not. FWIW, I did a clean upgrade to etch, using the netinstall CD, so all of the previous binaries and config files were over-written (nothing left behind to cause problems). As for the problem... on the OS/2 box, the shares on the debian box are displayed (just as the shares on the Win9x box are), but when I click on any of the debian shares, OS/2 reports that No objects were found that match the specified find criteria. So, none of the files that reside in the shared folders are displayed. It is as if the shares have no files in them (but they do!). OS/2 does appear to access the PDF Printer share OK, and acts as though it is printing to it, but I have no idea where the PDF files that it is printing are being saved. ;-) It cannot access any of the disk shares. Here is the smb.conf config file (with certain bits replaced with 'X'): [global] netbios name = XX server string = debian workgroup = XX hosts allow = 127. 192.168.X. #printcap name = /etc/printcap printcap name = cups load printers = yes printing = cups cups options = raw guest account = smbguest log file = /var/log/samba/samba.log max log size = 1000 security = user username level = 8 password level = 8 username map = /etc/samba/smbusers add user script = /usr/sbin/useradd -d /dev/null -g sambamachines -c 'Samba Machine Account' -s /dev/null -M '%u' smb passwd file = /etc/samba/smbpasswd encrypt passwords = yes unix password sync = no passwd program = /usr/bin/passwd '%u' passwd chat = *New*UNIX*password* %n\n *ReType*new*UNIX*password* %n\n *passwd:*all*authentication*tokens*updated*successfully*\n null passwords = no socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 interfaces = 127.0.0.1/8 192.168.X.X remote browse sync = 192.168.X.255 remote announce = 192.168.X.255 local master = no os level = 33 domain master = no preferred master = no time server = no domain logons = no logon drive = m: logon home = \\%L\homes\%u logon path = \\%L\profiles\%u logon script = %G.bat name resolve order = wins lmhosts bcast wins support = no msdfs root = yes wins proxy = no dns proxy = no preserve case = no winbind use default domain = yes idmap uid = 16777216-33554431 idmap gid = 16777216-33554431 template shell = /dev/null [homes] comment = Home Directories path = /home read only = no available = yes browseable = yes writable = yes guest ok = no public = no printable = no share modes = no locking = no [netlogon] comment = Network Logon Service path = /home/netlogon read only = no available = yes browseable = yes writable = no guest ok = no public = no printable = no share modes = no locking = no Thanks for your assistance! Hi Michael, add the following to the [global] section of smb.conf: ea support = yes Cheers, Guenter -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Support for multiple file streams?
Am Dienstag, 26. Juni 2007 22:07 schrieb Ephi Dror: Hello, Look like demand for multiple file streams support increased lately. Does samba 3 series intend to support it any time soon? Look like SAMBA 4 is working on it based on the following form Andrew Tridgell: One simple but important example of how the new NTVFS layer helps is the addition of support for NT file streams. A file in a NT filesystem can have multiple streams, where the primary stream (called :$DATA) is the normal file data that people are used to thinking about, but there can be any number of other named streams containing other types of data, such as meta-data describing who wrote the file, or an audio stream, or even some data from an anti-virus scan of the file. Importantly, recent updates to WindowsXP use streams to store security information about where a file came from, which allows Windows to display a warning when you try to execute a file that comes from an untrusted security zone. POSIX file systems have no concept of multiple streams, and as Samba was originally designed as a tool for representing a POSIX filesystem to Windows clients, there was no attempt to add stream support. The situation has now changed, with streams becoming a more essential feature for a file server for Windows clients, and at the same time user expectations for compatibility with WindowsNT have risen. This means we really need to support streams, but in order to do that properly, a lot of the internals of Samba needed to be updated. This is achieved in Samba4 using the new NTVFS layer, which allows streams to be represented either using an external database or using file xattrs, which is an extension recently added to Linux, and which is also present in a number of other, Unix-like systems. Does anyone aware on any experimental attempt to provide this functionality in samba 3.0.x or if it is on the roadmap. Cheers, Ephi Ephi, there is currently _no_ way to (exactly) represent MS ntfs alternate data streams on *nix file systems! The approach to store them on the *nix side into the xattr file space - or into a separate DB - (like samba4 is doing) is a first go, but can never meet the the nearly unlimited size of ads on MS systems. Ext2/ext3 has a limited xattr size of about 4KB (!), other file systems (reiserfs, xfs, jfs, ...) allow about (restricted multiples) of 64KB. Anyway - _big_ alternate data streams on current *nix systems is a no go! The good news. MS alternate data streams haven't been used heavily in the past - and the currently used sizes could be represented by using the very simple *nix xattr space. Samba4 is going that way, and samba3 atm has no chance to do it a different way... Cheers, Guenter -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Use metadata files in Samba
Am Sonntag, 27. Mai 2007 09:24 schrieb Thomas Bley: Hello, Often people (or applications) want to store additional information about a file. E.g. history, approval state, search tags, etc. Some file formats offer to integrate these metadata, some not (e.g. exif- headers, id3, etc.). My idea would be to create an additional filename.xyz.meta file next to a filename.xyz in the same folder. If the filename.xyz gets renamed/deleted/moved, the filename.xyz.meta file should be also renamed/deleted/moved in case it exists. Is this possible with Samba or are there better ways to do handle metadata ? Regards Thomas Hi Thomas, Samba is accessed from a lot of different clients. Many of them support meta file information - OS/2 extended attributes - windows alternate data streams and EAs - *nix xattr - Samba3 does support most of those meta file/dir information, but not 'alternate data streams'. Under linux have a look at 'man setxattr' how to cope with that. (see also cmds like setfattr, getfattr, ...) Samba3 itself uses VFS_* wrappers to convert the smb xattr calls into corresponding calls of the underlying operating system. File systems support different max. summed up sizes for all xattr, e.g. - ext2 / ext3 ~3.9KB - reiserfs/XFSN * 64KB - JFS 128KB Have a look at the end of http://samba.org/ftp/unpacked/samba4/howto.txt It's from samba4, but explains some basic requirements for xattr support. http://www.suse.de/~agruen/acl/linux-acls/online/ is a bit outdated, but does also mention 'extended attributes'. As the article claims, some care must be taken during backup / restore, when EAs or ACLs have been used. Your 2 file approach is not supported bei samba - and imho is always a bad idea. Cheers, Guenter -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Problems with Windows 2003 connecting a Samba server
Am Dienstag, 29. Mai 2007 22:12 schrieb Chan Jason: Hi list, I am encountering a problem in connecting a Windows 2003 to a Samba 3.0.21b server. The Samba server is configured to have a security = share option, so that no password is needed. I can connect to the server by typing net use z: \\192.168.51.1\data, and it is successful. However, if I try to do dir z:, no file found! Same behaviour are found in Windows operation, i.e. type \\192.168.51.1\data under Run box in Start Menu. Strangely, another server with 3.0.14a does not have such problem, and another Windows XP does not have such problem too! They can view the files in share easily. Here comes the log file: [2007/05/30 04:13:15, 1] smbd/service.c:close_cnum(885) 192.168.2.37 (192.168.2.37) closed connection to service data [2007/05/30 04:15:35, 1] smbd/service.c:make_connection_snum(693) 192.168.2.37 (192.168.2.37) connect to service data initially as user nobody (uid=99, gid=99) (pid 30283) [2007/05/30 04:17:00, 1] smbd/service.c:close_cnum(885) 192.168.2.37 (192.168.2.37) closed connection to service data [2007/05/30 04:17:00, 1] smbd/service.c:make_connection_snum(693) 192.168.2.37 (192.168.2.37) connect to service data initially as user nobody (uid=99, gid=99) (pid 30301) [2007/05/30 04:18:08, 1] smbd/service.c:close_cnum(885) 192.168.2.37 (192.168.2.37) closed connection to service data Here comes the testparm: [global] unix charset = big5 workgroup = CC netbios name = CCSERVER server string = Samba Server security = SHARE log file = /var/log/samba/%m.log max log size = 50 socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 printcap name = /etc/printcap dns proxy = No cups options = raw [homes] comment = Home Directories read only = No browseable = No [printers] comment = All Printers path = /var/spool/samba printable = Yes browseable = No [data] comment = Public Data path = /data read only = No create mask = 0777 guest ok = Yes Also here is the traffic log: 0.00 192.168.2.37 - 192.168.51.1 TCP 1902 microsoft-ds [SYN] Seq=2266364078 Ack=0 Win=65535 Len=0 0.000356 192.168.2.37 - 192.168.51.1 TCP 1903 netbios-ssn [SYN] Seq=1017632209 Ack=0 Win=65535 Len=0 0.010996 192.168.51.1 - 192.168.2.37 TCP microsoft-ds 1902 [SYN, ACK] Seq=1194648936 Ack=2266364079 Win=5808 Len=0 0.011333 192.168.2.37 - 192.168.51.1 TCP 1902 microsoft-ds [ACK] Seq=2266364079 Ack=1194648937 Win=65535 Len=0 0.011445 192.168.2.37 - 192.168.51.1 SMB Negotiate Protocol Request 0.011599 192.168.51.1 - 192.168.2.37 TCP netbios-ssn 1903 [SYN, ACK] Seq=1190050630 Ack=1017632210 Win=5808 Len=0 0.011758 192.168.2.37 - 192.168.51.1 TCP 1903 netbios-ssn [RST] Seq=1017632210 Ack=1017632210 Win=0 Len=0 0.022912 192.168.51.1 - 192.168.2.37 TCP microsoft-ds 1902 [ACK] Seq=1194648937 Ack=2266364216 Win=6432 Len=0 0.024424 192.168.51.1 - 192.168.2.37 SMB Negotiate Protocol Response 0.025427 192.168.2.37 - 192.168.51.1 SMB Session Setup AndX Request, User: EXPRESS-11AIQI4\Administrator; Tree Connect AndX, Path: \\192.168.51.1\DATA 0.039981 192.168.51.1 - 192.168.2.37 SMB Session Setup AndX Response; Tree Connect AndX 0.040262 192.168.2.37 - 192.168.51.1 SMB Transaction2 Request QUERY_PATH_INFORMATION, Path: 0.051879 192.168.51.1 - 192.168.2.37 SMB Transaction2 Response QUERY_PATH_INFORMATION 0.052291 192.168.2.37 - 192.168.51.1 SMB Transaction2 Request FIND_FIRST2, Pattern: \* 1.519710 192.168.2.37 - 192.168.51.1 SMB Transaction2 Request FIND_FIRST2, Pattern: \* 1.530914 192.168.51.1 - 192.168.2.37 TCP microsoft-ds 1902 [ACK] Seq=1194652038 Ack=2266364728 Win=7504 Len=0 51.023255 192.168.2.37 - 192.168.51.1 SMB Echo Request 51.033769 192.168.51.1 - 192.168.2.37 TCP microsoft-ds 1902 [ACK] Seq=1194652038 Ack=2266364781 Win=7504 Len=0 85.150658 192.168.2.37 - 192.168.51.1 TCP 1902 microsoft-ds [FIN, ACK] Seq=2266364781 Ack=1194649246 Win=65226 Len=0 85.169401 192.168.51.1 - 192.168.2.37 NBSS NBSS Continuation Message 85.169910 192.168.2.37 - 192.168.51.1 TCP 1902 microsoft-ds [ACK] Seq=2266364782 Ack=1194649246 Win=65226 Len=0 85.170486 192.168.2.37 - 192.168.51.1 TCP 1904 microsoft-ds [SYN] Seq=3224569487 Ack=0 Win=65535 Len=0 85.170724 192.168.2.37 - 192.168.51.1 TCP 1905 netbios-ssn [SYN] Seq=494418265 Ack=0 Win=65535 Len=0 85.179785 192.168.51.1 - 192.168.2.37 TCP microsoft-ds 1904 [SYN, ACK] Seq=1275220318 Ack=3224569488 Win=5808 Len=0 85.180158 192.168.2.37 - 192.168.51.1 TCP 1904 microsoft-ds [ACK] Seq=3224569488 Ack=1275220319 Win=65535 Len=0 85.180250 192.168.2.37 - 192.168.51.1 SMB Negotiate Protocol Request 85.183753 192.168.51.1 - 192.168.2.37 TCP netbios-ssn 1905 [SYN, ACK] Seq=1269633862 Ack=494418266
Re: [Samba] Use metadata files in Samba
Am Sonntag, 27. Mai 2007 09:24 schrieb Thomas Bley: Hello, Often people (or applications) want to store additional information about a file. E.g. history, approval state, search tags, etc. Some file formats offer to integrate these metadata, some not (e.g. exif- headers, id3, etc.). My idea would be to create an additional filename.xyz.meta file next to a filename.xyz in the same folder. If the filename.xyz gets renamed/deleted/moved, the filename.xyz.meta file should be also renamed/deleted/moved in case it exists. Is this possible with Samba or are there better ways to do handle metadata ? Regards Thomas Hi Thomas, Samba is accessed from a lot of different clients. Many of them support meta file information - OS/2 extended attributes - windows alternate data streams and EAs - *nix xattr - Samba3 does support most of those meta file/dir information, but not 'alternate data streams'. Under linux have a look at 'man setxattr' how to cope with that. (see also cmds like setfattr, getfattr, ...) Samba3 itself uses VFS_* wrappers to convert the smb xattr calls into corresponding calls of the underlying operating system. File systems support different max. summed up sizes for all xattr, e.g. - ext2 / ext3 ~3.9KB - reiserfs/XFS N * 64KB - JFS 128KB Have a look at the end of http://samba.org/ftp/unpacked/samba4/howto.txt It's from samba4, but explains some basic requirements for xattr support. http://www.suse.de/~agruen/acl/linux-acls/online/ is a bit outdated, but does also mention 'extended attributes'. As the article claims, some care must be taken during backup / restore, when EAs or ACLs have been used. Your 2 file approach is not supported bei samba - and imho is always a bad idea. Cheers, Guenter -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbmount
Am Montag, 7. Mai 2007 21:42 schrieb Chris Smith: On Monday 07 May 2007, John G Walker wrote: The files are on a W98 system for historical reasons and they are being slowly migrated off. However, the reason I can't just move them is because I'm using Windows programs on the legacy systems. Some I wrote myself, in Visual Basic, so I can't blame anybody else for the situation. Another program I use is Photoshop, which they won't port to Linux (despite the fact it is the program most wanted to be ported to Linux). Etc. I need to keep running Windows as long as I have the need for such stuff. The data files don't need to reside on that system. Virtually every app I know of, including Photoshop, can access, open, edit, and save files on remote shares. Some real legacy apps may require mapped drives instead of UNC paths but they should, in most cases, work just fine. Chris Hi all, just some additions and clarifications from my side. Samba3 / Samba4 === For some years now I'm trying hard to support the samba3 / samba4 team regarding missing features or bugs related to legacy clients - mainly OS/2, but also windows9x/me. Nice and interesting times and the experience, that the samba developers _always_ have had and _still_ have an open ear, when troubles or wishes are reported to them! The main problem is, that those missing stuff must be _reported_ to them! These days, most of the samba developers do not have any physical access to legacy client installations anymore. So it's getting more and more important to send them as much background information as possible, like detailed - debug 10 logs - network sniffs - used samba version and smb.conf settings - used operating systems (fixpak level) - used file systems (e.g. xattr support) - proposed patches - ... In addition, it's very important to help with testing suggested patches before they go mainstream. Cause some of those legacy questions can also easily be discussed on irc, some years ago I've opened 2 separate channels on irc.freenode.net: #samba-os2 #samba-os2-technical The names are a bit misleading - but all legacy smb users are welcome there. :-) To my knowledge, most of the outstanding (OS/2) glitches are solved now. CIFS kernel module: === When the first discussions about dropping the kernel module smbfs and its samba userland helpers - smbmount - smbmnt - smbumount were starting on @samba-technical about a year ago, Jeremy Allison (jra) told me on irc, that Steve French (sfrench) had already added some code to support legacy smb servers within cifs. That days I started to build my own cifs.ko from the samba hosted cifs-client svn repository, to be able to add and test code for possibly missing features regarding legacy smb servers. Cause I was not aware of the separately existing mailing list [EMAIL PROTECTED], private email exchange with Steve was starting to discuss and solve missing stuff - sending patches back and forth... for many weeks ... Steve also managed to get access to an OS/2 box, to test stuff himself. Afaik, he's testing against win9x, too. I must admit, that we had one big problem that days: Steve was doing his work on the kernel git-tree - and I was using the samba cifs-client svn repository... Both repos got more or less so worse out of sync, that the simple exchange of patches was no longer feasible. I'm working as a freelancer and got distracted from cifs due to other customer needs - which is a bit reflected in https://bugzilla.samba.org/show_bug.cgi?id=4090 Sorry for my probably upset comments... To solve the 2 repository problem, at the end of last year i did setup a completely separate linux box entirely for cifs stuff. Installed git, cogito and sparse - and joined LKML. I'm able to test here against 3 OS/2 and 1 win98 legacy box. One major issue was (and partly is) the reading and writing of file/directory time stamps - with ugly side-effects on the OS/2 side: due to the parameter lastwritetime = 0 used on SMBClose, all time stamps on the OS/2 side were reset to NULL during file- browsing. BTW - when browsing directories with konqueror, it usually tries to display some popup-contents of the file the mouse is over. - open file - read (part) of the file - close the file == SMBClose()!! = filetime = zero Another problem is the fact, that *nix and newer windows are using UTC as the base for time stamps, but some legacy servers always use localtime and send them on the wire. Today, afaik all of reading time stamps is fixed. But there are still issues when writing a file/dir. cp -p linux_src_file os2_dst_file does not preserve any time stamp (the legacy versions of setfileinfo() / setpathinfo() are not implemented atm). I mailed Steve, that this is even true, when copying to a win2k or winxp server. Setpathinfo() does not work, when the file is still open. _Only_ on winNT, a separate open, setfileinfo, close
Re: [Samba] Building Samba 4 - Includes.c missing?
Am Mittwoch, 28. Februar 2007 03:24 schrieb Frank Gruman: Hello all, I've been peacefully using Samba 3 for about 3 years now, and it has done a wonderful job in my little world as domain member servers for file and print serving. Much bettetrver farms that some of my peers in the company are using. So I want to try Samba 4 and see if I can play with making it my PDC. The only problem is that when I go to make, I receive the following error: ... Creating torture/ndr/proto.h Generating dependencies for torture/ndr/ndr.c Generating dependencies for torture/local/local.c Removing precompiled headers Precompiling include/includes.h gcc: include/includes.c: No such file or directory gcc: no input files make: *** [include/includes.h.gch] Error 1 This, after a successful autoconf, configure, and make pch all. In looking in the include folder, there is only includes.h. I pulled the files straight from subversion, so would have hoped that I got everything necessary. Has anyone else had this issue building Samba 4? Regards, Frank Hi Frank, instead of using 'make pch all' just use 'make' the option 'pch' (pre-compiled headers) often does not work. :-( Cheers, Guenter -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Windows XP share charset problem
Am Dienstag, 28. November 2006 19:29 schrieb Arlequín: Hello, there I want to connect to a Windows XP share using the following line in my fstab \\WINDOWS-PC\SHARE /dir/to/mount/share smbfs auto,umask=0002,credentials=/etc/winpassword,iocharset=utf8,gid=0,noauto 0 0 It mounts OK but I can't get the charset shown correctly for non-ASCII chars like á ç ñ et cetera. I've even tried using cpage=850 option when mounting without success. I've looked for this issue on Samba documentation but wasn't able to find an example on how to solve it. Does anyone have any idea about how to deal with this kinda shares? T.I.A. -- Arlequín _o) amahoro_AT_adinet_DOT_com_DOT_uy / \\ http://counter.li.org/ _(___V Linux Registered User #207262 This issue has often been discussed - but you won't get a fix for it. smbfs is no longer maintained - use cifs instead, which is the successor of smbfs. (man mount.cifs) Please note, that the mount.cifs helper stuff is part of the samba suite, cifs itself is a kernel module! Cheers, Guenter -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Crippled file list on samba 3.0.23-c2. Debian Etch x64 (files randomly not showing up)
Am Samstag, 11. November 2006 16:24 schrieb Henrik Cednert: Sorry to bugger you people. But no one have any suggestions about this? /Henrik [EMAIL PROTECTED] wrote: Hi there people. My first post here at the list so I hope I havn't made any misstakes so far and that I can write in such a way so you people understand me. =) The problem I have is that when I list folders on disks mouted with mount -t smbfs ... the file lists of folders are crippled. What I mean is that files are randomly missing in the lists even if they are there. A refresh of the dir can help sometimes but most of the time the missing files/files appear and some other files disappear. A huge problem here since i work with Shake and pretty large file sequences. I was adviced at the IRC-channel to downgrade to an earlier version but before I do that I wanted to try my luck here. I'm also in the middle of a project here at work so I don't want to mess to much with the computer just yet. Thanks in advance for any help that solves this. Sincerely, Henrik C, Sweden Hi Henrik, the _kernel_ module 'smbfs' is not related to samba - so you are asking in the wrong list! Anyway - smbfs is _no_ longer maintained (for a long while now). So you better use 'cifs' now, which is the successor of smbfs. The mount options are a bit different - have a look at 'man mount.cifs'. Please note, that the cifs userland helper 'mount.cifs' _is_ part of the samba distribution. Good luck. Guenter Kukkukk -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Problem mounting with credentials file
Am Freitag, 27. Oktober 2006 19:29 schrieb Jonathan Duncan:
On Fri, 27 Oct 2006, Ethy H. Brito wrote:
On Fri, 27 Oct 2006 10:55:08 -0600 (MDT)
Jonathan Duncan [EMAIL PROTECTED] wrote:
I am mounting as the root user because I have not given my user
permission to mount this share.
Following is the results of the troubleshooting steps that you gave me.
I did not understand what would be wrong from looking at the strace.
Please run locate mount.cifs or, if you dont have it installed,
find / -name mount.cifs 2/dev/null
It seems that you do not have mount.cifs installed or it is out of your
search PATH. mount is looking for it at /sbin. Provide a link, please.
Ethy
lstat64(/etc/mtab, {st_mode=S_IFREG|0644, st_size=286, ...}) = 0
stat64(/sbin/mount.cifs, 0xbffa1e70) = -1 ENOENT (No such file or
directory)
rt_sigprocmask(SIG_BLOCK, ~[TRAP SEGV RTMIN RT_1], NULL, 8) = 0
mount(//192.168.0.2/share, /mnt/share, cifs,
MS_POSIXACL|MS_ACTIVE|MS_NOUSER|0xec, 0x80638f0) = -1 EINVAL
(Invalid argument)
rt_sigprocmask(SIG_UNBLOCK, ~[TRAP SEGV RTMIN RT_1], NULL, 8) = 0
write(2, mount: wrong fs type, bad option..., 111mount: wrong fs type,
bad option, bad superblock on //192.168.0.2/share,
missing codepage or other error
) = 111
locate and find both turned up nothing.
Apparently I do not have mount.cifs on my filesystem. That does not make
sense to me. CIFS works when I specify a username and password directly
but not when I use the credentials option. It would seem that CIFS is
installed.
Regards,
Jonathan
Hi Jonathan,
you _need_ mount.cifs when using a credentials file!
mount.cifs reads and parses the credentials file - the cifs kernel module does
_not_!
Good luck - Guenter Kukkukk
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Problem mounting with credentials file
Am Samstag, 28. Oktober 2006 02:14 schrieb Jonathan Duncan: On Sat, 28 Oct 2006, Guenter Kukkukk wrote: locate and find both turned up nothing. Apparently I do not have mount.cifs on my filesystem. That does not make sense to me. CIFS works when I specify a username and password directly but not when I use the credentials option. It would seem that CIFS is installed. Regards, Jonathan Hi Jonathan, you _need_ mount.cifs when using a credentials file! mount.cifs reads and parses the credentials file - the cifs kernel module does _not_! Thank you. This is probably dependant on my distribution, but how do I get that file? Is it usually installed with samba? Do I just create it? Thanks, Jonathan The mount.cifs helper stuff is part of samba. The binary is usually installed as /sbin/mount.cifs Guenter Hmm - should also send this to the list - done... -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Transfer rates faster than 23MBps?
On Saturday 23 September 2006 17:13, Doug VanLeuven wrote: Mark Smith wrote: I also tried your values, with the tcp_window_scaling, with no luck. It's enable by default, but I explicitly set options other options depend on. I set up my test rig again. Host server 2.6.12-1.1376_FC3, samba 3.0.23 Broadcom Nextreme BCM5702X Gigabit, tg3 driver default config Client 2.6.12-1.1381_FC3, samba 3.0.21pre3-SVN-build-11739 Intel Pro/1000, 82546GB Gigabit, e1000 driver default config HD Drives on both are 45-50MBps ...snip Hi Doug, have you ever tried netio to check for raw needwork speed? http://www.ars.de/ars/ars.nsf/docs/netio It does not add any overhead caused by file operations - so it can help to tune raw parameters. The source is included - so it can be tuned, too. When sniffing such traffic, also have a look, how tcpi/ip ACK packets are used and whether they are send immediately or with some delay. Good luck - Guenter Kukkukk -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] More on the archive bit saga
Using attrib -s on the file removed the access denied part. Strange that some files mysteriously got ACLs when others did not. Yes, map system = no is set. server:/share/personal/smith# getfattr -d foo.txt # file: foo.txt user.DOSATTRIB=0x0 Is that good or bad? Hi Aaron, assuming the following conditions are met: - the samba share is located on a file system which supports xattr - smb.conf has the following entries ea support = yes store dos attributes = yes map archive = no map hidden = no map system = no Expressing the DOS attribute bits in hexadecimal notation, you get the following - the user.DOSATTRIB like display is shown in braces: readonly 0x01 (0x1) hidden0x02 (0x2) system0x04 (0x4) archive 0x20 (0x20) Any mixture of no attribute to all attributes set is possible. The bits are ORed together. So, when all attributes are set: | is the OR operator 0x01 | 0x02 | 0x04 | 0x20 results to 0x27 getfattr -d foo.txt # file: foo.txt user.DOSATTRIB=0x27 matches the win console output: attrib foo.txt A SHR Z:\foo.txt When removing all attributes with attrib -r -h -s -a foo.txt windows shows: attrib foo.txt Z:\foo.txt and linux: getfattr -d foo.txt # file: foo.txt user.DOSATTRIB=0x0 As already noted, any mixture of bits is possible. Hope this helps. Guenter -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Enabling CIFS
I upgraded my SUSE 10.0 server to the Suse Projects 3.0.23c rpms. When I try to use cifs to mount, I get the error: mount error 112: Host is down by using this syntax: # mount -t cifs -o ro //p-t18/G /mnt/test What do I need to do to make this work? ... Hi Felix, if you try to mount a server which is using an old SMB dialect (like OS/2), you get this error. Some weeks ago we already discussed that. The current cifs is atm not enabled to support the older dialects. That was the reason we built our own kernel with cifs enabled to also negotiate an older dialect. The current cifs code must be enhanced (and tested) to support some more aspects of the older SMB dialect. With your own special build of cifs you already noticed the wrong timestamps. Cheers, Guenter -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] OS/2 client crash on Find Close2
- Original Message - From: Jeremy Allison [EMAIL PROTECTED] To: Andreas Taegener [EMAIL PROTECTED] Cc: samba@lists.samba.org Sent: Tuesday, August 08, 2006 4:17 AM Subject: Re: [Samba] OS/2 client crash on Find Close2 On Mon, Aug 07, 2006 at 07:44:12PM +0200, Andreas Taegener wrote: Hello, I have just migrated an old OS/2 file server to a Linux box with Samba 3.0.23a. Now the OS/2 clients crash from time to time. I found a way to reproduce/force the crash using PMMail and did some experiments. The popuplog.os2 on the clients (Warp4 and eComStation) always names a sys3175 in pmshell.exe / doscall1.dll. Using Ethereal and comparing the network traffic between a) a client and the Samba server and b) the same client and an OS/2 server (in this setup the client doesn't crash) I found at least one difference in the SMB protocol. It is the Find Close2 Response SMB message. Kukks - could you please investigate. Sorry, I have to delegate OS/2 fixes as I don't have a client setup that's easy to get to. Thanks, Jeremy. Jeremy, I'll have a look at this later today. Will drop you a note then. Guenter -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] samba 3.0.22 and OS/2 connectivity
Hi Peter, cut some stuff ... Needless to say whatever I have done to the samba configuration does not seem to upset Windows2000 - I can startup my VPC w2k installation and have no problems at all accessing the nslu2 shares for reading and writing... I am now starting to wonder if there is something a little flaky as regards samba 3.0.22 and OS/2 connectivity? - or is there some secret parameter I've missed in the smb.conf file? Any/All help appreciated. Pete -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba latest samba 3.0.22 does a pretty good job regarding OS/2 connectivity - but, as often, there are some pitfalls - additional thougths and checks apply. The most basic difference of OS/2 is its usage of 'extended attributes' (EAs). Samba can handle EAs pretty well - but _only_, if the used *nix kernel and the used file system can handle EAs, too. In *nix terms, EAs are called 'xattr'. Sorry, the Linksys NSLU2 is new to me - so I had a short look into the specs. The specs claim, that 'FAT32', 'NTFS' or 'ext3' can be used... To _really_ work properly (in all cases), OS/2 needs an EA space of 64KB! Even if xattr support is compiled into the kernel - and 'ext3' is enabled (in fstab) for xattr usage: /dev/hdb6/ext3ext3 acl,user_xattr 1 2 xattr limitations of 'ext3' would count. 'ext3' is only able to store about 3.9KB EAs! reiserfs, JFS and XFS are file systems, which support 64KB EAs. Sadly ext3 is the filesystem used by the NSLU2 and must be used on the 1st partition of any disk that the NSLU2 is Unslung to. Alternative filesystems do not seem to include jfs (a more natural choice for an OS/2 user) or xfs - in fact we are talking fat, fat32 and ntfs as alternatives according to this doc http://www.nslu2-linux.org/wiki/Unslung/R63DiskBehaviour So, if you _really_ don't need EAs to be stored onto the Linksys samba server, some entries in your smb.conf should be checked. Think twice - the OS/2 workplace shell is using EAs heavily - so you won't be able to use that GUI stuff anyway! (The WPS flags nearly _any_ EA error). Maybe I got too used to the fact that the samba 2.?.?? used in the Linksys firmware v23r29 worked fine? Samba3 has some minor glitches, when the used file system does _not_ support EAs - but you told it to use EAs in smb.conf. (Directories - which are told to contain EAs - might be created, and short lateron an error EAS_NOT_SUPPORTED is returned... so then you have that subdir created ... but OS/2 got confused...) Peter, a 1st try to get better results should be ea support = no in smb.conf Extremely Bad move - End of graphical access to the samba shares from an OS/2 based system. That is Not acceptable. I may be able to cope with command line access but I do not expect other users here to be able to cope. Access using the network gui is a necessity. Based on the above advice I must reconsider whether Unslinging the NSLU2 has been a good move. No doubt it brings many improvements - and fixes - over the Linksys standard firmware but it also introduces problems as regards samba. Interestingly I have discussed this problem before when querying the behaviour of samba 3.0.11 The response was: I probably fixed all these issues concerning File services with Jeremy about release 3.0.16. So 3.0.20a shold work fine. Looks like the problems have resurfaced in 3.0.22 :-( xcopy should behave much more as expected. (still sending expected EA warnings) Please post your smb.conf! Must admint that there is more than a good possibility that I've got something wrong in that file - especially as I now find that I cannot open the smb.conf file from my OS/2 system; access denied. That is behaviour that has changed since yesterday when I did try some fine tuning but I do not see what is causing the access denied as I am logged on using an Administrator login. The below is copied from the Full View using SWAT - and seems to include a lot that is not actually in the smb.conf that I last edited using a text editor... ...cut your smb.conf ... Thanks Pete Believe me, samba 3.0.22 _is_ doing a really good job regarding os/2 connectivity. :-) (And I know, what I talk about ... did hundreds of tests in the past...) My intention was, to do a step by step approach to solve your needs. The suggestion to do a 1st try with ea support = no in smb.conf was related to your 'xcopy' anomalies, you described before. Are your xcopy anomalies gone, when you change that in smb.conf? My guess is, that your kernel and/or ext3 file system does not handle xattr correctly at all. (== no xattr support available). That is _not_ a samba fault! To simulate your system, I added a 'ext3noxattr' mount to my linux test
Re: [Samba] samba 3.0.22 and OS/2 connectivity
Hi Peter, - Original Message - From: Peter Brown [EMAIL PROTECTED] To: samba@lists.samba.org Sent: Friday, May 12, 2006 9:39 PM Subject: [Samba] samba 3.0.22 and OS/2 connectivity Hi All I have a Linksys NSLU2 device which is used to hook USB2 drives upto my network as network attached storage. The Linksys firmware upgrade for this device includes samba 3.0.11 which is a non-starter regarding OS/2 connectivity. There is an alternative firmware based on the Linksys firmware called Unslung from http://www.nslu2-linux.org/ The Unslung firmware allows unslinging the operating system from firmware to disk and allows upgrade and additional packages. Having followed the instructions carefully I managed to Unsling the NSLU2 and apply the samba 3.0.22 upgrade available for this system. After a bit of hunting around I managed to find the smb.conf parameter that allows OS/2 based systems to access samba shares and can now read from the shares fine. What I cannot do is write easily to any of the shares; ie Selecting a folder on my local drive and dragging it to a shared folder on the NSLU2 results in this OS/2 error:- SYS0266 : The specified file was not copied Inspecting the shared folder reveals that the folder has been created but is empty - no file copying performed. I investigated command line alternatives to copying files using xcopy with some strange results. In these screensnaps S: is a mapped drive of the nslu2 share /disk2 aka For everyone [S:\Pete]xcopy i:\temp temp /s /e /v /h /t /r The current target for XCOPY, temp, can be a directory or file name and must be specified. Respond Y if the target is a directory or N if the target is a file name. Does temp specify a directory (Y/N)? y SYS1693: The system cannot create the directory. 0 file(s) copied. [S:\Pete] If I make a directory, change to that directory and then perform an xcopy it works:- [S:\Pete\temp]xcopy j:\temp\* /s /e /v /h /t /r The extended attributes for the file or directory were discarded because the target file system does not support them. The extended attributes for the file or directory were discarded because the target file system does not support them. Source files are being read... J:\temp\History.txt J:\temp\ide.txt J:\temp\OS2_Install.exe J:\temp\OS2_UnZip.exe J:\temp\WDSibyl.dat 5 file(s) copied. [S:\Pete\temp] But if the source contains a subdirectory I get an error and the whole process stops:- [S:\Pete\temp]md PostArmor [S:\Pete\temp]cd PostArmor [S:\Pete\temp\PostArmor]xcopy j:\PostArmor\* /s /e /v /h /t /r The extended attributes for the file or directory were discarded because the target file system does not support them. The extended attributes for the file or directory were discarded because the target file system does not support them. Source files are being read... SYS1248: A subdirectory or file S:\Pete\temp\PostArmor\docs already exists. 0 file(s) copied. [S:\Pete\temp\PostArmor] I tried getting around that error with the xcopy /o parameter:- [S:\Pete\temp\PostArmor]xcopy j:\PostArmor\* /s /e /v /h /t /r /o The extended attributes for the file or directory were discarded because the target file system does not support them. The extended attributes for the file or directory were discarded because the target file system does not support them. Source files are being read... The extended attributes for the file or directory were discarded because the target file system does not support them. SYS1248: A subdirectory or file S:\Pete\temp\PostArmor\docs\images already exists. 0 file(s) copied. Needless to say whatever I have done to the samba configuration does not seem to upset Windows2000 - I can startup my VPC w2k installation and have no problems at all accessing the nslu2 shares for reading and writing... I am now starting to wonder if there is something a little flaky as regards samba 3.0.22 and OS/2 connectivity? - or is there some secret parameter I've missed in the smb.conf file? Any/All help appreciated. Pete -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba latest samba 3.0.22 does a pretty good job regarding OS/2 connectivity - but, as often, there are some pitfalls - additional thougths and checks apply. The most basic difference of OS/2 is its usage of 'extended attributes' (EAs). Samba can handle EAs pretty well - but _only_, if the used *nix kernel and the used file system can handle EAs, too. In *nix terms, EAs are called 'xattr'. Sorry, the Linksys NSLU2 is new to me - so I had a short look into the specs. The specs claim, that 'FAT32', 'NTFS' or 'ext3' can be used... To _really_ work properly (in all cases), OS/2 needs an EA space of 64KB! Even if xattr support is compiled into the kernel - and 'ext3' is enabled (in fstab) for xattr usage: /dev/hdb6
Re: [Samba] NET VIEW equivalent in Samba
- Original Message - From: Henrik Zagerholm [EMAIL PROTECTED] To: samba@lists.samba.org Sent: Tuesday, December 13, 2005 11:45 PM Subject: [Samba] NET VIEW equivalent in Samba Hi! Is there a NET VIEW equivalent in samba? I looked at smbclient -L but then I have to know the browser master. I only want to specifiy a workgroup.. Regards, Henrik -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba Hi Henrik, 'findsmb' is worth a try - but I don't use it! I haven't proved, if it is still under development at all... You can also try 'smbtree' (my favourite). Have a look at the manpage. Something like the following should initially work: smbtree -Uvaliduser%thepassword Here a user and its password is requested - to 'browse' all the (allowed) network shares... You can fine-tune the result (a bit). Best wishes - Guenter PS - and always think twice - is there a 'local' or 'master browser' running - or not? Broadcasts can only reach the local subnet! -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Backup Tape
- Original Message - From: Sandy McCarthy [EMAIL PROTECTED] To: samba@lists.samba.org Sent: Wednesday, November 16, 2005 11:22 AM Subject: [Samba] Backup Tape I am at my final stages of switching my file server from my ageing Novell Netware 5.0 to Linux Suse SLE9. All my workstations are WinXP and Win2000 so I am relying on samba for file sharing. My last stage to resolve is having a backup strategy for the server. I already have a SCSI HP Dat drive I can install in the server but need some easy to use software to back my files. It would need to be able to keep all the file security and ACL info so if I need to restore any files, no further configuration is required. Would I need a backup solution that accommodates samba? If so, any recommendations on what software to use. I only have 10 users and my current Novell server is only at 15gb so we don't have a heavily used server. Has anyone else made the transition from Netware to Linux? In terms of administration, is their anything else I need to look out for? Thanks Sandy -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba Hi Sandy, you mention ACLs - and, if configured so, samba might store some file meta data into xattr (extended attributes). You should take care, that that info (if used) is not getting lost during backup/restore. I found that http://www.suse.de/~agruen/acl/linux-acls/online/ is very helpful regarding ACLs and EAs. There are some extra notes at the end regarding backup/restore pitfalls and possibilities. Cheers, Guenter Kukkukk -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba and ACL's
Hello Travis, Hey All, I am trying to get Samba to work with winbind and ACL's on Fedora Core 2. So far so good as far as getting winbind to work with Samba but I am having trouble getting Samba to recognize ACL's. I am wondering if there is a command I can run to determine if my Samba install is ACL capable... Any ideas? Cheers, Travis -- to use ACLs, the filesystem, on which your samba shares are located, must support xattr (extended attributes). If your kernel is compiled right and the used filesystem is mounted right, you should get xattr support. - ext3 supports xattr of max. size about 3.9 kB - reiserfs allows xattr size of max. 64 kB On SuSE 9.1, 9.2 systems xattr support is available out of the box. On other distributions you might need to ask in their own mailing lists or newsgroups. Below i append an excerpt from samba 4.0 howto.txt (written by A. Tridgell). Those suggested checks should also apply to xattr support on samba 3.0.x. Best wishes - Guenter -- excerpt from samba 4.0 howto.txt -- NOTE about filesystem support - To use the advanced features of Samba4 you need a filesystem that supports both the user and system xattr namespaces. If you run Linux with a 2.6 kernel and ext3 this means you need to include the option user_xattr in your /etc/fstab. For example: /dev/hda3 /home ext3user_xattr 1 1 You also need to compile your kernel with the XATTR and SECURITY options for your filesystem. For ext3 that means you need: CONFIG_EXT3_FS_XATTR=y CONFIG_EXT3_FS_SECURITY=y If you don't have a filesystem with xattr support, then you can simulate it by using the option: posix:eadb = /usr/local/samba/eadb.tdb that will place all extra file attributes (NT ACLs, DOS EAs, streams etc), in that tdb. It is not efficient, and doesn't scale well, but at least it gives you a choice when you don't have a modern filesystem. Testing your filesystem --- To test your filesystem support, install the 'attr' package and run the following 4 commands as root: touch test.txt setfattr -n user.test -v test test.txt setfattr -n security.test -v test2 test.txt getfattr -d test.txt getfattr -n security.test -d test.txt You should see output like this: # file: test.txt user.test=test # file: test.txt security.test=test2 If you get any Operation not supported errors then it means your kernel is not configured correctly, or your filesystem is not mounted with the right options. If you get any Operation not permitted errors then it probably means you didn't try the test as root. -- end of excerpt from samba 4.0 howto.txt-- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba 3.0 + eCS (os/2)
Hello Dietrich, Hi, I use eCS as client for samba. with samba 2.2.x I have never problems after configuration. With update my server from suse 8.1 to 9.1 was also samba changed from 2.2.x to 3.0.x. Since this I have only truble. max protocol lanman1 works without problems, only .. I have no longnames. The docs says, lanman1 is the first with long names support, also not about the pm (desktop from os2). With lanman2 (or higher) I see longnames in the commandline. I can save/create files, I can not copy this this commanline tools, only read and save as. no access about the pm, No Ideas, only dowgrade to Samba 2.2.x, this maks other truble with my wine. Dietrich a lot of work has been done by the samba team during the last weeks, to get eCS / OS/2 working right with _samba 4.0_. Samba 4.0 is the upcoming new version - a more or less complete re-write of samba with many, many new features The 4.0 release date is unknown at the moment. A. Tridgell: ... it will be released, when it is ready for release... If you need further information, you can also contact me directly at [EMAIL PROTECTED] Cheers, Guenter btw - two samba - os/2 related IRC channels have been setup on irc.freenode.net #samba-os2 #samba-os2-technical Everyone should feel free to join those channels - it's not too crowded there at the moment. :-) -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Re: Samba 3.0.4 and DOS 6.2.2 - MSDOS Copy problem
- Original Message - From: Craig Funk [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, November 16, 2004 10:20 PM Subject: Re: [Samba] Re: Samba 3.0.4 and DOS 6.2.2 - MSDOS Copy problem It also works for me on Win98,NT,W2K and XP. Only having problems on DOS 6.2.2. Unfortunately we are still stuck using DOS 6.2.2 on some machines because we have programs that do not work on DOS 7 and up. So it would be nice to get this working. So is there a different COPY command that we could use? I have found that XCOPY works but it has an annoying prompt that you have to answer telling it whether the file is a file or directory. I can also use TYPE FILENAME.DAT NEWFILE.DAT Thanks Hi Craig, could you (temporarely) set the samba debuglevel to 10? smbcontrol smbd debug 10 and redo your copy? Then post that part of your samba logfile, please. Cheers, Guenter -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba + OS/2 LS read error
- Original Message - From: Alex Masterov [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, October 22, 2004 11:11 AM Subject: [Samba] Samba + OS/2 LS read error Hello! We have Samba 3.0.7 on FreeBSD 5.2.1-RELEASE, installed from FreeBSD ports as server. There is PC with OS/2 Warp Server for E-Business (Aurora) in our LAN, it uses shared resourses from Samba. Problem: while OS/2 PC archives directories from network drives (from Samba) archivation freezes on random file about a minute, and then breaks with Read error. The same effect exists while using DBF databases on network drives from DOS FoxPro programs (returns File read error). In the moment of freezing archivation, the message Invalid secondary trans2 packet appears in the log. In Samba 2.2.8a on RedHat 7.3 everything is OK. Other computers in the network work without this problem. Here is smb.log (log level 3) [2004/10/22 15:10:03, 0] smbd/trans2.c:reply_trans2(4110) reply_trans2: Invalid secondary trans2 packet [2004/10/22 15:10:03, 3] smbd/error.c:error_packet(145) error packet at smbd/trans2.c(4293) cmd=50 (SMBtrans2) eclass=1 ecode=87 [2004/10/22 15:10:03, 3] smbd/process.c:process_smb(1092) Transaction 434366 of length 2339 [2004/10/22 15:10:03, 3] smbd/process.c:switch_message(887) switch message SMBtranss2 (pid 35438) conn 0x8325800 [skip] [2004/10/22 15:11:12, 3] smbd/process.c:timeout_processing(1332) timeout_processing: End of file from client (client has disconnected). [2004/10/22 15:11:12, 3] smbd/sec_ctx.c:set_sec_ctx(288) setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0 [2004/10/22 15:11:12, 2] smbd/server.c:exit_server(571) Closing connections [2004/10/22 15:11:12, 3] smbd/sec_ctx.c:set_sec_ctx(288) setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0 [2004/10/22 15:11:12, 1] smbd/service.c:close_cnum(837) bbs (192.168.1.204) closed connection to service foru [2004/10/22 15:11:12, 3] smbd/connection.c:yield_connection(69) Yielding connection to foru [2004/10/22 15:11:12, 3] smbd/sec_ctx.c:set_sec_ctx(288) setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0 [2004/10/22 15:11:12, 3] smbd/sec_ctx.c:set_sec_ctx(288) setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0 [2004/10/22 15:11:12, 1] smbd/service.c:close_cnum(837) bbs (192.168.1.204) closed connection to service forr [2004/10/22 15:11:12, 3] smbd/connection.c:yield_connection(69) Yielding connection to forr [2004/10/22 15:11:12, 3] smbd/sec_ctx.c:set_sec_ctx(288) setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0 [2004/10/22 15:11:12, 3] smbd/sec_ctx.c:set_sec_ctx(288) setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0 [2004/10/22 15:11:12, 1] smbd/service.c:close_cnum(837) bbs (192.168.1.204) closed connection to service forp [2004/10/22 15:11:12, 3] smbd/connection.c:yield_connection(69) Yielding connection to forp [2004/10/22 15:11:12, 3] smbd/sec_ctx.c:set_sec_ctx(288) setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0 [2004/10/22 15:11:12, 2] smbd/close.c:close_normal_file(262) alex closed file TEMP/data_pr/FK_ZAKAZ/DATA/zakaztov.dbf (numopen=0) [2004/10/22 15:11:12, 3] smbd/sec_ctx.c:set_sec_ctx(288) setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0 [2004/10/22 15:11:12, 1] smbd/service.c:close_cnum(837) bbs (192.168.1.204) closed connection to service forl [2004/10/22 15:11:12, 3] smbd/connection.c:yield_connection(69) Yielding connection to forl [2004/10/22 15:11:12, 3] smbd/sec_ctx.c:set_sec_ctx(288) setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0 [2004/10/22 15:11:12, 3] smbd/sec_ctx.c:set_sec_ctx(288) setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0 [2004/10/22 15:11:12, 1] smbd/service.c:close_cnum(837) bbs (192.168.1.204) closed connection to service fork [2004/10/22 15:11:12, 3] smbd/connection.c:yield_connection(69) Yielding connection to fork [2004/10/22 15:11:12, 3] smbd/sec_ctx.c:set_sec_ctx(288) setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0 [2004/10/22 15:11:12, 3] smbd/connection.c:yield_connection(69) Yielding connection to [2004/10/22 15:11:12, 3] smbd/server.c:exit_server(614) Server exit (normal exit) [2004/10/22 15:11:13, 2] param/loadparm.c:do_section(3407) Processing section [homes] On the client side: [...] AddingL:\TEMP\data_pr\FK_ZAKAZ\DATA\zakaztov.cdx OK AddingL:\TEMP\data_pr\FK_ZAKAZ\DATA\zakaztov.dbf 15% Read error in the file L:\TEMP\data_pr\FK_ZAKAZ\DATA\zakaztov.dbf Program aborted [G:\Archives\testarc]echo | time Current time is: 15:11:13,29 Here is my smb.conf [global] workgroup = HELMI server string = Samba Server %v on %L security = user hosts allow = 192.168. 212.94.111.33 load printers = yes admin users = root, van, alex printing = bsd log file = /var/log/samba/log.%m max log size = 5 passdb backend = tdbsam include = /usr/local/etc/smb.conf.%m
[Samba] samba 3.06rc2, suse 64amd and os2
Hi, when I tried to connect our SuSE 9.1 linux server running samba-3.0.5.1 to our anchient - but still pretty well running - OS/2 Warpserver, I ran into a lot of troubles. So I had a closer look into the samba-sources and with the help of ethereal I found some bugs, which made it impossible to talk to the OS/2 Warpserver, which is running the LANMAN2.1-protocol: On 30.07.2004 I posted a bug in the LANMAN2.1 session setup code: Summary: LANMAN2 protocol (and lower) broken in samba-3.x https://bugzilla.samba.org/show_bug.cgi?id=1571 This bug has already been fixed in 3.0.5.x by Andrew Bartlett. From now on the two machines were able to setup a session, but the linux machine was still not able to send any data to the Warpserver. Further investigation lead to another bug-report on 7.08.2004: Summary: Any writing and spooling to LANMAN2 server broken (OS/2 Warpserver) https://bugzilla.samba.org/show_bug.cgi?id=1590 This really strange looking bug *is still unresolved* - may be I should raise it to critical I did all the changes to the 3.0.5.1 source locally on my linux machine - recompiled and installed it. Now all is working as expected! Best wishes. Guenter Kukkukk -- Günter Kukkukk Entwicklungsbüro f. Informationstechnologien Damaschkestraße 24 D-10711 Berlin Tel. +49 30 327 024 50 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
