[Bugs] [Bug 1596904] remove-brick is failing to remove hidden dot files

[bugzilla at redhat.com]

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

Nithya Balachandran <nbalacha at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |CLOSED
         Resolution|---                         |NOTABUG
        Last Closed|                            |2018-07-24 00:25:43



--- Comment #5 from Nithya Balachandran <nbalacha at redhat.com> ---
(In reply to Chris King from comment #4)
> (In reply to Nithya Balachandran from comment #3)
> > Hi Chris,
> > 
> > I need more info to figure this out. IIUC,the bricks that were removed were
> > disk1 and disk3. So disk5, where you see the original files, is still a part
> > of your volume.
> 
> Nithya, the overall exercise was to add two 8TB SAS drives, expand the
> volumes over bricks on these drives (which went well) and then remove two
> two 6TB SATA drives.
> 
> I should have shown the listing of disk3 (not disk 5) my mistake. Disk 3 was
> also zero sized.
> 
> # ls -la /mnt/disk3/conoak-photos-data/Photos/2003/2003-05-02/.picasa.ini
> ---------T 2 chris nasusers 0 Mar  7 07:10
> /mnt/disk3/conoak-photos-data/Photos/2003/2003-05-02/.picasa.ini
> 
> 
> > What is the output of gluster volume info <volname>?
> 
> # gluster volume info conoak-photos-data
> Volume conoak-photos-data does not exist
> [root at liberator ~]# gluster volume info conoak-photos
> 
> Volume Name: conoak-photos
> Type: Distributed-Replicate
> Volume ID: 9d5c2238-6f37-4f75-a2ea-5348b174fbb1
> Status: Started
> Snapshot Count: 0
> Number of Bricks: 2 x 2 = 4
> Transport-type: tcp
> Bricks:
> Brick1: liberator:/mnt/disk5/conoak-photos-data
> Brick2: liberator:/mnt/disk7/conoak-photos-data
> Brick3: liberator:/mnt/disk2/conoak-photos-data
> Brick4: liberator:/mnt/disk6/conoak-photos-data
> Options Reconfigured:
> changelog.changelog: on
> geo-replication.ignore-pid-check: on
> geo-replication.indexing: on
> transport.address-family: inet
> nfs.disable: on
> performance.client-io-threads: off
> 
> 
> > Having zero sized 'T' files on the removed bricks (disk1 and disk3) is not a
> > problem.
> 
> OK its not a serious, but it does not seem right that all files except the
> "dot files" are removed completely and only the dot files remain (even if
> they are zero sized)

It is possible that those linkto files (the 'T' files) were already present on
those bricks for some reason (maybe the files were renamed at some point). 
Gluster will not migrate linkto files - there is no point doing so as they are
internal files.


I'm closing this BZ as this is not a bug.

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