From: Tomas Szepe <szepe@pinerecords.com>
To: Hans Reiser <reiser@namesys.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
Oleg Drokin <green@namesys.com>,
zam@namesys.com, umka <umka@thebsh.namesys.com>
Subject: Re: [BK][PATCH] Reiser4, will double Linux FS performance, pleaseapply
Date: Fri, 1 Nov 2002 11:23:27 +0100 [thread overview]
Message-ID: <20021101102327.GA26306@louise.pinerecords.com> (raw)
In-Reply-To: <3DC1DF02.7060307@namesys.com>
> The atomic transactions that reiser4 offers are a much higher level of
> data security than data journaling. Really, you should read the 17 page
> papers I send you URLs to;-).....
> (www.namesys.com/v4/fast_reiser4.html).
Am I to assume the following is expected behavior then?
# mkfs.reiser4 /dev/sda2
mkfs.reiser4, 0.1.0
Information: Reiser4 is going to be created on /dev/sda2.
(Yes/No): y
Creating reiser4 on /dev/sda2 with default40 profile...done
Synchronizing /dev/sda2...done
# mount /dev/sda2 /ap
# df /ap
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/sda2 1490332 136 1490196 1% /ap
# (cd /ap && tar xzf /usr/src/linux-2.5.45.tgz)
# df /ap
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/sda2 1490332 200508 1289824 14% /ap
# sync
# df /ap
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/sda2 1490332 200468 1289864 14% /ap
# rm -rf /ap/linux-2.5.45
# df /ap
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/sda2 1490332 255436 1234896 18% /ap
# # wtf is going on here?
# sync
# df /ap
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/sda2 1490332 85848 1404484 6% /ap
# umount /ap
# mount /dev/sda2 /ap
# df /ap
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/sda2 1490332 54532 1435800 4% /ap
# # and here?
T.
next prev parent reply other threads:[~2002-11-01 10:17 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-31 21:23 [BK][PATCH] Reiser4, will double Linux FS performance, please apply Hans Reiser
2002-10-31 22:34 ` Dieter Nützel
2002-10-31 22:34 ` Dieter Nützel
2002-10-31 22:47 ` Hans Reiser
2002-10-31 22:47 ` Hans Reiser
2002-11-01 1:17 ` [BK][PATCH] Reiser4, will double Linux FS performance, pleaseapply Andrew Morton
2002-11-01 1:27 ` Andrew Morton
2002-11-05 21:39 ` reiser
2002-11-01 1:27 ` Hans Reiser
2002-11-01 1:33 ` Andrew Morton
2002-11-01 1:44 ` Dieter Nützel
2002-11-01 4:36 ` Linus Torvalds
2002-11-01 10:59 ` Nikita Danilov
2002-11-01 1:55 ` Hans Reiser
2002-11-01 10:23 ` Tomas Szepe [this message]
2002-11-01 17:19 ` Alexander Zarochentcev
2002-11-02 13:24 ` Tomas Szepe
2002-11-04 11:00 ` Nikita Danilov
2002-11-04 19:56 ` Andreas Dilger
2002-11-02 13:38 ` Tomas Szepe
2002-11-04 12:02 ` Nikita Danilov
2002-11-04 17:10 ` Tomas Szepe
2002-11-04 17:53 ` Nikita Danilov
2002-11-04 18:10 ` Tomas Szepe
2002-11-05 7:30 ` reiser
2002-11-05 8:28 ` Alexander Zarochentcev
2002-11-05 9:29 ` Andreas Dilger
2002-11-05 9:59 ` Tomas Szepe
2002-11-05 10:08 ` Alexander Zarochentcev
2002-11-05 10:23 ` Tomas Szepe
2002-11-05 10:46 ` Nikita Danilov
2002-11-05 8:44 ` reiser
2002-11-05 8:49 ` Alexander Zarochentcev
2002-11-05 21:08 ` reiser
[not found] <877555917@toto.iv>
2002-11-05 23:09 ` Peter Chubb
2002-11-06 1:33 ` reiser
2002-11-06 14:25 ` Daniel Egger
2002-11-07 17:19 ` Pavel Machek
2002-11-07 16:58 ` Bill Davidsen
-- strict thread matches above, loose matches on Subject: below --
2002-11-06 18:37 Tom Reinhart
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=20021101102327.GA26306@louise.pinerecords.com \
--to=szepe@pinerecords.com \
--cc=green@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiser@namesys.com \
--cc=umka@thebsh.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.