[Gluster-users] Hundreds of duplicate files
Anatoly Pugachev
matorola at gmail.com
Wed Dec 17 09:39:50 UTC 2014
On Wed, Dec 17, 2014 at 4:07 AM, <tbenzvi at 3vgeomatics.com> wrote:
> Hi everyone, we have noticed some extremely odd behaviour with our
> distributed Gluster volume where duplicate files (same name, same or
> different content) are being created and stored on multiple bricks. The only
> consistent clue is that one of the duplicate files has the sticky bit set. I
> am hoping someone will be able to shed some light on why this is happening
> and how we can restore the volume as there appear to be hundreds of such
> files. I will try to provide as much pertinent information as I can.
>
> We have a 130TB Gluster volume consisting of two 20TB bricks on server1, and
> three 40TB bricks on a server2 which were added at a later date (and
> rebalancing was done). The volume is mounted on server1, and accessed only
> through this server but by many users. Both servers went down due to power
> loss several days ago after which this problem was first noticed. We ran a
> rebalance command on the volumes, this has not fixed the problem.
>
>
> Gluster volume info:
> Volume Name: safari
> Type: Distribute
> Volume ID: d48d0e6b-4389-4c2c-8fd1-cd2854121eda
> Status: Started
> Number of Bricks: 5
> Transport-type: tcp
> Bricks:
> Brick1: server1:/data/glusterfs/safari/brick00/brick
> Brick2: server1:/data/glusterfs/safari/brick01/brick
> Brick3: server2:/data/glusterfs/safari/brick02/brick
> Brick4: server2:/data/glusterfs/safari/brick03/brick
> Brick5: server2:/data/glusterfs/safari/brick04/brick
>
>
> Size information:
> /dev/sdc 37T 16T 22T 42% /data/glusterfs/safari/brick02
> /dev/sdd 37T 16T 22T 42% /data/glusterfs/safari/brick03
> /dev/sde 37T 17T 21T 45% /data/glusterfs/safari/brick04
> /dev/md126 11T 7.7T 2.8T 74% /data/glusterfs/safari/brick00
> /dev/md124 11T 8.0T 2.5T 77% /data/glusterfs/safari/brick01
> server2:/safari 130T 63T 68T 48% /sar
>
>
> Example 1:
> -Two files with the same name exist in one directory
> -They have different contents and attributes
> -A file listing on the mounted volume shows the same inode
> -The newer file has sticky bit set
> -Neither file is corrupted, they can both be viewed by using the absolute
> path (on the bricks)
>
> File listing on the mounted volume
> 13036730497538635177 -rw-rw-r-T 1 jon users 924 Dec 15 10:42 RSLC_tab
> 13036730497538635177 -rw-rw-r-- 1 jon users 418 Mar 18 2013 RSLC_tab
>
> Listing of the files on the bricks:
> 8925798411 -rw-rw-r-T+ 2 jon users 924 Dec 15 10:42
> /data/glusterfs/safari/brick00/brick/complete/shm/rs2/ottawa/mf6_asc/stack_org/RSLC_tab
> 51541886672 -rw-rw-r--+ 2 1002 users 418 Mar 18 2013
> /data/glusterfs/safari/brick02/brick/complete/shm/rs2/ottawa/mf6_asc/stack_org/RSLC_tab
>
>
> Example 2:
> -Two files with the same name exist in one directory
> -They have the same content and attributes
> -No sticky bit is set when looking at file listing on the mounted volume
> -Sticky bit is set for one while when looking at file listing on the bricks
> -Files are corrupted
>
> File listing on the mounted volume:
> 13012555852904096080 -rw-rw-r-- 1 tom users 2393848 Dec 8 2013
> ifg_lr/20130226_20130813.diff.phi.ras
> 13012555852904096080 -rw-rw-r-- 1 tom users 2393848 Dec 8 2013
> ifg_lr/20130226_20130813.diff.phi.ras
>
> Listing of the files on the bricks:
> 17058578 -rw-rw-r-T+ 2 tom users 2393848 Dec 13 17:11
> /data/glusterfs/safari/brick00/brick/rsc/rs2/calgary/u22_dsc/stack_org/ifg_lr/20130226_20130813.diff.phi.ras
> 57986922129 -rw-rw-r--+ 2 1010 users 2393848 Dec 8 2013
> /data/glusterfs/safari/brick02/brick/rsc/rs2/calgary/u22_dsc/stack_org/ifg_lr/20130226_20130813.diff.phi.ras
>
>
> Additionally, only some files in this directory are duplicated. The
> duplicated files are corrupted (can not be viewed as Raster images: the
> original file type)
> The files which are not duplicated are not corrupted.
>
> File command: (notice duplicate and singleton files)
> ifg_lr/20091021_20100218.diff.phi.ras: Sun raster image data, 1208 x 1981,
> 8-bit, RGB colormap
> ifg_lr/20091021_20101016.diff.phi.ras: data
> ifg_lr/20091021_20101016.diff.phi.ras: data
> ifg_lr/20091021_20101109.diff.phi.ras: Sun raster image data, 1208 x 1981,
> 8-bit, RGB colormap
> ifg_lr/20091021_20101203.diff.phi.ras: Sun raster image data, 1208 x 1981,
> 8-bit, RGB colormap
> ifg_lr/20091021_20101227.diff.phi.ras: Sun raster image data, 1208 x 1981,
> 8-bit, RGB colormap
> ifg_lr/20091021_20110120.diff.phi.ras: Sun raster image data, 1208 x 1981,
> 8-bit, RGB colormap
> ifg_lr/20091021_20110213.diff.phi.ras: data
> ifg_lr/20091021_20110213.diff.phi.ras: data
> ifg_lr/20091021_20110309.diff.phi.ras: data
> ifg_lr/20091021_20110309.diff.phi.ras: sticky data
> ifg_lr/20091021_20110402.diff.phi.ras: Sun raster image data, 1208 x 1981,
> 8-bit, RGB colormap
Tom,
can you please stop glusterfs daemons (glusterd, glusterfsd) umount
brick devices and check filesystems for consistency (fsck or
xfs_check). If there's errors on filesystems, you will need to remove
duplicate files manually, leaving one of the "good" file. And I don't
know what to do with .glusterfs brick subdirectory, if fsck will "fix"
it (probably just remove it).
More information about the Gluster-users
mailing list