linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: starlight@binnacle.cx
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] cmp of inactive mirrored LV fails
Date: Fri, 02 Dec 2011 16:27:24 -0500	[thread overview]
Message-ID: <6.2.5.6.2.20111202162035.063ebe80@binnacle.cx> (raw)
In-Reply-To: <alpine.LRH.2.00.1112021553440.5337@bmsred.bmsi.com>

At 04:01 PM 12/2/2011 -0500, Stuart D. Gathman wrote:
>Both MD and LVM support
>DISCARD, and discarded blocks are not necessarily synced
>between mirror legs.

Googled it--seems like DISCARD (aka TRIM) is about
telling SSDs that blocks are no longer in use so
that the SSDs can optimally release tracking of the
storage.  I can see how this might result
in random data appearing in the "discarded"
region.  I don't see how the 'mdadm' mirror
check will cope with that result unless SSDs
return zeros or some other constant value when
TRIMed blocks are subsequently read.

However this is a hard-drive scenario--no SSDs.
It would seem that hard drives generally will
either ignore TRIM operations or via drive
flags inform the kernel to not attempt them.

So this leaves me with two LVs where it's
clear that LVM mirroring failed to maintain
synchronization at some point in the last
year or two.

Also based on this thread
http://www.issociate.de/board/post/507507/SSD_-_TRIM_command.html
it would seem TRIM is very much a bleeding-edge
feature.  Unlikely it appears in the CentOS 5.7
kernel in use on the affected system.

So I'm sticking with "turkey" as the appropriate
characterization of LVM mirroring.

  parent reply	other threads:[~2011-12-02 21:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-02 17:20 [linux-lvm] cmp of inactive mirrored LV fails starlight
2011-12-02 18:34 ` starlight
2011-12-02 21:01   ` Stuart D. Gathman
2011-12-02 21:14     ` starlight
2011-12-02 21:54       ` Stuart D. Gathman
2011-12-02 22:02         ` starlight
2011-12-02 21:27     ` starlight [this message]
2011-12-02 21:47     ` starlight
2011-12-02 23:57       ` Ron Johnson
2011-12-03  3:44       ` starlight
2012-01-02 13:38   ` Lars Ellenberg

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=6.2.5.6.2.20111202162035.063ebe80@binnacle.cx \
    --to=starlight@binnacle.cx \
    --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).