From: Vitaly Fertman <vitaly@namesys.com>
To: Bartlomiej Pater <noster@venture.org.pl>
Cc: reiserfs-list@namesys.com
Subject: Re: bad sb - mounting problem
Date: Wed, 16 Apr 2003 21:17:30 +0400 [thread overview]
Message-ID: <200304162117.30155.vitaly@namesys.com> (raw)
In-Reply-To: <200304161841.46413.noster@venture.org.pl>
Hi,
> -----------------------
> Apr 16 18:24:03 monada kernel: Using r5 hash to sort names
> Apr 16 18:24:03 monada kernel: ReiserFS version 3.6.25
> Apr 16 18:24:03 monada kernel: reiserfs: checking transaction log
> (device 03:07) ...
> Apr 16 18:24:03 monada kernel: journal-1204: REPLAY FAILURE fsck
> required! Trying to replay onto a log block
> Apr 16 18:24:03 monada kernel: Replay Failure, unable to mount
> Apr 16 18:24:03 monada kernel: reiserfs_read_super: unable to
> initialize journal space
> ------------------------
>
> now one of my partitions is unavailable. I've tried fsck with
> --rebuild-sb and --rebuild-tree options but with no results [and no
> errors either]. I've googled through internet and searched this
> mailing list archives.
What do you mean by saying "no results [and no errors either]"?
Do you mean that reiserfsck --rebuild-tree finishes with no problem,
but on fs mount the kernel sais "REPLAY FAILURE" again?
> I've downloaded v3.6.5 [+patch] of reiserfsprogs
right.
> and compiled kernel with debug on but with no changes. Is there something
> I can do to salvage the data?
What does reiserfsck --check say?
So, you still have the same "REPLAY FAILURE" on mount, right?
--
Thanks,
Vitaly Fertman
prev parent reply other threads:[~2003-04-16 17:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-16 16:41 bad sb - mounting problem Bartlomiej Pater
2003-04-16 17:17 ` Vitaly Fertman [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=200304162117.30155.vitaly@namesys.com \
--to=vitaly@namesys.com \
--cc=noster@venture.org.pl \
--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.