After having setup our workarounds for NFS we are very happy with how it's working. Now we're looking at Samba. But we have quite a showstopper right at the beginning. The smb/cifs clients, be it smbclient or Windows XP, don't like their TCP stream being resetted and don't retry/reconnect (contrary to NFS). It looks like the protocol has no considerations for retries above the TCP/IP level. So when the TCP stream is torn on the server's side due to relocation (either due to crash/fencing or soft) any client smb/cifs activity is broken at that time. This means that any data transfer via smb/cifs shares during the relocation will fail, and there is nothing we can do on the server's side. Or is there? -- Axel.Thimm at ATrpms.net
Attachment:
pgp1AgXxdRNUX.pgp
Description: PGP signature
-- Linux-cluster@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/linux-cluster
