我有一個SLES 11.2 PPC(3.0.58-0.6.6-ppc64)系統,它失去了對其卷組的跟蹤(包含數據并不重要的LV,但回來會很好).磁盤通過SAN的兩條光纖路徑連接.

當我在上周五計劃停電之前重新啟動它時,問題就出現了.我沒有時間進行故障排除再次將其關閉.該卷組先前已成功使用了大約兩年.

vgscan和pvscan什么都不返回：

# pvscan -vP

Partial mode. Incomplete logical volumes will be processed.

Wiping cache of LVM-capable devices

Wiping internal VG cache

Walking through all physical volumes

No matching physical volumes found

# vgscan -vP

Partial mode. Incomplete logical volumes will be processed.

Wiping cache of LVM-capable devices

Wiping internal VG cache

Reading all physical volumes. This may take a while...

Finding all volume groups

No volume groups found

vgcfgrestore報告無法找到PV：

# vgcfgrestore vgclients

Couldn't find device with uuid PyKfIa-cCs9-gBoh-Qb50-yOw4-dHQw-N1YELU.

Couldn't find device with uuid FXfSAO-P9hO-Dgtl-0Ihf-x2jX-TnHU-kSqUA2.

Cannot restore Volume Group vgclients with 2 PVs marked as missing.

Restore failed.

然而,blkid可以找到那些UUID：

# blkid -t UUID=PyKfIa-cCs9-gBoh-Qb50-yOw4-dHQw-N1YELU

/dev/mapper/3600a0b800029df24000011084db97741: UUID="PyKfIa-cCs9-gBoh-Qb50-yOw4-dHQw-N1YELU" TYPE="LVM2_member"

/dev/sdl: UUID="PyKfIa-cCs9-gBoh-Qb50-yOw4-dHQw-N1YELU" TYPE="LVM2_member"

/dev/sdw: UUID="PyKfIa-cCs9-gBoh-Qb50-yOw4-dHQw-N1YELU" TYPE="LVM2_member"

# blkid -t UUID=FXfSAO-P9hO-Dgtl-0Ihf-x2jX-TnHU-kSqUA2

/dev/mapper/3600a0b800029df24000017ae4f45f30b: UUID="FXfSAO-P9hO-Dgtl-0Ihf-x2jX-TnHU-kSqUA2" TYPE="LVM2_member"

/dev/sdg: UUID="FXfSAO-P9hO-Dgtl-0Ihf-x2jX-TnHU-kSqUA2" TYPE="LVM2_member"

/dev/sdr: UUID="FXfSAO-P9hO-Dgtl-0Ihf-x2jX-TnHU-kSqUA2" TYPE="LVM2_member"

/ etc / lvm / backup / vgclients具有所有正確的信息,并沒有說PV缺失：

# egrep "(N1YELU|kSqUA2|dm-|ALLOC)" /etc/lvm/backup/vgclients

id = "PyKfIa-cCs9-gBoh-Qb50-yOw4-dHQw-N1YELU"

device = "/dev/dm-7" # Hint only

status = ["ALLOCATABLE"]

id = "FXfSAO-P9hO-Dgtl-0Ihf-x2jX-TnHU-kSqUA2"

device = "/dev/dm-12" # Hint only

status = ["ALLOCATABLE"]

我在SAN上確認了該服務器上LVM專用(和命名)的卷,并且標識符(以f30b或7741結尾)在SAN和服務器上匹配：

# multipath -ll | egrep -A5 "(f30b|7741)"

3600a0b800029df24000017ae4f45f30b dm-7 IBM,1814 FAStT

size=575G features='1 queue_if_no_path' hwhandler='1 rdac' wp=rw

|-+- policy='round-robin 0' prio=6 status=active

| `- 6:0:0:1 sdr 65:16 active ready running

`-+- policy='round-robin 0' prio=1 status=enabled

