[Gluster-devel] [Gluster-users] Fencing FOPs on data-split-brained files

Emmanuel Dreyfus manu at netbsd.org
Sat Nov 16 09:20:56 UTC 2013

Anand Avati <avati at gluster.org> wrote:

> Regarding your concern about complications while healing - we should change
> our "manual fixing" instructions to:
> - go to backend, access through gfid path or normal path
> - rmxattr the afr changelogs
> - truncate the file to 0 bytes (like "> filename")

What about a adding a gluster command like this?
gluster rm path [-r] [-b brick|-a]
-r recursive
-b specify brick, use relative path to find if not specified
-a remove on all other bricks

That could even help removing files in non split-brain scenarios, where
it takes age because rm -rf goes through several FOPs for each file.

And while we are here, I would dream of a tar that could bypass FUSE
FOPs. which is very long for big archives. Just supporting -x -c and -f
would be enough, if someone has another archive type, it could unpack to
stdout and pipe to gluster tar -xf - or gluster tar cf -

gluster tar could be very valuable for backup/restore.
gluster tar -xf file.tar

Emmanuel Dreyfus
manu at netbsd.org

More information about the Gluster-devel mailing list