首页
学习
活动
专区
圈层
工具
发布
社区首页 >问答首页 >缺少第二个逻辑区

缺少第二个逻辑区
EN

Server Fault用户
提问于 2019-05-07 02:54:43
回答 1查看 344关注 0票数 0

编辑1:只是为了澄清没有数据被写入到新的范围。我知道这一点,因为管理员在执行lv可扩展性之后就使用fdisk生成了文件系统,然后重新启动以使更改生效。重新启动时,新的块设备丢失了。

以下是sys管理员所做的工作。

添加了一个新的块设备,然后他将新的块设备添加到现有的卷组中,然后决定对卷组执行一个扩展:

代码语言:javascript
复制
vgextend archive1-retain /dev/sdd1
lvextend -l +31 /dev/archive1-retain/data

本质上是用新的物理卷扩展卷组。然后他重新启动并以某种方式失去了新的物理卷成员(sdd1)。但是,逻辑卷挂载,所有数据看起来都完好无损。

我确信,在意外添加第二个逻辑范围(sdd1)之后,实际上没有向卷组写入任何数据。下面是我剩下的内容,请注意第二个逻辑范围上的未知(缺失)设备,这是预期的:

代码语言:javascript
复制
archive1:~ # lvdisplay -am
  /dev/archive1-retain/data: read failed after 0 of 512 at 4400059711488: Input/output error
  /dev/archive1-retain/data: read failed after 0 of 512 at 4400059768832: Input/output error
  Couldn't find device with uuid W0btGW-Zp3R-yoAC-dkow-PabM-1Vri-3VUQo1.
  --- Logical volume ---
  LV Name                /dev/archive1-retain/data
  VG Name                archive1-retain
  LV UUID                fLG6tU-6tla-h49c-KOf2-LIAh-uIFy-wH0XB5
  LV Write Access        read/write
  LV Creation host, time archive1, 2015-06-12 11:50:30 -0700
  LV Status              available
  # open                 1
  LV Size                4.00 TiB
  Current LE             65566
  Segments               2
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     1024
  Block device           253:3

  --- Segments ---
  Logical extent 0 to 65534:
    Type                linear
    Physical volume     /dev/sda
    Physical extents    0 to 65534

  Logical extent 65535 to 65565:
    Type                linear
    Physical volume     unknown device
    Physical extents    0 to 30

这是我试过的。回首过去,我不应该使用武力,但幸运的是,当时的音量被装上了:

代码语言:javascript
复制
archive1:~ # vgreduce archive1-retain --removemissing
  /dev/archive1-retain/data: read failed after 0 of 512 at 4400059711488: Input/output error
  /dev/archive1-retain/data: read failed after 0 of 512 at 4400059768832: Input/output error
  Couldn't find device with uuid W0btGW-Zp3R-yoAC-dkow-PabM-1Vri-3VUQo1.
  WARNING: Partial LV data needs to be repaired or removed.
  There are still partial LVs in VG archive1-retain.
  To remove them unconditionally use: vgreduce --removemissing --force.
  Proceeding to remove empty missing PVs.

archive1:~ # vgreduce archive1-retain --removemissing --force
  /dev/archive1-retain/data: read failed after 0 of 512 at 4400059711488: Input/output error
  /dev/archive1-retain/data: read failed after 0 of 512 at 4400059768832: Input/output error
  Couldn't find device with uuid W0btGW-Zp3R-yoAC-dkow-PabM-1Vri-3VUQo1.
  Removing partial LV data.
  device-mapper: remove ioctl on  failed: Device or resource busy
  device-mapper: remove ioctl on  failed: Device or resource busy
  device-mapper: remove ioctl on  failed: Device or resource busy
  device-mapper: remove ioctl on  failed: Device or resource busy
  device-mapper: remove ioctl on  failed: Device or resource busy
  device-mapper: remove ioctl on  failed: Device or resource busy
  device-mapper: remove ioctl on  failed: Device or resource busy
  device-mapper: remove ioctl on  failed: Device or resource busy
  device-mapper: remove ioctl on  failed: Device or resource busy
  device-mapper: remove ioctl on  failed: Device or resource busy
  device-mapper: remove ioctl on  failed: Device or resource busy
  device-mapper: remove ioctl on  failed: Device or resource busy
  device-mapper: remove ioctl on  failed: Device or resource busy
  device-mapper: remove ioctl on  failed: Device or resource busy
  device-mapper: remove ioctl on  failed: Device or resource busy
  device-mapper: remove ioctl on  failed: Device or resource busy
  device-mapper: remove ioctl on  failed: Device or resource busy
  Unable to deactivate archive1--retain-data (253:3)
  Unable to deactivate logical volume "data"

一些补充信息:

代码语言:javascript
复制
archive1:~ # lsblk
NAME                                     MAJ:MIN RM   SIZE RO MOUNTPOINT
xvdb                                     202:16   0   249G  0
└─xvdb1                                  202:17   0   249G  0 /var/log/retain-tomcat7
xvda                                     202:0    0    80G  0
├─xvda1                                  202:1    0     2G  0 [SWAP]
└─xvda2                                  202:2    0    78G  0 /
sda                                        8:0    0     4T  0
└─archive1--retain-data (dm-3)           253:3    0     4T  0 /var/opt/beginfinite/retain
sdc                                        8:32   0   750G  0
└─gwsystem-data (dm-0)                   253:0    0   750G  0 /gwsystem
sdb                                        8:16   0     1T  0
└─archive1--sql-data (dm-1)              253:1    0  1024G  0 /var/lib/mysql
archive1--retain-data-missing_1_0 (dm-2) 253:2    0     2G  0
└─archive1--retain-data (dm-3)           253:3    0     4T  0 /var/opt/beginfinite/retain

逻辑卷装入并可用:

代码语言:javascript
复制
archive1:~ # df -h
Filesystem                         Size  Used Avail Use% Mounted on
/dev/xvda2                          77G   35G   41G  46% /
udev                                19G  120K   19G   1% /dev
tmpfs                               19G     0   19G   0% /dev/shm
/dev/xvdb1                         246G   62G  172G  27% /var/log/retain-tomcat7
/dev/mapper/gwsystem-data          739G  590G  112G  85% /gwsystem
/dev/mapper/archive1--sql-data     1.0T  330G  695G  33% /var/lib/mysql
/dev/mapper/archive1--retain-data  4.0T  2.9T  1.2T  73% /var/opt/beginfinite/retain
EN

回答 1

Server Fault用户

发布于 2019-05-07 15:49:58

在卸载FS之后,我会这样做:

步骤1-用于标识文件的vgcfgrestore -l具有正确的lvm元数据( sdd1扩展名之前的元数据)

步骤2-实际还原旧的lvm元数据的vgcfgrestore -f filename

票数 0
EN
页面原文内容由Server Fault提供。腾讯云小微IT领域专用引擎提供翻译支持
原文链接:

https://serverfault.com/questions/966127

复制
相关文章

相似问题

领券
问题归档专栏文章快讯文章归档关键词归档开发者手册归档开发者手册 Section 归档