All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tuomas Jormola <tjormola@cc.hut.fi>
To: reiserfs-list@namesys.com
Subject: Re: LVM array, one disk failed
Date: 03 Jan 2003 00:04:01 +0200	[thread overview]
Message-ID: <1041545041.13918.7.camel@ganga> (raw)
In-Reply-To: <20021228113942.A6599@namesys.com>

On Sat, 2002-12-28 at 10:39, Oleg Drokin wrote:
> Hello!
> 
> On Sat, Dec 28, 2002 at 05:07:31AM +0200, Tuomas Jormola wrote:
> > I have a 110GiB LVM array constructed using EVMS. It consists of three
> > IDE hard disks from which the last one died the other day. The
> > filesystem is ReiserFS, of course. Array is a linear one and there was
> > about 15GiB free space when disk died so I'm hoping there was a somewhat
> > resonable way to recover the data on two disks that are full and in
> > front of the array. The failed disk is totally dead, not just a couple
> > of bad sectors. It spins but it's not detected on boot. When I try to
> > mount the volume with only two disks connected, it get this:
> > sh-2029: reiserfs read_bitmaps: bitmap block (#19234816) reading failed
> > reiserfs_read_super: unable to read bitmap
> 
> This is hardware problem ;)
> 
> But if your raid setup does not use any stripping, this is possible to
> rercover from such a situation.
> The easiest way that comes to mind is to add another disk instead failed one so
> that all of the FS blocks still accessible.
> Then you can mount the FS and all the data would be intact (only bitmaps and
> other stuff from failed disk would be corrupted).
> 
> If you do not plan to add anymore drives or if you just don't have
> spare drive, you probably can run reiserfsck --rebuild-sb and after
> couple of questions it will write updated superblock that
> respects changed filesystem size (actually for this to work you first need
> to tell your LVM to report current volume size that is now shorter
> than it was at creation time).
reiserfsck says

Reiserfs with standard journal found, but there was specified a journal dev

I guess guess it's bad thing :/

-- 
Tuomas Jormola <tjormola@cc.hut.fi>


  reply	other threads:[~2003-01-02 22:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-28  3:07 LVM array, one disk failed Tuomas Jormola
2002-12-28  8:39 ` Oleg Drokin
2003-01-02 22:04   ` Tuomas Jormola [this message]
2003-01-06  7:01     ` Oleg Drokin
2003-01-06 18:33       ` Tuomas Jormola
2003-01-07 11:40         ` Vitaly Fertman
2002-12-29  1:04 ` Erik Tews

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=1041545041.13918.7.camel@ganga \
    --to=tjormola@cc.hut.fi \
    --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.