[Gluster-users] Hardlink misbehaviour

Allan Latham alatham at flexsys-group.de
Sun Jul 14 11:24:04 UTC 2013


Hi all

I'm running some initial sanity and performance checks on this:

root at h06 /root # glusterd -V
glusterfs 3.4.0beta4 built on Jul 10 2013 15:14:50

I want to hard link a file, delete the original and rename the hard
linked file back to its original name

Here it is on an ext4 filesystem:

root at h06 /root/mnt/h06 # ls -i installimage.debug*
26 installimage.debug
root at h06 /root/mnt/h06 # ln installimage.debug installimage.debug.hardlink
root at h06 /root/mnt/h06 # ls -i installimage.debug*
26 installimage.debug  26 installimage.debug.hardlink
root at h06 /root/mnt/h06 # rm installimage.debug
rm: remove regular file `installimage.debug'? y
root at h06 /root/mnt/h06 # ls -i installimage.debug*
26 installimage.debug.hardlink
root at h06 /root/mnt/h06 # mv installimage.debug.hardlink installimage.debug
root at h06 /root/mnt/h06 # ls -i installimage.debug*
26 installimage.debug


Here it is on gluster:

root at h06 /gluster/mnt/20 # ls -i installimage.debug*
9397531713154926553 installimage.debug

root at h65 /gluster/mnt/20 # ls -i installimage.debug*
9397531713154926553 installimage.debug

root at h06 /gluster/mnt/20 # ln installimage.debug installimage.debug.hardlink
root at h06 /gluster/mnt/20 # ls -i installimage.debug*
9397531713154926553 installimage.debug
9397531713154926553 installimage.debug.hardlink

root at h65 /gluster/mnt/20 # ls -i installimage.debug*
9397531713154926553 installimage.debug
9397531713154926553 installimage.debug.hardlink
root at h65 /gluster/mnt/20 # rm installimage.debug
rm: remove regular file `installimage.debug'? y
root at h65 /gluster/mnt/20 # ls -i installimage.debug*
9397531713154926553 installimage.debug.hardlink

root at h06 /gluster/mnt/20 # ls -i installimage.debug*
9397531713154926553 installimage.debug.hardlink
root at h06 /gluster/mnt/20 # mv installimage.debug.hardlink installimage.debug
mv: `installimage.debug.hardlink' and `installimage.debug' are the same file
root at h06 /gluster/mnt/20 # ls -i installimage.debug*
9397531713154926553 installimage.debug.hardlink

At this point something is clearly wrong. The file installimage.debug
does not exist and the mv should have succeeded.

root at h65 /gluster/mnt/20 # ls -i installimage.debug*
9397531713154926553 installimage.debug.hardlink
root at h65 /gluster/mnt/20 # mv installimage.debug.hardlink installimage.debug
mv: cannot move `installimage.debug.hardlink' to `installimage.debug':
Software caused connection abort
root at h65 /gluster/mnt/20 # ls -i installimage.debug*
ls: cannot access installimage.debug*: Transport endpoint is not connected

umount /gluster/mnt
mount /gluster/mnt

is needed to re-enable gluster on h65.

Any ideas?

All the best

Allan




More information about the Gluster-users mailing list