mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Cole <elenstev@mesatop.com>
To: Alex Zarochentsev <zam@namesys.com>
Cc: Hans Reiser <reiser@namesys.com>, Oleg Drokin <green@namesys.com>,
	reiserfs-dev@namesys.com, reiserfs-list@namesys.com,
	linux-kernel@vger.kernel.org, demidov <demidov@namesys.com>,
	god@namesys.com
Subject: Re: reiser4 snapshot for August 26th.
Date: 26 Aug 2003 13:14:46 -0600	[thread overview]
Message-ID: <1061925286.1666.31.camel@spc9.esa.lanl.gov> (raw)
In-Reply-To: <20030826184114.GP5448@backtop.namesys.com>

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 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





  reply	other threads:[~2003-08-26 19:18 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-26 10:22 Oleg Drokin
2003-08-26 18:20 ` Steven Cole
2003-08-26 18:26   ` Alex Zarochentsev
2003-08-26 19:36     ` Felipe Alfaro Solana
2003-08-26 19:43       ` Oleg Drokin
2003-08-26 19:51         ` Steven Cole
2003-08-26 20:05           ` Mike Fedyk
2003-08-26 20:13             ` Steven Cole
2003-08-26 20:26               ` Mike Fedyk
2003-08-26 20:25                 ` Steven Cole
2003-08-26 20:30                 ` Hans Reiser
2003-08-26 20:28           ` Hans Reiser
2003-08-26 19:53         ` Mike Fedyk
2003-08-26 19:57       ` how to log reiser and raid0 crash? 2.6.0-t4 Resident Boxholder
2003-08-26 22:20         ` Resident Boxholder
2003-08-27 10:35         ` Oleg Drokin
2003-08-28  7:28           ` Resident Boxholder
2003-08-26 18:38   ` reiser4 snapshot for August 26th Steven Cole
2003-08-26 19:22     ` Hans Reiser
2003-08-26 18:38   ` Oleg Drokin
2003-08-26 18:41   ` Hans Reiser
2003-08-26 18:41     ` Alex Zarochentsev
2003-08-26 19:14       ` Steven Cole [this message]
2003-08-28 11:46         ` Alex Zarochentsev
2003-08-28 15:12           ` Steven Cole
2003-08-28 16:33           ` Tupshin Harper
2003-08-26 19:15       ` Hans Reiser
2003-08-28 18:31   ` Vladimir Demidov
2003-08-26 21:28 ` Diego Calleja García
2003-08-27  7:38   ` Oleg Drokin
2003-08-27  5:52 ` Ian Wienand
2003-08-27  6:03   ` Yury Umanets
2003-08-27 11:19     ` Felipe Alfaro Solana
2003-08-27 15:54       ` Hans Reiser
2003-09-15 11:15 ` reiser4 snapshot 20030905 [OOPS] Maciej Soltysiak
2003-09-15 13:52   ` Nikita Danilov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1061925286.1666.31.camel@spc9.esa.lanl.gov \
    --to=elenstev@mesatop.com \
    --cc=demidov@namesys.com \
    --cc=god@namesys.com \
    --cc=green@namesys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reiser@namesys.com \
    --cc=reiserfs-dev@namesys.com \
    --cc=reiserfs-list@namesys.com \
    --cc=zam@namesys.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®