From: "Vladimir V. Saveliev" <vs@namesys.com>
To: Payal Rathod <payal-reiserfs@scriptkitchen.com>
Cc: reiserfs-list@namesys.com
Subject: Re: where is the journal kept?
Date: Mon, 15 Aug 2005 16:58:44 +0400 [thread overview]
Message-ID: <43009184.2080201@namesys.com> (raw)
In-Reply-To: <20050815125025.GA29390@tranquility.scriptkitchen.com>
Hello
Payal Rathod wrote:
> On Mon, Aug 15, 2005 at 04:25:37PM +0400, Vladimir V. Saveliev wrote:
>
>>Each journaling filesystem keeps its journal by its own way.
>>In reiserfs by default journal is kept in statically pre-allocated on mkfs
>>time 8192 blocks (4096 bytes each) starting from 18-th block.
>
>
> Is it kept in some sort of file?
No. That area of filesystem does not belong to any files stored on that filesystem.
You can read it from device directly: dd if=/dev/hda1 bs=4096 count=8192.
I am not sure that it can be of any interest, because you will see just binary data.
I mean can I see the file contents
> using normal UNIX tools? If yes how do I do it?
>
You can use
debugreiserfs -j /dev/hda1 /dev/hda1
to see journal content. This will decode binary data into human readable form.
> With warm regards,
> -Payal
>
>
next prev parent reply other threads:[~2005-08-15 12:58 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 [this message]
2005-08-15 13:12 ` Pat Double
2005-08-15 14:26 ` Vladimir V. Saveliev
2005-08-15 15:52 ` David Masover
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=43009184.2080201@namesys.com \
--to=vs@namesys.com \
--cc=payal-reiserfs@scriptkitchen.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.