From: Yury Umanets <umka@namesys.com>
To: Yury Umanets <umka@namesys.com>
Cc: Julian Hall <jules@acris.co.uk>, reiserfs-list@namesys.com
Subject: Re: Reiserfs with standard journal found, but there was specified a journal dev
Date: Mon, 10 Mar 2003 22:23:41 +0300 [thread overview]
Message-ID: <3E6CE63D.3060304@namesys.com> (raw)
In-Reply-To: <3E6CE559.1010400@namesys.com>
Yury Umanets wrote:
> Julian Hall wrote:
>
>> My FS never had an external journal device. I've used 'dd' to
>> transfer it to a different partition and am trying to get it to work,
>> but I get the following messages from reiserfsck:
>>
>> vengeance:~# reiserfsck --rebuild-sb /dev/hdc1
>>
>> <-------------reiserfsck, 2002------------->
>> reiserfsprogs 3.6.4
>> [...]
>> Will check superblock and rebuild it if needed
>> Will put log info to 'stdout'
>>
>> Do you want to run this program?[N/Yes] (note need to type Yes if you
>> do):Yes
>> super.c 228 rebuild_sb
>> Reiserfs with standard journal found, but there was specified a
>> journal dev
>
>
> It means, that superblock has journal dev field initialized by not zero.
>
>>
>>
>>
>> Do I need to use the --no-journal-available option? Or is it
>> something else. If I just run --check rather than anything else, it
>> manages to check the journal OK, but then complains that
>> --rebuild-tree didn't finish last time.
>
>
> I can do the following:
Sorry :) I wanted to say, that you can do the listed operations :)
>
>>
>>
>> Any ideas?
>>
>> Jules
>>
>>
>>
>>
>
>
--
Yury Umanets
next prev parent reply other threads:[~2003-03-10 19:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-10 19:03 Reiserfs with standard journal found, but there was specified a journal dev Julian Hall
2003-03-10 19:19 ` Yury Umanets
2003-03-10 19:23 ` Yury Umanets [this message]
2003-03-10 19:30 ` Julian Hall
2003-03-11 6:48 ` Oleg Drokin
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=3E6CE63D.3060304@namesys.com \
--to=umka@namesys.com \
--cc=jules@acris.co.uk \
--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.