On Tue, 6 Jul 2010 12:53:37 +0300
Stas Oskin <sta...@gm...> wrote:
> > I bet it is due to reserved blocks for root.
> > If you run ext2/3/4 try:
> > tune2fs -m 0 /dev/bla with ext2/3 tune4fs if ext4.
> > No need to unmount or put the volume read-only.
> > Some space will be kept as used, but formatting is taking a bunch of
> > blocks.
> >
> >
> Yep, that was it, thanks!
>
> Speaking of ext4, have you tried it with mfs? I seen some bad experience
> posted here about this.
The only mail I found is « I tried it on secondary cluster in ext4 and
btrfs, for 3 months ok, failed after I could not find the reason, »
I'd blame btrfs for sure, as it is still experimental.
I have two boxes whose moosefs volume is ext4, no problem up to now.
Actually, to be more precise, the file which is loop-mounted is stored
on ext4. the FS in the given file is ext3. (yes, yes, testing
deployment for now).
Other than that, I have 2 classical volume of 14TB each running ext4
without a glitch. Yes, they do not run mfs, but as mfs is in
user-space, it can't be blamed for FS problems (which are kernel-space).
Hope it helps.
--
Laurent Wandrebeck
HYGEOS, Earth Observation Department / Observation de la Terre
Euratechnologies
165 Avenue de Bretagne
59000 Lille, France
tel: +33 3 20 08 24 98
http://www.hygeos.com
GPG fingerprint/Empreinte GPG: F5CA 37A4 6D03 A90C 7A1D 2A62 54E6 EF2C
D17C F64C
|