[Bugs] [Bug 1368185] Directory on volume seems to be empty, but brick contains data

[bugzilla at redhat.com]

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

Sebbo <sebastian.kraetzig at itonics.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
              Flags|needinfo?(sebastian.kraetzi |
                   |g at itonics.de)               |



--- Comment #13 from Sebbo <sebastian.kraetzig at itonics.de> ---
No, I just did it like below:

1. Remove brick from volume
   gluster volume remove-brick gfsvbackup
p-v00283.itonicsit.de:/export/disk1/brick

2. Remove GlusterFS data from brick (to give the ability to add it later again,
if required)
   setfattr -x trusted.glusterfs.volume-id /export/disk1/brick
   setfattr -x trusted.gfid /export/disk1/brick
   rm -rf /export/disk1/brick/.glusterfs/

I didn't know, that there are parameters like "start" and "commit" for this
task. You may should add these parameters as required parameter, if they are
really necessary to prevent such issues.

You said, that the command is not valid without the parameter "start" or
"commit". I can't remember myself, if I may have used the parameter "start",
but anyway: I've only executed one command and after that, I've took a look at
the volume status, where I could see, that the brick was removed. Due of this
information, I've detached the brick (hard disk) from the volume and attached
it on the other server, where the volume was added back to the volume.

No, I did NOT delete the data. I've only removed the brick from the volume,
attached the storage to another server and added the brick back to the volume.

Yes, I did run a rebalance after add-brick:

   gluster volume add-brick <VOLUME-NAME> <server03:/path/to/brick>
   gluster volume rebalance <VOLUME-NAME> fix-layout start
   gluster volume rebalance <VOLUME-NAME> start

These commands were used therefore.

Yes, I've executed all your mentioned commands - also 'rm -rf'.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=pQbdf8FHjY&a=cc_unsubscribe