From: Oleg Drokin <green@namesys.com>
To: Mike Fedyk <mfedyk@matchmail.com>
Cc: reiserfs-list@namesys.com
Subject: Re: another seriously corrupt ext3 -- pesky journal
Date: Tue, 19 Aug 2003 13:28:01 +0400 [thread overview]
Message-ID: <20030819092801.GA30729@namesys.com> (raw)
In-Reply-To: <20030818201609.GB10320@matchmail.com>
Hello!
On Mon, Aug 18, 2003 at 01:16:09PM -0700, Mike Fedyk wrote:
> IIUC, reiserfs uses a logical journal, and it only does meta-data
> journaling, but not to the level of ext3's writeback mode.
You probably meant ext3's jordered mode.
ext3's writeback mode is somewhat like reiserfs' default mode of operations
without extra journaling patches.
> There are patches to add ext3-like data journaling to reiserfs that are
> planned to be submitted for one of the next couple 2.4-pre kernels.
True.
Also Chris should be working on porting those to 2.6. At least I hope so.
> I'd be very interested in how reiserfs (and reiserfsck!) might handle a
> similar scenario.
We do not have journal inode. If you get your journal header or superblock
corrupted, you need to run "reiserfsck --rebuild-sb" and answer some questions
about what was your FS look like (amount of questions depends on how much
journal header and superblock were damaged).
All other corruptions (bitmaps and stuff) should be handled by usual reiserfsck modes.
(reiserfsck --rebuild-tree, if corruption was not trivial)
Bye,
Oleg
prev parent reply other threads:[~2003-08-19 9:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200308181639.h7IGdkWq019919@filer.fsl.cs.sunysb.edu>
[not found] ` <20030818181354.GC10270@think>
2003-08-18 20:16 ` another seriously corrupt ext3 -- pesky journal Mike Fedyk
2003-08-19 9:28 ` Oleg Drokin [this message]
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=20030819092801.GA30729@namesys.com \
--to=green@namesys.com \
--cc=mfedyk@matchmail.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.