Re: [Samba] GFS and samba problem, again
Hi,
I proved strace -f -ttT -o /tmp/smbd.out -p smbd-pid to guess
what's happenning, and it seems that system calls like
write,open,flock, never finish until samba is restarted.
4665 11:09:31.068381 kill(4666, SIG_0 unfinished ...
4665 11:09:31.068750 ... kill resumed ) = -1 EPERM (Operation not
permitted) 0.000310
4665 11:09:31.068996 kill(4665, SIG_0 unfinished ...
4665 11:09:31.069260 ... kill resumed ) = 0 0.000205
4665 11:09:31.069458 kill(4667, SIG_0 unfinished ...
4665 11:09:31.069617 ... kill resumed ) = 0 0.99
4665 11:09:31.069781 open(cint95-intel.mtw, O_RDONLY|O_LARGEFILE
unfinished ...
4665 11:09:31.070150 ... open resumed ) = 22 0.000293
4665 11:09:31.070396 geteuid32( unfinished ...
4665 11:09:31.070649 ... geteuid32 resumed ) = 503 0.000195
4665 11:09:31.070937 write(19, prova03 opened file cint95-intel...,
67 unfinished ...
4665 11:09:31.071282 ... write resumed ) = 67 0.000261
4665 11:09:31.071511 flock(22, 0x60 /* LOCK_??? */ unfinished ...
4665 11:09:31.071770 ... flock resumed ) = 0 0.000197
4665 11:09:31.072127 write(5,
\0\0\0g\377SMB\242\0\0\0\0\210\1\310\0\0\0\0\0\0\0\0\0..., 107
unfinished ...
4665 11:09:31.072447 ... write resumed ) = 107 0.000212
.
4665 11:09:31.242316 ... geteuid32 resumed ) = 503 0.000118
4665 11:09:31.242405 write(19, close fd=22 fnum=6371 (numopen=2...,
34) = 34 0.31
4665 11:09:31.242572 nanosleep({0, 201}, unfinished ...
4667 11:09:31.245063 kill(4665, SIG_0) = 0 0.18
4665 11:09:31.248047 ... nanosleep resumed NULL) = 0 0.005406
4665 11:09:31.249355 nanosleep({0, 201}, NULL) = 0 0.002621
4665 11:09:31.252091 nanosleep({0, 201}, NULL) = 0 0.003853
4665 11:09:31.256088 nanosleep({0, 201}, NULL) = 0 0.003906
.. a lot of nanosleeps ..
4665 11:10:04.887037 nanosleep({0, 201}, unfinished ...
4665 11:10:04.887219 ... nanosleep resumed 0) = ?
ERESTART_RESTARTBLOCK (To be restarted) 0.000111
4665 11:10:04.888197 +++ killed by SIGKILL +++
4667 11:10:04.890712 kill(4665, SIG_0 unfinished ...
4666 11:10:04.920965 kill(4665, SIG_0) = -1 ESRCH (No such process)
0.17
4667 11:10:04.934486 kill(4665, SIG_0 unfinished ...
BTW, it is a _REALLY_ bad idea to export the same fs via two
cluster nodes at the same time with current Samba.
At this time, we aren't exporting the same fs via two cluster nodes
since samba in node2 is stopped, and the problem remains.
Any help will be appreciated,
Sandra Hernàndez
Volker Lendecke wrote:
On Wed, Oct 04, 2006 at 02:15:45PM +0200, sandra-llistes wrote:
When we try to access from a single windows client it works fine, but
when we try to access to the same file from 2 or more windows clients
simoultaneously, windows hangs and samba also does. This seems not to
happen with concurrent access to different files or with linux clients.
To really figure out what's going on you need to strace the
smbd process.
strace -ttT -o /tmp/smbd.out -p smbd-pid
If you have the hang then wait some seconds, kill the
appropriate smbd and look at /tmp/smbd.out where the smbd
has been stuck. 99% it's in a filesystem related call, and
then it's a GFS problem. I'm pretty sure this is GFS because
I do not see any reason why Samba itself would behave
differently when running on two cluster nodes.
BTW, it is a _REALLY_ bad idea to export the same fs via two
cluster nodes at the same time with current Samba. It
_might_ be ok because you have one read only and only one
r/w. If you had both r/w then data corruption would
inevitably follow, we're right now working on a cluster
version of Samba that would allow this properly.
Volker
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] GFS and samba
Hi Andrew, We open a bug-request to GFS-developers and send an e-mail to linux-cluster list but received no answers yet. As I said the files aren't accessed simoultaneously, one Node (node1) is sharing information about programs used in our university (share1), this share is used by windows clients that only are connected to node1. Other clients (Linux) connect to node2 that shares the same, but that clients aren't accessing to the same information because the programs used are different. Any idees in order to debug it? It's good news to know that clusterizable samba is a proposal and I will subscribe to samba-technical to read about that. I read too that we can put samba configuration and files in the GFS filesystem in order to share states,information,locks and so on. We are mounting a test environment with two test servers, one GFS filesystem and samba to see what configurations can be used to make it working better. Best Regards, Sandra Andrew Bartlett wrote: On Wed, 2006-09-27 at 17:20 +0200, sandra-llistes wrote: Hello, We have two Fedora 5 Servers clustered with GFS. We installed samba and exported the same shares in both of them. All went fine at first, with people accessing to theirs own files and so, but for some programs (minitab, matlab, ...) people need to access the same file at once. Then samba begins to fail and clients hang. In order to fix samba is necessary to restart the service. We've tried to put the shares in a filesystem without GFS and all goes well, people can access the same file without problems simultaneously. This certainly looks weird. If the files are only ever accessed from one node, then it *should* work, but I don't know if this is something that has been tested with GFS specifically. Serious damage starts to happen when we have Samba accessing the same files on both nodes, because all the state information isn't shared between nodes. (Proposals for a scalable solution for Samba to do this are due on samba-technical in the next week). If you are only using one node for Samba, it should be the same as a local non-cluster filesystem, so perhaps raise this with the GFS developers. Andrew Bartlett -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] GFS and samba
Hello, We have two Fedora 5 Servers clustered with GFS. We installed samba and exported the same shares in both of them. All went fine at first, with people accessing to theirs own files and so, but for some programs (minitab, matlab, ...) people need to access the same file at once. Then samba begins to fail and clients hang. In order to fix samba is necessary to restart the service. We've tried to put the shares in a filesystem without GFS and all goes well, people can access the same file without problems simultaneously. Is a weird behaviour because the shares are exported from the two servers, but we really only access files simoultaneuosly using the s first server, the other server exports the shares too but isn't used by that clients. I don't know how to debug this problem to see what is happening. It seems something related to GFS and Samba. I have seen mails of people with samba+GFS problems, but we aren't using the same configuration, and the GFS rpm are updated: GFS-6.1.5-0.FC5.1 GFS-kernel-2.6.15.1-5.FC5.32 Any help will be greatly apreciated. Thanks, Sandra -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
