From: lJoublanc@softhome.net
To: reiserfs-list@namesys.com
Subject: reiser4progs-1.0.3 : superblock backups
Date: Wed, 15 Dec 2004 11:30:38 -0700 [thread overview]
Message-ID: <courier.41C082CE.00004F63@softhome.net> (raw)
Regarding the new release of reiser4progs:
it's unclear to me from the release announcement whether prevoius versions
of reiser4progs correctly backup superblocks or not. You imply it's been
corrected - so it wasn't working before?
i.e. if I had previously used libaal 1.0.2, and my superblock got corrupted,
could I rebuild it from teh backup if upgarded to 1.0.3?
I'm asking because recently that's exactly what happened to me. My disc is
failing due to hardware level problems, the superblock is wrecked, it won't
mount, and I need to recover my stuff!
In a final rescue effort, I've updated to 1.0.3, but if I run fsck.reiser4
--build-sb, I get:
[...]
Warn : A new master superblock is created on '/dev/hdd1'.
Enter the key plugin name [key_large]:
Error: Can't read bitmap block 18. Input/output error.
Error: Can't load ondisk bitmap.
Error: Can't initialize block allocator.
Fatal: Failed to open the block allocator.
Can anyone tell me what it means? Is the problem to do with reiser4
superblocks or is the disk so buggered it can't write the table anymore?
Any help is greatly appreciated...
Luciano
p.s. shame I'm having these hardware problems, as besides that r4 has worked
pretty well!
next reply other threads:[~2004-12-15 18:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-15 18:30 lJoublanc [this message]
2004-12-15 22:10 ` reiser4progs-1.0.3 : superblock backups 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=courier.41C082CE.00004F63@softhome.net \
--to=ljoublanc@softhome.net \
--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.