Mirrored LVs
Why cannot the mirrorlog be stored persistently in one or more LEs in the LV? Why the need for a seperate PV for this?
Since most servers I work with have two disks for the system, this force me to use md for mirroring, adding unneeded complexity for a simple mirror.
Signature · 6 lines
//Morten Torstensen //Email: [email protected] //IM: [email protected] I can't listen to that much Wagner. I start getting the urge to conquer Poland. -- Woody Allen
Quoted 2 lines · Morten Torstensen [[email protected]] wrote:
Why cannot the mirrorlog be stored persistently in one or more LEs in the LV? Why the need for a seperate PV for this?
For better redundancy...
Quoted 2 lines
Since most servers I work with have two disks for the system, this force me to use md for mirroring, adding unneeded complexity for a simple mirror.
Use "--alloc anywhere" to place the log LV on one of them when you create your mirror.
Quoted 4 lines
Quoted 2 lines
Why cannot the mirrorlog be stored persistently in one or more LEs in the LV? Why the need for a seperate PV for this?
For better redundancy...
In a LE it would be mirrored too and a copy would be in each mirror...
Quoted 2 lines
Use "--alloc anywhere" to place the log LV on one of them when you create your mirror.
Yes, but this will have the side effect of not ensuring separate PVs for the mirrored LV? An the mirror log would still not be mirrored, so in a failure situation you would still face data loss or force a fully resync of the mirror.
Signature · 2 lines
//Morten //[email protected]
2009/10/23 <[email protected]>:
Quoted 5 lines
Quoted 2 lines · Morten Torstensen [[email protected]] wrote:
Why cannot the mirrorlog be stored persistently in one or more LEs in the LV? Why the need for a seperate PV for this?
For better redundancy...
That is something I do not clearly see.
I am not going to enumarate em all, but mdadm stores the bitmap on each mirror leg, HP-UX LVM store the MWC on each mirror leg .... what makes them less redundant?
If we came to loose the LVM2 mirror third log device, what would happen (you already answered me on this topic that the mirror would stop).
I saw that there is some work being done to add a fourth log device to address this SPOF.
I think the current implementation, by trying to be the MOST redundant one, is getting too complex, or too expensive (each mirror device requiring 3 or 4 devices even if the 1 or 2 log devices are a few Megs) that one would, in the best case, use corelog instead, or partition the drives to mirror with 1 small log partition and the remaining space for data : both cases got off of the redundancy targeted.
Worst case one would use mdadm as underlying RAID.
Quoted 7 lines
Quoted 3 lines
Since most servers I work with have two disks for the system, this force me to use md for mirroring, adding unneeded complexity for a simple mirror.
Use "--alloc anywhere" to place the log LV on one of them when you create your mirror.
It still requires/creates a log LV ?
Quoted 6 lines
_______________________________________________
linux-lvm mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
Brem
Quoted 6 lines · Morten Torstensen [[email protected]] wrote:
Quoted 4 lines
Quoted 2 lines
Why cannot the mirrorlog be stored persistently in one or more LEs in the LV? Why the need for a seperate PV for this?
For better redundancy...
In a LE it would be mirrored too and a copy would be in each mirror...
That is not possible with the current LVM code. The log can't be a 'mirror' segment. Jonathan posted few patches to place the log on mirrored segment but the code is not in the upstream yet!
Quoted 7 lines
Quoted 2 lines
Use "--alloc anywhere" to place the log LV on one of them when you create your mirror.
Yes, but this will have the side effect of not ensuring separate PVs for the mirrored LV? An the mirror log would still not be mirrored, so in a failure situation you would still face data loss or force a fully resync of the mirror.
Agreed!
Specify ranges of physical extents at the end of the command line along with --alloc anywhere to get the layout of your choosing.
e.g. lvcreate ... /dev/sdb:0-2000 /dev/sdc:0-2000 /dev/sdd:0
(Sometimes you need to force a single-extent gap to make it do what you want, so sdb:0 sdb:2-2000 ...)
Alasdair
Quoted 8 lines · brem belguebli [[email protected]] wrote:
Quoted 4 lines
Quoted 2 lines
Why cannot the mirrorlog be stored persistently in one or more LEs in the LV? Why the need for a seperate PV for this?
For better redundancy...
That is something I do not clearly see.
I am not going to enumarate em all, but mdadm stores the bitmap on each mirror leg, HP-UX LVM store the MWC on each mirror leg .... what makes them less redundant?
They are NOT less redundant as they store the bit map on both the legs. Linux LVM can't place the log on both the legs at the moment so a leg that has your log goes down, then you don't have the log data at all.
I heard another reason for not placing the log on the same PV as your mirror leg -- performance. Since the logical block address for the log data and the leg data will be far apart, you may cause disk seeking back and forth. I don't know how much degradation in reality though. A non issue when we go to SSD...
Quoted 3 lines
If we came to loose the LVM2 mirror third log device, what would happen (you already answered me on this topic that the mirror would stop).
Currently either log failure or leg failure would transform your 'mirror' to a 'leaner' LV in linux. In other words, it can't handle transient device failures at all.
Quoted 2 lines
I saw that there is some work being done to add a fourth log device to address this SPOF.
Yes.
Quoted 7 lines
I think the current implementation, by trying to be the MOST redundant one, is getting too complex, or too expensive (each mirror device requiring 3 or 4 devices even if the 1 or 2 log devices are a few Megs) that one would, in the best case, use corelog instead, or partition the drives to mirror with 1 small log partition and the remaining space for data : both cases got off of the redundancy targeted.
I understand this as some missing functionality in Linux LVM rather than trying to make it "most redundant"...
Quoted 5 lines · On 23.10.2009 21:02, [email protected] wrote:
Quoted 1 line
In a LE it would be mirrored too and a copy would be in each mirror...
That is not possible with the current LVM code. The log can't be a 'mirror' segment. Jonathan posted few patches to place the log on mirrored segment but the code is not in the upstream yet!
So keep the map in the vgda, with a copy on each pv, or somewhere similar. It should just be a map of which LE is stale and doesn't have to be big anyway.
Maybe IBM should donate some LVM code to linux :)
Signature · 6 lines
//Morten Torstensen //Email: [email protected] //IM: [email protected] I can't listen to that much Wagner. I start getting the urge to conquer Poland. -- Woody Allen