Hide Forgot
Description of problem: When I try to create a hard link where the source file and the hard link are in the same directory I get: [root@gqac031 gluster-mount]# ln link-source link-destiantion2 ln: creating hard link `link-destiantion2' => `link-source': No such file or directory If I run the exact command again it is successful: [root@gqac031 gluster-mount]# ln link-source link-destiantion2 [root@gqac031 gluster-mount]# sh link-destiantion2 Hello World [root@gqac031 gluster-mount]# cat link-source #!/bin/bash echo Hello World If I create a hardlink where the source and the hard link are not in the same dir it is successful on the first try: [root@gqac031 gluster-mount]# ln hardlinks-sources/100.sh hardlinks-destination/test [root@gqac031 gluster-mount]# ll hardlinks-destination/test -rw-r--r-- 3 root root 29 Oct 29 12:26 hardlinks-destination/test [root@gqac031 gluster-mount]# cat hardlinks-sources/100.sh #!/bin/bash echo Hello World [root@gqac031 gluster-mount]# sh hardlinks-destination/test Hello World Version-Release number of selected component (if applicable): glusterfs-3.4.0.33rhs-1.el6.x86_64 How reproducible: Every time I tried. Steps to Reproduce: 1. Create a hard link where the source and hard link are in the same directory. 2. 3. Actual results: [root@gqac031 gluster-mount]# ln link-source link-destiantion2 ln: creating hard link `link-destiantion2' => `link-source': No such file or directory Expected results: The hard link is successful on the first try. Additional info:
I tested this on a 1x2 volume: Volume Name: healtest Type: Replicate Volume ID: 089aad16-3b59-4f65-840b-03d5c4913555 Status: Started Number of Bricks: 1 x 2 = 2 Transport-type: tcp Bricks: Brick1: gqac016.sbu.lab.eng.bos.redhat.com:/bricks/healtest_brick0 Brick2: qe-blade-03.idm.lab.bos.redhat.com:/bricks/healtest_brick1
Patch: https://code.engineering.redhat.com/gerrit/#/c/16181/
*** Bug 1059677 has been marked as a duplicate of this bug. ***
Merged as a part of rebase
Verified on glusterfs-3.6.0.14-1.el6rhs.x86_64.
Hi Vijaikumar, Please review the edited doc text for technical accuracy and sign off.
Doc text looks good to me
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2014-1278.html