
简述
大家在生产环境一般多使用LVM来管理逻辑卷,因为它会在物理存储上创建一个提取层,以便我们创建逻辑存储卷,这比直接使用物理存储的方式具有更大的灵活性。我们比较熟悉的使用场景为:
-
灵活的容量
当使用逻辑卷时,文件系统可在多个磁盘间扩展,将磁盘和分区集合成一个逻辑卷。
-
重新调整存储池的大小
使用简单的软件命令扩展逻辑卷或减小逻辑卷的大小,而无需重新格式化和重新分区基础磁盘设备。
但对于LVM还可以用作磁盘镜像可能不了解,这类似于Raid1,即多块磁盘互相同步备份,可以有效避免数据丢失的尴尬。
下面我们就通过实战来了解下。
1.新建磁盘分区
新建4个分区/dev/sdb1,/dev/sdb2,/dev/sdb3,/dev/sdb4,如:
Disk /dev/sdb: 1999.8 GB, 1999844147200 bytes
255 heads, 63 sectors/track, 243133 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdb1 1 374 3004123+ 83 Linux
/dev/sdb2 375 748 3004155 83 Linux
/dev/sdb3 749 1122 3004155 83 Linux
/dev/sdb4 1123 1496 3004155 83 Linux
其中:
-
/dev/sdb1、/dev/sdb2用作数据磁盘 -
/dev/sdb2作为/dev/sdb1的镜像 -
/dev/sdb3作为日志 -
/dev/sdb4作为备用盘
当sdb1或sdb2损害时备用,类似于raid5中的热备盘。
2.创建pv和vg
pvcreate /dev/sdb1
pvcreate /dev/sdb2
pvcreate /dev/sdb3
pvcreate /dev/sdb4
vgcreate vg_test /dev/sdb1 /dev/sdb2 /dev/sdb3
其中:/dev/sdb4暂未使用,待备用
3.创建包含镜像功能的逻辑卷(mirror_test)
[root@localhost ~]# lvcreate -L 2.8G -m1 -n mirror_test vg_test /dev/sdb1 /dev/sdb2 /dev/sdb3
Rounding up size to full physical extent 2.80 GB
Logical volume "mirror_test" created
[root@localhost ~]# lvs -a -o +devices
LV VG Attr LSize Origin Snap% Move Log Copy% Convert Devices
mirror_test vg_test mwi-a- 2.80G mirror_test_mlog 24.27 mirror_test_mimage_0(0),mirror_test_mimage_1(0)
[mirror_test_mimage_0] vg_test Iwi-ao 2.80G /dev/sdb1(0)
[mirror_test_mimage_1] vg_test Iwi-ao 2.80G /dev/sdb2(0)
[mirror_test_mlog] vg_test lwi-ao 4.00M /dev/sdb3(0)
其中:
-
-m1参数为创建镜像; -
-L参数为设定镜像卷的大小为2.8G; -
-n参数为指定镜像名称;
这个镜像包括三部分:sdb1和sdb2位数据卷和镜像卷,sdb3为日志卷。
查看镜像状态:
[root@localhost ~]# lvdisplay /dev/vg_test/mirror_test
--- Logical volume ---
LV Name /dev/vg_test/mirror_test
VG Name vg_test
LV UUID RUamnD-nYCt-D9yp-cNdX-ix1y-r9P9-wenSjb
LV Write Access read/write
LV Status available
# open 0
LV Size 2.80 GB
Current LE 717
Mirrored volumes 2
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:8
4.格式化挂载
[root@localhost ~]# mkfs.ext3 /dev/vg_test/mirror_test
[root@localhost ~]# mkdir -p /test
[root@localhost ~]# mount /dev/vg_test/mirror_test /test
5.测试
-
创建测试文件
[root@localhost ~]# cd /test
[root@localhost test]# echo "lvm mirror test" > test.txt
[root@localhost test]# cat test.txt
lvm mirror test
-
模拟对/dev/sdb2进行破坏
[root@localhost ~]# dd if=/dev/zero of=/dev/sdb2 count=10 bs=1M
10+0 records in
10+0 records out
10485760 bytes (10 MB) copied, 0.008574 seconds, 1.2 GB/s
[root@localhost ~]# lvs -a -o +devices
Couldn't find device with uuid z74R0l-ZLUV-X6TS-QrpF-nXDZ-gc74-UvwGC0.
LV VG Attr LSize Origin Snap% Move Log Copy% Convert Devices
mirror_test vg_test mwi-ao 2.80G mirror_test_mlog 100.00 mirror_test_mimage_0(0),mirror_test_mimage_1(0)
[mirror_test_mimage_0] vg_test iwi-ao 2.80G /dev/sdb1(0)
[mirror_test_mimage_1] vg_test iwi-ao 2.80G unknown device(0)
[mirror_test_mlog] vg_test lwi-ao 4.00M /dev/sdb3(0)
此时查看状态发现/dev/sdb2处于“unknown device(0)”状态。
[root@localhost ~]# lvscan
Couldn't find device with uuid z74R0l-ZLUV-X6TS-QrpF-nXDZ-gc74-UvwGC0.
ACTIVE '/dev/vg_test/mirror_test' [2.80 GB] inherit
-
重新挂载确认数据可读取
[root@localhost ~]# umount /test
[root@localhost test]# cd
[root@localhost ~]# mount /dev/vg_test/mirror_test /test
[root@localhost ~]# cat /test/test.txt
lvs mirror test
-
将坏掉的设备删除
[root@localhost ~]# vgreduce --removemissing --force vg_test
Couldn't find device with uuid z74R0l-ZLUV-X6TS-QrpF-nXDZ-gc74-UvwGC0.
WARNING: Bad device removed from mirror volume, vg_test/mirror_test
WARNING: Mirror volume, vg_test/mirror_test converted to linear due to device failure.
Wrote out consistent volume group vg_test
移除后vgdisplay /dev/vg_test发现mirrored volumes选项没有了;并且由于sdb2的失效,镜像mirror_test也已经有mirror模式转变成线性模式,如果恢复我们需要用到lvconvert命令来恢复。
-
镜像数据恢复
使用备份盘/dev/sdb4进行数据恢复
[root@localhost ~]# vgextend vg_test /dev/sdb4
Volume group "vg_test" successfully extended
[root@localhost ~]# lvconvert -m1 /dev/vg_test/mirror_test /dev/sdb1 /dev/sdb4 /dev/sdb3
vg_test/mirror_test: Converted: 0.0%
vg_test/mirror_test: Converted: 20.8%
vg_test/mirror_test: Converted: 40.4%
vg_test/mirror_test: Converted: 60.1%
vg_test/mirror_test: Converted: 79.4%
vg_test/mirror_test: Converted: 99.2%
vg_test/mirror_test: Converted: 100.0%
ok,恢复完成,我们来查看下状态:
[root@localhost ~]# lvdisplay /dev/vg_test
--- Logical volume ---
LV Name /dev/vg_test/mirror_test
VG Name vg_test
LV UUID RUamnD-nYCt-D9yp-cNdX-ix1y-r9P9-wenSjb
LV Write Access read/write
LV Status available
# open 1
LV Size 2.80 GB
Current LE 717
Mirrored volumes 2
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:8
[root@localhost ~]# cat /test/test.txt
lvs mirror test
[root@localhost ~]# lvs -a -o +devices
LV VG Attr LSize Origin Snap% Move Log Copy% Convert Devices
mirror_test vg_test mwi-ao 2.80G mirror_test_mlog 100.00 mirror_test_mimage_0(0),mirror_test_mimage_1(0)
[mirror_test_mimage_0] vg_test iwi-ao 2.80G /dev/sdb1(0)
[mirror_test_mimage_1] vg_test iwi-ao 2.80G /dev/sdb4(0)
[mirror_test_mlog] vg_test lwi-ao 4.00M /dev/sdb3(0)
经过数据恢复,镜像卷由原来的sdb2转变为sdb4。
总结
在实际的生产环境,服务器基本都有不同级别的RAID,因此LVM的镜像卷使用场景很少。但如果你正面临以下情况:
-
磁盘数量比较吃紧,但磁盘空间需求大 -
服务器仅支持RAID1,空间使用率减半 -
对性能要求不高,但要保证一定的数据冗余
那么我们此时可以考虑使用LVM镜像卷来解决防止数据丢失的问题了。
原文始发于微信公众号(运维贼船):Linux骚操作:LVM逻辑卷实现磁盘镜像
版权声明:本文内容由互联网用户自发贡献,该文观点仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 举报,一经查实,本站将立刻删除。
文章由极客之音整理,本文链接:https://www.bmabk.com/index.php/post/176808.html