`- 5:0:0:1 sdg 8:96 active ghost running

--

3600a0b800029df24000011084db97741 dm-12 IBM,1814 FAStT

size=834G features='1 queue_if_no_path' hwhandler='1 rdac' wp=rw

|-+- policy='round-robin 0' prio=6 status=active

| `- 5:0:0:7 sdl 8:176 active ready running

`-+- policy='round-robin 0' prio=1 status=enabled

`- 6:0:0:7 sdw 65:96 active ghost running

兩個設備都沒有分區表(按設計)：

# fdisk -l /dev/dm-7 /dev/dm-12 | grep table

Disk /dev/dm-7 doesn't contain a valid partition table

Disk /dev/dm-12 doesn't contain a valid partition table

我可以直接從設備上讀取：

# dd if=/dev/dm-7 of=/tmp/a bs=1024 count=1

1+0 records in

1+0 records out

1024 bytes (1.0 kB) copied, 0.00121051 s, 846 kB/s

# strings /tmp/a

LABELONE

LVM2 001FXfSAOP9hODgtl0Ihfx2jXTnHUkSqUA2

我嘗試重新啟動并刪除sd(r | g | l | w)和dm-(7 | 12)并重新掃描,但沒有效果.

我嘗試使用備份值重新創建PV,但它仍然說它找不到它們.

# pvcreate --uuid "PyKfIa-cCs9-gBoh-Qb50-yOw4-dHQw-N1YELU" --restorefile /etc/lvm/backup/vgclients /dev/mapper/3600a0b800029df24000011084db97741 -t

Test mode: Metadata will NOT be updated and volumes will not be (de)activated.

Couldn't find device with uuid PyKfIa-cCs9-gBoh-Qb50-yOw4-dHQw-N1YELU.

Couldn't find device with uuid FXfSAO-P9hO-Dgtl-0Ihf-x2jX-TnHU-kSqUA2.

Device /dev/mapper/3600a0b800029df24000011084db97741 not found (or ignored by filtering).

這是我的lvm.conf,雖然據我所知,我所做的唯一改變是增加日志級別：

# egrep -v "^( *#|$)" /etc/lvm/lvm.conf

devices {

dir = "/dev"

scan = [ "/dev" ]

preferred_names = [ ]

filter = [ "a|^/dev/sda$|", "r/.*/" ]

cache = "/etc/lvm/.cache"

write_cache_state = 1

sysfs_scan = 1

md_component_detection = 1

ignore_suspended_devices = 0

}

log {

verbose = 0

syslog = 1

overwrite = 0

level = 2

indent = 1

command_names = 0

prefix = " "

}

backup {

backup = 1

backup_dir = "/etc/lvm/backup"

archive = 1

archive_dir = "/etc/lvm/archive"

retain_min = 10

retain_days = 30

}

shell {

history_size = 100

}

global {

umask = 077

test = 0

units = "h"

activation = 1

proc = "/proc"

locking_type = 3

fallback_to_clustered_locking = 1

fallback_to_local_locking = 1

locking_dir = "/var/run/lvm/lock"

}

activation {

missing_stripe_filler = "/dev/ioerror"

reserved_stack = 256

reserved_memory = 8192

process_priority = -18

mirror_region_size = 512

readahead = "auto"

mirror_log_fault_policy = "allocate"

mirror_device_fault_policy = "remove"

udev_rules = 1

udev_sync = 1

}

dmeventd {

mirror_library = "libdevmapper-event-lvm2mirror.so"

snapshot_library = "libdevmapper-event-lvm2snapshot.so"

}

什么賦予了什么？我的VG去了哪里,我該如何取回它？

總結

以上是生活随笔為你收集整理的linux lvm uuid绑定,LVM：“找不到具有uuid的设备”但是blkid找到了UUID的全部內容，希望文章能夠幫你解決所遇到的問題。

如果覺得生活随笔網站內容還不錯，歡迎將生活随笔推薦給好友。