From: David Masover <ninja@slaphack.com>
To: "Vladimir V. Saveliev" <vs@namesys.com>
Cc: pat@patdouble.com, reiserfs-list@namesys.com
Subject: Re: where is the journal kept?
Date: Mon, 15 Aug 2005 10:52:18 -0500 [thread overview]
Message-ID: <4300BA32.7080101@slaphack.com> (raw)
In-Reply-To: <4300A603.2050602@namesys.com>
Vladimir V. Saveliev wrote:
> Hello
>
> Pat Double wrote:
>
>> Stupid, question. I thought that reiser4 had no journal,
>
>
> reiser4 has no filesystem area dedicated for journal.
> Instead it allocats log(journal) records dynamically.
>
> it is transactional.
>
>> If that's the case, why this option in debug.reiser4 :
>>
>> Usage: /sbin/debugfs.reiser4 [ options ] FILE
>> Print options:
>> -j, --print-journal prints journal.
>>
>
> yes, this prints reiser4 "wandering logs".
Not to beat a dead horse, but it might make things go faster if people
thought of the journal as an invisible, inaccessible file, because
everyone knows that files can be fragmented, and everyone also knows
that fragmented files can be reassembled and serialized (cat file).
Only possible difference is, I don't know if the reiser4 log comes out
of debugfs in any particular order.
It's an oversimplification, but probably a useful one.
next prev parent reply other threads:[~2005-08-15 15:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-15 11:53 where is the journal kept? Payal Rathod
2005-08-15 12:25 ` Vladimir V. Saveliev
2005-08-15 12:50 ` Payal Rathod
2005-08-15 12:58 ` Vladimir V. Saveliev
2005-08-15 13:12 ` Pat Double
2005-08-15 14:26 ` Vladimir V. Saveliev
2005-08-15 15:52 ` David Masover [this message]
2005-08-15 16:19 ` Shawn Rutledge
2005-08-15 17:34 ` Vladimir V. Saveliev
2005-08-15 18:08 ` Shawn Rutledge
2005-08-16 19:59 ` Hans Reiser
2005-08-16 20:27 ` Shawn Rutledge
2005-08-16 22:30 ` David Masover
2005-08-16 23:23 ` Shawn Rutledge
2005-08-17 0:02 ` David Masover
2005-08-17 0:47 ` Shawn Rutledge
2005-08-17 5:51 ` Hans Reiser
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=4300BA32.7080101@slaphack.com \
--to=ninja@slaphack.com \
--cc=pat@patdouble.com \
--cc=reiserfs-list@namesys.com \
--cc=vs@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.