Thank you for your advice, yesterday, after 5 hours vm ovirt-engine starts. I suffered all the virtual machines on the old server Xen., except for one large volume. Later, when I can move and it will be to understand what happened to the ISCSI storage.
On Sun, Feb 19, 2017 at 12:42 PM, Денис Мишанин <mishanindv@gmail.com> wrote:
> Hello.
> After restarting the ISCSI storage I can not run ovirt-engine in prodation
> use I am looking for help
You have this in vdsm.log:
Thread-640::DEBUG::2017-02-19
13:40:35,756::lvm::288::Storage.Misc.excCmd::(cmd) /usr/bin/taskset
--cpu-list 0-23 /usr/bin/sudo -n /usr/sbin/lvm vgs --config ' devices
{ preferred_names = [
"^/dev/mapper/"] ignore_suspended_devices=1 write_cache_state=0
disable_after_error_count=3 filter = [
'\''a|/dev/mapper/3600605b00a20bf201e29c6bf236a6651|'\'',
'\''r|.*|'\'' ] } global {
locking_type=1 prioritise_write_locks=1 wait_for_locks=1
use_lvmetad=0 } backup { retain_min = 50 retain_days = 0 } '
--noheadings --units b --nosuffix --separator '|' --ignoreskippe
dcluster -o uuid,name,attr,size,free,extent_size,extent_count,free_count,tags,vg_mda_size,vg_mda_free,lv_count,pv_count,pv_name
c7c466c5-983d-40b2-8f8c-d569755281f5 (cwd None)
Thread-640::DEBUG::2017-02-19
13:40:35,784::lvm::288::Storage.Misc.excCmd::(cmd) FAILED: <err> = '
WARNING: Not using lvmetad because config setting use_lvmetad=0.\n
WARNING: To avoid cor
ruption, rescan devices to make changes visible (pvscan --cache).\n
Volume group "c7c466c5-983d-40b2-8f8c-d569755281f5" not found\n
Cannot process volume group c7c466c5-983d-40b2-8f8c-d56
9755281f5\n'; <rc> = 5
Thread-640::WARNING::2017-02-19
13:40:35,785::lvm::376::Storage.LVM::(_reloadvgs) lvm vgs failed: 5 []
[' WARNING: Not using lvmetad because config setting use_lvmetad=0.',
' WARNING: To
avoid corruption, rescan devices to make changes visible (pvscan
--cache).', ' Volume group "c7c466c5-983d-40b2-8f8c-d569755281f5" not
found', ' Cannot process volume group c7c466c5-983d-
40b2-8f8c-d569755281f5']
Not sure what might have caused this.
Is your iSCSI storage ok after the reboot?
You might try to reboot the client (host) or further debug it on
kernel/iSCSI level. Check e.g. 'lsblk', iscsiadm, etc.
Best,
--
Didi