Re: [Samba] SAMBA bringing NFS server to a halt
Hey Metthew, I think you might have a chance. Did you try clearing binary data stored by samba? There's a whole bunch of stuff in tdb files in potentially more than one place (on Debian it's under /var/lib/samba). Parts are temporary data and safe to remove. Thereof cached data, connection data and I think file locking information too. Some other files contain credentials and perhaps ID mapping data you better preserve (was it secrets.tdb?). In my experience, things can become corrupted and samba fails in some way. You can always backup that stuff and try after 6 PM. Andreas On 06.03.13 12:33, Joseph, Matthew (EXP) wrote: Hello, We have a Red Hat 5.3 SAMBA 3.0.33-3.7 Server that shares a few directories to 4 other servers. The other servers are Red Hat 5.3 and one Solaris 10 server. I configured SAMBA to do the following for each share; Force User: User1 Force Group: Group1 Create Mask: 02770 Security Mask: 02770 Directory Mask: 02770 Directory Security Mask: 02770 Inherit Permissions: Yes Inherit ACLS: Yes Inherit Owner: Yes Guest Okay: Yes When the other servers mount the SAMBA shares they work fine until someone starts using SVN or Eclipse. This brings the SAMBA server to basically a halt. Looking at the processes I see about 15000 instances of SMB running. I try running top to see a list of processes but it takes about 10 minutes for it to start and then it will hang when it tries to do its first refresh. Looking at the logs I don't see anything that really stands out on why it is slowing down. Is there something I'm doing wrong in this configuration? Thanks. -- Andreas Gaiser Berlin -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] SAMBA bringing NFS server to a halt
Hello, We have a Red Hat 5.3 SAMBA 3.0.33-3.7 Server that shares a few directories to 4 other servers. The other servers are Red Hat 5.3 and one Solaris 10 server. I configured SAMBA to do the following for each share; Force User: User1 Force Group: Group1 Create Mask: 02770 Security Mask: 02770 Directory Mask: 02770 Directory Security Mask: 02770 Inherit Permissions: Yes Inherit ACLS: Yes Inherit Owner: Yes Guest Okay: Yes When the other servers mount the SAMBA shares they work fine until someone starts using SVN or Eclipse. This brings the SAMBA server to basically a halt. Looking at the processes I see about 15000 instances of SMB running. I try running top to see a list of processes but it takes about 10 minutes for it to start and then it will hang when it tries to do its first refresh. Looking at the logs I don't see anything that really stands out on why it is slowing down. Is there something I'm doing wrong in this configuration? Thanks. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] SAMBA bringing NFS server to a halt
On Wed, 2013-03-06 at 06:33 -0500, Joseph, Matthew (EXP) wrote: Hello, We have a Red Hat 5.3 SAMBA 3.0.33-3.7 Server that shares a few directories to 4 other servers. The other servers are Red Hat 5.3 and one Solaris 10 server. Stop right there. Nobody here could care less about someone running a wildly out of date server. There are numerous NFS and Samba fixes in RHEL 5.9 over 5.3 some of which are critical bugs, performance issues and others are ones that make your box open to remote root compromises. Upgrade to RHEL 5.9 and get back if you still have a problem. JAB. -- Jonathan A. Buzzard Email: jonathan (at) buzzard.me.uk Fife, United Kingdom. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] SAMBA bringing NFS server to a halt
I disagree. There can be many reasons why using a later version of a system or an application is not possible. Just as an example, I manage a number of UNIX servers running a range of very old OSes - Solaris 8, AIX 4 and others. I think the oldest operating system we have is a version of MPE/iX. That is part of how we make money. Apart from that, your tone seems to suggest that your mission is not to help and support, but to put somebody down and make them feel stupid; not very commendable, I think. /jan From: samba-boun...@lists.samba.org [samba-boun...@lists.samba.org] on behalf of Jonathan Buzzard [jonat...@buzzard.me.uk] Sent: 06 March 2013 13:02 To: Joseph, Matthew (EXP) Cc: samba@lists.samba.org Subject: Re: [Samba] SAMBA bringing NFS server to a halt On Wed, 2013-03-06 at 06:33 -0500, Joseph, Matthew (EXP) wrote: Hello, We have a Red Hat 5.3 SAMBA 3.0.33-3.7 Server that shares a few directories to 4 other servers. The other servers are Red Hat 5.3 and one Solaris 10 server. Stop right there. Nobody here could care less about someone running a wildly out of date server. There are numerous NFS and Samba fixes in RHEL 5.9 over 5.3 some of which are critical bugs, performance issues and others are ones that make your box open to remote root compromises. Upgrade to RHEL 5.9 and get back if you still have a problem. JAB. -- Jonathan A. Buzzard Email: jonathan (at) buzzard.me.uk Fife, United Kingdom. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] samba over nfs mount and free space problem
On 03/19/2012 10:30 PM, Alex Mestiashvili wrote:
On 03/19/2012 08:35 PM, Volker Lendecke wrote:
On Mon, Mar 19, 2012 at 03:55:44PM +0100, Alex Mestiashvili wrote:
dfree command also didn't help.
The dfree command should always help. You could fake 100GB
free space always.
Volker
Hi,
that is my dfree command ( I added simple logging )
#!/bin/sh
/usr/sbin/df -k $1 | /usr/bin/tail -1 | /opt/csw/bin/gawk '{print $2
$4}'
/bin/echo $1 | /usr/bin/logger -t smbd_dfree_args -p local7.notice
/bin/echo `pwd` | /usr/bin/logger -t smbd_dfree_cwd -p local7.notice
the output is like that :
$/usr/local/bin/dfree
629145600 354102404
df output for nfs share looks like that:
df -k |head-1
Filesystemkbytesused avail capacity Mounted on
cd /home/mygroup/myuser
df -k .
nfsserver:/users/myuser
629145600 275043196 35410240444%
/home/mygroup/myuser
df -k for local fs:
localzfs/users/myuser
1948778496 42750990 914183310 5%
/home/mygroup/myuser
nevertheless when I access nfs share via samba I get no free space .
with local fs it is ok .
The same happens in windows when one maps a network drive.
I will check again tomorrow, but may be I am missing something simple
and obvious ?
Thank you,
Alex
I changed dfree script to the very simple one:
#cat dfree
#!/bin/sh
echo 524150168 524150168
now if I access a share which is a local filesystem to the samba server
I get with df -h :
Size 500G Used 0B Available 500Gi
so dfree works fine in that case.
if I access via smb nfs mounted filesystem I get totally different result:
Size 186M Used 186M Available 0B
So obviously dfree doen't work in this case .
What else mechanism is used to determine share size ?
Thank you,
Alex
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
[Samba] samba over nfs mount and free space problem
Hi All, I see a strange behavior with samba server and nfs mounts. We have a number of shares mounted via nfs on the smabaserver. When I connect from apple mac computers to a samba share which is an nfs mountpoint, the free space of the share is reported as zero. And obviously Finder is not able to copy anything to the share because it thinks that there is no free space left. But copy from the terminal works fine! In case when samba share is a local filesystem everything works just fine. I tried max disk size option, but is didn't work for NFS, but worked for a local filesystem. Didn't work means that available space was reported as zero and I couldn't copy file to the share. That's why I think that the problem is somehow samba related and not the apple software. dfree command also didn't help. Why there is a difference between the way free space is calculated between nfs and local filesystems ? And what else can I try to workaround this problem ? here is the output of smbd -b http://www.biotec.tu-dresden.de/~alex/smb_build_options.txt Thank you in advance, Alex -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] samba over nfs mount and free space problem
On Mon, Mar 19, 2012 at 03:55:44PM +0100, Alex Mestiashvili wrote: dfree command also didn't help. The dfree command should always help. You could fake 100GB free space always. Volker -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] samba over nfs mount and free space problem
On 03/19/2012 08:35 PM, Volker Lendecke wrote:
On Mon, Mar 19, 2012 at 03:55:44PM +0100, Alex Mestiashvili wrote:
dfree command also didn't help.
The dfree command should always help. You could fake 100GB
free space always.
Volker
Hi,
that is my dfree command ( I added simple logging )
#!/bin/sh
/usr/sbin/df -k $1 | /usr/bin/tail -1 | /opt/csw/bin/gawk '{print $2 $4}'
/bin/echo $1 | /usr/bin/logger -t smbd_dfree_args -p local7.notice
/bin/echo `pwd` | /usr/bin/logger -t smbd_dfree_cwd -p local7.notice
the output is like that :
$/usr/local/bin/dfree
629145600 354102404
df output for nfs share looks like that:
df -k |head-1
Filesystemkbytesused avail capacity Mounted on
cd /home/mygroup/myuser
df -k .
nfsserver:/users/myuser
629145600 275043196 35410240444%
/home/mygroup/myuser
df -k for local fs:
localzfs/users/myuser
1948778496 42750990 914183310 5%
/home/mygroup/myuser
nevertheless when I access nfs share via samba I get no free space .
with local fs it is ok .
The same happens in windows when one maps a network drive.
I will check again tomorrow, but may be I am missing something simple
and obvious ?
Thank you,
Alex
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] samba CPD nfs lock
Well, I put my home and profile data on a local partition again after migration. Much faster and no more oplock problem. Seems that mouting partition over nfs is not so usual for samba Thanks for your advice Sébastien Prouff _ Responsable du pôle TICE CDDP de la Charente Maritime tel : 05 46 00 34 73 http://web.crdp-poitiers.org/cddp17 Le 10/01/2012 12:40, Volker Lendecke a écrit : On Tue, Jan 10, 2012 at 11:49:23AM +0100, sebastien PROUFF wrote: Hi all, I got a problem after a samba CPD migration. here is configuration before migration : OS : ubuntu 10.04 samba/LDAP CPD home, profile share on a local disk Here is the configuration after migration OS : debian squeeze samba/LDAP CPD( migration of sid and ldap directory succesful) home and profile share on a nfs share. Try kernel oplocks = no and posix locking = no. Much less intrusive than locking = no. Volker -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] samba CPD nfs lock
Hi all, I got a problem after a samba CPD migration. here is configuration before migration : OS : ubuntu 10.04 samba/LDAP CPD home, profile share on a local disk Here is the configuration after migration OS : debian squeeze samba/LDAP CPD( migration of sid and ldap directory succesful) home and profile share on a nfs share. What's works : connexion to the domain, file creation. What's does not work When i open a file on my home share, modify and record it, it does not work. I got a message like another process accessing to the file so this process can't access to!) What I did ? I modified my smb.conf and add locking = no to the home and profile share. So, my questions are : - is it a known issue ? - is it possible to have my home and profile on a nfs share ? If yes, what did I miss to get it work properly? - is it dangerous to enable locking = no for these share ? ( because only the authentificated user can access to these share ) Thank you for your advice Sébastien -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] samba CPD nfs lock
On Tue, Jan 10, 2012 at 11:49:23AM +0100, sebastien PROUFF wrote: Hi all, I got a problem after a samba CPD migration. here is configuration before migration : OS : ubuntu 10.04 samba/LDAP CPD home, profile share on a local disk Here is the configuration after migration OS : debian squeeze samba/LDAP CPD( migration of sid and ldap directory succesful) home and profile share on a nfs share. Try kernel oplocks = no and posix locking = no. Much less intrusive than locking = no. Volker -- SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen phone: +49-551-37-0, fax: +49-551-37-9 AG Göttingen, HRB 2816, GF: Dr. Johannes Loxen http://www.sernet.de, mailto:kont...@sernet.de -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] samba with nfs mount in path and MS Office App's
This is a item concerning locking and msoffice-files, nfs. I bet not msoffice-files are working. Disable locking on the nfs shares and it should work. --- EDV Daniel Müller Leitung EDV Tropenklinik Paul-Lechler-Krankenhaus Paul-Lechler-Str. 24 72076 Tübingen Tel.: 07071/206-463, Fax: 07071/206-499 eMail: muel...@tropenklinik.de Internet: www.tropenklinik.de --- -Ursprüngliche Nachricht- Von: samba-boun...@lists.samba.org [mailto:samba-boun...@lists.samba.org] Im Auftrag von Robert Adkins II Gesendet: Mittwoch, 12. Oktober 2011 16:36 An: free...@gmx.ch; samba@lists.samba.org Betreff: Re: [Samba] samba with nfs mount in path and MS Office App's Review all of your permissions and confirm that those permissions are the same for all users having this issues on the server that is sharing the NFS share. I have a feeling that this is a share/permissions issue as much as it could be an NFS share issue. -- Regards, Robert Adkins -Original Message- From: samba-boun...@lists.samba.org [mailto:samba-boun...@lists.samba.org] On Behalf Of free...@gmx.ch Sent: Wednesday, October 12, 2011 10:30 AM To: samba@lists.samba.org Subject: [Samba] samba with nfs mount in path and MS Office App's Hi Listmembers Problem: Windows Clients having problems with Microsoft Office App's (Excel, Word) when the files are on the Samba Share documents (which is mapped through a Windows Drive Letter on the client). Two clients have MS Office 2003. They can open doc Documents but when they want to save it error messages are appearing (message about to less space on drive, but this is a false errormessage). Saving of documents does not work and MS Office crashes. Sometimes Word is crashing already when the user opens a document. Same with XLS document. One client has MS Office 2010. He can open and save changes in Microsoft Office Documents. But saving changes, even small ones, are taking 30 seconds. Clients which are using Open Office having no problems. They can even open and saving the MS Office document without Problem. Also with other Applications there are no problems (ex. opening pdf documents, txt documents with notepad etc.). So the problems occurs only while working with this share documents and using Microsoft Office. I've got another share on the same Samba Server named personal. The Microsoft Office clients have no problems on this share. The only difference is that the path from personal share in smb.conf is not a NFS Mount but a location on the harddisk of the server itselve (ext3 partition). So the problem has something to do with using Samba shares which have their path on NFS Mounts. System environment: Centos 5.x Server Samba Version 3.0.33 ***Samba Config [global] workgroup = OfficeLAN server string = qube2 lanman auth = Yes client NTLMv2 auth = Yes time server = Yes add machine script = /usr/sbin/useradd -d /dev/null -g samba-clients -s /bin/false -M %u logon script = %U.bat logon drive = M: logon home = \\%N\profiles\%U logon path = domain logons = Yes os level = 65 preferred master = Yes domain master = Yes wins server = 10.0.10.12 wins support = Yes ldap ssl = no admin users = @sysadmin printer admin = @sysadmin cups options = raw [documents] comment = documents path = /home/nfs_qube2/documents force user = admin read only = No guest ok = Yes *** The documents share is on a NFS Mount which is mounted in /etc/fstab 10.0.10.13:/vol/nfs_qube2/office-data /home/nfs_qube2 nfs rw,bg,vers=3,tcp,timeo=600,rsize=32768,wsize=32768,hard,intr Thanks for any advice -- NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurück-Garantie! Jetzt informieren: http://www.gmx.net/de/go/freephone -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] samba with nfs mount in path and MS Office App's
Hi Thanks for the input so far So far i've tried following: Setting *** strict locking = yes oplocks = no *** in Smb.conf. This didnt work. Then i've tried to mount the nfs with nolock Option (but without above samba locking parameters). Problems still persists. I've need now to test some combinations of these settings. I've also talked to a Netapp Engineer. The NFS Mount points to a FAS3140 Cluster with Ontap 7.3.2 on it. The volume with the data which is referred in path of Samba config is a qtree. There are three different types of qtree security settings on Netapp Files: mixed,unix,windows. It might have something to do with the choosen security style. Netapp itself is using NFS3 (nfs4 can be turned on optionally): http://www.netapp.com/us/communities/tech-ontap/nfsv4-0408.html I've also tried some setfacl commands on the nfs mount and it said: Operation not supported... So i've got several possible reasons for the problem now: - samba config (locking parameters) - nfs mount options (locking parameters) - Right issues (acl or similiar) - qtree securtity style on Netapp I will test some things and let you knowi will start with the netapp qtree issues... Best Regards -- NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurück-Garantie! Jetzt informieren: http://www.gmx.net/de/go/freephone -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] samba with nfs mount in path and MS Office App's
Is the samba server your PDC? Maybe the trick is to use the NetApp as a windows server- if you can join it to the Samba domain. On 10/13/2011 07:38 AM, free...@gmx.ch wrote: Hi Thanks for the input so far So far i've tried following: Setting *** strict locking = yes oplocks = no *** in Smb.conf. This didnt work. Then i've tried to mount the nfs with nolock Option (but without above samba locking parameters). Problems still persists. I've need now to test some combinations of these settings. I've also talked to a Netapp Engineer. The NFS Mount points to a FAS3140 Cluster with Ontap 7.3.2 on it. The volume with the data which is referred in path of Samba config is a qtree. There are three different types of qtree security settings on Netapp Files: mixed,unix,windows. It might have something to do with the choosen security style. Netapp itself is using NFS3 (nfs4 can be turned on optionally): http://www.netapp.com/us/communities/tech-ontap/nfsv4-0408.html I've also tried some setfacl commands on the nfs mount and it said: Operation not supported... So i've got several possible reasons for the problem now: - samba config (locking parameters) - nfs mount options (locking parameters) - Right issues (acl or similiar) - qtree securtity style on Netapp I will test some things and let you knowi will start with the netapp qtree issues... Best Regards -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] samba with nfs mount in path and MS Office App's
Hi Is the samba server your PDC? No. Actually i have no domain. The samba shares are only for a few internal clients which are in the same workgroup as the Samba Server. But it looks like i've found the problem. I have now made a test with another volume on the Netapp which has qtree security style mixed (the live volume has qtree security style unix). This test volume i have mounted on the Samba Server with nolock option in NFS Options. It looks like this solved the problem because on this test volume the problems doesnt exists. In another test i've also tried qtree security style ntfs but this did not work at all...the clients did not even had access to this second test. So it seems the qtree security style on the Netapp NFS Export Volume was the problem; maybe in connection with the nolock NFS Options. I've to observe it further but for now it looks like the problem is solved. Thanks for help -- NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurück-Garantie! Jetzt informieren: http://www.gmx.net/de/go/freephone -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] samba with nfs mount in path and MS Office App's
Hi Listmembers Problem: Windows Clients having problems with Microsoft Office App's (Excel, Word) when the files are on the Samba Share documents (which is mapped through a Windows Drive Letter on the client). Two clients have MS Office 2003. They can open doc Documents but when they want to save it error messages are appearing (message about to less space on drive, but this is a false errormessage). Saving of documents does not work and MS Office crashes. Sometimes Word is crashing already when the user opens a document. Same with XLS document. One client has MS Office 2010. He can open and save changes in Microsoft Office Documents. But saving changes, even small ones, are taking 30 seconds. Clients which are using Open Office having no problems. They can even open and saving the MS Office document without Problem. Also with other Applications there are no problems (ex. opening pdf documents, txt documents with notepad etc.). So the problems occurs only while working with this share documents and using Microsoft Office. I've got another share on the same Samba Server named personal. The Microsoft Office clients have no problems on this share. The only difference is that the path from personal share in smb.conf is not a NFS Mount but a location on the harddisk of the server itselve (ext3 partition). So the problem has something to do with using Samba shares which have their path on NFS Mounts. System environment: Centos 5.x Server Samba Version 3.0.33 ***Samba Config [global] workgroup = OfficeLAN server string = qube2 lanman auth = Yes client NTLMv2 auth = Yes time server = Yes add machine script = /usr/sbin/useradd -d /dev/null -g samba-clients -s /bin/false -M %u logon script = %U.bat logon drive = M: logon home = \\%N\profiles\%U logon path = domain logons = Yes os level = 65 preferred master = Yes domain master = Yes wins server = 10.0.10.12 wins support = Yes ldap ssl = no admin users = @sysadmin printer admin = @sysadmin cups options = raw [documents] comment = documents path = /home/nfs_qube2/documents force user = admin read only = No guest ok = Yes *** The documents share is on a NFS Mount which is mounted in /etc/fstab 10.0.10.13:/vol/nfs_qube2/office-data /home/nfs_qube2 nfs rw,bg,vers=3,tcp,timeo=600,rsize=32768,wsize=32768,hard,intr Thanks for any advice -- NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurück-Garantie! Jetzt informieren: http://www.gmx.net/de/go/freephone -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] samba with nfs mount in path and MS Office App's
Review all of your permissions and confirm that those permissions are the same for all users having this issues on the server that is sharing the NFS share. I have a feeling that this is a share/permissions issue as much as it could be an NFS share issue. -- Regards, Robert Adkins -Original Message- From: samba-boun...@lists.samba.org [mailto:samba-boun...@lists.samba.org] On Behalf Of free...@gmx.ch Sent: Wednesday, October 12, 2011 10:30 AM To: samba@lists.samba.org Subject: [Samba] samba with nfs mount in path and MS Office App's Hi Listmembers Problem: Windows Clients having problems with Microsoft Office App's (Excel, Word) when the files are on the Samba Share documents (which is mapped through a Windows Drive Letter on the client). Two clients have MS Office 2003. They can open doc Documents but when they want to save it error messages are appearing (message about to less space on drive, but this is a false errormessage). Saving of documents does not work and MS Office crashes. Sometimes Word is crashing already when the user opens a document. Same with XLS document. One client has MS Office 2010. He can open and save changes in Microsoft Office Documents. But saving changes, even small ones, are taking 30 seconds. Clients which are using Open Office having no problems. They can even open and saving the MS Office document without Problem. Also with other Applications there are no problems (ex. opening pdf documents, txt documents with notepad etc.). So the problems occurs only while working with this share documents and using Microsoft Office. I've got another share on the same Samba Server named personal. The Microsoft Office clients have no problems on this share. The only difference is that the path from personal share in smb.conf is not a NFS Mount but a location on the harddisk of the server itselve (ext3 partition). So the problem has something to do with using Samba shares which have their path on NFS Mounts. System environment: Centos 5.x Server Samba Version 3.0.33 ***Samba Config [global] workgroup = OfficeLAN server string = qube2 lanman auth = Yes client NTLMv2 auth = Yes time server = Yes add machine script = /usr/sbin/useradd -d /dev/null -g samba-clients -s /bin/false -M %u logon script = %U.bat logon drive = M: logon home = \\%N\profiles\%U logon path = domain logons = Yes os level = 65 preferred master = Yes domain master = Yes wins server = 10.0.10.12 wins support = Yes ldap ssl = no admin users = @sysadmin printer admin = @sysadmin cups options = raw [documents] comment = documents path = /home/nfs_qube2/documents force user = admin read only = No guest ok = Yes *** The documents share is on a NFS Mount which is mounted in /etc/fstab 10.0.10.13:/vol/nfs_qube2/office-data /home/nfs_qube2 nfs rw,bg,vers=3,tcp,timeo=600,rsize=32768,wsize=32768,hard,intr Thanks for any advice -- NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurück-Garantie! Jetzt informieren: http://www.gmx.net/de/go/freephone -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] samba with nfs mount in path and MS Office App's
I believe I remember seeing a similar thread and it was disabling oplocks in samba ? On 10/12/2011 10:30 AM, free...@gmx.ch wrote: Hi Listmembers Problem: Windows Clients having problems with Microsoft Office App's (Excel, Word) when the files are on the Samba Share documents (which is mapped through a Windows Drive Letter on the client). Two clients have MS Office 2003. They can open doc Documents but when they want to save it error messages are appearing (message about to less space on drive, but this is a false errormessage). Saving of documents does not work and MS Office crashes. Sometimes Word is crashing already when the user opens a document. Same with XLS document. One client has MS Office 2010. He can open and save changes in Microsoft Office Documents. But saving changes, even small ones, are taking 30 seconds. Clients which are using Open Office having no problems. They can even open and saving the MS Office document without Problem. Also with other Applications there are no problems (ex. opening pdf documents, txt documents with notepad etc.). So the problems occurs only while working with this share documents and using Microsoft Office. I've got another share on the same Samba Server named personal. The Microsoft Office clients have no problems on this share. The only difference is that the path from personal share in smb.conf is not a NFS Mount but a location on the harddisk of the server itselve (ext3 partition). So the problem has something to do with using Samba shares which have their path on NFS Mounts. System environment: Centos 5.x Server Samba Version 3.0.33 ***Samba Config [global] workgroup = OfficeLAN server string = qube2 lanman auth = Yes client NTLMv2 auth = Yes time server = Yes add machine script = /usr/sbin/useradd -d /dev/null -g samba-clients -s /bin/false -M %u logon script = %U.bat logon drive = M: logon home = \\%N\profiles\%U logon path = domain logons = Yes os level = 65 preferred master = Yes domain master = Yes wins server = 10.0.10.12 wins support = Yes ldap ssl = no admin users = @sysadmin printer admin = @sysadmin cups options = raw [documents] comment = documents path = /home/nfs_qube2/documents force user = admin read only = No guest ok = Yes *** The documents share is on a NFS Mount which is mounted in /etc/fstab 10.0.10.13:/vol/nfs_qube2/office-data /home/nfs_qube2 nfs rw,bg,vers=3,tcp,timeo=600,rsize=32768,wsize=32768,hard,intr Thanks for any advice -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] samba with nfs mount in path and MS Office App's
I have Solaris 10. I used to use UFS for the file system - which is I think similar enough to ext3 for this situation. It supports the basic ugo perms as well as some ACL's.In general, a samba share on top of an autofs mount was OK. For example, the H: drive would be mapped to /home on server1, which in turn would include user home directories from server1 or server2. I actually ran into a lot more problems when I switched to ZFS file system which is closer to Windows 200x/XP etc. It did help identify what Office would try to do. Microsoft office likes to change the permissions on existing files. It will also sometimes delete a file and rewrite all the data to a new file (with the same name as the old file.) This means that not only does MS Office have to be able to write to the file, it has to have permissions on the parent directory to create files and set change the access control entries. Does getfacl and setfacl under linux work on the NFS directories and files? Are you mounting the nfs directory via NFS v3 or NFS v4. NFS v3 is the default. NFS v4 shd allow acl's to be maintained. Does documents have to be NFS or can you use a direct path? -Original Message- From: samba-boun...@lists.samba.org [mailto:samba-boun...@lists.samba.org] On Behalf Of free...@gmx.ch Sent: Wednesday, October 12, 2011 10:30 AM To: samba@lists.samba.org Subject: [Samba] samba with nfs mount in path and MS Office App's Hi Listmembers Problem: Windows Clients having problems with Microsoft Office App's (Excel, Word) when the files are on the Samba Share documents (which is mapped through a Windows Drive Letter on the client). Two clients have MS Office 2003. They can open doc Documents but when they want to save it error messages are appearing (message about to less space on drive, but this is a false errormessage). Saving of documents does not work and MS Office crashes. Sometimes Word is crashing already when the user opens a document. Same with XLS document. One client has MS Office 2010. He can open and save changes in Microsoft Office Documents. But saving changes, even small ones, are taking 30 seconds. Clients which are using Open Office having no problems. They can even open and saving the MS Office document without Problem. Also with other Applications there are no problems (ex. opening pdf documents, txt documents with notepad etc.). So the problems occurs only while working with this share documents and using Microsoft Office. I've got another share on the same Samba Server named personal. The Microsoft Office clients have no problems on this share. The only difference is that the path from personal share in smb.conf is not a NFS Mount but a location on the harddisk of the server itselve (ext3 partition). So the problem has something to do with using Samba shares which have their path on NFS Mounts. System environment: Centos 5.x Server Samba Version 3.0.33 ***Samba Config [global] workgroup = OfficeLAN server string = qube2 lanman auth = Yes client NTLMv2 auth = Yes time server = Yes add machine script = /usr/sbin/useradd -d /dev/null -g samba-clients -s /bin/false -M %u logon script = %U.bat logon drive = M: logon home = \\%N\profiles\%U logon path = domain logons = Yes os level = 65 preferred master = Yes domain master = Yes wins server = 10.0.10.12 wins support = Yes ldap ssl = no admin users = @sysadmin printer admin = @sysadmin cups options = raw [documents] comment = documents path = /home/nfs_qube2/documents force user = admin read only = No guest ok = Yes *** The documents share is on a NFS Mount which is mounted in /etc/fstab 10.0.10.13:/vol/nfs_qube2/office-data /home/nfs_qube2 nfs rw,bg,vers=3,tcp,timeo=600,rsize=32768,wsize=32768,hard,intr Thanks for any advice -- NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurück-Garantie! Jetzt informieren: http://www.gmx.net/de/go/freephone -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba Serving NFS Mounted Directories
On 1/23/2010 5:19 AM, Nicholas Brealey wrote: The Sun 7310 is a storage appliance. It is not running Solaris 10 but runs an OS based on Open Solaris with CIFS and Windows style authentication integrated in the kernel. I lied a little. I do know how to login to this box, but that's only because a Sun support person told me how. This was necessary to fix a non-Samba related problem. It sure looks like Solaris to me. In any case, I had to promise I wouldn't make any changes that weren't authorized by Sun. I intend on keeping this promise. Installing Samba is not an option. I agree 100%. You really should be using the integrated CIFs server. It is probably simpler to set up than Samba but is probably not as flexible (has fewer configuration options). I'm not sure how simple it is to setup. For example, I couldn't even figure out what share name it generates. Although the performance and price of the 7310 are excellent, its documentation is not. There is a simulator you can play with to learn how to set it up. I know. I used it when I was deciding whether to buy the 7310. The manual is available on the Internet or from the storage device. The manual is just the help system on the device, as you say. It says very little about how to set up CIFS shares. There is a forum where these devices are discussed. You almost certainly got a support contract when you bough the device. I didn't know about a support forum. I'll check into that. I do have a support contract but if it's necessary to call support for something as simple as this, then somebody has blown it - either Sun or me. If you cannot use its CIFS server (ie if you are using a NT 4 style domain or a Samba PDC) perhaps using iSCSI to the Linux box and sharing with Samba is the next best option. None of these apply. Besides, I'd still like to understand the fundamental issue, which is why Samba behaves differently when it server NFS mounts than it does when it serves local files. http://forums.sun.com/forum.jspa?forumID=831 I'll check there. Thanks. Cordially, -- Jon Forrest Research Computing Support College of Chemistry 173 Tan Hall University of California Berkeley Berkeley, CA 94720-1460 510-643-1032 jlforr...@berkeley.edu -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba Serving NFS Mounted Directories
On 1/23/2010 12:48 AM, Volker Lendecke wrote: You need to get over that. Running Samba on NFS imports is a really bad idea. At least every month people report strange lockups, timeouts and other weird things on this list that can be attributed to NFS imports. I'm not doubting that what you say is true, since I've seen it myself, but whenever possible I try to get deeper understanding of what causes these strange problems. That's one of the reasons why I posted my question. So, I'll restate the question - what is it about NFS exports that gives Samba trouble that doesn't occur when serving local files? Cordially, -- Jon Forrest Research Computing Support College of Chemistry 173 Tan Hall University of California Berkeley Berkeley, CA 94720-1460 510-643-1032 jlforr...@berkeley.edu -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba Serving NFS Mounted Directories
On 1/22/2010 5:00 PM, Ray Van Dolson wrote: First of all, you really don't want to re-export NFS mounts via Samba. I can't argue with this since I've felt the pain. However, I still can't say that I understand its fundamental cause. Here's my current understanding. Assuming that network bandwidth isn't an issue, which it isn't in my case, then, the lockups, timeouts, and other weird things that occur must be because related to how Samba emulates Windows' locking behavior on top of NFS mounts, which have their own locking semantics. Although I'd be the first to admit that what I'm doing isn't very common, and probably doesn't deserve much, if any, attention from the Samba developers, I think that this should work - at least it should work better than it currently does. Secondly, if you absolutely must do it, I recommend the following settings: [global] # your other options here... oplocks = No level2 oplocks = No On certain shares, you may want to set: posix locking = No These settings seem to do the trick. I sincerely appreciate the comments that I received on this issue. I hope bring this up helps other people facing this problem, if any. Cordially, -- Jon Forrest Research Computing Support College of Chemistry 173 Tan Hall University of California Berkeley Berkeley, CA 94720-1460 510-643-1032 jlforr...@berkeley.edu -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba Serving NFS Mounted Directories
Hallo, Jon, Du meintest am 25.01.10: First of all, you really don't want to re-export NFS mounts via Samba. I can't argue with this since I've felt the pain. I have tried it (NFS mount as share). Sometimes it run, sometimes it creeped, sometimes it was dead. All oplocks were set as recommended - wasn't enough to cure the system. Mounting per cifs: no more problems. Viele Gruesse! Helmut -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba Serving NFS Mounted Directories
On Sat, Jan 23, 2010 at 10:33:36AM -0800, Jon Forrest wrote: So, I'll restate the question - what is it about NFS exports that gives Samba trouble that doesn't occur when serving local files? Mostly it is locking problems. Some daemons not started, daemons not 100% working right, etc. Then it is also a big performance drain. Sending data over the net twice without proper caching is really subobptimal. Then, potentially not all features fully supported (EAs, ACLs, etc). This is just a pain in the neck. And, for us here on this list it is a pain because all those problems show up for the Samba clients, so by definition those bugs appear to be Samba bugs while they are NFS problems. Volker -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba Serving NFS Mounted Directories
On Fri, Jan 22, 2010 at 04:49:33PM -0800, Jon Forrest wrote: I have a Sun 7310 storage server. This is running Solaris 10 but it's self-contained and I can't login to it or run Samba on it. I manage it with a web interface. You need to get over that. Running Samba on NFS imports is a really bad idea. At least every month people report strange lockups, timeouts and other weird things on this list that can be attributed to NFS imports. You should really contact SUN for information how to log into that box and install Samba. Volker signature.asc Description: Digital signature -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba Serving NFS Mounted Directories
The Sun 7310 is a storage appliance. It is not running Solaris 10 but runs an OS based on Open Solaris with CIFS and Windows style authentication integrated in the kernel. Installing Samba is not an option. You really should be using the integrated CIFs server. It is probably simpler to set up than Samba but is probably not as flexible (has fewer configuration options). There is a simulator you can play with to learn how to set it up. Sun offer courses on setting it up. Sun offer a service to set it up for you. The manual is available on the Internet or from the storage device. There is a forum where these devices are discussed. You almost certainly got a support contract when you bough the device. If you cannot use its CIFS server (ie if you are using a NT 4 style domain or a Samba PDC) perhaps using iSCSI to the Linux box and sharing with Samba is the next best option. See: http://wikis.sun.com/display/FishWorks/Fishworks http://forums.sun.com/forum.jspa?forumID=831 Nick Jon Forrest wrote: I have a Sun 7310 storage server. This is running Solaris 10 but it's self-contained and I can't login to it or run Samba on it. I manage it with a web interface. I have a CentOS 5.3 machine that mounts a bunch of file systems via NFS from the Sun server. This works fine. I installed Samba 3.4.5 on the CentOS machine and configured it to share some of the directories that are actually NFS mounts from the Sun server. I'm able to map these directories from both Windows XP and Windows 7. I'm seeing several problems: 1) Accessing the mapped directories from Windows when running Microsoft Office apps is extremely slow. I don't have any exact numbers but let's say the speed is unusable. Ironically, other programs, such as 'vim' and 'notepad' don't have this speed problem when accessing the same shares. 2) Again, using Microsoft Office apps, Windows XP machines see files as read-only. Windows 7 works fine on the same files. The Sun has a non-Samba CIFS implementation but it's non-intuitive to set up so I haven't tried it. I'm wondering if what I describe should work. Here's the smb.conf configuration for the share: [bgroup] valid users = bgroup path = /home/bgroup public = no writeable = yes browseable = no create mask = 012 create mode = 0660 directory mode = 0770 Any comments or suggestions? Cordially, -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Samba Serving NFS Mounted Directories
I have a Sun 7310 storage server. This is running Solaris 10 but it's self-contained and I can't login to it or run Samba on it. I manage it with a web interface. I have a CentOS 5.3 machine that mounts a bunch of file systems via NFS from the Sun server. This works fine. I installed Samba 3.4.5 on the CentOS machine and configured it to share some of the directories that are actually NFS mounts from the Sun server. I'm able to map these directories from both Windows XP and Windows 7. I'm seeing several problems: 1) Accessing the mapped directories from Windows when running Microsoft Office apps is extremely slow. I don't have any exact numbers but let's say the speed is unusable. Ironically, other programs, such as 'vim' and 'notepad' don't have this speed problem when accessing the same shares. 2) Again, using Microsoft Office apps, Windows XP machines see files as read-only. Windows 7 works fine on the same files. The Sun has a non-Samba CIFS implementation but it's non-intuitive to set up so I haven't tried it. I'm wondering if what I describe should work. Here's the smb.conf configuration for the share: [bgroup] valid users = bgroup path = /home/bgroup public = no writeable = yes browseable = no create mask = 012 create mode = 0660 directory mode = 0770 Any comments or suggestions? Cordially, -- Jon Forrest Research Computing Support College of Chemistry 173 Tan Hall University of California Berkeley Berkeley, CA 94720-1460 510-643-1032 jlforr...@berkeley.edu -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba Serving NFS Mounted Directories
On Fri, Jan 22, 2010 at 04:49:33PM -0800, Jon Forrest wrote: I have a Sun 7310 storage server. This is running Solaris 10 but it's self-contained and I can't login to it or run Samba on it. I manage it with a web interface. I have a CentOS 5.3 machine that mounts a bunch of file systems via NFS from the Sun server. This works fine. I installed Samba 3.4.5 on the CentOS machine and configured it to share some of the directories that are actually NFS mounts from the Sun server. I'm able to map these directories from both Windows XP and Windows 7. I'm seeing several problems: 1) Accessing the mapped directories from Windows when running Microsoft Office apps is extremely slow. I don't have any exact numbers but let's say the speed is unusable. Ironically, other programs, such as 'vim' and 'notepad' don't have this speed problem when accessing the same shares. 2) Again, using Microsoft Office apps, Windows XP machines see files as read-only. Windows 7 works fine on the same files. The Sun has a non-Samba CIFS implementation but it's non-intuitive to set up so I haven't tried it. I'm wondering if what I describe should work. Here's the smb.conf configuration for the share: [bgroup] valid users = bgroup path = /home/bgroup public = no writeable = yes browseable = no create mask = 012 create mode = 0660 directory mode = 0770 Any comments or suggestions? Cordially, First of all, you really don't want to re-export NFS mounts via Samba. Secondly, if you absolutely must do it, I recommend the following settings: [global] # your other options here... oplocks = No level2 oplocks = No On certain shares, you may want to set: posix locking = No Ray -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba, and NFS. lag?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 That hasnt helped either. Same lag on file modification. Thanks. On 01/16/2010 05:46 AM, Volker Lendecke wrote: On Fri, Jan 15, 2010 at 03:20:36PM -0500, Nathan Lager wrote: Any suggestions? Anything i can check? Am i perhaps looking an an NFS performance issue? I'm able to modify files over the nfs mount from the smb server without an issue. No, this is probably not a NFS performance thing, NFS is not *that* slow. Next try after kernel oplocks = no would be posix locking = no. Volker - -- - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Nathan Lager System Administrator 11 Pardee Hall Lafayette College, Easton, PA 18042 610-330-5907 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAktXPUkACgkQsZqG4IN3sulhJwCgqciUoWOtxcpRbMORwpWrSXMk MIgAnRRMhaEWU7mynN7B6N8UVOCqJsPk =aypr -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba, and NFS. lag?
On Wed, Jan 20, 2010 at 12:28:41PM -0500, Nathan Lager wrote: That hasnt helped either. Same lag on file modification. Thanks. Please connect, look in smbstatus which process is responsible for your client and strace it. strace -ttT -o /tmp/smbd.strace -p smbd-pid Upload /tmp/smbd.strace somewhere please. Volker pgpZSCKMDlyzR.pgp Description: PGP signature -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba, and NFS. lag?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thank's, i'll get on that. in the meantime. I've run wireshark during the write process. Here's what i've come up with. When i initiate the write (file-save), i see, from my workstation, to the smb server and NT Create Andx request path: \test\testfile.txt Immediately after that, i get a response from the smb server, to my workstation: microsoft-ds cognex-insight [ACK] seq=1 Ack=127 Win=36448 Len:0 28 seconds later, i get, from my workstation, to the server: Echo Request Immdiately after that, i get another microsoft-ds cognex-insight [ACK] Then the whole thing seems to start over again, except this time, no 28 second pause, and the write completes. On 01/20/2010 12:56 PM, Volker Lendecke wrote: On Wed, Jan 20, 2010 at 12:28:41PM -0500, Nathan Lager wrote: That hasnt helped either. Same lag on file modification. Thanks. Please connect, look in smbstatus which process is responsible for your client and strace it. strace -ttT -o /tmp/smbd.strace -p smbd-pid Upload /tmp/smbd.strace somewhere please. Volker - -- - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Nathan Lager System Administrator 11 Pardee Hall Lafayette College, Easton, PA 18042 610-330-5907 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAktXRxEACgkQsZqG4IN3suknRQCfUFc86qkDPr1twg4zE2+qA1Tr sxEAn0TsA1sVV1m56QOCbsr+hXec/ywT =hqfY -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba, and NFS. lag?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 OK, Here we go. http://www.undrground.org/smb/smbd.strace On 01/20/2010 12:56 PM, Volker Lendecke wrote: On Wed, Jan 20, 2010 at 12:28:41PM -0500, Nathan Lager wrote: That hasnt helped either. Same lag on file modification. Thanks. Please connect, look in smbstatus which process is responsible for your client and strace it. strace -ttT -o /tmp/smbd.strace -p smbd-pid Upload /tmp/smbd.strace somewhere please. Volker -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAktXTSIACgkQsZqG4IN3sunZqACffagPWZAH3BKFTfe2NSytiOWx zfAAoJgks2s5Dt1Pg0vh+49o9FMIcRWj =uCY5 -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba, and NFS. lag?
On Wed, 20 Jan 2010 13:36:18 -0500 Nathan Lager lag...@lafayette.edu wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 OK, Here we go. http://www.undrground.org/smb/smbd.strace On 01/20/2010 12:56 PM, Volker Lendecke wrote: On Wed, Jan 20, 2010 at 12:28:41PM -0500, Nathan Lager wrote: That hasnt helped either. Same lag on file modification. Thanks. Please connect, look in smbstatus which process is responsible for your client and strace it. strace -ttT -o /tmp/smbd.strace -p smbd-pid Upload /tmp/smbd.strace somewhere please. Volker -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAktXTSIACgkQsZqG4IN3sunZqACffagPWZAH3BKFTfe2NSytiOWx zfAAoJgks2s5Dt1Pg0vh+49o9FMIcRWj =uCY5 -END PGP SIGNATURE- Looks like it's taking forever for flock() calls to time out, and then it finally fails with -ENOLCK: 13:24:00.268018 flock(28, 0x60 /* LOCK_??? */) = -1 ENOLCK (No locks available) 30.000971 ...often that means that you don't have rpc.statd running on the client. -- Jeff Layton jlay...@samba.org -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba, and NFS. lag?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/20/2010 03:00 PM, Jeff Layton wrote: ...often that means that you don't have rpc.statd running on the client. I officially feel like a dolt now. Thank you for pointing out what should have been painfully obvious. I started up the nfslock service on my samba server, and the issue is gone. Thanks! Here's to public humiliation. :P -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAktXaRUACgkQsZqG4IN3sumEiwCgjsu7CywPEauep8TZAufwL2fH RzgAnjgDPui2dwBd75efZ7UPahhtYgko =VNjc -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba, and NFS. lag?
On Fri, Jan 15, 2010 at 03:20:36PM -0500, Nathan Lager wrote: Any suggestions? Anything i can check? Am i perhaps looking an an NFS performance issue? I'm able to modify files over the nfs mount from the smb server without an issue. No, this is probably not a NFS performance thing, NFS is not *that* slow. Next try after kernel oplocks = no would be posix locking = no. Volker signature.asc Description: Digital signature -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Samba, and NFS. lag?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Afternoon! I have a samba server, which shares out an NFS mounted share. It seems that everything works rather well, except that i get some lag when modifying a file. If i share a directory which is local to the samba server, no lag, everything works perfectly. However, when i share an NFS mounted volume, i get about 30 seconds of lag while writing a file after it's been modified. In my test, i did the following: - From Windows xp, browse to \\smbserver\share\ browse to a directory which you have permission to write to. open an existing file (in my case, a text file, using Notepad). Add a line to the file. save the file. Notepad hangs for about 30 seconds, and then successfully completes its write. The only thin special about this windows XP client is that it has the Novell mobile client installed. I ran into an issue where windows was first trying to access my smb server using novell's ncp, but this was corrected by moving around the provider order in Windows networking. Any suggestions? Anything i can check? Am i perhaps looking an an NFS performance issue? I'm able to modify files over the nfs mount from the smb server without an issue. Thanks! - -- - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Nathan Lager System Administrator 11 Pardee Hall Lafayette College, Easton, PA 18042 610-330-5907 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAktQzhQACgkQsZqG4IN3sumiIACgq9ms6T+hVVBVgdCyPztB6SMV bhYAnRM+bEJ3Mz5Gu96/iVqVYS4Hz/cH =v0Q/ -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba, and NFS. lag?
Nathan Lager wrote: Afternoon! I have a samba server, which shares out an NFS mounted share. It seems that everything works rather well, except that i get some lag when modifying a file. If i share a directory which is local to the samba server, no lag, everything works perfectly. However, when i share an NFS mounted volume, i get about 30 seconds of lag while writing a file after it's been modified. Hey Nathan, A 30 second lag is normally an indication of an oplock break timeout. Just an fyi...If you are re-exporting an nfs mounted volume on linux, try setting kernel oplocks = no since I don't bnelieve the kernel file lease mechanism is availble on an NFS mount but I could be wrong on that one. Just a suggestion. cheers, jerry signature.asc Description: OpenPGP digital signature -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba, and NFS. lag?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This didnt seem to help. As a side, note, i've also tried it without the Novell client. This didnt help either. Thanks just the same for the response. On 01/15/2010 03:48 PM, Gerald Carter wrote: Nathan Lager wrote: Afternoon! I have a samba server, which shares out an NFS mounted share. It seems that everything works rather well, except that i get some lag when modifying a file. If i share a directory which is local to the samba server, no lag, everything works perfectly. However, when i share an NFS mounted volume, i get about 30 seconds of lag while writing a file after it's been modified. Hey Nathan, A 30 second lag is normally an indication of an oplock break timeout. Just an fyi...If you are re-exporting an nfs mounted volume on linux, try setting kernel oplocks = no since I don't bnelieve the kernel file lease mechanism is availble on an NFS mount but I could be wrong on that one. Just a suggestion. cheers, jerry - -- - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Nathan Lager System Administrator 11 Pardee Hall Lafayette College, Easton, PA 18042 610-330-5907 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAktQ3OMACgkQsZqG4IN3sun27wCeL3TzsFao7x12Dgh+F/OABf2X CTAAmQE54iRoF7WuKtfJVT3IdbBNoGXw =EKvT -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba and NFS locking on Netapp filers ?
On Tue, Sep 29, 2009 at 04:54:15PM +0200, Frank Bonnet wrote: I have troubles with some shares that are NFS mounted to a Netapp filer, if I enable locking on that share, the file cannot be opened by the windows client in write mode ( read only after a looong time ) Anyone has the same problem , it seems to be a Netapp bug but they do not support samba at all :-) so I don't expect any answer from them. We strongly advise against re-exporting NFS imports via Samba, this is asking for trouble on many fronts. You're seeing one symptom of this. It might be the NetApp box, it might also be flaws in the NFS client implementation, who knows. Please enable the CIFS exports directly on the NetApp filer. If for some reason you can't, you might try posix locking = no on the samba server. Volker signature.asc Description: Digital signature -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Samba and NFS locking on Netapp filers ?
Hello I have troubles with some shares that are NFS mounted to a Netapp filer, if I enable locking on that share, the file cannot be opened by the windows client in write mode ( read only after a looong time ) Anyone has the same problem , it seems to be a Netapp bug but they do not support samba at all :-) so I don't expect any answer from them. thanks -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Samba with NFS
We're having a problem with a combination of NFS and Samba that I'm hoping someone here has seen before and knows the solution for. In this case, the Samba server is an NFS client, and the Samba share is actually an NFS mount to an NFS server. The problem we see is when a Windows client tries to open a file on the Samba share, the application hangs, and eventually comes back saying something to the effect that it couldn't open the file. Doesn't matter whether the application is notepad, Word, Excel, etc. Windows client is XP SP 2 Samba server/NFS client - tried a couple of different systems, both show the same symptoms: Fedora Core release 5, Samba 3.0.24-7.FC5, nfs-utils-lib-1.0.8.4.FC5, kernel: 2.6.20-1.2320.fc5 Fedora Core release 2, Samba 3.0.7-2.FC2, nfs-utils-lib-1.0.6-22, kernel: 2.6.11-7.1smp NFS Server Red Hat Enterprise ES release 4 update 5, nfs-utils-lib-1.0.6-8, kernel: 2.6.9-4.ELsmp We've been doing this for years using a different NFS server. We've recently upgrade to new hardware and OS on this NFS server, and this has been a problem ever since. Any thoughts? Thanks, in advance. David Harfst Senior Systems Engineer - Information Systems CMS, Inc. - http://www.cmsrtp.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba with NFS
David Harfst wrote: We're having a problem with a combination of NFS and Samba that I'm hoping someone here has seen before and knows the solution for. In this case, the Samba server is an NFS client, and the Samba share is actually an NFS mount to an NFS server. The problem we see is when a Windows client tries to open a file on the Samba share, the application hangs, and eventually comes back saying something to the effect that it couldn't open the file. Doesn't matter whether the application is notepad, Word, Excel, etc. Windows client is XP SP 2 Samba server/NFS client - tried a couple of different systems, both show the same symptoms: Fedora Core release 5, Samba 3.0.24-7.FC5, nfs-utils-lib-1.0.8.4.FC5, kernel: 2.6.20-1.2320.fc5 Fedora Core release 2, Samba 3.0.7-2.FC2, nfs-utils-lib-1.0.6-22, kernel: 2.6.11-7.1smp NFS Server Red Hat Enterprise ES release 4 update 5, nfs-utils-lib-1.0.6-8, kernel: 2.6.9-4.ELsmp We've been doing this for years using a different NFS server. We've recently upgrade to new hardware and OS on this NFS server, and this has been a problem ever since. Any thoughts? Thanks, in advance. David Harfst Senior Systems Engineer - Information Systems CMS, Inc. - http://www.cmsrtp.com Have you tried dropping the firewall on the Red Hat 4 NFS server to see if the problem goes away? -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba with NFS
On Wed, Sep 26, 2007 at 09:14:21AM -0500, David Harfst wrote: We've been doing this for years using a different NFS server. We've recently upgrade to new hardware and OS on this NFS server, and this has been a problem ever since. Any thoughts? Just DON'T re-export NFS imports with Samba. See a thread a couple of weeks ago. If you are really desperate, try posix locking = no and kernel oplocks = no. Volker pgpiwjhIYdQ0F.pgp Description: PGP signature -- 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 NFS quota problem
Hello, I don't know if anyone has any ideas on how to solve this. The same issue seems to occur in Red Hat EL 4 as well. CentOS 3.8 seems to be normal with both 23d and built in 3.0.9, so does Fedora Core 6. It seems to be something to do with NFS; though I don't know what's happening. If I change the window size of the NFS mount, although everythings normal on the underlying unix box samba changes the free space on the drive wildly. I don't think it's related to quotas but disk space. This occurs in any samba 3 I try it on. I've put more examples below illustrating what is happening. Does anyone have any ideas? NFS Server space: 17GB, free 468MB mount -o wsize=512 Samba shows on windows: 54MB free of 2.07GB mount -o wsize=1024 Samba shows on windows: 218MB free of 8.30GB mount -o wsize=2048 Samba shows on windows: 109MB free of 4.15GB Mount -o wsize=4096 Samba shows on windows: 54.6MB free of 2.07GB mount -o wsize=8192 Samba shows on windows 27.3MB free of 1.03GB mount -o wsize=16384 Samba shows on windows 13.6MB free of 531MB Mount -o wsize=32768 (default?) Samba shows on windows 6.8MB free of 265MB -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steve Goodman (lists) Sent: 16 December 2006 19:23 To: samba@lists.samba.org Subject: RE: [Samba] Samba and NFS quota problem Hi, Just in case someone has any idea on how to solve this, I've done some further testing. I get the same error below on both a fresh CentOS 4.4 install on x86 (not x64, to rule that out) using built-in RHEL packages; and on the original x64 server when compiling from sources (with sys quotas and disk quotas enabled or disabled). As I say I can see the quota correctly on the Samba server using the unix quota command but on the windows client the samba mapped drive shows entirely the wrong value as free/used. If I make the home directory on a local disk which doesn't use quotas all is fine. Am I missing something really obvious? Kind Regards, Steve -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steve Goodman (lists) Sent: 15 December 2006 15:42 To: samba@lists.samba.org Subject: [Samba] Samba and NFS quota problem Hello, I am mounting via NFS a number of volumes and re-sharing these as CIFS. We have been using this arrangement successfully for a number of years. We are replacing the CIFSNFS proxy servers (which are also PDC/BDCs to OpenLDAP) and a weird problem seems to occur. The problem is the quota/disk size appears to be wrong. For example, if I use the unix quota command on the SMB server, it shows correctly the quota and usage. However on the windows machine this is showing incorrectly. The NFS is mounted with no special options, and I have tried against different NFS servers, different Samba versions and can replicate the problem on both the PDC and BDC servers (which are setup identically) OS: CentOS 4.4 x64 Hardware: Dell Poweredge 2950 Current Samba version: samba3-client-3.0.23d-30 samba3-3.0.23d-30 (Also occurs on CentOS/RHEL Samba-3.0.10) NFS server: Solaris 9, default settings. Also it shows the wrong quota information using another NFS server (EMC Celerra NAS 5.5) Quota shows correctly using quota command: Filesystem blocks quota limit grace files quota limit grace helios:/adm/d501 359519 50 500500 668 0 0 Disk usage on the windows system shows: 8.98MB free of 265MB - writing any file to this fails. Samba also appears to be compiled with quota options enabled: # smbd -b| grep QUOTA HAVE_SYS_QUOTA_H HAVE_LINUX_XFS_QUOTAS HAVE_QUOTACTL_LINUX HAVE_SYS_QUOTAS HAVE_XFS_QUOTAS WITH_QUOTAS WITH_QUOTAS Any thoughts on this problem would be greatly appreciated. I am about to compile from source to see if this still occurs. Steve Goodman -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- 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 NFS quota problem
Hi, Just in case someone has any idea on how to solve this, I've done some further testing. I get the same error below on both a fresh CentOS 4.4 install on x86 (not x64, to rule that out) using built-in RHEL packages; and on the original x64 server when compiling from sources (with sys quotas and disk quotas enabled or disabled). As I say I can see the quota correctly on the Samba server using the unix quota command but on the windows client the samba mapped drive shows entirely the wrong value as free/used. If I make the home directory on a local disk which doesn't use quotas all is fine. Am I missing something really obvious? Kind Regards, Steve -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steve Goodman (lists) Sent: 15 December 2006 15:42 To: samba@lists.samba.org Subject: [Samba] Samba and NFS quota problem Hello, I am mounting via NFS a number of volumes and re-sharing these as CIFS. We have been using this arrangement successfully for a number of years. We are replacing the CIFSNFS proxy servers (which are also PDC/BDCs to OpenLDAP) and a weird problem seems to occur. The problem is the quota/disk size appears to be wrong. For example, if I use the unix quota command on the SMB server, it shows correctly the quota and usage. However on the windows machine this is showing incorrectly. The NFS is mounted with no special options, and I have tried against different NFS servers, different Samba versions and can replicate the problem on both the PDC and BDC servers (which are setup identically) OS: CentOS 4.4 x64 Hardware: Dell Poweredge 2950 Current Samba version: samba3-client-3.0.23d-30 samba3-3.0.23d-30 (Also occurs on CentOS/RHEL Samba-3.0.10) NFS server: Solaris 9, default settings. Also it shows the wrong quota information using another NFS server (EMC Celerra NAS 5.5) Quota shows correctly using quota command: Filesystem blocks quota limit grace files quota limit grace helios:/adm/d501 359519 50 500500 668 0 0 Disk usage on the windows system shows: 8.98MB free of 265MB - writing any file to this fails. Samba also appears to be compiled with quota options enabled: # smbd -b| grep QUOTA HAVE_SYS_QUOTA_H HAVE_LINUX_XFS_QUOTAS HAVE_QUOTACTL_LINUX HAVE_SYS_QUOTAS HAVE_XFS_QUOTAS WITH_QUOTAS WITH_QUOTAS Any thoughts on this problem would be greatly appreciated. I am about to compile from source to see if this still occurs. Steve Goodman -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Samba and NFS quota problem
Hello, I am mounting via NFS a number of volumes and re-sharing these as CIFS. We have been using this arrangement successfully for a number of years. We are replacing the CIFSNFS proxy servers (which are also PDC/BDCs to OpenLDAP) and a weird problem seems to occur. The problem is the quota/disk size appears to be wrong. For example, if I use the unix quota command on the SMB server, it shows correctly the quota and usage. However on the windows machine this is showing incorrectly. The NFS is mounted with no special options, and I have tried against different NFS servers, different Samba versions and can replicate the problem on both the PDC and BDC servers (which are setup identically) OS: CentOS 4.4 x64 Hardware: Dell Poweredge 2950 Current Samba version: samba3-client-3.0.23d-30 samba3-3.0.23d-30 (Also occurs on CentOS/RHEL Samba-3.0.10) NFS server: Solaris 9, default settings. Also it shows the wrong quota information using another NFS server (EMC Celerra NAS 5.5) Quota shows correctly using quota command: Filesystem blocks quota limit grace files quota limit grace helios:/adm/d501 359519 50 500500 668 0 0 Disk usage on the windows system shows: 8.98MB free of 265MB - writing any file to this fails. Samba also appears to be compiled with quota options enabled: # smbd -b| grep QUOTA HAVE_SYS_QUOTA_H HAVE_LINUX_XFS_QUOTAS HAVE_QUOTACTL_LINUX HAVE_SYS_QUOTAS HAVE_XFS_QUOTAS WITH_QUOTAS WITH_QUOTAS Any thoughts on this problem would be greatly appreciated. I am about to compile from source to see if this still occurs. Steve Goodman -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Samba and NFS file access problem.
Hi, I've got samba 3.0.14a server and on the same machine is nfs server. Some files are share for Windows and Linux clients. The problme is when two clients one from win other from Linux try to open the same file. If Linux user first open file Samba user can open it (i/o error), in oposite situation Linux user can open the file to rw (!?) - the same file is edited by both - when win try to save error occurs. Is there any solution for this situation. I've tried turn off oplocks - didn't help, i've looked almost evereywhere and can't find soulution. If it possible that if samba user open file it will open readonly for nfs user and if nfs user opens file samba user will open if ro. Thanks for any help! With best regards Grzegorz -- Jestes kierowca? To poczytaj! http://link.interia.pl/f199e -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Samba or NFS for a new domain member server
I have 10 XP clients authenticating against a Samba PDC, using passwd as the passdb backend. The Samba PDC provides several shares to the XP clients. Priviledges on the Samba PDC are controlled by *nix user and group permissions. I do not have any Windows servers on my network, so we do not use any of the Windows group capabilities beyond the default groups. My Samba PDC is running out of room, so I want to move the shares to a new server with more storage, but I want the Samba PDC to continue to authenticate my XP clients. Should I maintain the definition of the shares on the Samba PDC, but actually store the data on the new server and make it available to the PDC via NFS. In other words, do not use Samba on the new server, but use NFS instead? OR Should I use Samba and winbind on the new server to provide access to the shares and control permissions? Any thoughts or experiences are appreciated. Scott Rosa Debian-sarge, Samba 3.0.14 --- MY CURRENT EXPERIENCE SO FAR --- Note: I know that the simple solution would have been to make the new box the PDC, which I may still do. However, I may be adding a second member server soon, so I needed to figure out how to integrate the member server into my network anyway. I have been able to get samba on the new server to use the old PDC to authenticate the users. And, I have been able to verify with wbinfo -u. However, I run into a problem with group permissions. When I do a wbinfo -r username on the member server, I get a list of numeric group ids for the user. The count matches the number of groups that the user belongs to on the PDC. Having virtually no experience with samba, I thought that might not be a big deal, especially since I could determine the group name by using the following commands: wbinfo -G group-id wbinfo -s SID from the command above For, example: wbinfo -G 10012 returns S-1-5-21-...-3003 S-1-5-21-...-3003 returns PP+fl_staff 2 However, when I tried to set up one of the directories that I want to move from the existing PDC to the member server, I could not assign the appropriate group to the directory. For examble, on the member server: chgrp PP+fl_staff pub chgrp PP+fl_staff pub chgrp PP+fl_staff 2 pub all return an error: chgrp: invalid group name `PP+fl_staff' Now, if I change the group ownership to the appropriate GID (in this case, 10012), the chgrp command works and my XP clients can access the directory with the appropriate permissions, which I guess I can do. But, if something happens to winbind idmap tables and things get renumbered for some reason, I don't want to have to face the task of fixing the GIDs across some files and directories. Sent via the WebMail system at preventionpartners.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Samba or NFS for a new domain member server
Please forgive me if this post appears multiple times. I have had trouble posting and I cannot be sure if any of my other posts have made it to the list. I have 10 XP clients authenticating against a Samba PDC, using passwd as the passdb backend. The Samba PDC provides several shares to the XP clients. Priviledges on the Samba PDC are controlled by *nix user and group permissions. I do not have any Windows servers on my network, so we do not use any of the Windows group capabilities beyond the default groups. My Samba PDC is running out of room, so I want to move the shares to a new server with more storage, but I want the Samba PDC to continue to authenticate my XP clients. Should I maintain the definition of the shares on the Samba PDC, but actually store the data on the new server and make it available to the PDC via NFS. In other words, do not use Samba on the new server, but use NFS instead? OR Should I use Samba and winbind on the new server to provide access to the shares and control permissions? Any thoughts or experiences are appreciated. Scott Rosa Debian-sarge, Samba 3.0.14 --- MY CURRENT EXPERIENCE SO FAR --- Note: I know that the simple solution would have been to make the new box the PDC, which I may still do. However, I may be adding a second member server soon, so I needed to figure out how to integrate the member server into my network anyway. I have been able to get samba on the new server to use the old PDC to authenticate the users. And, I have been able to verify with wbinfo -u. However, I run into a problem with group permissions. When I do a wbinfo -r username on the member server, I get a list of numeric group ids for the user. The count matches the number of groups that the user belongs to on the PDC. Having virtually no experience with samba, I thought that might not be a big deal, especially since I could determine the group name by using the following commands: wbinfo -G group-id wbinfo -s SID from the command above For, example: wbinfo -G 10012 returns S-1-5-21-...-3003 S-1-5-21-...-3003 returns PP+fl_staff 2 However, when I tried to set up one of the directories that I want to move from the existing PDC to the member server, I could not assign the appropriate group to the directory. For examble, on the member server: chgrp PP+fl_staff pub chgrp PP+fl_staff pub chgrp PP+fl_staff 2 pub all return an error: chgrp: invalid group name `PP+fl_staff' Now, if I change the group ownership to the appropriate GID (in this case, 10012), the chgrp command works and my XP clients can access the directory with the appropriate permissions, which I guess I can do. But, if something happens to winbind idmap tables and things get renumbered for some reason, I don't want to have to face the task of fixing the GIDs across some files and directories. Sent via the WebMail system at preventionpartners.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Samba or NFS for a new domain member server
Please forgive me if this post appears multiple times. I have had trouble posting and I cannot be sure if any of my other posts have made it to the list. I have 10 XP clients authenticating against a Samba PDC, using passwd as the passdb backend. The Samba PDC provides several shares to the XP clients. Priviledges on the Samba PDC are controlled by *nix user and group permissions. I do not have any Windows servers on my network, so we do not use any of the Windows group capabilities beyond the default groups. My Samba PDC is running out of room, so I want to move the shares to a new server with more storage, but I want the Samba PDC to continue to authenticate my XP clients. Should I maintain the definition of the shares on the Samba PDC, but actually store the data on the new server and make it available to the PDC via NFS. In other words, do not use Samba on the new server, but use NFS instead? OR Should I use Samba and winbind on the new server to provide access to the shares and control permissions? Any thoughts or experiences are appreciated. Scott Rosa Debian-sarge, Samba 3.0.14 --- MY CURRENT EXPERIENCE SO FAR --- Note: I know that the simple solution would have been to make the new box the PDC, which I may still do. However, I may be adding a second member server soon, so I needed to figure out how to integrate the member server into my network anyway. I have been able to get samba on the new server to use the old PDC to authenticate the users. And, I have been able to verify with wbinfo -u. However, I run into a problem with group permissions. When I do a wbinfo -r username on the member server, I get a list of numeric group ids for the user. The count matches the number of groups that the user belongs to on the PDC. Having virtually no experience with samba, I thought that might not be a big deal, especially since I could determine the group name by using the following commands: wbinfo -G group-id wbinfo -s SID from the command above For, example: wbinfo -G 10012 returns S-1-5-21-...-3003 S-1-5-21-...-3003 returns PP+fl_staff 2 However, when I tried to set up one of the directories that I want to move from the existing PDC to the member server, I could not assign the appropriate group to the directory. For examble, on the member server: chgrp PP+fl_staff pub chgrp PP+fl_staff pub chgrp PP+fl_staff 2 pub all return an error: chgrp: invalid group name `PP+fl_staff' Now, if I change the group ownership to the appropriate GID (in this case, 10012), the chgrp command works and my XP clients can access the directory with the appropriate permissions, which I guess I can do. But, if something happens to winbind idmap tables and things get renumbered for some reason, I don't want to have to face the task of fixing the GIDs across some files and directories. Sent via the WebMail system at preventionpartners.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba or NFS for a new domain member server
Gary, Thanks for taking the time to respond. My network is really small right now, so I can live with having to add the *nix groups locally. For some reason, I just assumed that winbind, which provided usernames for the matching UID, would do the same for *nix groups. I guess I really need to be using ldap, but that learning curve is going to be longer than I have to get these two servers in place. Thanks again for your help. -- Original Message -- From: Gary Dale [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] Date: Tue, 09 May 2006 10:46:00 -0400 Samba Administrator wrote: Please forgive me if this post appears multiple times. I have had trouble posting and I cannot be sure if any of my other posts have made it to the list. I have 10 XP clients authenticating against a Samba PDC, using passwd as the passdb backend. The Samba PDC provides several shares to the XP clients. Priviledges on the Samba PDC are controlled by *nix user and group permissions. I do not have any Windows servers on my network, so we do not use any of the Windows group capabilities beyond the default groups. My Samba PDC is running out of room, so I want to move the shares to a new server with more storage, but I want the Samba PDC to continue to authenticate my XP clients. Should I maintain the definition of the shares on the Samba PDC, but actually store the data on the new server and make it available to the PDC via NFS. In other words, do not use Samba on the new server, but use NFS instead? OR Should I use Samba and winbind on the new server to provide access to the shares and control permissions? Any thoughts or experiences are appreciated. Scott Rosa Debian-sarge, Samba 3.0.14 --- MY CURRENT EXPERIENCE SO FAR --- Note: I know that the simple solution would have been to make the new box the PDC, which I may still do. However, I may be adding a second member server soon, so I needed to figure out how to integrate the member server into my network anyway. I have been able to get samba on the new server to use the old PDC to authenticate the users. And, I have been able to verify with wbinfo -u. However, I run into a problem with group permissions. When I do a wbinfo -r username on the member server, I get a list of numeric group ids for the user. The count matches the number of groups that the user belongs to on the PDC. Having virtually no experience with samba, I thought that might not be a big deal, especially since I could determine the group name by using the following commands: wbinfo -G group-id wbinfo -s SID from the command above For, example: wbinfo -G 10012 returns S-1-5-21-...-3003 S-1-5-21-...-3003 returns PP+fl_staff 2 However, when I tried to set up one of the directories that I want to move from the existing PDC to the member server, I could not assign the appropriate group to the directory. For examble, on the member server: chgrp PP+fl_staff pub chgrp PP+fl_staff pub chgrp PP+fl_staff 2 pub all return an error: chgrp: invalid group name `PP+fl_staff' Now, if I change the group ownership to the appropriate GID (in this case, 10012), the chgrp command works and my XP clients can access the directory with the appropriate permissions, which I guess I can do. But, if something happens to winbind idmap tables and things get renumbered for some reason, I don't want to have to face the task of fixing the GIDs across some files and directories. Sent via the WebMail system at preventionpartners.com I'd avoid using NFS in this situation. Why make the file access go through two servers? If you make the new server a domain controller, you get some redundancy in your authentication, in case your PDC has problems. To avoid remapping shares, you can rename your PDC and file server so that the shares continue to map the same server name. re. your group problem: it sounds like the group names don't exist on the new server. Since you say you are using *nix groups instead of Windows groups, that could be the problem. I don't think it's a big deal. As long as the group numbers match, things should work. To get the names to show, you need to add the *nix groups locally. You could try copying the /etc/group from your PDC, or at least the portion with group numbers 1. Sent via the WebMail system at preventionpartners.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba over NFS: Total and Free disk incorrect in Windows.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jeremy, I can reproduce this as well. Is it somethign we can fix? Or more of a don't do that kind of thing? cheers, jerry samba.list wrote: | Hello, | | I have a Linux machine auto-mounting an NFS share, | then sharing it out via Samba (not my idea). Everything | is fine - except: On Windows machines that have mapped | a drive to the Samba share the Total Size and Free Space | for the mapped network drive (Samba/NFSshare) shows | Total Size of 20.0 MB and Free Space of 0 bytes. | | To rule out a very simple Samba problem I created | a new (local) directory on the Linux machine and | shared it with Samba. No problem. Total and | Free show correctly. | | Thoughts? | | Some details: | | Linux is 2.4.21-15.ELsmp (RHEL3, recent load; fully updated) | Samba is: samba-common-3.0.9-1.3E.5 | | smb.conf (with some details 'd out) | [global] | |workgroup = |server string = Samba Server |browseable = yes |security = server |dns proxy = No |encrypt passwords = yes |log file = /usr/local/samba/var/log.%m |max log size = 50 |password server = X |netbios name = X |socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 |#logon drive = i: | | | [home] |comment = home Directories |path = /home |browseable = yes |writable = yes | | -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDc1cXIR7qMdg1EfYRAt7BAJ0Sk8hsex1HRCWO7XCChpaDfe7ppQCfaDKb N87oIRwwSDOt35rAKFf3ZtM= =FMOV -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Samba over NFS: Total and Free disk incorrect in Windows.
Hi, Im running also samba with nfs and no problems here, disk size and free space are ok here. Im using samba 3.0.14a-debian Kernel 2.6.8-debian Louis -Oorspronkelijk bericht- Van: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Namens Gerald (Jerry) Carter Verzonden: donderdag 10 november 2005 15:20 Aan: Jeremy Allison CC: samba@lists.samba.org Onderwerp: Re: [Samba] Samba over NFS: Total and Free disk incorrect in Windows. -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jeremy, I can reproduce this as well. Is it somethign we can fix? Or more of a don't do that kind of thing? cheers, jerry samba.list wrote: | Hello, | | I have a Linux machine auto-mounting an NFS share, | then sharing it out via Samba (not my idea). Everything | is fine - except: On Windows machines that have mapped | a drive to the Samba share the Total Size and Free Space | for the mapped network drive (Samba/NFSshare) shows | Total Size of 20.0 MB and Free Space of 0 bytes. | | To rule out a very simple Samba problem I created | a new (local) directory on the Linux machine and | shared it with Samba. No problem. Total and | Free show correctly. | | Thoughts? | | Some details: | | Linux is 2.4.21-15.ELsmp (RHEL3, recent load; fully updated) | Samba is: samba-common-3.0.9-1.3E.5 | | smb.conf (with some details 'd out) | [global] | |workgroup = |server string = Samba Server |browseable = yes |security = server |dns proxy = No |encrypt passwords = yes |log file = /usr/local/samba/var/log.%m |max log size = 50 |password server = X |netbios name = X |socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 |#logon drive = i: | | | [home] |comment = home Directories |path = /home |browseable = yes |writable = yes | | -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDc1cXIR7qMdg1EfYRAt7BAJ0Sk8hsex1HRCWO7XCChpaDfe7ppQCfaDKb N87oIRwwSDOt35rAKFf3ZtM= =FMOV -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba over NFS: Total and Free disk incorrect in Windows.
On Thu, Nov 10, 2005 at 08:20:07AM -0600, Gerald (Jerry) Carter wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jeremy, I can reproduce this as well. Is it somethign we can fix? Or more of a don't do that kind of thing? No, people want to do this. Is the Linux disk free request failing on NFS drives ? What happens with a df command (which should call the same functions). I try not to nfs export anything at home (but will if I have to to fix this :-). Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba over NFS: Total and Free disk incorrect in Windows.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jeremy Allison wrote: | On Thu, Nov 10, 2005 at 08:20:07AM -0600, Gerald (Jerry) Carter wrote: | -BEGIN PGP SIGNED MESSAGE- | Hash: SHA1 | | Jeremy, | | I can reproduce this as well. Is it somethign we can fix? | Or more of a don't do that kind of thing? | | No, people want to do this. Is the Linux disk free request | failing on NFS drives ? What happens with a df command (which | should call the same functions). I try not to nfs export anything | at home (but will if I have to to fix this :-). Here you go. NFS; $ df -k . Filesystem 1K-blocks Used Available Use% Mounted on ahab.plainjoe.org:/export/u3 ~ 110728544 81326496 23777312 78% /home/queso local: # df -k /export/u3 Filesystem 1K-blocks Used Available Use% Mounted on /dev/hda5110728544 81326504 23777284 78% /export SAMBA_3_0 with Windows 2000 client: H:\ dir Volume in drive H is jerry Volume Serial Number is 0467-0568 Directory of H:\ 11/10/2005 11:08a DIR . 09/06/2005 05:08p DIR .. 09/08/2005 06:41a 1,018 dump 10/19/2005 02:13p 572,514 regmon.log 10/30/2005 01:33p 430 foo.log 03/11/2005 08:37a 0 NFS mount FS.txt 13 File(s)581,105 bytes 16 Dir(s) 3,043,495,936 bytes free ciao, jerry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDc5oOIR7qMdg1EfYRArRUAJ4jD/SvCOBSDf9US2CmixeTtqWsuwCg3+nb BX+JBkeXxNXbDpyIXZXs14A= =eC1c -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Samba over NFS: Total and Free disk incorrect in Windows.
Hello, I have a Linux machine auto-mounting an NFS share, then sharing it out via Samba (not my idea). Everything is fine - except: On Windows machines that have mapped a drive to the Samba share the Total Size and Free Space for the mapped network drive (Samba/NFSshare) shows Total Size of 20.0 MB and Free Space of 0 bytes. To rule out a very simple Samba problem I created a new (local) directory on the Linux machine and shared it with Samba. No problem. Total and Free show correctly. Thoughts? Some details: Linux is 2.4.21-15.ELsmp (RHEL3, recent load; fully updated) Samba is: samba-common-3.0.9-1.3E.5 smb.conf (with some details 'd out) [global] workgroup = server string = Samba Server browseable = yes security = server dns proxy = No encrypt passwords = yes log file = /usr/local/samba/var/log.%m max log size = 50 password server = X netbios name = X socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 #logon drive = i: # Share Definitions == [home] comment = home Directories path = /home browseable = yes writable = yes -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] samba on NFS share with quota support
Dear List, How to get quota support on samba on the NFS disk, right now i'm using XFS on the NFS and samba-3.0.20b Thanks -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] samba and nfs locking
bones! anyone has played with nfs and samba locking? im setting a nfs and samba environment i have problems with locking files and i was reading some smb.conf setting, but still got no idea on how to handle and mix this with nfs to avoid data corruption. any hints will be apreciated abo -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] SAMBA and NFS
Can samba connect to an NFS share and then re-export that share so my windows XP users can connect to it? Basically I have a NFS share that all of my windows XP users need read-only access to. The goal of this project is to replace an old MS Gateway Services for Novell server (using IPX) with something that can do the same thing but over IP. I am pretty sure Novell and AD can share files using Native File Access, but that would require the Novell admins to get CIFS setup on the Novell side. The Novell server we are using has NFS already setup and getting that much setup was like pulling teeth. Thanks, BOFH1234 _ Is your PC infected? Get a FREE online computer virus scan from McAfee® Security. http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] SAMBA and NFS
On Wed, Jul 07, 2004 at 01:23:37PM -0400, bastard operater wrote: BOFH1234 == bastard operater [EMAIL PROTECTED] writes: BOFH1234 Can samba connect to an NFS share and then re-export BOFH1234 that share so my windows XP users can connect to it? BOFH1234 Basically I have a NFS share that all of my windows XP BOFH1234 users need read-only access to. The goal of this BOFH1234 project is to replace an old MS Gateway Services for BOFH1234 Novell server (using IPX) with something that can do the BOFH1234 same thing but over IP. I am pretty sure Novell and AD BOFH1234 can share files using Native File Access, but that would BOFH1234 require the Novell admins to get CIFS setup on the BOFH1234 Novell side. The Novell server we are using has NFS BOFH1234 already setup and getting that much setup was like BOFH1234 pulling teeth. Samba can share any filesystem that the Samba server can see. Your performance will be degraded because you have the dual overhead of Samba and NFS, but you can share the filesystem. -- Eric M. Boehm /\ ASCII Ribbon Campaign [EMAIL PROTECTED] \ / No HTML or RTF in mail X No proprietary word-processing Respect Open Standards / \ files in mail -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] SAMBA and NFS
Thank you for the response. Would there still be a performance problem if I had two NICs in the PC? One to connect to the NFS share and the second NIC to connect to the windows PCs? I am talking about a maximum of 20 people connecting to the samba share with at most 5-6 people passing data over the share. The samba server would be a 2.2GHz PC with 512MB of RAM. Thanks, BOFH1234 From: Eric Boehm [EMAIL PROTECTED] Reply-To: Eric Boehm [EMAIL PROTECTED] To: bastard operater [EMAIL PROTECTED] CC: [EMAIL PROTECTED] Subject: Re: [Samba] SAMBA and NFS Date: Wed, 7 Jul 2004 13:35:28 -0400 On Wed, Jul 07, 2004 at 01:23:37PM -0400, bastard operater wrote: BOFH1234 == bastard operater [EMAIL PROTECTED] writes: BOFH1234 Can samba connect to an NFS share and then re-export BOFH1234 that share so my windows XP users can connect to it? BOFH1234 Basically I have a NFS share that all of my windows XP BOFH1234 users need read-only access to. The goal of this BOFH1234 project is to replace an old MS Gateway Services for BOFH1234 Novell server (using IPX) with something that can do the BOFH1234 same thing but over IP. I am pretty sure Novell and AD BOFH1234 can share files using Native File Access, but that would BOFH1234 require the Novell admins to get CIFS setup on the BOFH1234 Novell side. The Novell server we are using has NFS BOFH1234 already setup and getting that much setup was like BOFH1234 pulling teeth. Samba can share any filesystem that the Samba server can see. Your performance will be degraded because you have the dual overhead of Samba and NFS, but you can share the filesystem. -- Eric M. Boehm /\ ASCII Ribbon Campaign [EMAIL PROTECTED] \ / No HTML or RTF in mail X No proprietary word-processing Respect Open Standards / \ files in mail _ Get tips for maintaining your PC, notebook accessories and reviews in Technology 101. http://special.msn.com/tech/technology101.armx -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] SAMBA and NFS
On Wed, Jul 07, 2004 at 02:49:30PM -0400, bastard operater wrote: bastard == bastard operater [EMAIL PROTECTED] writes: bastard Thank you for the response. Would there still be a bastard performance problem if I had two NICs in the PC? One to bastard connect to the NFS share and the second NIC to connect to bastard the windows PCs? I am talking about a maximum of 20 bastard people connecting to the samba share with at most 5-6 bastard people passing data over the share. The samba server bastard would be a 2.2GHz PC with 512MB of RAM. I don't think that will help you. I am talking about the overhead of the two protocols. For example, if you were access files via NFS, you might see something like this client - NFS - NFS server and for samba client - SMB (CIFS) - Samba server However, in your example, client - SMB (CIFS) - Samba server - NFS - NFS server The client has to go through two network file systems to get to the data. -- Eric M. Boehm /\ ASCII Ribbon Campaign [EMAIL PROTECTED] \ / No HTML or RTF in mail X No proprietary word-processing Respect Open Standards / \ files in mail -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] SAMBA and NFS
Eric Boehm wrote: On Wed, Jul 07, 2004 at 02:49:30PM -0400, bastard operater wrote: bastard == bastard operater [EMAIL PROTECTED] writes: bastard Thank you for the response. Would there still be a bastard performance problem if I had two NICs in the PC? One to bastard connect to the NFS share and the second NIC to connect to bastard the windows PCs? I am talking about a maximum of 20 bastard people connecting to the samba share with at most 5-6 bastard people passing data over the share. The samba server bastard would be a 2.2GHz PC with 512MB of RAM. I don't think that will help you. I am talking about the overhead of the two protocols. For example, if you were access files via NFS, you might see something like this client - NFS - NFS server and for samba client - SMB (CIFS) - Samba server However, in your example, client - SMB (CIFS) - Samba server - NFS - NFS server The client has to go through two network file systems to get to the data. Not really much of a slowdown. I have that confirugation setup within my own network with roughly 25 users. Primarily, they are accessing Samba from the server hosting the files, however if need be those Samba shares can be accessed via NFS then Samba off the second Server. I configured the two servers 'identically' with the second server running an rsyne between the 'share' and a 'share2' over NFS, that way if the primary server fails, all I need to do is change umount 'share2' and remount it as 'share' and voila no other changes are necesary, since the same fileshares are already available through Samba via both servers. If I wanted to, I could quickly edit the smb.conf file to change the 'server' name the second server broadcasts and within a few minutes everyone will be 'reconnected' to the 'original' server. In my tests, there really is very little difference in performance. -Rob -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] SAMBA and NFS
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I think you won't have a performance problem. i have a DELL P4 2.8 with 256 ram rinning samba+rsync+heartbeat+nfs and 20 clients. everything is ok. bastard operater wrote: | Thank you for the response. Would there still be a performance problem | if I had two NICs in the PC? One to connect to the NFS share and the | second NIC to connect to the windows PCs? I am talking about a maximum | of 20 people connecting to the samba share with at most 5-6 people | passing data over the share. The samba server would be a 2.2GHz PC with | 512MB of RAM. | | Thanks, | | BOFH1234 | | From: Eric Boehm [EMAIL PROTECTED] | Reply-To: Eric Boehm [EMAIL PROTECTED] | To: bastard operater [EMAIL PROTECTED] | CC: [EMAIL PROTECTED] | Subject: Re: [Samba] SAMBA and NFS | Date: Wed, 7 Jul 2004 13:35:28 -0400 | | On Wed, Jul 07, 2004 at 01:23:37PM -0400, bastard operater wrote: | BOFH1234 == bastard operater [EMAIL PROTECTED] writes: | | BOFH1234 Can samba connect to an NFS share and then re-export | BOFH1234 that share so my windows XP users can connect to it? | BOFH1234 Basically I have a NFS share that all of my windows XP | BOFH1234 users need read-only access to. The goal of this | BOFH1234 project is to replace an old MS Gateway Services for | BOFH1234 Novell server (using IPX) with something that can do the | BOFH1234 same thing but over IP. I am pretty sure Novell and AD | BOFH1234 can share files using Native File Access, but that would | BOFH1234 require the Novell admins to get CIFS setup on the | BOFH1234 Novell side. The Novell server we are using has NFS | BOFH1234 already setup and getting that much setup was like | BOFH1234 pulling teeth. | | Samba can share any filesystem that the Samba server can see. Your | performance will be degraded because you have the dual overhead of | Samba and NFS, but you can share the filesystem. | | -- | Eric M. Boehm /\ ASCII Ribbon Campaign | [EMAIL PROTECTED] \ / No HTML or RTF in mail | X No proprietary word-processing | Respect Open Standards / \ files in mail | | | _ | Get tips for maintaining your PC, notebook accessories and reviews in | Technology 101. http://special.msn.com/tech/technology101.armx | - -- ~ ___ ~| henrique paiva | ~|___| ~| email: [EMAIL PROTECTED] | ~|___| ~| icq: 320094827 | ~|___| Este email foi assinado pelo Gnupg http://www.gnupg.com e ~ Mozilla Thunderbird Enigmail http://enigmail.mozdev.org Solicite minha chave pública. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFA7GgmeE6sZ+g/aaURAj37AKCfFEBodopuepG9K27yFvH5yQnp6wCgm7CF laGw0bZaxf7bWj3qR7pryEs= =uUOR -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] samba on nfs server or client
Hello all. I hope this question is not too dumb, but I thought I'd ask it anyway since I'd like to get the opinion of the samba gurus out there. My question is this: -- is it better to run smbd and nmbd on a server that acts as a NFS server and has disks directly attached to it or is it better to run samba on a seperate machine that acts as a client to the NFS server? In other words, in the first scenario, there is no middleman server sitting between the NFS server and the windows client. Are there any advantages / disadvantages to this approach? It seems that this would be faster than having a dedicated samba server that acts as an NFS client since NFS calls are removed from the picture. Any insight on this is appreciated as I am purely speculating. Thanks. --Venkata -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] samba (vs. nfs) in all unix environment
Hi! I have had a short look at that comparison document and have to say that it sounds very biased. Additionally, it is not really applicable to the original problem, because it does not consider an all Unix environment as given. (it states for example that for CIFS you don't have to install anything on the client PCs) just my 2 cents.. greetings, Nils rruegner [EMAIL PROTECTED] wrote (Wed, 12 Nov 2003 18:40:28 +0100): Hi, i can only answer to one thing, if no windows is involved you havent to use smb at all, for mount files via network. But i remember that i had to use it with a Linux Coldfusion setup, cause the cold fusion server was not able to handle nfs shares. I think i depends deep in what you want to do with your machines to find out what protokoll may the best for you. For courier nfs should be enough, but look here http://www.facetcorp.com/competition_nfs_cifs_comparison.html for more info Let us know your results Best Regards - Original Message - From: Mariano Absatz [EMAIL PROTECTED] To: Samba Mailing List [EMAIL PROTECTED] Sent: Wednesday, November 12, 2003 6:28 PM Subject: [Samba] samba (vs. nfs) in all unix environment Hi, I'm sorry if this is a very FAQ, I've been googling around and searchin' the list archive and I'll gladly accept RTFMs with somehow precise URLs(including URLs to the list archives). I'm on the drawing board (no equipment yet) for a server farm that will have a SteelEye linux cluster behind to provide (among other services) with networked file access. The setup is all-linux (likely RHEL 2.1, less likely RHL 8.0, almost unlikely RHEL 3.0), that is, there will not be no windows clients nor servers. The shared filesystems will be used by a Courier-IMAP server and an Apache httpd 2.0 server. I always did these kind of stuff with NFS and I know it would work, but recently someone told me maybe SMB would yeld better performance and resilience in case of a cluster node failing over to the other one... The point is, I don't know anything about this, and searching the web, newsgroups and mailing list archives didn't bring much light into it. I asked in the Courier-IMAP mailing list and the only answer (from Courier-IMAP developer) only stated that he thought samba wouldn't be able to correctly handle : charaters in filenames (which Courier-IMAP uses). I did a really quick check with stock samba 2.2.7 included in RedHat 7.3 and I can create a file named hi:bye and I can read it thru an smb mount... buy if I list the directory containing it, it appears as HIBYE~7C, so it's obviously doing some mangling in there. First question is, can I disable all name mangling on a share that will be accessed only by unix machines? or is there any mounting options that allows me to do this? Second (and most important) question is... will SMB provide better performance or more resilience in an all-linux environment? or should I stick with NFS? TIA. -- Mariano Absatz El Baby -- Double your drive space - delete Windows! -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] samba (vs. nfs) in all unix environment
Hi, I'm sorry if this is a very FAQ, I've been googling around and searchin' the list archive and I'll gladly accept RTFMs with somehow precise URLs (including URLs to the list archives). I'm on the drawing board (no equipment yet) for a server farm that will have a SteelEye linux cluster behind to provide (among other services) with networked file access. The setup is all-linux (likely RHEL 2.1, less likely RHL 8.0, almost unlikely RHEL 3.0), that is, there will not be no windows clients nor servers. The shared filesystems will be used by a Courier-IMAP server and an Apache httpd 2.0 server. I always did these kind of stuff with NFS and I know it would work, but recently someone told me maybe SMB would yeld better performance and resilience in case of a cluster node failing over to the other one... The point is, I don't know anything about this, and searching the web, newsgroups and mailing list archives didn't bring much light into it. I asked in the Courier-IMAP mailing list and the only answer (from Courier-IMAP developer) only stated that he thought samba wouldn't be able to correctly handle : charaters in filenames (which Courier-IMAP uses). I did a really quick check with stock samba 2.2.7 included in RedHat 7.3 and I can create a file named hi:bye and I can read it thru an smb mount... buy if I list the directory containing it, it appears as HIBYE~7C, so it's obviously doing some mangling in there. First question is, can I disable all name mangling on a share that will be accessed only by unix machines? or is there any mounting options that allows me to do this? Second (and most important) question is... will SMB provide better performance or more resilience in an all-linux environment? or should I stick with NFS? TIA. -- Mariano Absatz El Baby -- Double your drive space - delete Windows! -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] samba (vs. nfs) in all unix environment
Hi, i can only answer to one thing, if no windows is involved you havent to use smb at all, for mount files via network. But i remember that i had to use it with a Linux Coldfusion setup, cause the cold fusion server was not able to handle nfs shares. I think i depends deep in what you want to do with your machines to find out what protokoll may the best for you. For courier nfs should be enough, but look here http://www.facetcorp.com/competition_nfs_cifs_comparison.html for more info Let us know your results Best Regards - Original Message - From: Mariano Absatz [EMAIL PROTECTED] To: Samba Mailing List [EMAIL PROTECTED] Sent: Wednesday, November 12, 2003 6:28 PM Subject: [Samba] samba (vs. nfs) in all unix environment Hi, I'm sorry if this is a very FAQ, I've been googling around and searchin' the list archive and I'll gladly accept RTFMs with somehow precise URLs (including URLs to the list archives). I'm on the drawing board (no equipment yet) for a server farm that will have a SteelEye linux cluster behind to provide (among other services) with networked file access. The setup is all-linux (likely RHEL 2.1, less likely RHL 8.0, almost unlikely RHEL 3.0), that is, there will not be no windows clients nor servers. The shared filesystems will be used by a Courier-IMAP server and an Apache httpd 2.0 server. I always did these kind of stuff with NFS and I know it would work, but recently someone told me maybe SMB would yeld better performance and resilience in case of a cluster node failing over to the other one... The point is, I don't know anything about this, and searching the web, newsgroups and mailing list archives didn't bring much light into it. I asked in the Courier-IMAP mailing list and the only answer (from Courier-IMAP developer) only stated that he thought samba wouldn't be able to correctly handle : charaters in filenames (which Courier-IMAP uses). I did a really quick check with stock samba 2.2.7 included in RedHat 7.3 and I can create a file named hi:bye and I can read it thru an smb mount... buy if I list the directory containing it, it appears as HIBYE~7C, so it's obviously doing some mangling in there. First question is, can I disable all name mangling on a share that will be accessed only by unix machines? or is there any mounting options that allows me to do this? Second (and most important) question is... will SMB provide better performance or more resilience in an all-linux environment? or should I stick with NFS? TIA. -- Mariano Absatz El Baby -- Double your drive space - delete Windows! -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Samba versus NFS/ftp
I ran some tests today, ftp'ing a 288MB file to the server was completed in 29.3 seconds, ~10 MB/sec. This is 3 times faster than Samba! which needed 82 seconds using drag/drop on W2K. NFS needed 39 seconds. I have read the 'performance tuning' documents and have done all/most of the changes they recommend but nothing appears to increase the speed. We are running Solaris 8 with Samba V2.2.7. Server has 2GB RAM and (6) mirrored 180GB drives. Does anyone know of any other tuning or what might be happening? Thanks for any help. Graeme Walker System Administrator Exco Engineering [global] workgroup = EXCOENG netbios name = MARS netbios aliases = PHOBOS security = DOMAIN encrypt passwords = Yes password server = trident, rodeo log level = 1 log file = /var/samba/logs/log.%m max log size = 500 name resolve order = host wins bcast deadtime = 15 lpq cache time = 30 socket options = TCP_NODELAY IPTOS_LOWDELAY SO_SNDBUF=16384 SO_RCVBUF=16384 lock dir = /var/samba/locks pid directory = /var/samba/locks write list = administrator printer admin = administrator print command = echo Printing %s at %p /tmp/print.log; /usr/ucb/lpr -P %p %s; rm %s [Eng_share] comment = Engineering data path = /data1/Eng_share read only = No create mask = 0664 force create mode = 0664 directory mask = 0775 force directory mode = 0775 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Samba versus NFS client??
We have been running Samba for several years, recently V2.0.7 on Solaris 7 but just upgraded to V2.2.7 on Solaris 8. The servers are linked to Cisco switches via gigabit adapter and all UNIX and Windows clients are on 100/Full. We have a mixture of AIX, Solaris, NT and 2000 clients We deal the typical Word/Excel/PowerPoint files but also have very large CAD files, 50MB to 2GB. We have never used Samba to serve these larger files because of performance reasons, instead we used Hummingbird Maestro NFS Client on NT/2000. The download speed to UNIX clients has never been a problem and typically works out to be about 5-8MB/sec I did some benchmarks this past week and using NFS the client took 38 seconds to upload a 288MB file to the server while Samba took 82 seconds! Download was, nfs - 50 seconds, Samba - 60 seconds, for the same file. My issue now is that I to get rid of Maestro. I have tried different settings of SO_SNDBUF and SO_RCVBUF, varying from 4096 to 32768, with no net change in speed. Is this just inherent in the smb protocol versus nfs, which is what I have been lead to believe from previous sysadmins? How can I make Samba as fast as NFS? [global] workgroup = EXCOENG netbios name = MARS netbios aliases = PHOBOS security = DOMAIN encrypt passwords = Yes password server = trident, rodeo log level = 1 log file = /var/samba/logs/log.%m max log size = 500 name resolve order = host wins bcast deadtime = 15 lpq cache time = 30 socket options = TCP_NODELAY IPTOS_LOWDELAY lock dir = /var/samba/locks pid directory = /var/samba/locks write list = administrator printer admin = administrator print command = echo Printing %s at %p /tmp/print.log; /usr/ucb/lpr -P %p %s; rm %s [Eng_share] comment = Engineering data path = /data1/Eng_share read only = No create mask = 0664 force create mode = 0664 directory mask = 0775 force directory mode = 0775 Graeme Walker System Administrator Exco Engineering -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Samba to NFS gateway; incorrect mounted space shown on clients
Greetings - and hats off to the Samba coders. ;-) You guys are awesome. Likewise I would like to thank the entire open source community for your hard work, generosity, and for their tolerance. :-/ For those in a rush to want to know what the interesting problem is, skip down to the heading The Problem: at the end of the e-mail. Then come back and read the rest if you're interested. (Yes, I know I'm verbose - as the saying goes, if I had time I'd write a shorter letter.) What we're doing: We've got a machine running Samba 2.2.3a which is acting both as a PDC for XP machines _as well as_ acting as an SMB -- NFS gateway. (I.E. Windows file sharing of nfs automounted directories). Yes, we've gotten that all working. No, it wasn't easy. It's a RedHat 7.2 machine running a stock kernel, but has been updated with Samba 2.2.3a. In brief, the network diagram looks something like this: (Note: this diagram was made in a console text editor) UNIX NFS machines Samba machine Windows clients nfs1 ---\ /- client1 \/ nfs2 -\ /--- client2 \ Samba ---/ nfs_automounter -/ eth0 eth1\ client3 / \ nfs3 /\-- client4 / \ nfs4 --/\ client5 . . . . . . Why we did this: 1. We were dumb and started using Windows XP for clients, not realizing that the nfs client programs that we bought did not support Windows XP. Upon further investigation, none of the nfs clients support automounting, which sucks. 2. We're cheap. We run a tight budget, and we just don't have the funds available to buy nfs clients at $120 a pop for all the machines. 3. Integration considerations. We wanted a single way to deal with all the Windows clients regardless of OS type. Right now we've got many different nfs clients being used (Solstice, WRQ, and Hummingbird) and none of them do everything on all versions of Windows. 4. Ease of install. With this Samba solution, there is no need to install any software on each client to get access to file shares. 5. Peace of mind. It's free software, there are no licenses to have to worry about. 6. Support. Yes I said support. Of the commercial vendors we deal with, we have many that won't bother to return a phone call until a week or so later. By then we've either worked it out for ourselves or we got somebody we knew to do help. The open source community has more often than not been our solution for supporting our problems _anyway_. ;-) What's working: - The user's home directories are mounted through nfs automount, and that seems to work (for the most part), even though the actual location of the nfs share may be on one of 5 machines, yet it appears that all users are under /home. - The Samba machine is able to be a Primary Domain Controller, even for XP machines. Unfortunately we're probably not going to use this capacity due to the requirement for automatic failover to a BDC. In addition, we're not really using the PDC for authentication purposes anyway, so it might not matter in our case. The main thing we're getting out of the PDC is the ability to run a script upon login to track installed software on PC's. - We've set up two interfaces on the Samba machine with a firewall to try to separate smb requests from nfs requests, which seems to be working satisfactorily. - The box has got software root raid with the ability to boot up on both drives. Installing grub on both drives to allow for bootup on both drives was a bit tricky. - We set up a cool text dashboard which uses splitvt to split the terminal window up _three_ ways (ran splitvt, in the upper window ran splitvt again.) The bottom window runs top, the uppermost window runs sar to show network bandwidth information, the middle window shows raid status. We used the 'open' command to run the script in an unused tty at boot time without a login. The problem: - The Samba machine seems to report the incorrect amount of free space to Windows clients on some NFS shares, but reports correctly on others. I.E. Windows clients mount drives using the net use command, and when the free space is checked, some of the mounts show 20 MB
