Bug 765443 (GLUSTER-3711) - glusterd log shows "file sizes are different" after rebalance is performed
Summary: glusterd log shows "file sizes are different" after rebalance is performed
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-3711
Product: GlusterFS
Classification: Community
Component: core
Version: 3.2.4
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Raghavendra G
QA Contact: shylesh
URL:
Whiteboard:
: GLUSTER-3812 (view as bug list)
Depends On:
Blocks: 817967 850503 852367
TreeView+ depends on / blocked
 
Reported: 2011-10-11 06:21 UTC by shylesh
Modified: 2013-07-24 17:15 UTC (History)
6 users (show)

Fixed In Version: glusterfs-3.4.0
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-24 17:15:51 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Amar Tumballi 2011-10-11 05:54:28 UTC
As per the code flow, this should not be happening. But, I see that 'fstat()' is returning lesser size than what is expected (as while debugging, we can see file sizes are same on the bricks).

Shylesh, Is it possible to build glusterfs from source there?

Comment 1 shylesh 2011-10-11 06:21:50 UTC
1. Created a distribute volume 
2. Added some files from mount point 
3. added a new brick 
4. Initiate reblance

Bug
----
After rebalance number of files on mount point increased because of .*.gfs files on mount point.
glusterd log shows that there is a difference in file sizes .

=============================================================
[2011-10-11 01:52:12.614577] E [glusterd-rebalance.c:84:migrate_xattrs_of_file] 0-glusterfs: failed to set the xattr for key security.selinux (Operation not supported)
[2011-10-11 01:52:12.614616] W [glusterd-rebalance.c:207:gf_glusterd_rebalance_move_data] 0-glusterfs: failed to copy the extended attributes from source file /etc/glusterd/mount/vol-dis/12
[2011-10-11 01:52:12.990545] E [glusterd-rebalance.c:84:migrate_xattrs_of_file] 0-glusterfs: failed to set the xattr for key security.selinux (Operation not supported)
[2011-10-11 01:52:12.990596] W [glusterd-rebalance.c:207:gf_glusterd_rebalance_move_data] 0-glusterfs: failed to copy the extended attributes from source file /etc/glusterd/mount/vol-dis/14
[2011-10-11 01:52:13.204584] E [glusterd-rebalance.c:84:migrate_xattrs_of_file] 0-glusterfs: failed to set the xattr for key security.selinux (Operation not supported)
[2011-10-11 01:52:13.204617] W [glusterd-rebalance.c:207:gf_glusterd_rebalance_move_data] 0-glusterfs: failed to copy the extended attributes from source file /etc/glusterd/mount/vol-dis/15
[2011-10-11 01:52:13.302086] E [glusterd-rebalance.c:84:migrate_xattrs_of_file] 0-glusterfs: failed to set the xattr for key security.selinux (Operation not supported)
[2011-10-11 01:52:13.302114] W [glusterd-rebalance.c:207:gf_glusterd_rebalance_move_data] 0-glusterfs: failed to copy the extended attributes from source file /etc/glusterd/mount/vol-dis/16
[2011-10-11 01:52:13.318665] E [glusterd-rebalance.c:84:migrate_xattrs_of_file] 0-glusterfs: failed to set the xattr for key security.selinux (Operation not supported)
[2011-10-11 01:52:13.318695] W [glusterd-rebalance.c:207:gf_glusterd_rebalance_move_data] 0-glusterfs: failed to copy the extended attributes from source file /etc/glusterd/mount/vol-dis/17
[2011-10-11 01:52:13.319286] W [glusterd-rebalance.c:251:gf_glusterd_rebalance_move_data] 0-glusterfs: file sizes are not same : /etc/glusterd/mount/vol-dis/17
===========================================================================

Comment 2 shylesh 2011-10-11 08:03:41 UTC
Works fine with write-behind OFF

Comment 3 Anand Avati 2011-11-03 10:18:06 UTC
CHANGE: http://review.gluster.com/665 (stat returned in setattr_cbk can be cached by the kernel. Hence it is) merged in release-3.2 by Anand Avati (avati)

Comment 4 Raghavendra G 2011-11-17 02:09:46 UTC
*** Bug 3812 has been marked as a duplicate of this bug. ***

Comment 5 Amar Tumballi 2011-11-22 23:51:53 UTC
Don't we need the fix in master branch?

Comment 6 Raghavendra G 2011-11-22 23:58:13 UTC
(In reply to comment #5)
> Don't we need the fix in master branch?

http://review.gluster.com/#change,713 and
http://review.gluster.com/#change,712

for master will fix this. For some reason, the bug-id in the patches was not updated.

Comment 7 shishir gowda 2012-03-26 07:03:52 UTC
Can we verify if this issue still exists?

Comment 8 Anand Avati 2012-03-27 18:29:11 UTC
CHANGE: http://review.gluster.com/3011 (performance/write-behind: queue setattr fop with writes always.) merged in master by Vijay Bellur (vijay)

Comment 9 Kaushal 2012-05-29 10:57:12 UTC
Checked on release-3.3 branch. 
These messages are no longer present in the rebalance log files even with write-behind on.


Note You need to log in before you can comment on or make changes to this bug.