From: Edward Shishkin <edward@namesys.com>
To: "Ronny T. Lampert" <telecaadmin@uni.de>,
Vitaly Fertman <vitaly@namesys.com>
Cc: reiserfs-list@namesys.com
Subject: Re: reiserfsck failing with external journal
Date: Thu, 30 Sep 2004 18:52:09 +0400 [thread overview]
Message-ID: <415C1D99.9050005@namesys.com> (raw)
In-Reply-To: <415C0EEC.30906@uni.de>
Ronny T. Lampert wrote:
> Hi,
>
> I've made a fs with the newest reiserfs-progs.
>
> #> mkreiserfs -j /dev/hda5 /dev/hda6
>
> Mounting is fine.
> But reiserfsck fails every time with:
>
> -o-o-
>
> ###########
> reiserfsck --check started at Thu Sep 30 15:42:47 2004
> ###########
>
> reiserfs_open_journal: journal parameters from the super block does
> not match
> to journal parameters from the journal. You should run reiserfsck
> with --rebuild-sb to check your superblock consistency.
Hello.
It is essential to specify right journal device for fsck, although I am
not sure
if this warning is correct. As I remember, fsck should ask for a
correct journal
device or suggest to use the option --no-journal-available (then you'll
be invited
to assign new journal device by reiserfstune). Vitaly?..
>
> -o-o-
>
> If I do as adviced (reiserfsck --rebuild-sb), it says the superblock
> is fine.
> Next time it fails with the same message.
>
> Only supplying -j /dev/hda5 to every reiserfs-prog will help :(
> Doing an
>
> #> reiserfstune --new-journal-dev /dev/hda5
>
> doesn't cure it, too.
>
> I think, that is not as it's supposed to work because it'll _break all
> system boot-up scripts_ !
Let's first take a look at the scripts that will be broken ;)
Edward.
>
> Is it some subtle bug in the reiserfs-progs, because they try to
> extract the journal_dev from the SB (as a quick look at the source
> reveals) but don't use it properly?
>
> Kind regards,
> Ronny
>
>
next prev parent reply other threads:[~2004-09-30 14:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-30 13:49 reiserfsck failing with external journal Ronny T. Lampert
2004-09-30 14:52 ` Edward Shishkin [this message]
2004-09-30 15:11 ` Ronny T. Lampert
2004-10-01 15:18 ` Vitaly Fertman
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=415C1D99.9050005@namesys.com \
--to=edward@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=telecaadmin@uni.de \
--cc=vitaly@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.