On 10/18/2012 10:15 PM, Emmanuel Dreyfus wrote:
Vijay Bellur <vbellur@xxxxxxxxxx> wrote:
Can you try with a custom volume file with just posix translator in it?
If the test passes successfully there, we can add more translators into
the mix and see where the problem comes from.
We assume it is server side?
Not really. You could start with a custom volume file like:
volume foo-posix
type storage/posix
option directory /tmp/foo1
option volume-id 3103a755-72fb-4d0d-8cd4-89845592ad98
end-volume
You can then mount with:
glusterfs -f <custom_volfile> -l <log> </mount/point>
If the problem happens with the basic posix translator and the implicit
fuse translator, we would have narrowed down the problem. If not, we can
start adding more translators into the custom volume file and arrive at
the set of translators that will cause this problem.
Thanks,
Vijay
