From: Sander <sander@humilis.net>
To: Vitaly Fertman <vitaly@namesys.com>
Cc: Ookhoi <ookhoi@xs4all.nl>, reiserfs-list@namesys.com
Subject: Re: reiser4progs 1.0.4
Date: Tue, 22 Feb 2005 21:08:09 +0100 [thread overview]
Message-ID: <20050222200809.GA15179@favonius> (raw)
In-Reply-To: <200502211659.53972.vitaly@namesys.com>
Vitaly Fertman wrote (ao):
> On Monday 21 February 2005 16:59, Vitaly Fertman wrote:
> > On Monday 21 February 2005 16:10, Ookhoi wrote:
> > > On Sun, Feb 20, 2005 at 01:44:41PM +0300, Vitaly Fertman wrote:
> > > > The new reiser4progs package is available on our ftp
> > > > site (ftp://ftp.namesys.com/pub/reiser4progs/).
> > >
> > > Thank you for this release. It doesn't crash anymore :-)
> > >
> > > But it does tell me:
> > > "NO REISER4 METADATA WERE FOUND. FS RECOVERY IS NOT POSSIBLE."
> > no master super block, no format-specific super block, no backup
> > blocks, no status block, all bitmap blocks are not valid, no one
> > reiser4 formatted node has been found ... what you are fscking does
> > not look like a reiser4 filesystem at all.
As said before I was very much asleep when I ran the fsck command. It
should have been hda2, not hda1.
Btw, hda1 contained an ext2 filesystem which was not mountable and not
recoverable after running all the fsck.reiser4 commands on it. Can't
blame it I guess :-) Luckily it was only /boot and thus easy to
recover.
I managed to reboot the machine and mount the fs. Some files where
corrupted, but on the whole the fs seems fine now. So a big thumbs up
for this release of fsck.reiser4 :-)
Btw, I blame the corruption on the combination kernel and a forced
hard-reboot during shutdown (it hung).
Again, thumbs up. This all made me much more confident wrt Reiser4.
With kind regards, Sander
next prev parent reply other threads:[~2005-02-22 20:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-20 10:44 reiser4progs 1.0.4 Vitaly Fertman
2005-02-21 13:10 ` Ookhoi
2005-02-21 13:59 ` Vitaly Fertman
2005-02-21 17:01 ` Ookhoi
2005-02-22 20:08 ` Sander [this message]
2005-02-21 14:35 ` Jindrich Makovicka
2005-02-21 16:49 ` Vitaly Fertman
2005-03-18 18:59 ` Jindrich Makovicka
2005-03-19 14:23 ` Vitaly Fertman
2005-03-19 18:03 ` Jindrich Makovicka
2005-03-21 13:30 ` 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=20050222200809.GA15179@favonius \
--to=sander@humilis.net \
--cc=ookhoi@xs4all.nl \
--cc=reiserfs-list@namesys.com \
--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.