[Gluster-users] help with replace-brick migrate
Mariusz Sobisiak
MSobisiak at ydp.pl
Wed Dec 18 12:21:26 UTC 2013
> I don't knew that can be a lot of trash (orphan) files in .glusterfs,
so here what i do:
I think you can easily check by this command (on old gluster server):
find .glusterfs/ -type f -links 1
If something returns that means file have only one link and doesn't have
a "real" file on the brick so it unintended (and it's orphan file).
> # du -hs *
> 3.5G documents
> 341G home
> 58G archives
> 808G secure_folder
> 93G secure_folder2
So you have files on new gluster. I understood that you have just
.glusterfs directory...
> 1.3T .glusterfs/
It looks OK. It's not taking any space because it's hardlinks.
> So, i have 1.3Tb in gluster!! So, i think that replace-brick worked
correctly ... right ?
Probably yes.
> So, how can i restart the replace-brick command again ?
I am not sure what for you want to restart the replace-brick command?
You wrote that status show: migration complete... So it's ok and do just
commit (first ensure is everything is OK).
If you're not sure if all files had copied maybe you can compare files
on both nodes (old one and migrated) like this:
find /where/the/brick/is/ -path "*/.glusterfs/*" -prune -o -name '*'
-print|wc -l
If the command return the same values that mean you have all files :D
But In my opinion everything looks okay (except that why so many files
are orphaned on old glusterfs).
--
Mariusz
More information about the Gluster-users
mailing list