From: brem belguebli <brem.belguebli@gmail.com>
To: lvm-devel@redhat.com
Subject: [BUG-REPORT] mirror legs in the same PV with --alloc anywhere
Date: Thu, 06 May 2010 03:44:29 +0200 [thread overview]
Message-ID: <1273110269.2544.3.camel@localhost> (raw)
In-Reply-To: <87fx26zba5.fsf@twilight.int.mornfall.net.>
Hi Petr,
On Wed, 2010-05-05 at 16:13 +0200, Petr Rockai wrote:
> Takahiro Yasui <tyasui@redhat.com> writes:
> > On 04/23/10 17:09, brem belguebli wrote:
> >> On Fri, 2010-04-23 at 14:54 -0400, Takahiro Yasui wrote:
> >>> On 04/23/10 12:01, brem belguebli wrote:
> >>>> I've read in the RHEL 5.5 technical datasheet that the shipped LVM
> >>>> version 2.02.56 was alraedy capable of mirrored log.
> >>>
> >>> As far as I see lvm2 code, I don't think lvm2 in RHEL5.5 has
> >>> mirrored log feature. I'm not sure which document you referred to.
> >>> Could you tell me the exact name of "RHEL 5.5 technical datasheet"?
> >>
> >> http://www.redhat.com/f/pdf/rhel/RHEL_5_5_TechOverview_wp_web.pdf
> >> page 4, LVM
> >>
> >> " LVM ??? the Logical Volume Management storage suite has been augmented
> >> to provide hot sparing
> >> for mirror journals, enabling automatic replacement or removal of
> >> failed logging devices.
> >> "
> >
> > Thanks for the information, but I am not sure if this sentence is
> > telling 'mirrored log.' What I can say is the lvm2-2.02.56-8 doesn't
> > have 'mirrored log' feature. I hope someone may give you a explanation...
> For all I can tell, this means that if the log fails, it is
> automatically replaced when there's a hotspare. Which is true, but it
> does not imply mirroring.
>
I have never seen this documented anywhere, could you provide any link
to this hotspare based log replacement?
> Yours,
> Petr.
>
Thanks
Brem
> --
> lvm-devel mailing list
> lvm-devel at redhat.com
> https://www.redhat.com/mailman/listinfo/lvm-devel
next prev parent reply other threads:[~2010-05-06 1:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-15 21:13 [BUG-REPORT] mirror legs in the same PV with --alloc anywhere Takahiro Yasui
2010-04-15 22:03 ` Alasdair G Kergon
2010-04-16 15:19 ` Takahiro Yasui
2010-04-16 16:07 ` Alasdair G Kergon
2010-04-16 18:22 ` Takahiro Yasui
2010-04-16 18:42 ` Alasdair G Kergon
2010-04-16 18:50 ` malahal
2010-04-16 19:06 ` Alasdair G Kergon
2010-04-17 9:15 ` brem belguebli
2010-04-21 15:18 ` Takahiro Yasui
2010-04-21 17:36 ` brem belguebli
2010-04-23 16:01 ` brem belguebli
2010-04-23 18:54 ` Takahiro Yasui
2010-04-23 21:09 ` brem belguebli
2010-04-23 19:49 ` Takahiro Yasui
2010-05-05 14:13 ` Petr Rockai
2010-05-05 14:35 ` Malahal Naineni
2010-05-06 1:44 ` brem belguebli [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-04-23 20:01 Josh Moyer
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=1273110269.2544.3.camel@localhost \
--to=brem.belguebli@gmail.com \
--cc=lvm-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.