blocks|key|1063701|text|我从未使用过LVM镜像，但根据我对LVM的了解，您所挖掘的信息似乎是合理的。我会坚持MD+RAID-1，我自己。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|entityMap^0^^$0|@$1|2|3|4|5|6|7|C|8|@]|9|@]|A|$]]]|B|$]]

I've never used LVM mirroring, but the info you've dug up seems reasonable from what I know of LVM. I'd stick with MD RAID-1, myself.

blocks|key|5164400|text|LVM镜像用于将逻辑卷复制到不同的物理卷。它本质上意味着“将数据移动到不同的磁盘”。然后，镜像被打破，数据的旧位置被释放，以供使用；而在新的位置使用现有的数据。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5164401|RAID镜像是用来防止单驱动器硬件故障的。它的本质是“防止数据丢失，如果磁盘死了”。|5164402|为了您的目的，坚持在LVM镜像上使用RAID。|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|H|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|I|8|@]|9|@]|A|$]]]|F|$]]

LVM mirrors are for replication of a logical volume to a different physical volume. It's essentially meant to "move the data to a different disk". The mirror is then broken and the old location of the data freed for use; the existing data is utilized at the new location instead.

RAID mirrors are for providing a safeguard against single-drive hardware failures. It's essentially meant to "keep your data from being lost if a disk dies".

Stick with RAID over LVM mirroring for your purposes.

blocks|key|5164575|text|新版本的LVM可以使用来自MD的相同的raid实现。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5164576|浏览历史，raid4+4/5/6似乎在2.6.38和raid0/1之间出现在内核中，有时出现在两者之间。|5164577|还支持RHEL6.1(raid0+0/raid0+1)和RHEL6.3(raid0+4/5/6)+https://access.redhat.com/site/documentation/en-US/Red_帽子_企业_Linux/6/html/逻辑_音量_经理_行政/LVM_overview.html|offset|length|entityMap|0|LINK|mutability|MUTABLE|url|https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Logical_Volume_Manager_Administration/LVM_overview.html^0|0|0|1D|2V|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Q|8|@]|9|@$F|R|G|S|1|T]]|A|$]]]|H|$I|$5|J|K|L|A|$M|N]]]]

New versions of LVM can use the same raid implementations from MD.

Browsing the history, raid4/5/6 seems to appeared in the kernel in 2.6.38 and raid0/1 sometimes between that and 3.1

Supported also from RHEL 6.1 (raid0/raid1) and from RHEL 6.3 (raid4/5/6)
<a href="https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Logical_Volume_Manager_Administration/LVM_overview.html" rel="noreferrer">https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Logical_Volume_Manager_Administration/LVM_overview.html</a>

blocks|key|5164461|text|如果您希望在断电时尽量减少数据丢失的可能性，则始终需要禁用写缓存。如果您有md+RAID、LVM，或者什么都没有，这并不重要。您的驱动器可以在高速缓存中有16-64MB在现代设备上，它将解散。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5164462|除非你把速度看得比正确性更高，否则我会在驱动器上关闭缓存。|5164463|屏障是试图提高数据进入磁盘的机会的核心技术。直到2.6.29+LVMs忽略了他们。现在，LVM授予障碍(当且仅当你有一个线性目标和一个新的足够的内核)，所以如果你想要LVM的灵活性和屏障支持，你最好的选择是障碍上的md+RAID。|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|H|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|I|8|@]|9|@]|A|$]]]|F|$]]

Write cache disabling is always required if you want to minimise the chances of data loss when you have a power cut. It doesn't matter if you have md RAID, LVM, or nothing at all. Your drive can have 16 - 64 MB in the cache on a modern device, and it will dissapear. 

Unless you value speed over correctness, I'd switch write caching off on drives.

Barriers are a kernel techniue to try and improve the chances of data getting to disk. Up until 2.6.29 LVMs ignored them. Now LVM honours barriers (if and only if you have a linear target and a new enough kernel) so if you want the flexibility of LVM and barrier support your best bet is barrier-on-md RAID.

blocks|key|1063717|text|一个实际需要第三个磁盘来存储LVM日志。|type|blockquote|depth|inlineStyleRanges|entityRanges|data|1063718|在一个设置中，我将磁盘划分为一个主物理卷和另一个用于LVM日志的微小物理卷。如果我丢失了那个磁盘，我当然会丢失镜像日志，但这是可以的，因为当卷退化为未镜像时，它将不再需要日志。|unstyled|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|G|8|@]|9|@]|A|$]]]|E|$]]

<blockquote>
 one actually requires a 3rd disk for storing the LVM log
</blockquote>

In one setup I partitioned a disk into one main physical volume and another tiny physical volume for the LVM log. If I ever lost that disk I would of course lose the mirror log, but that's OK because when the volume degraded to unmirrored it would no longer need the log.

Having learned a bit about LVM mirroring, I thought about replacing the current RAID-1 scheme I'm using to gain some flexibility.
Problem is that according to what I found on the Internet, LVM is:
<ol>
<li>Slower than RAID-1, at least in reading (only single volume being used for reading).</li>
<li>Unreliable on power interrupts (requires disk cache disabling for prevention of data loss).</li>
</ol>
<a href="http://www.joshbryan.com/blog/2008/01/02/lvm2-mirrors-vs-md-raid-1/" rel="nofollow noreferrer">http://www.joshbryan.com/blog/2008/01/02/lvm2-mirrors-vs-md-raid-1/</a>
Also it seems, at least to several setup guides I read (<a href="http://www.tcpdump.com/kb/os/linux/lvm-mirroring/intro.html" rel="nofollow noreferrer">http://www.tcpdump.com/kb/os/linux/lvm-mirroring/intro.html</a>), that one actually requires a 3rd disk for storing the LVM log. This makes the setup completely unusable on 2 disks installations, and lowers the amount of used mirror disks on higher amount of disks.
Can anyone comment the above facts, and let me know his experience of using LVM mirroring?

LVM mirroring VS RAID1

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

在学习了一些关于LVM镜像的知识之后，我考虑替换当前的RAID-1方案，以获得一些灵活性。问题是，根据我在互联网上的发现，LVM是：比RAID-1慢，至少在读取方面是这样(只使用单个卷进行读取)。电源中断不可靠(需要禁用磁盘缓存以防止数据丢失)。http://www.joshbryan.com/blog/2008/01/02/lvm2-mirrors-vs-md-raid-1/而且，至少对我读过的

问LVM镜像与RAID1
EN

回答 5

Server Fault用户

Server Fault用户

Server Fault用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问LVM镜像与RAID1EN

回答 5

Server Fault用户

Server Fault用户

Server Fault用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问LVM镜像与RAID1
EN