Re: GFS and samba problem, again

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Sandra,
I tried your test with 4 windows machines. 3 real machines and 1 simulated in vmware - all running windows xp home. Everything runs fine:
smbstatus on the samba server shows me this:
[root@niobe-04 ~]# smbstatus

Samba version 3.0.10-1.4E.2
PID     Username      Group         Machine
-------------------------------------------------------------------
 775   testmonkey    testmonkeys   ccc-t3n2rexrla7 (10.15.80.203)
 777   testmonkey    testmonkeys   migael       (10.15.80.222)
 774   testmonkey    testmonkeys   bbb-34gtsedgprj (10.15.80.6)
 776   testmonkey    testmonkeys   schumi       (10.15.80.209)

Service      pid     machine       Connected at
-------------------------------------------------------
public         774   bbb-34gtsedgprj  Wed Oct 11 15:03:10 2006
public         776   schumi        Wed Oct 11 15:03:11 2006
IPC$           777   migael        Wed Oct 11 15:43:58 2006
public         777   migael        Wed Oct 11 15:03:25 2006
public         775   ccc-t3n2rexrla7  Wed Oct 11 15:03:10 2006

Locked files:
Pid    DenyMode   Access      R/W        Oplock           Name
--------------------------------------------------------------
777 DENY_NONE 0x20089 RDONLY NONE /public/TruthHappens.ogg Wed Oct 11 17:39:16 2006 775 DENY_NONE 0x20089 RDONLY NONE /public/TruthHappens.ogg Wed Oct 11 17:39:16 2006 774 DENY_NONE 0x20089 RDONLY NONE /public/TruthHappens.ogg Wed Oct 11 17:39:07 2006 776 DENY_NONE 0x20089 RDONLY NONE /public/TruthHappens.ogg Wed Oct 11 17:39:06 2006

My smb.conf looks like this :
[public]
       comment         = ShareGFS
       path            = /public
       writeable       = No
       read only       = Yes
       write list      = @admsamba
       force group     = root
       create mask     = 0775
       directory mask  = 0775
       oplocks         = No
       locking = Yes
       strict locking = Yes

Also, since the share is readonly, there shouldn't be (m)any locks involved, which makes your problem seem all the more odd. Let me know if there's anything else I can try. Also, I'm curious about your test results with gfs2 and gfs1 from the RHEL4 branch.

Regards,
--Abhi

--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster

[Index of Archives]     [Corosync Cluster Engine]     [GFS]     [Linux Virtualization]     [Centos Virtualization]     [Centos]     [Linux RAID]     [Fedora Users]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Camping]

  Powered by Linux