From: Mike Fedyk <mfedyk@matchmail.com>
To: Hans Reiser <reiser@namesys.com>
Cc: Chris Mason <mason@suse.com>,
Bernd Schubert <bernd-schubert@web.de>,
reiserfs-list@namesys.com, Andrew Morton <akpm@osdl.org>
Subject: Re: reiserfs logging patches udpated
Date: Mon, 29 Mar 2004 10:49:06 -0800 [thread overview]
Message-ID: <40686FA2.1010501@matchmail.com> (raw)
In-Reply-To: <4068203E.4050700@namesys.com>
Hans Reiser wrote:
> Chris Mason wrote:
>
>> On Thu, 2004-03-25 at 15:41, Mike Fedyk wrote:
>>
>>
>>> Chris Mason wrote:
>>>
>>>
>>>> On Wed, 2004-03-24 at 22:56, Mike Fedyk wrote:
>>>>
>>>>
>>>>
>>>>
>>>>> And after having the difference of a block level journal (ext3),
>>>>> instead of a "virtual" journal(reiserfs, jfs, xfs) explained to me
>>>>> (check the ext3-users archives...) -- and how it can save your ass
>>>>> when there are hardware problems. I was convinced and switched
>>>>> everything back to ext3.
>>>>>
>>>>
>>>> reiserfs does block based logging ;-)
>>>>
>>>
>>> I stand corrected.
>>>
>>> Thanks Chris, I feel much better about reiserfs now, especially with
>>> your ordered/data journaling patches.
>>>
>>
>>
>> One other point, the current patch set only does data=ordered. I wanted
>> that fully stabilized before I enabled data=journal.
>>
>> -chris
>>
>>
>>
>>
>>
>>
> what is a virtual journal?
>
The basic idea of virtual vs block journals, is that instead of using a
few bytes to describe what you're changing in (for instance) the inode
table (or equivalent), ext3 (and reiser3 thanks to info from Chris
Mason) copies entire inode table block (usually 1-4k depending on block
size) into the journal.
next prev parent reply other threads:[~2004-03-29 18:49 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-24 17:29 reiserfs logging patches udpated Chris Mason
2004-03-24 19:08 ` Christian Mayrhuber
2004-03-24 19:43 ` Lamont R. Peterson
2004-03-24 19:49 ` Hubert Chan
2004-03-24 20:06 ` Chris Mason
2004-03-24 22:18 ` Andrew Morton
2004-03-24 22:26 ` Chris Mason
2004-03-24 22:35 ` Andrew Morton
2004-03-24 22:46 ` Chris Mason
2004-03-24 22:59 ` Andrew Morton
2004-03-24 23:03 ` Chris Mason
2004-03-25 0:47 ` Bernd Schubert
2004-03-25 1:00 ` Chris Mason
2004-03-25 1:14 ` Dieter Nützel
2004-03-25 18:11 ` Bernd Schubert
2004-03-25 18:19 ` Chris Mason
2004-03-25 18:59 ` Bernd Schubert
2004-03-25 19:07 ` Chris Mason
2004-03-25 19:22 ` Matthias Andree
2004-03-25 3:56 ` Mike Fedyk
2004-03-25 14:14 ` Chris Mason
2004-03-25 20:41 ` Mike Fedyk
2004-03-25 20:50 ` Chris Mason
2004-03-29 13:10 ` Hans Reiser
2004-03-29 18:49 ` Mike Fedyk [this message]
2004-03-30 17:16 ` Nikita Danilov
2004-03-30 19:06 ` Mike Fedyk
2004-03-25 16:51 ` Dieter Nützel
2004-03-25 19:02 ` Matthias Andree
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=40686FA2.1010501@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=akpm@osdl.org \
--cc=bernd-schubert@web.de \
--cc=mason@suse.com \
--cc=reiser@namesys.com \
--cc=reiserfs-list@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.