[Linuxtrent] Re: Proxmox: errore device md-4

# ls -la /dev/dm*
brw-rw---- 1 root disk 254, 0 Mar 29 08:10 /dev/dm-0
brw-rw---- 1 root disk 254, 1 Mar 29 08:10 /dev/dm-1
brw-rw---- 1 root disk 254, 2 Mar 29 08:10 /dev/dm-2
brw-rw---- 1 root disk 254, 3 Mar 29 08:10 /dev/dm-3
brw-rw---- 1 root disk 254, 4 Jun 11 22:12 /dev/dm-4
brw-rw---- 1 root disk 254, 5 Jun 11 22:12 /dev/dm-5
brw-rw---- 1 root disk 254, 6 Jun 11 22:12 /dev/dm-6


Il giorno 14 giugno 2012 13:49, Gianni Caldonazzi <
gianni.caldonazzi@xxxxxxxxx> ha scritto:

> Strada rapida:
>
> ls -al /dev/disk/by-id/
>
>
Visto che effettivamente sono pochi dischi..
# ls -la /dev/disk/by-id/
total 0
drwxr-xr-x 2 root root 540 Jun 11 22:12 .
drwxr-xr-x 5 root root 100 Mar 29 08:10 ..
lrwxrwxrwx 1 root root  10 Mar 29 08:10 dm-name-fileserver-backup1 ->
../../dm-3
lrwxrwxrwx 1 root root  10 Mar 29 08:10 dm-name-pve-data -> ../../dm-2
lrwxrwxrwx 1 root root  10 Jun 11 22:12 dm-name-pve-data-real -> ../../dm-5
lrwxrwxrwx 1 root root  10 Mar 29 08:10 dm-name-pve-root -> ../../dm-1
lrwxrwxrwx 1 root root  10 Mar 29 08:10 dm-name-pve-swap -> ../../dm-0
lrwxrwxrwx 1 root root  10 Jun 11 22:12 dm-name-pve-vzsnap--px1--0 ->
../../dm-4
lrwxrwxrwx 1 root root  10 Jun 11 22:12 dm-name-pve-vzsnap--px1--0-cow ->
../../dm-6
lrwxrwxrwx 1 root root  10 Jun 11 22:12
dm-uuid-LVM-AXHmW86yg0TePA47NHKTgspsJwcD9VCi7ObcTIZ0ol3T2oy1t10Sah7jLjVp0qY7
-> ../../dm-4
lrwxrwxrwx 1 root root  10 Jun 11 22:12
dm-uuid-LVM-AXHmW86yg0TePA47NHKTgspsJwcD9VCi7ObcTIZ0ol3T2oy1t10Sah7jLjVp0qY7-cow
-> ../../dm-6
lrwxrwxrwx 1 root root  10 Mar 29 08:10
dm-uuid-LVM-AXHmW86yg0TePA47NHKTgspsJwcD9VCiTOibnl0rmrJDxoH2Cx0wFhpK2n2VaGsT
-> ../../dm-0
lrwxrwxrwx 1 root root  10 Mar 29 08:10
dm-uuid-LVM-AXHmW86yg0TePA47NHKTgspsJwcD9VCiU2Tm4mypwAq3QE6BKYNWn3OWSlG2LGWZ
-> ../../dm-1
lrwxrwxrwx 1 root root  10 Mar 29 08:10
dm-uuid-LVM-AXHmW86yg0TePA47NHKTgspsJwcD9VCijEgRCIgaRd9G38BEMnHKgRzjnVWq5D4P
-> ../../dm-2
lrwxrwxrwx 1 root root  10 Jun 11 22:12
dm-uuid-LVM-AXHmW86yg0TePA47NHKTgspsJwcD9VCijEgRCIgaRd9G38BEMnHKgRzjnVWq5D4P-real
-> ../../dm-5
lrwxrwxrwx 1 root root  10 Mar 29 08:10
dm-uuid-LVM-byXBUe92TeNeYpVoNegZPP1nv0Wc5Qlh47Wb2YPr9LQW18mT1WXFPxWDWzTLL5AF
-> ../../dm-3

[ho tolto alcune cose superflue]

e
# ls -la /dev/mapper/
crw-rw----  1 root root  10, 62 Mar 29 08:10 control
brw-rw----  1 root disk 254,  3 Mar 29 08:10 fileserver-backup1
brw-rw----  1 root disk 254,  2 Mar 29 08:10 pve-data
brw-rw----  1 root disk 254,  5 Jun 11 22:12 pve-data-real
brw-rw----  1 root disk 254,  1 Mar 29 08:10 pve-root
brw-rw----  1 root disk 254,  0 Mar 29 08:10 pve-swap
brw-rw----  1 root disk 254,  4 Jun 11 22:12 pve-vzsnap--px1--0
brw-rw----  1 root disk 254,  6 Jun 11 22:12 pve-vzsnap--px1--0-cow

seguendo i consigli di Roberto ho provato a rimuovere l'elemento
# dmsetup remove /dev/mapper/pve-vzsnap--px1--0
device-mapper: remove ioctl failed: Device or resource busy
Command failed

senza risultato.
Con il comando mount ho visto che è ancora montata :
/dev/mapper/pve-vzsnap--px1--0 on /mnt/vzsnap0 type ext3 (rw)

con ps ax abbiamo notato che erano attivi ancora i processi del vzdump.
ps ax | grep snap
31034 ?        Ss     0:00 /usr/bin/perl -w /usr/sbin/vzdump --quiet --node
1 --snapshot --storage Backup1 --maxfiles 20 --mailto XXXXXXX

Quindi un bel kill 31034  e poi un
killall vmtar (che anch'esso attivo)

poi
umount  /dev/mapper/pve-vzsnap--px1--0
e infine
lvremove pve/vzsnap-px1-0
 /dev/dm-4: read failed after 0 of 4096 at 0: Input/output error
Do you really want to remove active logical volume "vzsnap-px1-0"? [y/n]:
y

Vediamo se passa la notte.

Un grazie a Roberto che mi ha dato supporto on-line

A.

Other related posts: