Hi!
This is nothing serious. These are files which were opened by a user and
were deleted. POSIX demands to have the file opened even if it was deleted
as long as it is opened. So that's why these files appear.
You can find this file in a "reserved" folder when you mount "meta" resource
(option -o mfsmeta for mfsmount). It would stay there as long as it is used
by some client(s). If none of the clients uses it it would be automatically
deleted (by default after 2 hours as far as we remember). So again - this is
nothing to worry about.
Kind regards
Michał Borychowski
MooseFS Support Manager
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Gemius S.A.
ul. Wołoska 7, 02-672 Warszawa
Budynek MARS, klatka D
Tel.: +4822 874-41-00
Fax : +4822 874-41-01
-----Original Message-----
From: Giovanni Toraldo [mailto:gt...@li...]
Sent: Thursday, January 27, 2011 10:24 AM
To: moo...@li...
Subject: [Moosefs-users] currently unavailable chunk and reserved files
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/
|
