From: sean finney <seanius@seanius.net>
To: "Vladimir V. Saveliev" <vs@namesys.com>
Cc: reiserfs-list@namesys.com
Subject: Re: reiserfsprogs: options for recovering from reiserfsck/"Not enough allocable blocks"
Date: Tue, 23 Jan 2007 17:05:26 +0100 [thread overview]
Message-ID: <1169568327.5468.71.camel@localhost> (raw)
In-Reply-To: <200701231919.37775.vs@namesys.com>
[-- Attachment #1: Type: text/plain, Size: 1059 bytes --]
hi vladimir,
On Tue, 2007-01-23 at 19:19 +0300, Vladimir V. Saveliev wrote:
> You should setup a linear raid (IMPORTANT: with no persistent super block) of /dev/mapper/vg0-backup and some spare device.
> Spare device does not have to be big. I do not think that you can not find 50mb of disk space to create a loop device on that space.
> Then you have to run --rebuild-sb and --rebuild-tree
>
> See more details at http://www.mail-archive.com/reiserfs-list@namesys.com/msg21597.html
thanks for this. it's less complicated than i thought. i'll report
back tomorrow morning/afternoon after i've had the chance to run it.
> > (2) reiserfsprogs 3.6.20, which may have a fix? doesn't look released
> > yet, and i'm not sure how stable/dangerous it is.
> >
> 3.6.20 does not have a fix for that bug.
>
> > also, i've heard mention of --scan-whole-partition. would that be
> > advisable in this situation with 3.6.19?
>
> no
thanks for the clarifications on these, saves me some time and possible
fs corruption :)
sean
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 191 bytes --]
prev parent reply other threads:[~2007-01-23 16:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-23 13:29 reiserfsprogs: options for recovering from reiserfsck/"Not enough allocable blocks" sean finney
[not found] ` <200701231919.37775.vs@namesys.com>
2007-01-23 16:05 ` sean finney [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=1169568327.5468.71.camel@localhost \
--to=seanius@seanius.net \
--cc=reiserfs-list@namesys.com \
--cc=vs@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.