On Sunday 09 January 2005 23:31, Sergey S. Kostyliov wrote:
> Hello all,
>
> mkfs.reiser4 says that minimal fs size is 25 block.
>
>     [EMAIL PROTECTED] rathamahata $ dd if=/dev/zero of=image bs=4096
> count=1 1+0 records in
>     1+0 records out
>     [EMAIL PROTECTED] rathamahata $ /sbin/mkfs.reiser4 -y -f image
>     Error: Requested filesystem size (1) is too small. Reiser4 required
> minimal size 25 blocks long.
>     Error: Can't create filesystem on image.
>     [EMAIL PROTECTED] rathamahata $
>
> But that seems to be not true.
>
>     [EMAIL PROTECTED] rathamahata $ uname -a
>     Linux arise.vh.com.ru 2.6.10 #5 Sat Jan 8 21:06:34 MSK 2005 i686 AMD
> Athlon(TM) XP 2500+ AuthenticAMD GNU/Linux [EMAIL PROTECTED] rathamahata $
> /sbin/mkfs.reiser4 -V
>     /sbin/mkfs.reiser4 1.0.3
>     Copyright (C) 2001, 2002, 2003, 2004 by Hans Reiser, licensing governed
> by reiser4progs/COPYING.
>
>     [EMAIL PROTECTED] rathamahata $ dd if=/dev/zero of=image bs=4096
> count=25 25+0 records in
>     25+0 records out
>     [EMAIL PROTECTED] rathamahata $ /sbin/mkfs.reiser4 -y -f image
>     [EMAIL PROTECTED] rathamahata $ echo $?
>     0
>     [EMAIL PROTECTED] rathamahata $ /sbin/fsck.reiser4 -y image
>     *******************************************************************
>     This is an EXPERIMENTAL version of fsck.reiser4. Read README first.
>     *******************************************************************
>
>     Fscking the image block device.
>     Will check the consistency of the Reiser4 SuperBlock.
>     Will check the consistency of the Reiser4 FileSystem.
>     ***** fsck.reiser4 started at Sun Jan  9 23:19:41 2005
>     Fatal: Failed to open the reiser4 backup.
>     Fatal: Cannot open the FileSystem on (image).
>
>     1 fatal corruptions were detected in SuperBlock. Run with --build-sb
> option to fix them.
>
>     [EMAIL PROTECTED] rathamahata $
>
> It looks like either actual minimal size is large or there is bug in
> reiser4progs...

yes, it was a bug in reiser4progs, thank you for the report.



-- 
Thanks,
Vitaly Fertman


Reply via email to