archive mirror
 help / color / mirror / Atom feed
From: Stuart D Gathman <>
To: LVM general discussion and development <>
Subject: Re: [linux-lvm] Bypassing LVM Restrictions - RAID6 With Less Than 5 Disks
Date: Sun, 8 May 2022 09:25:54 -0400 (EDT)	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: text/plain, Size: 947 bytes --]

On Sat, 7 May 2022, Alex Lieflander wrote:

> I don’t trust the hardware I’m running on very much, but it’s all I have to work with at the moment; it’s important that the array is resilient to *any* (and multiple) single chunk corruptions because such corruptions are likely to happen in the future.
> For the last several months I’ve periodically been seeing (DM-Integrity) checksum mismatch warnings at various locations on all of my disks. I stopped using a few SATA ports that were explicitly throwing SATA errors, but I suspect that the remaining connections are unpredictably (albeit infrequently) corrupting data in ways that are more difficult to detect.

Sounds like a *great* test bed for software data integrity tools.  Don't
throw that system away when you get a more reliable one!

That sounds like a situation that btrfs with multiple copies could
handle.  Use a beefier checksum than the default crc-32 also.

[-- Attachment #2: Type: text/plain, Size: 202 bytes --]

linux-lvm mailing list
read the LVM HOW-TO at

  reply	other threads:[~2022-05-08 14:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-27 17:11 [linux-lvm] Bypassing LVM Restrictions - RAID6 With Less Than 5 Disks Alex Lieflander
2022-05-02  0:36 ` John Stoffel
2022-05-02 19:22   ` Alex Lieflander
2022-05-02 21:54     ` John Stoffel
2022-05-07  3:33       ` Alex Lieflander
2022-05-07 20:41         ` Stuart D Gathman
2022-05-07 23:14           ` Alex Lieflander
2022-05-08 13:25             ` Stuart D Gathman [this message]
2022-05-09  0:18             ` John Stoffel

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).