[Samba] samba + nfs locking doesn't work
this is the case: serverA [ CentOs 5.6 kernel 2.6.18-238.12.1.el5.centos.plus, Samba ver. 3.5.21 ] serverB [ CentOS 5.6 kernel 2.6.18-348.1.1.el5.centos.plus, Samba ver. 3.6.6-0.129.el5 ] clientA [ WindowsXP ] clientB [ WindowsXP ] The serverA shares via Samba the resource [test] [global] workgroup = DMIT netbios name = SAMBA server string = DMIT domain server interfaces = eth0 smb ports = 445 encrypt passwords = yes smb passwd file = /etc/samba/smbpasswd passdb backend = smbpasswd username map = /etc/samba/smbusers log file = /var/log/samba/pc/%m.log time server = Yes logon script = logon.bat logon path = logon drive = M: logon home = \\%L\%U domain logons = yes os level = 33 preferred master = yes domain master = yes local master = yes printjob username = %M\%U hide dot files = No[netlogon] path = /etc/samba/netlogon ; max protocol = smb2 [test] comment = test path = /test read only = no writable = yes create mode = 0775 force create mode = 0775 directory mode = 02775 force directory mode = 02775 public = no oplocks = no il serverB monta tramite client nfs la risorsa /test (mount serverA:/test /test) Queta e' il semplicissimo file di configurazione smb.conf di serverB: [global] workgroup = DMIT domain master = no domain logons = no encrypt passwords = yes security = server password server = serverA interfaces = eth0 smb ports = 445 [test] comment = test path = /test read only = no writable = yes create mode = 0775 force create mode = 0775 directory mode = 02775 force directory mode = 02775 public = no oplocks = no Now on the clientA I open an excel2003 file from \\serverA\test and on clientB i open the same file but from \\serverB\test (consider that test is the same directory mounter from serverA via nfs) This is what happens: 1) I can open without problem the file on clientA from \\serverA\test, instead I have problem to open the the same file from \\serverB\test (after 5min later it goes in timeout) 2) If I add posix locking = no on serverA and on serverB both excel2003 files open without the locking mechanism. 3) I tried various combinations changing kernel oplocks, oplocks, level2 oplocks, posix locking, locking, strict locking, nt acl support but nothing changed. 4) I tried to open the same file from the same serverA (from clientA and from clientB) without nfs and now the locking works well (both from \\serverA\test) The strange thing is that on my company newtwork there are many old samba servers (samba 2.3) and they works well within nfs. The proper way to use samba like a cluser is DFS insead of NFS, but now I can not consider a migration or an upgrade to all the newtork, so the best way at the moment is to use nfs, like the prevoiis sysadmin did. Have you had experience about this strange case? Are there known bugs regarding the new samba versions + nfs ? -- Vincenzo De Sanctis -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] samba + nfs locking doesn't work
is CTDB the solution? 2013/2/25 Vincenzo De Sanctis vincenzo.desanc...@gmail.com: this is the case: serverA [ CentOs 5.6 kernel 2.6.18-238.12.1.el5.centos.plus, Samba ver. 3.5.21 ] serverB [ CentOS 5.6 kernel 2.6.18-348.1.1.el5.centos.plus, Samba ver. 3.6.6-0.129.el5 ] clientA [ WindowsXP ] clientB [ WindowsXP ] The serverA shares via Samba the resource [test] [global] workgroup = DMIT netbios name = SAMBA server string = DMIT domain server interfaces = eth0 smb ports = 445 encrypt passwords = yes smb passwd file = /etc/samba/smbpasswd passdb backend = smbpasswd username map = /etc/samba/smbusers log file = /var/log/samba/pc/%m.log time server = Yes logon script = logon.bat logon path = logon drive = M: logon home = \\%L\%U domain logons = yes os level = 33 preferred master = yes domain master = yes local master = yes printjob username = %M\%U hide dot files = No[netlogon] path = /etc/samba/netlogon ; max protocol = smb2 [test] comment = test path = /test read only = no writable = yes create mode = 0775 force create mode = 0775 directory mode = 02775 force directory mode = 02775 public = no oplocks = no the serverB mounts through nfs the /test resource (mount serverA:/test /test) This is a very simple serverB smb.conf configuration: [global] workgroup = DMIT domain master = no domain logons = no encrypt passwords = yes security = server password server = serverA interfaces = eth0 smb ports = 445 [test] comment = test path = /test read only = no writable = yes create mode = 0775 force create mode = 0775 directory mode = 02775 force directory mode = 02775 public = no oplocks = no Now on the clientA I open an excel2003 file from \\serverA\test and on clientB i open the same file but from \\serverB\test (consider that test is the same directory mounter from serverA via nfs) This is what happens: 1) I can open without problem the file on clientA from \\serverA\test, instead I have problem to open the the same file from \\serverB\test (after 5min later it goes in timeout) 2) If I add posix locking = no on serverA and on serverB both excel2003 files open without the locking mechanism. 3) I tried various combinations changing kernel oplocks, oplocks, level2 oplocks, posix locking, locking, strict locking, nt acl support but nothing changed. 4) I tried to open the same file from the same serverA (from clientA and from clientB) without nfs and now the locking works well (both from \\serverA\test) The strange thing is that on my company newtwork there are many old samba servers (samba 2.3) and they works well within nfs. The proper way to use samba like a cluser is DFS insead of NFS, but now I can not consider a migration or an upgrade to all the newtork, so the best way at the moment is to use nfs, like the prevoiis sysadmin did. Have you had experience about this strange case? Are there known bugs regarding the new samba versions + nfs ? -- Vincenzo De Sanctis -- Vincenzo De Sanctis -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Samba + NFS + APACHE + PHP5 + Symfony
Hello All, I'm new here so I expect to learn a lot using this mail list. Let's directly to my problem. I have here 2 servers, one running Apache + php5 + Symfony, and other server with Samba and nfs. The web-server mount the data from the samba-server by nfs. there are developers that create and edit the data on the samba-server, but the Apache and Symfony create and edit data too, and i'm having serious troubles with permission. The developers access de data by samba, with a single user. the web-server, when mount the data, have permissoin to write, but when he writes, the owner of the file is different from the owner in the samba server. In other words, when the apache user write some data, the samba user cannot edit this data and vice-versa. It's a little hard to explain, so i tried to make as easy as possible to show the problem. I apreciate some help to solve this problem. Thanks for your atention Att. Fábio da Silva Júnior - [EMAIL PROTECTED] Laboratório de Computação Aplicada - G10 Laboratório de Redes UNIVALI - Universidade do Vale do Itajaí -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba + NFS + APACHE + PHP5 + Symfony
I think this is not so much samba related. Can't you just manage to make the webserver user a member of a group, which samba users accessing the files would also be member of ? Then you could only set the setgid bit on directories, and that would do the trick. On Wed, 10 Sep 2008 11:32:34 -0300, Fabio da Silva Junior [EMAIL PROTECTED] wrote: Hello All, I'm new here so I expect to learn a lot using this mail list. Let's directly to my problem. I have here 2 servers, one running Apache + php5 + Symfony, and other server with Samba and nfs. The web-server mount the data from the samba-server by nfs. there are developers that create and edit the data on the samba-server, but the Apache and Symfony create and edit data too, and i'm having serious troubles with permission. The developers access de data by samba, with a single user. the web-server, when mount the data, have permissoin to write, but when he writes, the owner of the file is different from the owner in the samba server. In other words, when the apache user write some data, the samba user cannot edit this data and vice-versa. It's a little hard to explain, so i tried to make as easy as possible to show the problem. I apreciate some help to solve this problem. Thanks for your atention Att. Fábio da Silva Júnior - [EMAIL PROTECTED] Laboratório de Computação Aplicada - G10 Laboratório de Redes UNIVALI - Universidade do Vale do Itajaí -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba + NFS + APACHE + PHP5 + Symfony
add to file /etc/smb.conf on the share in question [the-share] these directives: force user = apache-user force group = apache-user create mask = 0775 so, samba users files writes, just make sure you are matching the user and group to what apache can read :) and still a safer bet is to force EVERYONE to access the filesystem with samba no matter if they have direct access to the server bacuse it will maintain consistency --- On Wed, 9/10/08, François Legal [EMAIL PROTECTED] wrote: From: François Legal [EMAIL PROTECTED] Subject: Re: [Samba] Samba + NFS + APACHE + PHP5 + Symfony To: samba@lists.samba.org Date: Wednesday, September 10, 2008, 8:31 AM I think this is not so much samba related. Can't you just manage to make the webserver user a member of a group, which samba users accessing the files would also be member of ? Then you could only set the setgid bit on directories, and that would do the trick. On Wed, 10 Sep 2008 11:32:34 -0300, Fabio da Silva Junior [EMAIL PROTECTED] wrote: Hello All, I'm new here so I expect to learn a lot using this mail list. Let's directly to my problem. I have here 2 servers, one running Apache + php5 + Symfony, and other server with Samba and nfs. The web-server mount the data from the samba-server by nfs. there are developers that create and edit the data on the samba-server, but the Apache and Symfony create and edit data too, and i'm having serious troubles with permission. The developers access de data by samba, with a single user. the web-server, when mount the data, have permissoin to write, but when he writes, the owner of the file is different from the owner in the samba server. In other words, when the apache user write some data, the samba user cannot edit this data and vice-versa. It's a little hard to explain, so i tried to make as easy as possible to show the problem. I apreciate some help to solve this problem. Thanks for your atention Att. Fábio da Silva Júnior - [EMAIL PROTECTED] Laboratório de Computação Aplicada - G10 Laboratório de Redes UNIVALI - Universidade do Vale do Itajaí -- 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 / NFS performance
Alexander Gelf schrieb: Attached. You may want to experiment with these options: # Most people will find that this option gives better performance. # See the chapter 'Samba performance issues' in the Samba HOWTO Collection # and the manual pages for details. # You may want to add the following on a Linux system: ; socket options = SO_RCVBUF=8192 SO_SNDBUF=8192 You may also want to set these options explicitly (depending how you start Samba, but it won't hurt): log level = 0 syslog = 0 Otherwise, your Samba may be logging too much, causing unnecessary writes. Note that Samba will be always slower than a lower-level NFS (which, in turn will be slower than iSCSI etc.). -- Tomasz Chmielewski http://wpkg.org -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Samba / NFS performance
I have the following network configuration: Server FreeBSD 6.2 P4 3Ghz, 1GB RAM Samba 3.0.24 (options: WITH_ADS, WITH_PAM, WITH_SENDFILE, WITH_UTMP, WITH_WINBIND) Standard FreeBSD NFS Server Adaptec 2410SA controller with 4 drives running RAID5 Broadcom GigE Client Windows XP MCE Microsoft SFU 3.5 running NFS client over UDP The client and the server are connected to the same GigE switch. When I copy one large file (10GB) from the client to the server over an NFS mount I get an average performance of 18MB/s. The same file copied from the same directory on the client to the same directory on the server over a Samba mount averages 4Mb/s. Any ideas on why is there such a huge performance difference and what can I do to improve Samba performance are appreciated. Regards, AG -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba / NFS performance
Alexander Gelf schrieb: I have the following network configuration: Server FreeBSD 6.2 P4 3Ghz, 1GB RAM Samba 3.0.24 (options: WITH_ADS, WITH_PAM, WITH_SENDFILE, WITH_UTMP, WITH_WINBIND) Standard FreeBSD NFS Server Adaptec 2410SA controller with 4 drives running RAID5 Broadcom GigE Client Windows XP MCE Microsoft SFU 3.5 running NFS client over UDP The client and the server are connected to the same GigE switch. When I copy one large file (10GB) from the client to the server over an NFS mount I get an average performance of 18MB/s. The same file copied from the same directory on the client to the same directory on the server over a Samba mount averages 4Mb/s. Any ideas on why is there such a huge performance difference and what can I do to improve Samba performance are appreciated. your smb.conf? -- Tomasz Chmielewski http://wpkg.org -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba / NFS performance
Attached. AG Tomasz Chmielewski wrote: Alexander Gelf schrieb: I have the following network configuration: Server FreeBSD 6.2 P4 3Ghz, 1GB RAM Samba 3.0.24 (options: WITH_ADS, WITH_PAM, WITH_SENDFILE, WITH_UTMP, WITH_WINBIND) Standard FreeBSD NFS Server Adaptec 2410SA controller with 4 drives running RAID5 Broadcom GigE Client Windows XP MCE Microsoft SFU 3.5 running NFS client over UDP The client and the server are connected to the same GigE switch. When I copy one large file (10GB) from the client to the server over an NFS mount I get an average performance of 18MB/s. The same file copied from the same directory on the client to the same directory on the server over a Samba mount averages 4Mb/s. Any ideas on why is there such a huge performance difference and what can I do to improve Samba performance are appreciated. your smb.conf? # This is the main Samba configuration file. You should read the # smb.conf(5) manual page in order to understand the options listed # here. Samba has a huge number of configurable options (perhaps too # many!) most of which are not shown in this example # # For a step to step guide on installing, configuring and using samba, # read the Samba-HOWTO-Collection. This may be obtained from: # http://www.samba.org/samba/docs/Samba-HOWTO-Collection.pdf # # Many working examples of smb.conf files can be found in the # Samba-Guide which is generated daily and can be downloaded from: # http://www.samba.org/samba/docs/Samba-Guide.pdf # # Any line which starts with a ; (semi-colon) or a # (hash) # is a comment and is ignored. In this example we will use a # # for commentry and a ; for parts of the config file that you # may wish to enable # # NOTE: Whenever you modify this file you should run the command testparm # to check that you have not made any basic syntactic errors. # #=== Global Settings = [global] # workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH workgroup = MSHOME # server string is the equivalent of the NT Description field server string = Samba Server - BSD # Security mode. Defines in which mode Samba will operate. Possible # values are share, user, server, domain and ads. Most people will want # user level security. See the Samba-HOWTO-Collection for details. security = user # This option is important for security. It allows you to restrict # connections to machines which are on your local network. The # following example restricts access to two C class networks and # the loopback interface. For more examples of the syntax see # the smb.conf man page ; hosts allow = 192.168.1. 192.168.2. 127. ; hosts allow = 192.168.l6. 127. hosts allow = ; interfaces = bge0 lo0 # If you want to automatically load your printer list rather # than setting them up individually then you'll need this ; load printers = yes # you may wish to override the location of the printcap file ; printcap name = /etc/printcap # on SystemV system setting printcap name to lpstat should allow # you to automatically obtain a printer list from the SystemV spool # system ; printcap name = lpstat # It should not be necessary to specify the print system type unless # it is non-standard. Currently supported print systems include: # bsd, cups, sysv, plp, lprng, aix, hpux, qnx ; printing = cups # Uncomment this if you want a guest account, you must add this to /etc/passwd # otherwise the user nobody is used ; guest account = pcguest # this tells Samba to use a separate log file for each machine # that connects log file = /var/log/samba/log.%m # Put a capping on the size of the log files (in Kb). max log size = 50 # Use password server option only with security = server # The argument list may include: # password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name] # or to auto-locate the domain controller/s # password server = * ; password server = NT-Server-Name # Use the realm option only with security = ads # Specifies the Active Directory realm the host is part of ; realm = MY_REALM # Backend to store user information in. New installations should # use either tdbsam or ldapsam. smbpasswd is available for backwards # compatibility. tdbsam requires no further configuration. passdb backend = tdbsam # Using the following line enables you to customise your configuration # on a per machine basis. The %m gets replaced with the netbios name # of the machine that is connecting. # Note: Consider carefully the location in the configuration file of # this line. The included file is read at that point. ; include = /usr/local/etc/smb.conf.%m # Most people will find that this option gives better performance. # See the chapter 'Samba performance issues' in the Samba HOWTO Collection # and the manual pages for details. # You may want to add the following on a Linux system: ; socket options = SO_RCVBUF=8192 SO_SNDBUF=8192 # Configure
[Samba] Samba NFS
Hi! I have this linux box running Fedora 3 which mounts a NFS directory and inturn, exports this mounted directory to Windows clients using Samba. Everything works fine till I upgraded the box to Fedora 4. The error message from the Windows client says path not found when I try clicking on the shared folder. I can access the NFS mounted directory from the Linux box without any problem. The Samba configuration is correct as I have no problem sharing local drive in the linux box. Any clue how I can solve this problem? Thanks in advance! Victor -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba + NFS + Solaris 9
Jason, The private and samba configuration files are on the local disk on the Solaris machine. Particularly in /opt/csw/*. The only thing NFS mounted is /export from Machine A, which contains project folders and user directories. I am currently contemplating putting Samba on Machine A, seeing as this seems a bit impossible at the moment. I think this is the best work-around for the time being, unless someone can give me another solution. -Torey On Mon, 2005-07-18 at 11:28 -0500, Jason Signalness wrote: Torey, We used a similar configuration for quite some time. Are your Samba binaries (in particular, the private directory) on a local disk, or an NFS mount? We were trying to run Samba from an NFS mount, to share out other NFS mounts. It would not work unless the Samba binaries were on a local (non-nfs) disk. Hope that helps. -Jason Torey Alford wrote: I was trolling around on the lists, and noticed that there were a few people who had issues with making Samba share directories which happend to be NFS mounts. That is, on Machine A, I am exporting (via NFS) /export, and on Machine B, I have mounted MachineA:/export to /export on this machine. Machine B is also the Samba box in which I share /export/shared. Whenever a Win32 user browses the folders, it seems to be okay. However, the moment a write attempt occurs, the Samba process spazzes out, and the Win32 client freezes waiting for the spazzed process to complete. General Information: Machine A: (NFS box) * Sun Fire V440 * Solaris 9 Machine B: (Samba box) * Sun Enterprise 420 * Solaris 9 * Samba 3.0.14a Configuration File: [global] encrypt passwords = true netbios name = geometry server string = Information Server security = user workgroup = MyWorkgroup domain logons = yes domain master = yes local master = yes preferred master = yes os level = 255 wins support = yes time offset = 60 time server = True passdb backend = ldapsam:ldap://192.168.0.2/ ldap passwd sync = Yes ldap admin dn = uid=sysadmin,ou=people,dc=localhost ldap ssl = no password server = 192.168.0.2 ldap suffix = dc=localhost ldap machine suffix = ou=People ldap user suffix = ou=People ldap group suffix = ou=Groups ldap machine suffix = ou=Computers ldap passwd sync = yes log level = 1 logon home = \\%L\%U logon path = \\%L\profiles\%U logon drive = H: admin users = sysadmin tor Administrator # Needed for NFS handling lock directory = /opt/csw/var/locks/samba kernel oplocks = no oplocks = yes level2 oplocks = yes veto oplock files = /*.mdb/ posix locking = yes hide dot files = no [homes] read only = no create mode = 0600 directory mode = 0700 [share] path = /export/share create mode = 0664 read only = no [profiles] path = /export/profiles writeable = yes browseable = no create mask = 0600 directory mask = 0700 profile acls = yes Any help would be much appreciated! -Torey -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Samba + NFS + Solaris 9
I was trolling around on the lists, and noticed that there were a few people who had issues with making Samba share directories which happend to be NFS mounts. That is, on Machine A, I am exporting (via NFS) /export, and on Machine B, I have mounted MachineA:/export to /export on this machine. Machine B is also the Samba box in which I share /export/shared. Whenever a Win32 user browses the folders, it seems to be okay. However, the moment a write attempt occurs, the Samba process spazzes out, and the Win32 client freezes waiting for the spazzed process to complete. General Information: Machine A: (NFS box) * Sun Fire V440 * Solaris 9 Machine B: (Samba box) * Sun Enterprise 420 * Solaris 9 * Samba 3.0.14a Configuration File: [global] encrypt passwords = true netbios name = geometry server string = Information Server security = user workgroup = MyWorkgroup domain logons = yes domain master = yes local master = yes preferred master = yes os level = 255 wins support = yes time offset = 60 time server = True passdb backend = ldapsam:ldap://192.168.0.2/ ldap passwd sync = Yes ldap admin dn = uid=sysadmin,ou=people,dc=localhost ldap ssl = no password server = 192.168.0.2 ldap suffix = dc=localhost ldap machine suffix = ou=People ldap user suffix = ou=People ldap group suffix = ou=Groups ldap machine suffix = ou=Computers ldap passwd sync = yes log level = 1 logon home = \\%L\%U logon path = \\%L\profiles\%U logon drive = H: admin users = sysadmin tor Administrator # Needed for NFS handling lock directory = /opt/csw/var/locks/samba kernel oplocks = no oplocks = yes level2 oplocks = yes veto oplock files = /*.mdb/ posix locking = yes hide dot files = no [homes] read only = no create mode = 0600 directory mode = 0700 [share] path = /export/share create mode = 0664 read only = no [profiles] path = /export/profiles writeable = yes browseable = no create mask = 0600 directory mask = 0700 profile acls = yes Any help would be much appreciated! -Torey -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba + NFS + Solaris 9
Torey, We used a similar configuration for quite some time. Are your Samba binaries (in particular, the private directory) on a local disk, or an NFS mount? We were trying to run Samba from an NFS mount, to share out other NFS mounts. It would not work unless the Samba binaries were on a local (non-nfs) disk. Hope that helps. -Jason Torey Alford wrote: I was trolling around on the lists, and noticed that there were a few people who had issues with making Samba share directories which happend to be NFS mounts. That is, on Machine A, I am exporting (via NFS) /export, and on Machine B, I have mounted MachineA:/export to /export on this machine. Machine B is also the Samba box in which I share /export/shared. Whenever a Win32 user browses the folders, it seems to be okay. However, the moment a write attempt occurs, the Samba process spazzes out, and the Win32 client freezes waiting for the spazzed process to complete. General Information: Machine A: (NFS box) * Sun Fire V440 * Solaris 9 Machine B: (Samba box) * Sun Enterprise 420 * Solaris 9 * Samba 3.0.14a Configuration File: [global] encrypt passwords = true netbios name = geometry server string = Information Server security = user workgroup = MyWorkgroup domain logons = yes domain master = yes local master = yes preferred master = yes os level = 255 wins support = yes time offset = 60 time server = True passdb backend = ldapsam:ldap://192.168.0.2/ ldap passwd sync = Yes ldap admin dn = uid=sysadmin,ou=people,dc=localhost ldap ssl = no password server = 192.168.0.2 ldap suffix = dc=localhost ldap machine suffix = ou=People ldap user suffix = ou=People ldap group suffix = ou=Groups ldap machine suffix = ou=Computers ldap passwd sync = yes log level = 1 logon home = \\%L\%U logon path = \\%L\profiles\%U logon drive = H: admin users = sysadmin tor Administrator # Needed for NFS handling lock directory = /opt/csw/var/locks/samba kernel oplocks = no oplocks = yes level2 oplocks = yes veto oplock files = /*.mdb/ posix locking = yes hide dot files = no [homes] read only = no create mode = 0600 directory mode = 0700 [share] path = /export/share create mode = 0664 read only = no [profiles] path = /export/profiles writeable = yes browseable = no create mask = 0600 directory mask = 0700 profile acls = yes Any help would be much appreciated! -Torey -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba NFS Fedora Core 2 and Software Raid -- Ext3 fs got corrupted???
On Sat, 2004-07-03 at 04:13, Terry Bowling wrote: I'm running: Fedora Core 2 (2.6.6.1-435) Samba 3.0.3-5 My shared (raid1 mirror) data directory is: /dev/md3 (hda6,hdc6) mounted as Ext3 to /sites This is shared to 300 users as an nfs mount point to their Digital Unix workstations as well as a Samba share to their W2k PC's. My users just reported a bunch of read only error messages. Turns out, it corrupted the file system. It said it had no errors and when I did an mdadm --details /dev/md3 it said the raid devices were clean. But the filesystem was read only even for root. I finally gave up and rebooted and it said the filesystem was corrupted and I would have to run fsck manually. Are there any issues where Samba has been know to corrupt a filesystem? No. It is not possible for Samba (as a userspace application) to be responsible for filesystem corruption. This is the responsibility of the kernel. If you are seeing such corruption, then it is a kernel bug, and needs to be fixed there. I am also unaware of any situation in which Samba can 'trigger' such corruption, so I think you should look instead at the usual problems - unclean shutdowns etc, and/or possible kernel bugs. Were your filesystems mounted read-only, or just permissioned that way? Andrew Bartlett signature.asc Description: This is a digitally signed message part -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: Re: [Samba] samba nfs...
Just wanted you to know that this problem was solved by rebooting one of the nodes in our NFS fileservercluster. Since the user claimed one of his fellow-workers (with his home on the same node) was able to get locks on the fs I dismissed this cause earlier. What have we learned today? :) /shoe [2002/11/28 14:05:54, 0] locking/posix.c:(669) an No locks available error. This can happen when using 64 bit lock offsets [2002/11/28 14:05:54, 0] locking/posix.c:(670) on 32 bit NFS mounted file systems. Errr - I'd guess what's happening is what the error says :-). And when I added that message I thought it'd be very clear :-(. The kernel Samba is running on supports 64 bit fcntl locks, however the underlying (NFS) filesystem that the files are being shared from only supports 32 bit locks. Thus the lock request is being denied. If these files are only being accessed by Windows users (the usual case for MS-Office files, unless you have OpenOffice on IRIX) then you can turn off the mapping down to POSIX locking by setting the parameter posix locking = False. No harm done. Jeremy. ;) It's not that I didn't understand what the message itself meant, just that it worked a few days ago (or so I have been told :) and I haven't made any changes in the system. What could have been the source of this problem? The kernel has always been 64bit on this machine, and the NFS(3) as far as I know is always 64bit (XFS between two 64bit machines) so I just thought that since the err message said ..can happen.. I thought it could have other causes to. If I set posix locking = False, what potential dangers do I face? Except the obvious 'open one document from two locations' -issue. We don't use any form of Office suite on IRIX (unforitently), but the files are frequentlly used on the Unix side, via apache etc.. Thanks Jeremy! /shoe -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: Re: [Samba] samba nfs...
On Thu, 28 Nov 2002 [EMAIL PROTECTED] wrote: On Thu, Nov 28, 2002 at 05:02:24PM +0100, Stefan Nordlander wrote: Hi, I'm having problems with M$ Office files on an samba mounted fs. Here's the deal. Server A is an NFS server holding the homes. (Irix 6.5.14) Server B is the Samba server (Samba 2.2.2, kernel oplocks = no, Irix 6.5.14) The homes are nfs-mounted on the Samba server (autofs), and all is well until someone tries to open or create an Microsoft Office Document. I suppose it has something to do with the (bloody) ~$blahblah.doc files that are created by Office.. The log.smbd gives: [2002/11/28 14:05:54, 0] locking/posix.c:(667) posix_fcntl_lock: WARNING: lock request at offset 2147483538, length 1 returned [2002/11/28 14:05:54, 0] locking/posix.c:(669) an No locks available error. This can happen when using 64 bit lock offsets [2002/11/28 14:05:54, 0] locking/posix.c:(670) on 32 bit NFS mounted file systems. Errr - I'd guess what's happening is what the error says :-). And when I added that message I thought it'd be very clear :-(. The kernel Samba is running on supports 64 bit fcntl locks, however the underlying (NFS) filesystem that the files are being shared from only supports 32 bit locks. Thus the lock request is being denied. If these files are only being accessed by Windows users (the usual case for MS-Office files, unless you have OpenOffice on IRIX) then you can turn off the mapping down to POSIX locking by setting the parameter posix locking = False. No harm done. Jeremy. ;) It's not that I didn't understand what the message itself meant, just that it worked a few days ago (or so I have been told :) and I haven't made any changes in the system. What could have been the source of this problem? The kernel has always been 64bit on this machine, and the NFS(3) as far as I know is always 64bit (XFS between two 64bit machines) so I just thought that since the err message said ..can happen.. I thought it could have other causes to. If I set posix locking = False, what potential dangers do I face? Except the obvious 'open one document from two locations' -issue. We don't use any form of Office suite on IRIX (unforitently), but the files are frequentlly used on the Unix side, via apache etc.. Thanks Jeremy! /shoe -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] samba nfs...
Hi, I'm having problems with M$ Office files on an samba mounted fs. Here's the deal. Server A is an NFS server holding the homes. (Irix 6.5.14) Server B is the Samba server (Samba 2.2.2, kernel oplocks = no, Irix 6.5.14) The homes are nfs-mounted on the Samba server (autofs), and all is well until someone tries to open or create an Microsoft Office Document. I suppose it has something to do with the (bloody) ~$blahblah.doc files that are created by Office.. The log.smbd gives: [2002/11/28 14:05:54, 0] locking/posix.c:(667) posix_fcntl_lock: WARNING: lock request at offset 2147483538, length 1 returned [2002/11/28 14:05:54, 0] locking/posix.c:(669) an No locks available error. This can happen when using 64 bit lock offsets [2002/11/28 14:05:54, 0] locking/posix.c:(670) on 32 bit NFS mounted file systems. [2002/11/28 14:06:06, 0] locking/posix.c:(667) posix_fcntl_lock: WARNING: lock request at offset 2147483538, length 1 returned [2002/11/28 14:06:06, 0] locking/posix.c:(669) an No locks available error. This can happen when using 64 bit lock offsets [2002/11/28 14:06:06, 0] locking/posix.c:(670) on 32 bit NFS mounted file systems. [2002/11/28 14:06:32, 0] locking/posix.c:(667) posix_fcntl_lock: WARNING: lock request at offset 2147483538, length 1 returned [2002/11/28 14:06:32, 0] locking/posix.c:(669) an No locks available error. This can happen when using 64 bit lock offsets [2002/11/28 14:06:32, 0] locking/posix.c:(670) on 32 bit NFS mounted file systems. Does anyone have any idea what the h£$% is going on? Thanks! :wq //shoe - UNIX _IS_ user friendly, its just picky about who its friends are... -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] samba nfs...
On Thu, Nov 28, 2002 at 05:02:24PM +0100, Stefan Nordlander wrote: Hi, I'm having problems with M$ Office files on an samba mounted fs. Here's the deal. Server A is an NFS server holding the homes. (Irix 6.5.14) Server B is the Samba server (Samba 2.2.2, kernel oplocks = no, Irix 6.5.14) The homes are nfs-mounted on the Samba server (autofs), and all is well until someone tries to open or create an Microsoft Office Document. I suppose it has something to do with the (bloody) ~$blahblah.doc files that are created by Office.. The log.smbd gives: [2002/11/28 14:05:54, 0] locking/posix.c:(667) posix_fcntl_lock: WARNING: lock request at offset 2147483538, length 1 returned [2002/11/28 14:05:54, 0] locking/posix.c:(669) an No locks available error. This can happen when using 64 bit lock offsets [2002/11/28 14:05:54, 0] locking/posix.c:(670) on 32 bit NFS mounted file systems. Errr - I'd guess what's happening is what the error says :-). And when I added that message I thought it'd be very clear :-(. The kernel Samba is running on supports 64 bit fcntl locks, however the underlying (NFS) filesystem that the files are being shared from only supports 32 bit locks. Thus the lock request is being denied. If these files are only being accessed by Windows users (the usual case for MS-Office files, unless you have OpenOffice on IRIX) then you can turn off the mapping down to POSIX locking by setting the parameter posix locking = False. No harm done. Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba + NFS virtual directories question
Hey, Joseph. I don't know what OS you are using, I prefer to use home directories but I tried one set at /opt/applix (automounted to the opt) drive and mounted unde winnt as \\mfg\win_c. Worked perfectly fine with the size. Win 95, 98, ME, 2000, XP. All behave the same way on this. Check your /opt directory on your system. My guess is that it should look something like the following: drwxr-xr-x 2 root wheel 0 May 1 10:10 opt This means that the virtual directory where you're mounting your nfs shares does not have any space available. When you try to share this directory with samba, everything under it will show 0 space free. Try this: make a new share on your system, which looks like this: [win_test] path = /opt read only = Yes guest ok = Yes browseable = Yes After mounting a _directory_ under [win_test] on a client, and looking at the properties, you'll probably see that the share has 0 space. ;-) What you've got below works _because_ the actual share is _not_ of the /opt directory directly. [win_c] path = /opt/applix read only = Yes guest ok = Yes browsabel = yes auto.opt applix mfg:/export/home/opt/ local mfg:/export/home/opt/ netscapemfg:/export/home/opt/ netscape-6 mfg:/export/home/opt/ oracle mfg:/export/home/opt/ staroffice mfg:/export/home/opt/staroffice/5.2 auto.master /home /etc/auto.home /misc /etc/auto.misc --timeout=60 /opt/etc/auto.opt --timeout=60 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Samba + NFS virtual directories question
We're using a Samba machine as an SMB - NFS gateway. I.E. actual file shares are via nfs, and Windows clients make requests via Samba. There are virtual directories set up on the Samba machine for automounted nfs shares. (There are a number of nfs servers, and there are a couple of virtual directories where many of these shares show up.) Those virtual directories are being shared as samba shares. This is the only way we've found so far to share everything in these virtual directories easily. (Too many subdirectories to make individual shares). The problem is that when things are shared in this way, drive mounts on the Windows clients show that the share has no drive space left, and 20 MB total space. This makes sense, because the directory being used for automounting is a virtual directory, which has 0 bytes free. Note: a samba share of a directory _under_ the virtual directory where things are automounted does not have the problem and reports the correct amount of free space from the nfs server. User directories work fine because the CIFS homes share causes the user's home directory to automatically come up as a separate share, which alleviates the problem in that instance. A workaround which is useful, but not perfect, is to make a new directory on the local machine which is writable which contains links to the subdirectories of the virtual directory where nfs automounts reside. Sharing this directory then shows the free space available on the Samba machine, rather than of the nfs shares. This alleviates the client machines being shown that there are 0 bytes available for the shares. It also requires making links for every subdirectory in the automounted nfs shares, and having to maintain that list. Example for clarification purposes - /drive is one of the directories used for automount nfs shares. /drive/space1 is one of the directories that can be automounted /drive_links is a directory of links to subdirectories under /drive, and space1 is a link in this directory pointing to /drive/space1. smb.conf: --- a bunch of settings I'm leaving out [drive] path = /drive read only = No [drivelinks] path = /drive_links read only = No [space1] path = /drive/space1 read only = No In this example, after mounting the drives on the client, the [drive] share shows 0 bytes available, the [space1] share shows the available free space of the NFS share, and [drivelinks]/space1 shows the available free space of the partition on the Samba machine where the /drive_links directory resides. If anyone has come across with a solution for sharing an NFS automount directory that's a little more elegant than this I would really like to know. Thanks - Chris Chris Knadle [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba + NFS virtual directories question
I have automounts for my shares. Under windows 98 it shows the proper free space once you do a map. It is very similiar your part of the conf file. You might need to check how your automounts are working. Chris Knadle wrote: We're using a Samba machine as an SMB - NFS gateway. I.E. actual file shares are via nfs, and Windows clients make requests via Samba. There are virtual directories set up on the Samba machine for automounted nfs shares. (There are a number of nfs servers, and there are a couple of virtual directories where many of these shares show up.) Those virtual directories are being shared as samba shares. This is the only way we've found so far to share everything in these virtual directories easily. (Too many subdirectories to make individual shares). The problem is that when things are shared in this way, drive mounts on the Windows clients show that the share has no drive space left, and 20 MB total space. This makes sense, because the directory being used for automounting is a virtual directory, which has 0 bytes free. Note: a samba share of a directory _under_ the virtual directory where things are automounted does not have the problem and reports the correct amount of free space from the nfs server. User directories work fine because the CIFS homes share causes the user's home directory to automatically come up as a separate share, which alleviates the problem in that instance. A workaround which is useful, but not perfect, is to make a new directory on the local machine which is writable which contains links to the subdirectories of the virtual directory where nfs automounts reside. Sharing this directory then shows the free space available on the Samba machine, rather than of the nfs shares. This alleviates the client machines being shown that there are 0 bytes available for the shares. It also requires making links for every subdirectory in the automounted nfs shares, and having to maintain that list. Example for clarification purposes - /drive is one of the directories used for automount nfs shares. /drive/space1 is one of the directories that can be automounted /drive_links is a directory of links to subdirectories under /drive, and space1 is a link in this directory pointing to /drive/space1. smb.conf: --- a bunch of settings I'm leaving out [drive] path = /drive read only = No [drivelinks] path = /drive_links read only = No [space1] path = /drive/space1 read only = No In this example, after mounting the drives on the client, the [drive] share shows 0 bytes available, the [space1] share shows the available free space of the NFS share, and [drivelinks]/space1 shows the available free space of the partition on the Samba machine where the /drive_links directory resides. If anyone has come across with a solution for sharing an NFS automount directory that's a little more elegant than this I would really like to know. Thanks - Chris Chris Knadle [EMAIL PROTECTED] -- Joseph Loo [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
