One just has to be careful if the CloudStack runs sr scan, it means the lv will get open and closed during your operation and might lead to problems. In my case it closed lv before i could run repair on it. I might want to stop CS management servers, but because I have an idea to which chain it belongs to, i might just delete the template and recreate it. Hopefully this will delete whole chain. Noone is using it anyways.
Will make a new post about it. Hopefully next time I wont be just replying to myself. :-) Let’s see. Refards, F. On 09 Dec 2015, at 17:02, France <mailingli...@isg.si> wrote: > I guess i need to activate it first ‘cause it’s CLVM. :-) > > lvchange -ay and then deactivate it with lvchange -an. > > Will try now. Hopefully someone somewhere sometime might find this post > useful. > > Regards, > F. > > > > On 09 Dec 2015, at 13:56, France <mailingli...@isg.si> wrote: > >> Hi guys, >> >> I want to check corrupted VHD on a XenServer cluster with LVM over ISCSI. >> >> This is the VHD I want to check: >> [root@x3 ~]# lvs | grep 1a240d45-ee0a-4c30-809b-3114dfaf85ba >> VHD-1a240d45-ee0a-4c30-809b-3114dfaf85ba >> VG_XenStorage-3b6e386d-8736-6b6b-7006-f3f4df9bd586 -ri--- 136.00M >> >> How can I run vhd-util uppon it? >> I tried on cluster master like so, but failed: >> [root@x3 ~]# vhd-util check --debug -n >> /dev/VG_XenStorage-3b6e386d-8736-6b6b-7006-f3f4df9bd586/VHD-1a240d45-ee0a-4c30-809b-3114dfaf85ba >> cannot stat >> /dev/VG_XenStorage-3b6e386d-8736-6b6b-7006-f3f4df9bd586/VHD-1a240d45-ee0a-4c30-809b-3114dfaf85ba: >> 2 >> [root@x3 ~]# >> >> Please help. >> >> Thank you. >> F. >
