From: "Ragnar Kjørstad" <lvm@ragnark.vestdata.no>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] pv_move_pe() error again :/
Date: Fri, 7 Sep 2001 11:43:03 +0200 [thread overview]
Message-ID: <20010907114303.C19457@vestdata.no> (raw)
In-Reply-To: <E15f8l7-0008Di-00@hermes.sistina.com>; from fejf@gmx.de on Fri, Sep 07, 2001 at 01:41:22AM +0200
On Fri, Sep 07, 2001 at 01:41:22AM +0200, FEJF wrote:
> there are no io-errors... but as the hd makes really scary noise when pvmove
> tries to move the remaining bytes. so i think the hd is damaged.
> but all i want is to remove the damaged hd.
> but pvreduce says i have to use pvmove to get rid of the remaining data and
> pvmove gives the errors...
> so i can't remove it :/ - is there a way to get rid of the hd without
> destroying the rest of the data ? sth. like pvreduce --force ?
No, don't think so.
I have a patch, but I'm not so sure I can recommend that you use it.
I only wrote it to copy off a single block of a bad disk - I'm not sure
exactly how it will behave when moving multiple blocks (if the
non-corrupted blocks will end up in the right spot, or if it writes too
little data, so it will be some bytes off).
--
Ragnar Kjørstad
Big Storage
next prev parent reply other threads:[~2001-09-07 9:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-06 15:28 [linux-lvm] pv_move_pe() error again :/ FEJF
2001-09-06 20:05 ` Ragnar Kjørstad
2001-09-06 23:41 ` FEJF
2001-09-07 9:43 ` Ragnar Kjørstad [this message]
2001-09-07 11:36 ` FEJF
2001-09-09 22:16 ` Ragnar Kjørstad
2001-09-09 23:51 ` FEJF
2001-09-10 8:39 ` Ragnar Kjørstad
2001-09-10 11:27 ` Heinz J . Mauelshagen
2001-09-10 11:45 ` FEJF
2001-09-10 13:43 ` Heinz J . Mauelshagen
2001-09-10 13:49 ` FEJF
2001-09-10 15:38 ` Ragnar Kjørstad
2001-09-10 16:13 ` FEJF
2001-09-11 14:31 ` Heinz J . Mauelshagen
2001-09-11 17:26 ` Ragnar Kjørstad
2001-09-10 11:53 ` FEJF
2001-09-07 10:46 ` Heinz J . Mauelshagen
2001-09-07 11:45 ` FEJF
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=20010907114303.C19457@vestdata.no \
--to=lvm@ragnark.vestdata.no \
--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 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.