From: Anders Widman <andewid@tnonline.net>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] pvmove -i does not work..
Date: Mon Mar 4 05:34:01 2002 [thread overview]
Message-ID: <147246562.20020304123407@tnonline.net> (raw)
In-Reply-To: <20020304110128.A10007@sistina.com>
I guess not. It is lvmtools 1.0.3 with the patch to move beyond 2GB
limit.
//Anders
> On Mon, Mar 04, 2002 at 01:08:40AM +0100, Anders Widman wrote:
>> Has anyone tried pvmove -i on a faulty disk (bad blocks)?
>>
>> pvmove -i /dev/crashed /dev/new stops when it hits the bad blocks.
>> This wasn't so bad for me this time as I could use dd to move
>> everything from the bad disk to my new disk...
> Is that with the llseek patch for liblvm.h in?
>>
>> //Anders
>>
>>
>> _______________________________________________
>> linux-lvm mailing list
>> linux-lvm@sistina.com
>> http://lists.sistina.com/mailman/listinfo/linux-lvm
>> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
prev parent reply other threads:[~2002-03-04 5:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-03 18:08 [linux-lvm] pvmove -i does not work Anders Widman
2002-03-04 4:03 ` Heinz J . Mauelshagen
2002-03-04 5:34 ` Anders Widman [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=147246562.20020304123407@tnonline.net \
--to=andewid@tnonline.net \
--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