From: Roger Heflin <rogerheflin@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] bug? shrink lv by specifying pv extent to be removed does not behave as expected
Date: Tue, 11 Apr 2023 12:05:16 -0500 [thread overview]
Message-ID: <CAAMCDecPPh48=u-iECpf9YKUt4YA8KtkiMbwLEn+0UOkgZCN_Q@mail.gmail.com> (raw)
In-Reply-To: <1043528017.520337.1681071486811@mail.yahoo.com>
On Tue, Apr 11, 2023 at 1:44 AM matthew patton <pattonme@yahoo.com> wrote:
>
> > my plan is to scan a disk for usable sectors and map the logical volume
> > around the broken sectors.
>
> 1977 called, they'd like their non-self-correcting HD controller implementations back.
>
> From a real-world perspective there is ZERO (more like negative) utility to this exercise. Controllers remap blocks all on their own and the so-called geometry is entirely fictitious anyway. From a script/program "because I want to" perspective you could leave LVM entirely out of it and just use a file with arbitrary offsets scribbled with a "bad" signature.
The disks should be able to remap sectors all on their own. Few
(none?) of the sata/sas non-raid controllers I know of do any disk
level remapping. Some of the hardware raid ones may. As implemented
the decision to remap (in the disk) seems to not always work
correctly. I have a number of disks over several generations that
will refuse to re-map what is a clearly bad sector (re-writes to a
given sector succeed, and then immediate re-reads fail and on another
re-write succeed again and immediately fail on re-read, but do not get
remapped.
So given this, if one does not want to be replacing the given disks
there is room for software level remaps still to use the significant
number of disks with limited bad sectors on them.
_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
next prev parent reply other threads:[~2023-04-11 17:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1043528017.520337.1681071486811.ref@mail.yahoo.com>
2023-04-09 20:18 ` [linux-lvm] bug? shrink lv by specifying pv extent to be removed does not behave as expected matthew patton
2023-04-11 7:14 ` Roland
2023-04-12 9:24 ` Roberto Fastec
2023-04-12 9:28 ` Roberto Fastec
2023-04-11 17:05 ` Roger Heflin [this message]
2023-04-09 15:05 Roland
2023-04-09 17:32 ` Roger Heflin
2023-04-09 18:21 ` Roland
2023-04-09 18:53 ` Roger Heflin
2023-04-09 22:04 ` Roland
2023-04-09 23:50 ` Stuart D Gathman
2023-04-12 10:20 ` Zdenek Kabelac
2023-04-12 11:51 ` Roberto Fastec
2023-04-12 12:37 ` Roland
2023-04-12 13:16 ` Zdenek Kabelac
2023-04-12 13:53 ` Roberto Fastec
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='CAAMCDecPPh48=u-iECpf9YKUt4YA8KtkiMbwLEn+0UOkgZCN_Q@mail.gmail.com' \
--to=rogerheflin@gmail.com \
--cc=linux-lvm@redhat.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).