[Gluster-devel] Fwd: Fwd: Bug#751888: glusterfs-server: creating symlinks generates errors
Ravishankar N
ravishankar at redhat.com
Fri Jun 20 05:44:36 UTC 2014
Hi Matteo,
Thanks for the reproducer. I've filed a bug report here:
https://bugzilla.redhat.com/show_bug.cgi?id=1111454
Feel free to add yourself to the CC List to get notified of the fix.
Thanks,
Ravi
On 06/19/2014 06:57 PM, Patrick Matthäi wrote:
> Hello gluster list,
>
> could you have got a look on this bug?
> You can access all information on http://bugs.debian.org/751888
>
> I am on vacation from now on for nearly three weeks so I could not take
> care of it :-(
>
>
> -------- Weitergeleitete Nachricht --------
> Betreff: Bug#751888: glusterfs-server: creating symlinks generates errors
> Weitersenden-Datum: Wed, 18 Jun 2014 09:39:02 +0000
> Weitersenden-Von: Matteo Checcucci <matteo.checcucci at arnone.de.unifi.it>
> Weitersenden-An: debian-bugs-dist at lists.debian.org
> Weitersenden-CC: Patrick Matthäi <pmatthaei at debian.org>
> Datum: Wed, 18 Jun 2014 10:53:12 +0200
> Von: Matteo Checcucci <matteo.checcucci at arnone.de.unifi.it>
> Antwort an: Matteo Checcucci <matteo.checcucci at arnone.de.unifi.it>,
> 751888 at bugs.debian.org
> An: 751888 at bugs.debian.org
>
> On 06/17/2014 04:14 PM, Patrick Matthäi wrote:
>> Am 17.06.2014 15:29, schrieb Matteo Checcucci:
>>> ls -l, cp -a, ...).
>>> An especially troublesome consequence is that if I
>>>
>> What is the output of:
>> strace /bin/ls -l foobar?
>>
>> Anything in your server/client logs?
>>
> Hello.
> Thanks for your quick reply.
> I reproduced the bug on a newly created gluster volume (connection IP
> over Ethernet) with gluster 3.5.0-1:
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> SERVER: host07
> CLIENT: host01 , host02 , host03 , host04
>
> root at host07:~# service glusterfs-server start
> root at host07:~# gluster peer status
> root at host07:~# gluster peer probe host01
> root at host07:~# gluster peer probe host02
> root at host07:~# gluster peer probe host03
> root at host07:~# gluster peer probe host04
>
> root at host07:~# pdsh -w 'host[01-04]' gluster peer probe host07
> host01: peer probe: success.
> host02: peer probe: success.
> host03: peer probe: success.
> host04: peer probe: success.
>
> root at host07:~# gluster peer status
> root at host07:~# gluster volume create scratch01-04 stripe 4
> host01:/data/brick1 host02:/data/brick1 host03:/data/brick1
> host04:/data/brick1
> root at host07:~# gluster volume start scratch01-04
> root at host07:~# mkdir -p /storage/scratch01-04
> root at host07:~# mount -t glusterfs host07:/scratch01-04 /storage/scratch01-04
>
> root at host01:~# mkdir -p /storage/scratch01-04
> root at host01:~# mount -t glusterfs host07:/scratch01-04 /storage/scratch01-04
>
> root at host01:/storage/scratch01-04# ls
> root at host01:/storage/scratch01-04# mkdir test
> root at host01:/storage/scratch01-04# cd test/
> root at host01:/storage/scratch01-04/test# touch foo
> root at host01:/storage/scratch01-04/test# ln -s foo my_link
> root at host01:/storage/scratch01-04/test# ls -ltr
> ls: cannot read symbolic link my_link: No such file or directory
> total 0
> -rw-r--r-- 1 root root 0 Jun 18 10:07 foo
> lrwxrwxrwx 1 root root 3 Jun 18 10:08 my_link
>
>
> root at host01:~# strace /bin/ls -l foo 2> output_strace_foo
> root at host01:~# strace /bin/ls -l my_link 2> output_strace_my_link
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> The strace output and the logs of the server and client are attached.
> I hope this is useful to pinpoint the problem.
> Bye
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> Gluster-devel mailing list
> Gluster-devel at gluster.org
> http://supercolony.gluster.org/mailman/listinfo/gluster-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://supercolony.gluster.org/pipermail/gluster-devel/attachments/20140620/40432ab4/attachment-0001.html>
More information about the Gluster-devel
mailing list