GlusterFS_Buglist

博客公告：(1)本博客所有博客文章搬迁至《博客虫》http://www.blogchong.com/

(2)文章对应的源码下载链接参考博客虫网站首页的“代码GIT”直通车；

(3)更多的相关文章更新，以及代码等，请关注博客虫网站，网站中有技术Q群，以及代码共享链接。
 

 

 该文档为实实在在的原创文档，转载请注明：

http://blog.sina.com.cn/s/blog_8c243ea30101kkiy.html

目录

GlusterFS_Buglist. 1

1 文档说明... 1

2 Buglist. 1

2.1 AFR: cannot get volume status when one node down. 1

2.2 AFR: change one file in one brick,prompt "[READ ERRORS]" when open it in the client. 2

2.3 AFR: lose files in one node, "ls" failed in the client, but open normally. 2

2.4 AFR: “volume heal newvolume full” recover file -- deleted file not copy from carbon node. 3

 

1 文档说明

该文档为在进行GlusterFS_3.4.1版本实践中所遇到的Bug，至此，贴出来，是为了寻求大家的帮助，看看大家在使用的过程中有没有遇到相同的问题。

个人也想明确是个人使用有问题，还是系统真的有这些Bug。

目前以下4个Bug已经向红帽的bugzilla提交，有兴趣的也可以去看看。

以下给出4个bug的链接：

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

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

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

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

 

2 Buglist

2.1 AFR: cannot get volume status when one node down

Component：replicate

Version：3.4.1 & 3.3.2

Bug Number:1029482

 

Description of problem:

It is OK when all nodes are up,but break one(cut off net or shut down node) or more cannot get volume status(command:volume status).

 

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

3.4.1 & 3.3.2

 

How reproducible:

always

 

Steps to Reproduce:

1.create a AFR volume and start

2.gluster volume status(normal)

3.break one node (cut off net：make ethX down--ifconfig ethX down)

4.gluster volume status(abnormal)

 

Actual results:

cannot get anything or "Anthor transactior is in progress,Please try again after sometime"

 

Expected results:

get something about volume status

 

Additional info:

I get something from bug_807428,but it appear both in 3.4.1 and 3.3.2

 

 

2.2 AFR: change one file in one brick,prompt "[READ ERRORS]" when open it in the client

Component:replicate

Version:3.4.1 & 3.3.2

Bug Number:1029492

 

Description of problem:

AFR volume: change a file in one brick,execute "gluster volume heal afr_vol full"(actuclly,it doesnot work).open this file in the client,prompt "[READ ERRORS]".

 

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

3.4.1 & 3.3.2

 

How reproducible:

always and i have test many times.

 

Steps to Reproduce:

1.create a afr volume: gluster volume create afr_vol replica 3 192.168.8.{80,81,82}:/mnt/sdb1

2.started it: gluster volume start afr_vol

3.change one file in 192.168.8.80:/mnt/sdb1 (just add a row or delete a row)

4.execute heal:gluster volume heal afr_vol full(it doesnot work and you can see from 8.80:/mnt/sdb1)

5.open this file (used 'vim')

 

Actual results:

prompt "[READ ERRORS]"

 

Expected results:

open file normally

 

Additional info:

"volume heal Volume_name full" doesnot work and I have test many times.

 

 

2.3 AFR: lose files in one node, "ls" failed in the client, but open normally

Component:replicate

Version:3.4.1 & 3.3.2

Bug Number:1029496

 

Description of problem:

AFR volume: create a afr volume. delete a file in brick(default node:system get metadata from this node),"ls" failed in client,but open normally.

 

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

3.4.1 & 3.3.2

 

How reproducible:

only delete file in special node (default node)

 

Steps to Reproduce:

1.create a afr volume

2.delete a file in default node(system get metadata from this node)

3."ls" in client

 

Actual results:

cannot show this file,but can use it normally. And it can trigger heal.

 

Expected results:

show this file

 

Additional info:

 

2.4 AFR: “volume heal newvolume full” recover file -- deleted file not copy from carbon node

Component:replicate

Version:3.4.1 & 3.3.2

Bug Number:1029506

 

Description of problem:

AFR volume: create a AFR volume, and then change a file in one brick (just add a row, so it is a wrong file).I delete this wrong file in this brick, and then execute "gluster volume heal afr_full". Guess what? yes,it recover a file in this brick, but ... this file is a wrong file(changed by me),not a copy from carbon node. why ?

 

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

3.4.1 & 3.3.2

 

How reproducible:

always and I have test many times

 

Steps to Reproduce:

1.create a AFR volume : afr_vol

2.change a file in one brick (just add a row)

3.gluster volume heal afr_vol full

4.recover a file (changed by me,not a copy from carbon node)

 

Actual results:

this file is the file which changed by me

 

Expected results:

recover a normal file (copy from other node)

 

Additional info:

so why?