Re: reiser4 snapshot for August 26th.

[Alex Zarochentsev <zam@namesys.com>]

On Tue, Aug 26, 2003 at 01:14:46PM -0600, Steven Cole wrote:
> On Tue, 2003-08-26 at 12:41, Alex Zarochentsev wrote:
> > On Tue, Aug 26, 2003 at 10:41:45PM +0400, Hans Reiser wrote:
> > > Mr. Demidov, if you put code that does not compile into our tree you 
> > > need to make the config option for it be invisible.
> > 
> > There is such an option already, CONFIG_REISER4_FS_SYSCALL, 
> > seems it is off by default.
> 
> Yes, but I the simple minded user that I am turned it on without reading
> the Kconfig help carefully.  Now, it's off, and it compiles.
> 
> But, now for more interesting stuff:
> 
> [root@spc1 steven]# cd /
> [root@spc1 /]# mkdir share_r4
> [root@spc1 /]# mount -t reiser4 /dev/hda11 /share_r4
> [root@spc1 /]# df -T
> Filesystem    Type   1K-blocks      Used Available Use% Mounted on
> /dev/hda1     ext3      241116     89449    139219  40% /
> /dev/hda9     ext3    20556656  16526188   4030468  81% /home
> none         tmpfs      126784         0    126784   0% /dev/shm
> /dev/hda8     ext3      241116      4711    223957   3% /tmp
> /dev/hda6     ext3     3012204   2507596    351592  88% /usr
> /dev/hda7     ext3      489992     70721    393971  16% /var
> df: `/share_r4': Value too large for defined data type

I can't reproduce that.  Do you see df errors each time you mount just created
reiser4 fs?  Can you provide additional information about your system:
distro, libc which you used?  

My hypothesysis is that libc statfs or df itself want to convert "free inodes"
result parameter which is __u64 to shorter data type.  reiser4_statfs() sets
kstatfs->f_ffree to a large value which is close to 2^64.

> 
> I have recently run mkfs.reiser4 on /dev/hda11 with no options.
> The reiser4progs version is 0.4.12.
> 
> I made a local clone of the 2.6-test bk tree on the new reiser4
> file system and that worked OK.
> 
> I then did a "time bk -r check -acv", twice for both reiser4 and ext3.
> Here are the results for the second run for each (I neglected to
> preserve the results for the initial bk -r check -acv):
> 
> Reiser4:
> real    1m27.774s
> user    0m33.685s
> sys     0m16.059s
> 
> Ext3:
> real    2m55.179s
> user    0m32.752s
> sys     0m5.835s
> 
> Nice work.  I'll try to break Reiser4 now.
> 
> Steven
> 
> 
> 
> 

-- 
Alex.