[Gluster-users] Input/output error when trying to access a file on client

[Alessandro Ipe]

Hi,


In fact, going up one directory level (root of the gluster volume), I get similarly
1. # file: data/glusterfs/md1/brick1/
trusted.afr.md1-client-0=0x000000000000000000000000
trusted.afr.md1-client-1=0x000000000000000000000000
trusted.gfid=0x00000000000000000000000000000001
trusted.glusterfs.dht=0x0000000100000000aaaaaaaaffffffff
trusted.glusterfs.volume-id=0x6da4b9151def4df4a41c2f3300ebf16b
2. # file: data/glusterfs/md1/brick1/
trusted.afr.md1-client-0=0x000000000000000000000000
trusted.afr.md1-client-1=0x000000000000000000000000
trusted.gfid=0x00000000000000000000000000000001
trusted.glusterfs.dht=0x0000000100000000aaaaaaaaffffffff
trusted.glusterfs.volume-id=0x6da4b9151def4df4a41c2f3300ebf16b
3. # file: data/glusterfs/md1/brick1/
trusted.afr.md1-client-2=0x000000000000000000000000
trusted.afr.md1-client-3=0x000000000000000000000000
trusted.gfid=0x00000000000000000000000000000001
trusted.glusterfs.dht=0x00000001000000000000000055555554
trusted.glusterfs.volume-id=0x6da4b9151def4df4a41c2f3300ebf16b
4. # file: data/glusterfs/md1/brick1/
trusted.afr.md1-client-2=0x000000000000000000000000
trusted.afr.md1-client-3=0x000000000000000000000000
trusted.gfid=0x00000000000000000000000000000001
trusted.glusterfs.dht=0x00000001000000000000000055555554
trusted.glusterfs.volume-id=0x6da4b9151def4df4a41c2f3300ebf16b

These four bricks seem consistent, while the remaining two

5. # file: data/glusterfs/md1/brick1/
trusted.afr.md1-client-0=0x000000000000000000000000
trusted.afr.md1-client-1=0x000000000000000000000000
trusted.afr.md1-client-4=0x000000000000000000000000
trusted.afr.md1-client-5=0x000000000000000200000000
trusted.gfid=0x00000000000000000000000000000001
trusted.glusterfs.dht=0x000000010000000055555555aaaaaaa9
trusted.glusterfs.volume-id=0x6da4b9151def4df4a41c2f3300ebf16b
6. # file: data/glusterfs/md1/brick1/
trusted.afr.md1-client-0=0x000000000000000000000000
trusted.afr.md1-client-1=0x000000000000000000000000
trusted.afr.md1-client-4=0x000000000000000100000000
trusted.afr.md1-client-5=0x000000000000000000000000
trusted.gfid=0x00000000000000000000000000000001
trusted.glusterfs.dht=0x000000010000000055555555aaaaaaa9
trusted.glusterfs.volume-id=0x6da4b9151def4df4a41c2f3300ebf16b

show two extra entries trusted.afr.md1-client-0 & trusted.afr.md1-client-1 and
inconsistency between trusted.afr.md1-client-4 & trusted.afr.md1-client-5.

Could it be this issue which propagates to all subdirectories in the volume and thus 
results in the error message in the client log file ?

Should I remove trusted.afr.md1-client-0 & trusted.afr.md1-client-1 from brick5 & 
brick 6 ?

Meanwhile, I am performing on the client 
find /home/.md1 -type f -exec cat {} > /dev/null \;
to check if I can access the content of all files on the volume. For the moment, only 4 
files gave errors.

It is quite frustrating, because I believe that all my data is still intact on the bricks and 
it seems that it is only the metadata which got screwed... I am reluctant to perform 
something to heal by myself, because I have the feeling that it could do more harm 
than good. 

It's been more than 2 days now that my colleagues cannot access the data and I 
cannot make them wait much longer...


A.


On Thursday 12 March 2015 12:59:00 Alessandro Ipe wrote:


Hi,


Sorry about that, I thought I was using the -e hex... I must have removed it at some 
point accidentally.

Here they are
1. # file: data/glusterfs/md1/brick1/root
trusted.afr.md1-client-0=0x000000000000000000000000
trusted.afr.md1-client-1=0x000000000000000000000000
trusted.gfid=0xdc398cbd2ab440ec9fed3d5937654f4b
trusted.glusterfs.dht=0x0000000100000000aaaaaaaaffffffff

2. # file: data/glusterfs/md1/brick1/root
trusted.afr.md1-client-0=0x000000000000000000000000
trusted.afr.md1-client-1=0x000000000000000000000000
trusted.gfid=0xdc398cbd2ab440ec9fed3d5937654f4b
trusted.glusterfs.dht=0x0000000100000000aaaaaaaaffffffff

3. # file: data/glusterfs/md1/brick1/root
trusted.afr.md1-client-2=0x000000000000000000000000
trusted.afr.md1-client-3=0x000000000000000100000000
trusted.gfid=0xdc398cbd2ab440ec9fed3d5937654f4b
trusted.glusterfs.dht=0x00000001000000000000000055555554

4. getfattr: Removing leading '/' from absolute path names
# file: data/glusterfs/md1/brick1/root
trusted.afr.md1-client-2=0x000000000000000100000000
trusted.afr.md1-client-3=0x000000000000000000000000
trusted.gfid=0xdc398cbd2ab440ec9fed3d5937654f4b
trusted.glusterfs.dht=0x00000001000000000000000055555554

5. # file: data/glusterfs/md1/brick1/root
trusted.afr.md1-client-4=0x000000000000000000000000
trusted.afr.md1-client-5=0x000000000000000100000000
trusted.gfid=0xdc398cbd2ab440ec9fed3d5937654f4b
trusted.glusterfs.dht=0x000000010000000055555555aaaaaaa9

6. # file: data/glusterfs/md1/brick1/root
trusted.afr.md1-client-4=0x000000000000000100000000
trusted.afr.md1-client-5=0x000000000000000000000000
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20150312/e69ec875/attachment.html>