[Gluster-users] Questions and notes to "Simplify recovery steps of corrupted files"
spisla80 at gmail.com
Tue Mar 5 07:12:04 UTC 2019
Thank you for the clarification.
Am Mo., 4. März 2019 um 20:19 Uhr schrieb FNU Raghavendra Manjunath <
rabhat at redhat.com>:
> Hi David,
> Doing full heal after deleting the gfid entries (and the bad copy) is
> fine. It is not dangerous.
> On Mon, Mar 4, 2019 at 9:44 AM David Spisla <spisla80 at gmail.com> wrote:
>> Hello Gluster Community,
>> I have questions and notes concerning the steps mentioned in
>> " *2. Delete the corrupted files* ":
>> In my experience there are two GFID files if a copy gets corrupted.
>> *$ find /gluster/brick1/glusterbrick/.glusterfs -name
>> Both GFID files has to be deleted. If a copy is NOT corrupted, there
>> seems to be no GFID file in
>> *.glusterfs/quarantine . *Even one executes scub ondemand, the file is
>> not there. The file in *.glusterfs/quarantine* occurs if one executes
>> "scrub status".
>> " *3. Restore the file* ":
>> One alternatively trigger self heal manually with
>> *gluster vo heal VOLNAME*
>> But in my experience this is not working. One have to trigger a full heal:
>> *gluster vo heal VOLNAME* *full*
>> Imagine, one will restore a copy with manual self heal. It is neccesary
>> to set some VOLUME options (stat-prefetch, dht.force-readdirp and
>> performance.force-readdirp disabled) and mount via FUSE with some special
>> parameters to heal the file?
>> In my experience I do only a full heal after deleting the bad copy and
>> the GFID files.
>> This seems to be working. Or it is dangerous?
>> David Spisla
>> Gluster-users mailing list
>> Gluster-users at gluster.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Gluster-users