From: Michał B. <mic...@ge...> - 2011-11-05 07:03:34
|
Hi! Please check these locations for metadata file: /metadata.mfs.emergency /tmp/metadata.mfs.emergency /var/metadata.mfs.emergency /usr/metadata.mfs.emergency /usr/share/metadata.mfs.emergency /usr/local/metadata.mfs.emergency /usr/local/var/metadata.mfs.emergency /usr/local/share/metadata.mfs.emergency 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: Allen Landsidel [mailto:lan...@gm...] Sent: Friday, November 04, 2011 3:13 PM To: moo...@li... Subject: [Moosefs-users] Out of disk space on master / recovery failed So I didn't plan ahead well and ended up with /var filling up on my master over night, causing the master to crash. mfsmetarestore refused to recover the system, I think because it didn't get a chance to write out the metadata file. It seems there's something wrong with the way it's doing writes. After the crash both the metadata.mfs and metadata.mfs.back were 0 bytes, and mfsmetarestore (obviously) refused to read from them. Some but not all of the changelog files were 0 bytes as well. Same story on the backup (metalogger) server. Just a heads up, I think a little more checking would be in order here to make sure there is space available for the metadata, and at least to prevent the master from crashing when/if it can't write the metadata. If it had stayed up with all the metadata in memory I could've seen the disk issue and brought up another metalogger with more disk space to catch up and take over. ---------------------------------------------------------------------------- -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ moosefs-users mailing list moo...@li... https://lists.sourceforge.net/lists/listinfo/moosefs-users |