[Bugs] [Bug 1159485] New: down an re-up two glusterfsd, rm -rvf mountpoint/*, then ls mountpoint/ abnormal.

bugzilla at redhat.com bugzilla at redhat.com
Sat Nov 1 08:49:52 UTC 2014


https://bugzilla.redhat.com/show_bug.cgi?id=1159485

            Bug ID: 1159485
           Summary: down an re-up two glusterfsd, rm -rvf mountpoint/*,
                    then ls mountpoint/  abnormal.
           Product: GlusterFS
           Version: 3.6.0
         Component: disperse
          Severity: medium
          Assignee: bugs at gluster.org
          Reporter: jiademing.dd at gmail.com
                CC: bugs at gluster.org, gluster-bugs at redhat.com



Description of problem:
In disperse 5 redundancy 2 volume, aterf cp -r glusterfs-3.6.0bate3
mountpoint/, kill and re-up two glusterfsd, rm -rvf mountpoint/*, then ls
mountpoint/  abnormal.
sometimes:
[root at localhost ~]# ls /mnt/
ls: cannot access /mnt/contrib: No such file or directory
config.log  contrib


Version-Release number of selected component (if applicable):
3.6.0beta3

How reproducible:


Steps to Reproduce:
1.create disperse 5 redundancy 2 volume
2.cp -r glusterfs-3.6.0bate3 /mountpoint/
3.kill and re-up two glusterfsd programs
4.rm -rvf /mountpoint/*
5.manay times ls /mountpoint/

Actual results:
sometime:
ls: cannot access /mnt/contrib: No such file or directory
config.log  contrib

Expected results:
No any file or directory.

Additional info:

[2014-10-28 20:51:09.405233] W [socket.c:545:__socket_rwv] 0-management: readv
on /var/run/30894ba13cd0fff1fcc694e10f577a21.socket failed (Invalid argument)
[2014-10-28 20:51:09.405376] W [socket.c:545:__socket_rwv] 0-management: readv
on /var/run/ea8c3e4c6532255f431633b581724642.socket failed (Invalid argument)
[2014-10-28 20:51:12.406582] W [socket.c:545:__socket_rwv] 0-management: readv
on /var/run/30894ba13cd0fff1fcc694e10f577a21.socket failed (Invalid argument)
[2014-10-28 20:51:12.407319] W [socket.c:545:__socket_rwv] 0-management: readv
on /var/run/ea8c3e4c6532255f431633b581724642.socket failed (Invalid argument)
[2014-10-28 20:51:15.407567] W [socket.c:545:__socket_rwv] 0-management: readv
on /var/run/30894ba13cd0fff1fcc694e10f577a21.socket failed (Invalid argument)
[2014-10-28 20:51:15.408169] W [socket.c:545:__socket_rwv] 0-management: readv
on /var/run/ea8c3e4c6532255f431633b581724642.socket failed (Invalid argument)
[2014-10-28 20:51:18.408878] W [socket.c:545:__socket_rwv] 0-management: readv
on /var/run/30894ba13cd0fff1fcc694e10f577a21.socket failed (Invalid argument)
[2014-10-28 20:51:18.410454] W [socket.c:545:__socket_rwv] 0-management: readv
on /var/run/ea8c3e4c6532255f431633b581724642.socket failed (Invalid argument)
[2014-10-28 20:51:21.410678] W [socket.c:545:__socket_rwv] 0-management: readv
on /var/run/30894ba13cd0fff1fcc694e10f577a21.socket failed (Invalid argument)
[2014-10-28 20:51:21.411770] W [socket.c:545:__socket_rwv] 0-management: readv
on /var/run/ea8c3e4c6532255f431633b581724642.socket failed (Invalid argument)
[2014-10-28 20:51:24.410216] W [socket.c:545:__socket_rwv] 0-management: readv
on /var/run/30894ba13cd0fff1fcc694e10f577a21.socket failed (Invalid argument)
[2014-10-28 20:51:24.410336] W [socket.c:545:__socket_rwv] 0-management: readv
on /var/run/ea8c3e4c6532255f431633b581724642.socket failed (Invalid argument)
[2014-10-28 20:51:27.411213] W [socket.c:545:__socket_rwv] 0-management: readv
on /var/run/30894ba13cd0fff1fcc694e10f577a21.socket failed (Invalid argument)
[2014-10-28 20:51:27.411427] W [socket.c:545:__socket_rwv] 0-management: readv
on /var/run/ea8c3e4c6532255f431633b581724642.socket failed (Invalid argument)
[2014-10-28 20:51:30.412563] W [socket.c:545:__socket_rwv] 0-management: readv
on /var/run/30894ba13cd0fff1fcc694e10f577a21.socket failed (Invalid argument)
[2014-10-28 20:51:30.413529] W [socket.c:545:__socket_rwv] 0-management: readv
on /var/run/ea8c3e4c6532255f431633b581724642.socket failed (Invalid argument)
[2014-10-28 20:51:33.413019] W [socket.c:545:__socket_rwv] 0-management: readv
on /var/run/30894ba13cd0fff1fcc694e10f577a21.socket failed (Invalid argument)
[2014-10-28 20:51:33.413946] W [socket.c:545:__socket_rwv] 0-management: readv
on /var/run/ea8c3e4c6532255f431633b581724642.socket failed (Invalid argument)
[2014-10-28 20:51:36.413302] W [socket.c:545:__socket_rwv] 0-management: readv
on /var/run/30894ba13cd0fff1fcc694e10f577a21.socket failed (Invalid argument)
[2014-10-28 20:51:36.413439] W [socket.c:545:__socket_rwv] 0-management: readv
on /var/run/ea8c3e4c6532255f431633b581724642.socket failed (Invalid argument)
[2014-10-28 20:51:39.335355] I [digioceand-pmap.c:227:pmap_registry_bind]
0-pmap: adding brick /sda on port 49152
[2014-10-28 20:51:39.423479] W [socket.c:545:__socket_rwv] 0-management: readv
on /var/run/ea8c3e4c6532255f431633b581724642.socket failed (Invalid argument)
[2014-10-28 20:51:42.424209] W [socket.c:545:__socket_rwv] 0-management: readv
on /var/run/ea8c3e4c6532255f431633b581724642.socket failed (Invalid argument)
[2014-10-28 20:51:45.424774] W [socket.c:545:__socket_rwv] 0-management: readv
on /var/run/ea8c3e4c6532255f431633b581724642.socket failed (Invalid argument)
[2014-10-28 20:51:48.425443] W [socket.c:545:__socket_rwv] 0-management: readv
on /var/run/ea8c3e4c6532255f431633b581724642.socket failed (Invalid argument)
[2014-10-28 20:51:51.425861] W [socket.c:545:__socket_rwv] 0-management: readv
on /var/run/ea8c3e4c6532255f431633b581724642.socket failed (Invalid argument)
[2014-10-28 20:51:52.775787] I [digioceand-pmap.c:227:pmap_registry_bind]
0-pmap: adding brick /sdb on port 49153
The message "I [MSGID: 106005]
[digioceand-handler.c:4138:__digioceand_brick_rpc_notify] 0-management: Brick
10.10.101.111:/sda has disconnected from digioceand." repeated 34 times between
[2014-10-28 20:49:54.380534] and [2014-10-28 20:51:36.413329]
The message "I [MSGID: 106005]
[digioceand-handler.c:4138:__digioceand_brick_rpc_notify] 0-management: Brick
10.10.101.111:/sdb has disconnected from digioceand." repeated 39 times between
[2014-10-28 20:49:54.382038] and [2014-10-28 20:51:51.425950]

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the Bugs mailing list