[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Gluster-devel] Weird AFR behaviour with combination of local storage br
From: |
Sam Douglas |
Subject: |
[Gluster-devel] Weird AFR behaviour with combination of local storage bricks and remote volumes |
Date: |
Wed, 12 Dec 2007 13:42:26 +1300 |
Hello
With both 1.3.7 and TLA:
I have a test AFR setup along the lines of:
###
volume brickA
type storage/posix
option directory /stuff/brickA
end-volume
volume clientA
type protocol/client
option transport-type tcp/client
option remote-host 10.0.0.1 # On some other system
option remote-subvolume brickA
end-volume
volume afrA
type cluster/afr
option replicate *:2
subvolumes brickA clientA
end-volume
volume server
# exports brickA and afrA
end-volume
###
When a client mounts the AFR volume, files are not created on the
storage/posix volume, only on the client volume. Symlink, mknod etc.
still work.
Adding a debug/trace over the storage/posix shows that lookup and symlink fops
are being called on the brick, but no readv/writev and open calls.
If another protocol/client translator is added that connects to the
exported storage
volume via the server, then everything works as expected.
Any clues?
-- Sam Douglas
- [Gluster-devel] Weird AFR behaviour with combination of local storage bricks and remote volumes,
Sam Douglas <=