[Moosefs-users] currently unavailable chunk and reserved files

[Giovanni T. <gt...@li...>]

Hi,

I was testing master recovery after failure: after switching master, 127
missing chunks appeared.

currently unavailable chunk 0000000000001244 (inode: 193 ; index: 0)
currently unavailable chunk 0000000000001245 (inode: 193 ; index: 1)
[..]
currently unavailable chunk 00000000000012C1 (inode: 193 ; index: 125)
currently unavailable chunk 00000000000012C2 (inode: 193 ; index: 126)
+ currently unavailable reserved file 193:
images/60a81e97504d92ce5238400baba858954bce2ead
unavailable chunks: 127
unavailable reserved files: 1

I didn't found any data corruption on my services (I use mfs as
OpenNebula storage backend).

What to do when unavailable chunk appears? There is a way to tell Moose
to forget them after sometime?
And what about unavailable reserved file? I have no problems accessing
that file (I did a cat file > /dev/null).

Thanks for any reply.

-- 
Giovanni Toraldo
http://www.libersoft.it/