From: Erkki Seppala <flux@inside.org>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] pvmoving from a pv with bad sectors
Date: Sat Feb 9 09:10:02 2002 [thread overview]
Message-ID: <20020209150956.GA11057@xulfad.ton.tut.fi> (raw)
In-Reply-To: <20020209142411.GA10226@xulfad.ton.tut.fi>
It appears I didn't try rescuing the data a moment too soon, as the
drive stopped giving me data shortly after writing that message..
And as I predicted, /dev/archive is gone. Is there a way to retrieve
it, I imagine the lost device physically had only one logical volume
in it? The device had 20 gigabytes of data. I imagine reiserfs cannot
handle so big holes in filesystem, so I'll just hope the hole hits one
of the smaller, backed up logical volumes instead of the one, huge,
non-backed up volume :).
The output of vgscan -d is available at
http://xulfad.inside.org/~flux/vgscan . Also the latest backup of LVM
is at http://xulfad.inside.org/~flux/archive.conf .
I imagine I need to somehow remove the invalid device from the volume
group, but as I cannot even activate it, it cannot be done with
default utilities? Also the now-gone-and-disconnected physical volume
contained some data, and cannot be removed from the volume group
before the VG knows the device is empty. I can propably get a new disc
next week, would that make things easier?
--
_____________________________________________________________________
/ __// /__ ____ __ Erkki Sepp�l�\ \
/ /_ / // // /\ \/ //ircnet Modeemi Ry\ /
/_/ /_/ \___/ /_/\_\@modeemi.fi http://www.modeemi.fi/~flux/
next prev parent reply other threads:[~2002-02-09 9:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-09 8:24 [linux-lvm] pvmoving from a pv with bad sectors Erkki Seppala
2002-02-09 9:10 ` Erkki Seppala [this message]
2002-02-11 14:53 ` [linux-lvm] rescuing a VG with one missing PV Erkki Seppala
2002-02-12 3:24 ` Heinz J . Mauelshagen
2002-02-12 6:58 ` Erkki Seppala
2002-02-12 8:07 ` Heinz J . Mauelshagen
2002-02-12 15:37 ` Erkki Seppala
2002-02-13 3:27 ` Heinz J . Mauelshagen
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=20020209150956.GA11057@xulfad.ton.tut.fi \
--to=flux@inside.org \
--cc=linux-lvm@sistina.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).