All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heinz Mauelshagen <heinzm@redhat.com>
To: dm-devel@redhat.com
Subject: Re: dm_mirror/dm_raid1 limitations ?.
Date: Mon, 26 Jan 2015 15:16:47 +0100	[thread overview]
Message-ID: <54C64C4F.6090601@redhat.com> (raw)
In-Reply-To: <4d982ea8-3769-46d2-ba73-2d1525faa63b@default>


[-- Attachment #1.1: Type: text/plain, Size: 1029 bytes --]


On 01/26/2015 02:51 PM, Suresh Babu Kandukuru wrote:
>
> Use case is : Two luns are mapped from storage array to linux host 
> which are in same SAN fabric . we want to create a mirror on the linux 
> host with these two luns and let  host use that mirror lun .  basic 
> tests suggest that dm_mirror working fine . when we have any 
> intermittent path issues with between host and san array , host i/o 
> just freeze , never returns back even after the path is online.
>

Hard to tell what's happening without any kernel log.

> Is dm_mirror viable solution here  ?. Can you point me any link which 
> gives the limitations of dm_mirror ? . another alternate solutions you 
> propose here ?. Thanks in advance .
>

We've switched the default away from "mirror" to "raid1" in order to 
take advantage of th MD runtime.
Have you tested  "lvcreate --type raid1 ..." yet?
Please do.

Regards,
Heinz

> Thanks
>
> /Suresh
>
>
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel


[-- Attachment #1.2: Type: text/html, Size: 3715 bytes --]

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



  reply	other threads:[~2015-01-26 14:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-26 13:51 dm_mirror/dm_raid1 limitations ? Suresh Babu Kandukuru
2015-01-26 14:16 ` Heinz Mauelshagen [this message]
2015-01-26 15:34   ` suresh.babu.kandukuru
2015-01-26 19:01     ` Marian Csontos
2015-01-28  4:03       ` Suresh Babu Kandukuru

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=54C64C4F.6090601@redhat.com \
    --to=heinzm@redhat.com \
    --cc=dm-devel@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 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.