From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] pvmove and badsectors
Date: Thu Jul 10 17:21:02 2003 [thread overview]
Message-ID: <20030711001930.F23240@sistina.com> (raw)
In-Reply-To: <5.2.0.9.2.20030710233915.03308cf8@pop.tvnet.hu>; from newsmail@satimex.tvnet.hu on Fri, Jul 11, 2003 at 12:08:57AM +0100
On Fri, Jul 11, 2003 at 12:08:57AM +0100, Newsmail wrote:
> -i, --ignore_read_errors
> Ignore read errors while moving data. Usefull in case data is moved
> away from a broken or unac
> cessable disk (area).
> Hi everybody I would like to know, if pvmove finds an unreadable block in a
> PV, does it ignore the complete PV or just the bad area? I mean if a 32MB
> PV has a bad block, the complete 32 megs get ignored, or only the
> problematic area?
pvmove moves data chunk by chunk (64kB).
If such chunk read fails, it retries rereading the failed chunk sector
by sector in order to retrieve as much data as possible.
> thx in advance,
> greg
>
>
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
--
Regards,
Heinz -- The LVM Guy --
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Am Sonnenhang 11
56242 Marienrachdorf
Germany
Mauelshagen@Sistina.com +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2003-07-10 17:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-10 17:07 [linux-lvm] pvmove and badsectors Newsmail
2003-07-10 17:21 ` Heinz J . Mauelshagen [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-01 6:11 Dieter Stueken
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=20030711001930.F23240@sistina.com \
--to=mauelshagen@sistina.com \
--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.