Remove Master Data Domain in oVirt 3.5.0
by s k
--_bb8b9ee9-e969-42e3-b3dd-4e5e09ce289a_
Content-Type: text/plain; charset="iso-8859-7"
Content-Transfer-Encoding: quoted-printable
Hello=2C
I would like to remove the Master Data Domain because I need to decommissio=
n the underlying storage device.
Is there a way to manually change the Master Data Domain? Will the Master D=
ata Domain be reassigned automatically when the current one is deleted?
Thank you=2C
Sokratis =
--_bb8b9ee9-e969-42e3-b3dd-4e5e09ce289a_
Content-Type: text/html; charset="iso-8859-7"
Content-Transfer-Encoding: quoted-printable
<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 12pt=3B
font-family:Calibri
}
--></style></head>
<body class=3D'hmmessage'><div dir=3D'ltr'>Hello=2C<div><br></div><div><br>=
</div><div>I would like to remove the Master Data Domain because I need to =
decommission the underlying storage device.</div><div><br></div><div><br></=
div><div>Is there a way to manually change the Master Data Domain? Will the=
Master Data Domain be reassigned automatically when the current one is del=
eted?</div><div><br></div><div><br></div><div>Thank you=2C</div><div><br></=
div><div><br></div><div>Sokratis</div> </div></body>
</html>=
--_bb8b9ee9-e969-42e3-b3dd-4e5e09ce289a_--
9 years
Ovirt/VDSM hooks for el7
by Punit Dambiwal
Hi,
I have checked and found that there is no hooks available for el7....is
there any tentative planning for those hooks to cover in el7...
Thanks,
Punit
9 years
VDSM Network Bug or Feature?
by ml＠ohnewald.net
Hello List,
i think i found a nasty Bug (or feature) of ovirt.
One of my network cards was set up with dhcp. At this specific time
there was not yet a dhcp server set up which could respond to dhcp requests.
Therefore my network interface was not able to obtain an ip address.
This „failure“ leaded to that my ovirtmgnt bride would not get startet.
__Maybe__ because ovirtmgmt is alpha numeric after dbvlan116? Because
all my bonding interfaces bond0 and bond1 started just fine.
I was able to solve it by moving my /sbin/dhclient to
/sbin/dhclient.backup and creating a dummy exit0 bash script as
/sbin/dhclient.
Then the network startup process seems to progress to my ovirtmgmt
interface. From now on i was able to connect and manage my host again
and to set up my dbvlan116 interface from dhcp to none.
Here is the process list it seems to loop in:
root 2554 0.0 0.0 115612 1988 ? S< 10:06 0:00
/bin/bash /etc/sysconfig/network-scripts/ifup-eth ifcfg-dbvlan116
root 2594 0.0 0.0 104208 15620 ? S< 10:06 0:00
/sbin/dhclient -H ovirt-node06-stgt -1 -q -lf
/var/lib/dhclient/dhclient--dbvlan116.lease -pf /var/run/
root 32047 0.0 0.0 115348 1676 ? S<s 10:06 0:00 /bin/sh
/usr/libexec/vdsm/vdsmd_init_common.sh --pre-start
root 32142 1.5 0.0 348460 24952 ? S< 10:06 0:00
/usr/bin/python /usr/share/vdsm/vdsm-restore-net-config
Just killing the dhclient does not seem to work. It keeps retrying.
I reported a bug before, but maybe its better to discuss it here first
and explain the bug properly to that the Bugtracker guys know what i
mean and what the problem is? :)
Maybe its best to start the ovirtmgmt interface first? Otherwise a wrong
configured interface will lock you out of the system.
Thanks for your time,
Mario
9 years
ovirt-shell for ubuntu
by Nathanaël Blanchet
Hi all,
Does an ovirt-shell-cli equivalent exist for debian/ubuntu client?
knowing it is written in python, it must be quite easy to port it...
9 years
oVirt 3.5 - Node Non-Operational
by Marcelo Donato
*Hi everyone! Suggestions are welcome and since I thank you.*
*I have the following scenario:*
Host-01: sequoia.din.uem.br - 10.30.4.1 - Manager
Host-02: jacaranda.din.uem.br - 10.30.4.2 - Node-01
*As indicated below, the hosts communicate normally:*
[root@jacaranda ~]# ping -c 3 sequoia
PING sequoia.din.uem.br (10.30.4.1) 56(84) bytes of data.
64 bytes from sequoia.din.uem.br (10.30.4.1): icmp_seq=1 ttl=64 time=0.436
ms
64 bytes from sequoia.din.uem.br (10.30.4.1): icmp_seq=2 ttl=64 time=0.612
ms
64 bytes from sequoia.din.uem.br (10.30.4.1): icmp_seq=3 ttl=64 time=0.635
ms
[root@sequoia ~]# ping -c 3 jacaranda
PING jacaranda.din.uem.br (10.30.4.2) 56(84) bytes of data.
64 bytes from jacaranda.din.uem.br (10.30.4.2): icmp_seq=1 ttl=64
time=0.443 ms
64 bytes from jacaranda.din.uem.br (10.30.4.2): icmp_seq=2 ttl=64
time=0.587 ms
64 bytes from jacaranda.din.uem.br (10.30.4.2): icmp_seq=3 ttl=64
time=0.563 ms
*Network interfaces*
[root@jacaranda ~]# ifconfig ovirtmgmt
ovirtmgmt Link encap:Ethernet Endereço de HW D4:AE:52:78:4C:17
inet end.: 10.30.4.2 Bcast:10.30.4.255 Masc:255.255.255.0
[root@sequoia ~]# ifconfig
eth0 Link encap:Ethernet Endereço de HW 52:54:00:D2:0F:95
inet end.: 10.30.4.1 Bcast:10.30.4.255 Masc:255.255.255.0
*However engine.log, as highlighted below, the problem is in the
network.*
2015-03-26 15:00:01,799 ERROR
[org.ovirt.engine.core.bll.SetNonOperationalVdsCommand]
(DefaultQuartzScheduler_Worker-91) [35dba220] Host Node-01 is set to
Non-Operational, it is missing the following networks: ovirtmgmt
2015-03-26 15:00:01,806 WARN
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(DefaultQuartzScheduler_Worker-91) [35dba220] Correlation ID: 35dba220, Job
ID: 1b3c2410-a941-4d65-b39d-1a3d2ef378b8, Call Stack: null, Custom Event
ID: -1, Message: Host Node-01 does not comply with the cluster Cst-01
networks, the following networks are missing on host: 'ovirtmgmt'
2015-03-26 15:00:01,864 INFO
[org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo]
(DefaultQuartzScheduler_Worker-91) [6ba58858] Host
4aaf9afb-ae0e-40af-9ef8-ef098d3be91e : Node-01 is already in NonOperational
status for reason NETWORK_UNREACHABLE. SetNonOperationalVds command is
skipped.
[image: Imagem inline 1]
--
Ao encaminhar esta mensagem, por favor:
1. Apague o meu e-mail e o meu nome.
2. Apague também os endereços dos amigos antes de reenviar
3. Use Cco ou Bcc para enviar mensagens!
Dificulte a disseminação de vírus e spam.
9 years
Storage domain issue
by Jonas Israelsson
Greetings.
Running oVirt 3.5 with a mix of NFS and FC Storage.
Engine running on a seperate KVM VM and Node installed with a pre 3.5
ovirt-node "ovirt-node-iso-3.5.0.ovirt35.20140912.el6 (Edited)"
I had some problems with my FC-Storage where the LUNS for a while became
unavailable to my Ovirt-host. Everything is now up and running and those
luns again are accessible by the host. The NFS domains goes back online
but the FC does not.
Thread-22::DEBUG::2015-03-23
14:53:02,706::lvm::290::Storage.Misc.excCmd::(cmd) /usr/bin/sudo -n
/sbin/lvm vgs --config ' devices { preferred_names = ["^/dev/mapper/"]
ignore_suspended_devices=1 write_cache_state=0
disable_after_error_count=3 obtain_device_list_from_udev=0 filter = [
'\''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 '|'
--ignoreskippedcluster -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
29f9b165-3674-4384-a1d4-7aa87d923d56 (cwd None)
Thread-24::DEBUG::2015-03-23
14:53:02,981::lvm::290::Storage.Misc.excCmd::(cmd) FAILED: <err> = '
Volume group "29f9b165-3674-4384-a1d4-7aa87d923d56" not found\n
Skipping volume group 29f9b165-3674-4384-a1d4-7aa87d923d56\n'; <rc> = 5
Thread-24::WARNING::2015-03-23
14:53:02,986::lvm::372::Storage.LVM::(_reloadvgs) lvm vgs failed: 5 []
[' Volume group "29f9b165-3674-4384-a1d4-7aa87d923d56" not found', '
Skipping volume group 29f9b165-3674-4384-a1d4-7aa87d923d56']
Running the command above manually does indeed give the same output:
# /sbin/lvm vgs --config ' devices { preferred_names = ["^/dev/mapper/"]
ignore_suspended_devices=1 write_cache_state=0
disable_after_error_count=3 obtain_device_list_from_udev=0 filter = [
'\''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 '|'
--ignoreskippedcluster -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
29f9b165-3674-4384-a1d4-7aa87d923d56
Volume group "29f9b165-3674-4384-a1d4-7aa87d923d56" not found
Skipping volume group 29f9b165-3674-4384-a1d4-7aa87d923d56
What puzzles me is that those volume does exist.
lvm vgs
VG #PV #LV #SN Attr VSize VFree
22cf06d1-faca-4e17-ac78-d38b7fc300b1 1 13 0 wz--n- 999.62g 986.50g
29f9b165-3674-4384-a1d4-7aa87d923d56 1 8 0 wz--n- 99.62g 95.50g
HostVG 1 4 0 wz--n- 13.77g 52.00m
--- Volume group ---
VG Name 29f9b165-3674-4384-a1d4-7aa87d923d56
System ID
Format lvm2
Metadata Areas 2
Metadata Sequence No 20
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 8
Open LV 0
Max PV 0
Cur PV 1
Act PV 1
VG Size 99.62 GiB
PE Size 128.00 MiB
Total PE 797
Alloc PE / Size 33 / 4.12 GiB
Free PE / Size 764 / 95.50 GiB
VG UUID aAoOcw-d9YB-y9gP-Tp4M-S0UE-Aqpx-y6Z2Uk
lvm vgs --config ' devices { preferred_names = ["^/dev/mapper/"]
ignore_suspended_devices=1 write_cache_state=0
disable_after_error_count=3 obtain_device_list_from_udev=0 } 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 '|' --ignoreskippedcluster -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
29f9b165-3674-4384-a1d4-7aa87d923d56
aAoOcw-d9YB-y9gP-Tp4M-S0UE-Aqpx-y6Z2Uk|29f9b165-3674-4384-a1d4-7aa87d923d56|wz--n-|106971529216|102542344192|134217728|797|764|MDT_LEASETIMESEC=60,MDT_CLASS=Data,MDT_VERSION=3,MDT_SDUUID=29f9b165-3674-4384-a1d4-7aa87d923d56,MDT_PV0=pv:36001405c94d80be2ed0482c91a1841b8&44&uuid:muHcYl-sobG-3LyY-jjfg-3fGf-1cHO-uDk7da&44&pestart:0&44&pecount:797&44&mapoffset:0,MDT_LEASERETRIES=3,MDT_VGUUID=aAoOcw-d9YB-y9gP-Tp4M-S0UE-Aqpx-y6Z2Uk,MDT_IOOPTIMEOUTSEC=10,MDT_LOCKRENEWALINTERVALSEC=5,MDT_PHYBLKSIZE=512,MDT_LOGBLKSIZE=512,MDT_TYPE=FCP,MDT_LOCKPOLICY=,MDT_DESCRIPTION=Master,RHAT_storage_domain,MDT_POOL_SPM_ID=-1,MDT_POOL_DESCRIPTION=Elementary,MDT_POOL_SPM_LVER=-1,MDT_POOL_UUID=8c3c5df9-e8ff-4313-99c9-385b6c7d896b,MDT_MASTER_VERSION=10,MDT_POOL_DOMAINS=22cf06d1-faca-4e17-ac78-d38b7fc300b1:Active&44&c434ab5a-9d21-42eb-ba1b-dbd716ba3ed1:Active&44&96e62d18-652d-401a-b4b5-b54ecefa331c:Active&44&29f9b165-3674-4384-a1d4-7aa87d923d56:Active&44&1a0d3e5a-d2ad-4829-8ebd-ad3ff5463062:Active,MDT__SHA_CKSUM=7ea9af890755d96563cb7a736f8e3f46ea986f67,MDT_ROLE=Regular|134217728|67103744|8|1|/dev/sda
[root@patty vdsm]# vdsClient -s 0 getStorageDomainsList (Returns all but
only the NFS-Domains)
c434ab5a-9d21-42eb-ba1b-dbd716ba3ed1
1a0d3e5a-d2ad-4829-8ebd-ad3ff5463062
a8fd9df0-48f2-40a2-88d4-7bf47fef9b07
engine=# select id,storage,storage_name,storage_domain_type from
storage_domain_static ;
id | storage |
storage_name | storage_domain_type
--------------------------------------+----------------------------------------+------------------------+---------------------
072fbaa1-08f3-4a40-9f34-a5ca22dd1d74 |
ceab03af-7220-4d42-8f5c-9b557f5d29af | ovirt-image-repository | 4
1a0d3e5a-d2ad-4829-8ebd-ad3ff5463062 |
6564a0b2-2f92-48de-b986-e92de7e28885 | ISO | 2
c434ab5a-9d21-42eb-ba1b-dbd716ba3ed1 |
bb54b2b8-00a2-4b84-a886-d76dd70c3cb0 | Export | 3
22cf06d1-faca-4e17-ac78-d38b7fc300b1 |
e43eRZ-HACv-YscJ-KNZh-HVwe-tAd2-0oGNHh | Hinken | 1
<---- 'GONE'
29f9b165-3674-4384-a1d4-7aa87d923d56 |
aAoOcw-d9YB-y9gP-Tp4M-S0UE-Aqpx-y6Z2Uk | Master | 1 <---- 'GONE'
a8fd9df0-48f2-40a2-88d4-7bf47fef9b07 |
0299ca61-d68e-4282-b6c3-f6e14aef2688 | NFS-DATA | 0
When manually trying to activate one of the above domains the following
is written to the engine.log
2015-03-23 16:37:27,193 INFO
[org.ovirt.engine.core.bll.storage.SyncLunsInfoForBlockStorageDomainCommand]
(org.ovirt.thread.pool-8-thread-42) [5f2bcbf9] Running command:
SyncLunsInfoForBlockStorageDomainCommand internal: true. Entities
affected : ID: 29f9b165-3674-4384-a1d4-7aa87d923d56 Type: Storage
2015-03-23 16:37:27,202 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetVGInfoVDSCommand]
(org.ovirt.thread.pool-8-thread-42) [5f2bcbf9] START,
GetVGInfoVDSCommand(HostName = patty.elemementary.se, HostId =
38792a69-76f3-46d8-8620-9d4b9a5ec21f,
VGID=aAoOcw-d9YB-y9gP-Tp4M-S0UE-Aqpx-y6Z2Uk), log id: 6e6f6792
2015-03-23 16:37:27,404 ERROR
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetVGInfoVDSCommand]
(org.ovirt.thread.pool-8-thread-28) [3258de6d] Failed in GetVGInfoVDS method
2015-03-23 16:37:27,404 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetVGInfoVDSCommand]
(org.ovirt.thread.pool-8-thread-28) [3258de6d] Command
org.ovirt.engine.core.vdsbroker.vdsbroker.GetVGInfoVDSCommand return value
OneVGReturnForXmlRpc [mStatus=StatusForXmlRpc [mCode=506,
mMessage=Volume Group does not exist: (u'vg_uuid:
aAoOcw-d9YB-y9gP-Tp4M-S0UE-Aqpx-y6Z2Uk',)]]
2015-03-23 16:37:27,406 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetVGInfoVDSCommand]
(org.ovirt.thread.pool-8-thread-28) [3258de6d] HostName =
patty.elemementary.se
2015-03-23 16:37:27,407 ERROR
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetVGInfoVDSCommand]
(org.ovirt.thread.pool-8-thread-28) [3258de6d] Command
GetVGInfoVDSCommand(HostName = patty.elemementary.se, HostId =
38792a69-76f3-46d8-8620-9d4b9a5ec21f,
VGID=aAoOcw-d9YB-y9gP-Tp4M-S0UE-Aqpx-y6Z2Uk) execution failed.
Exception: VDSErrorException: VDSGenericException: VDSErrorException:
Failed to GetVGInfoVDS, error = Volume Group does not exist: (u'vg_uuid:
aAoOcw-d9YB-y9gP-Tp4M-S0UE-Aqpx-y6Z2Uk',), code = 506
2015-03-23 16:37:27,409 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetVGInfoVDSCommand]
(org.ovirt.thread.pool-8-thread-28) [3258de6d] FINISH,
GetVGInfoVDSCommand, log id: 2edb7c0d
2015-03-23 16:37:27,410 ERROR
[org.ovirt.engine.core.bll.storage.SyncLunsInfoForBlockStorageDomainCommand]
(org.ovirt.thread.pool-8-thread-28) [3258de6d] Command
org.ovirt.engine.core.bll.storage.SyncLunsInfoForBlockStorageDomainCommand
throw Vdc Bll exception. With error message VdcBLLException:
org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException:
VDSGenericException: VDSErrorException: Failed to GetVGInfoVDS, error =
Volume Group does not exist: (u'vg_uuid:
aAoOcw-d9YB-y9gP-Tp4M-S0UE-Aqpx-y6Z2Uk',), code = 506 (Failed with error
VolumeGroupDoesNotExist and code 506)
2015-03-23 16:37:27,413 INFO
[org.ovirt.engine.core.vdsbroker.irsbroker.ActivateStorageDomainVDSCommand]
(org.ovirt.thread.pool-8-thread-28) [3258de6d] START,
ActivateStorageDomainVDSCommand( storagePoolId =
8c3c5df9-e8ff-4313-99c9-385b6c7d896b, ignoreFailoverLimit = false,
storageDomainId = 29f9b165-3674-4384-a1d4-7aa87d923d56), log id: 795253ee
2015-03-23 16:37:27,482 ERROR
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetVGInfoVDSCommand]
(org.ovirt.thread.pool-8-thread-42) [5f2bcbf9] Failed in GetVGInfoVDS method
2015-03-23 16:37:27,482 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetVGInfoVDSCommand]
(org.ovirt.thread.pool-8-thread-42) [5f2bcbf9] Command
org.ovirt.engine.core.vdsbroker.vdsbroker.GetVGInfoVDSCommand return value
OneVGReturnForXmlRpc [mStatus=StatusForXmlRpc [mCode=506,
mMessage=Volume Group does not exist: (u'vg_uuid:
aAoOcw-d9YB-y9gP-Tp4M-S0UE-Aqpx-y6Z2Uk',)]]
Could someone (pretty please with sugar on top) point me in the right
direction ?
Brgds Jonas
9 years
Re: [ovirt-users] VMs freezing during heals
by Alastair Neil
Pranith
I have run a pretty straightforward test. I created a two brick 50 G
replica volume with normal lvm bricks, and installed two servers, one
centos 6.6 and one centos 7.0. I kicked off bonnie++ on both to generate
some file system activity and then made the volume replica 3. I saw no
issues on the servers.
Not clear if this is a sufficiently rigorous test and the Volume I have had
issues on is a 3TB volume with about 2TB used.
-Alastair
On 19 March 2015 at 12:30, Alastair Neil <ajneil.tech(a)gmail.com> wrote:
> I don't think I have the resources to test it meaningfully. I have about
> 50 vms on my primary storage domain. I might be able to set up a small 50
> GB volume and provision 2 or 3 vms running test loads but I'm not sure it
> would be comparable. I'll give it a try and let you know if I see similar
> behaviour.
>
> On 19 March 2015 at 11:34, Pranith Kumar Karampuri <pkarampu(a)redhat.com>
> wrote:
>
>> Without thinly provisioned lvm.
>>
>> Pranith
>>
>> On 03/19/2015 08:01 PM, Alastair Neil wrote:
>>
>> do you mean raw partitions as bricks or simply with out thin provisioned
>> lvm?
>>
>>
>>
>> On 19 March 2015 at 00:32, Pranith Kumar Karampuri <pkarampu(a)redhat.com>
>> wrote:
>>
>>> Could you let me know if you see this problem without lvm as well?
>>>
>>> Pranith
>>>
>>> On 03/18/2015 08:25 PM, Alastair Neil wrote:
>>>
>>> I am in the process of replacing the bricks with thinly provisioned lvs
>>> yes.
>>>
>>>
>>>
>>> On 18 March 2015 at 09:35, Pranith Kumar Karampuri <pkarampu(a)redhat.com>
>>> wrote:
>>>
>>>> hi,
>>>> Are you using thin-lvm based backend on which the bricks are
>>>> created?
>>>>
>>>> Pranith
>>>>
>>>> On 03/18/2015 02:05 AM, Alastair Neil wrote:
>>>>
>>>> I have a Ovirt cluster with 6 VM hosts and 4 gluster nodes. There are
>>>> two virtualisation clusters one with two nehelem nodes and one with four
>>>> sandybridge nodes. My master storage domain is a GlusterFS backed by a
>>>> replica 3 gluster volume from 3 of the gluster nodes. The engine is a
>>>> hosted engine 3.5.1 on 3 of the sandybridge nodes, with storage broviede by
>>>> nfs from a different gluster volume. All the hosts are CentOS 6.6.
>>>>
>>>> vdsm-4.16.10-8.gitc937927.el6
>>>>> glusterfs-3.6.2-1.el6
>>>>> 2.6.32 - 504.8.1.el6.x86_64
>>>>
>>>>
>>>> Problems happen when I try to add a new brick or replace a brick
>>>> eventually the self heal will kill the VMs. In the VM's logs I see kernel
>>>> hung task messages.
>>>>
>>>> Mar 12 23:05:16 static1 kernel: INFO: task nginx:1736 blocked for
>>>>> more than 120 seconds.
>>>>> Mar 12 23:05:16 static1 kernel: Not tainted
>>>>> 2.6.32-504.3.3.el6.x86_64 #1
>>>>> Mar 12 23:05:16 static1 kernel: "echo 0 >
>>>>> /proc/sys/kernel/hung_task_timeout_secs" disables this message.
>>>>> Mar 12 23:05:16 static1 kernel: nginx D 0000000000000001 0
>>>>> 1736 1735 0x00000080
>>>>> Mar 12 23:05:16 static1 kernel: ffff8800778b17a8 0000000000000082
>>>>> 0000000000000000 00000000000126c0
>>>>> Mar 12 23:05:16 static1 kernel: ffff88007e5c6500 ffff880037170080
>>>>> 0006ce5c85bd9185 ffff88007e5c64d0
>>>>> Mar 12 23:05:16 static1 kernel: ffff88007a614ae0 00000001722b64ba
>>>>> ffff88007a615098 ffff8800778b1fd8
>>>>> Mar 12 23:05:16 static1 kernel: Call Trace:
>>>>> Mar 12 23:05:16 static1 kernel: [<ffffffff8152a885>]
>>>>> schedule_timeout+0x215/0x2e0
>>>>> Mar 12 23:05:16 static1 kernel: [<ffffffff8152a503>]
>>>>> wait_for_common+0x123/0x180
>>>>> Mar 12 23:05:16 static1 kernel: [<ffffffff81064b90>] ?
>>>>> default_wake_function+0x0/0x20
>>>>> Mar 12 23:05:16 static1 kernel: [<ffffffffa0210a76>] ?
>>>>> _xfs_buf_read+0x46/0x60 [xfs]
>>>>> Mar 12 23:05:16 static1 kernel: [<ffffffffa02063c7>] ?
>>>>> xfs_trans_read_buf+0x197/0x410 [xfs]
>>>>> Mar 12 23:05:16 static1 kernel: [<ffffffff8152a61d>]
>>>>> wait_for_completion+0x1d/0x20
>>>>> Mar 12 23:05:16 static1 kernel: [<ffffffffa020ff5b>]
>>>>> xfs_buf_iowait+0x9b/0x100 [xfs]
>>>>> Mar 12 23:05:16 static1 kernel: [<ffffffffa02063c7>] ?
>>>>> xfs_trans_read_buf+0x197/0x410 [xfs]
>>>>> Mar 12 23:05:16 static1 kernel: [<ffffffffa0210a76>]
>>>>> _xfs_buf_read+0x46/0x60 [xfs]
>>>>> Mar 12 23:05:16 static1 kernel: [<ffffffffa0210b3b>]
>>>>> xfs_buf_read+0xab/0x100 [xfs]
>>>>> Mar 12 23:05:16 static1 kernel: [<ffffffffa02063c7>]
>>>>> xfs_trans_read_buf+0x197/0x410 [xfs]
>>>>> Mar 12 23:05:16 static1 kernel: [<ffffffffa01ee6a4>]
>>>>> xfs_imap_to_bp+0x54/0x130 [xfs]
>>>>> Mar 12 23:05:16 static1 kernel: [<ffffffffa01f077b>]
>>>>> xfs_iread+0x7b/0x1b0 [xfs]
>>>>> Mar 12 23:05:16 static1 kernel: [<ffffffff811ab77e>] ?
>>>>> inode_init_always+0x11e/0x1c0
>>>>> Mar 12 23:05:16 static1 kernel: [<ffffffffa01eb5ee>]
>>>>> xfs_iget+0x27e/0x6e0 [xfs]
>>>>> Mar 12 23:05:16 static1 kernel: [<ffffffffa01eae1d>] ?
>>>>> xfs_iunlock+0x5d/0xd0 [xfs]
>>>>> Mar 12 23:05:16 static1 kernel: [<ffffffffa0209366>]
>>>>> xfs_lookup+0xc6/0x110 [xfs]
>>>>> Mar 12 23:05:16 static1 kernel: [<ffffffffa0216024>]
>>>>> xfs_vn_lookup+0x54/0xa0 [xfs]
>>>>> Mar 12 23:05:16 static1 kernel: [<ffffffff8119dc65>]
>>>>> do_lookup+0x1a5/0x230
>>>>> Mar 12 23:05:16 static1 kernel: [<ffffffff8119e8f4>]
>>>>> __link_path_walk+0x7a4/0x1000
>>>>> Mar 12 23:05:16 static1 kernel: [<ffffffff811738e7>] ?
>>>>> cache_grow+0x217/0x320
>>>>> Mar 12 23:05:16 static1 kernel: [<ffffffff8119f40a>]
>>>>> path_walk+0x6a/0xe0
>>>>> Mar 12 23:05:16 static1 kernel: [<ffffffff8119f61b>]
>>>>> filename_lookup+0x6b/0xc0
>>>>> Mar 12 23:05:16 static1 kernel: [<ffffffff811a0747>]
>>>>> user_path_at+0x57/0xa0
>>>>> Mar 12 23:05:16 static1 kernel: [<ffffffffa0204e74>] ?
>>>>> _xfs_trans_commit+0x214/0x2a0 [xfs]
>>>>> Mar 12 23:05:16 static1 kernel: [<ffffffffa01eae3e>] ?
>>>>> xfs_iunlock+0x7e/0xd0 [xfs]
>>>>> Mar 12 23:05:16 static1 kernel: [<ffffffff81193bc0>]
>>>>> vfs_fstatat+0x50/0xa0
>>>>> Mar 12 23:05:16 static1 kernel: [<ffffffff811aaf5d>] ?
>>>>> touch_atime+0x14d/0x1a0
>>>>> Mar 12 23:05:16 static1 kernel: [<ffffffff81193d3b>] vfs_stat+0x1b/0x20
>>>>> Mar 12 23:05:16 static1 kernel: [<ffffffff81193d64>]
>>>>> sys_newstat+0x24/0x50
>>>>> Mar 12 23:05:16 static1 kernel: [<ffffffff810e5c87>] ?
>>>>> audit_syscall_entry+0x1d7/0x200
>>>>> Mar 12 23:05:16 static1 kernel: [<ffffffff810e5a7e>] ?
>>>>> __audit_syscall_exit+0x25e/0x290
>>>>> Mar 12 23:05:16 static1 kernel: [<ffffffff8100b072>]
>>>>> system_call_fastpath+0x16/0x1b
>>>>
>>>>
>>>>
>>>> I am wondering if my volume settings are causing this. Can anyone
>>>> with more knowledge take a look and let me know:
>>>>
>>>> network.remote-dio: on
>>>>> performance.stat-prefetch: off
>>>>> performance.io-cache: off
>>>>> performance.read-ahead: off
>>>>> performance.quick-read: off
>>>>> nfs.export-volumes: on
>>>>> network.ping-timeout: 20
>>>>> cluster.self-heal-readdir-size: 64KB
>>>>> cluster.quorum-type: auto
>>>>> cluster.data-self-heal-algorithm: diff
>>>>> cluster.self-heal-window-size: 8
>>>>> cluster.heal-timeout: 500
>>>>> cluster.self-heal-daemon: on
>>>>> cluster.entry-self-heal: on
>>>>> cluster.data-self-heal: on
>>>>> cluster.metadata-self-heal: on
>>>>> cluster.readdir-optimize: on
>>>>> cluster.background-self-heal-count: 20
>>>>> cluster.rebalance-stats: on
>>>>> cluster.min-free-disk: 5%
>>>>> cluster.eager-lock: enable
>>>>> storage.owner-uid: 36
>>>>> storage.owner-gid: 36
>>>>> auth.allow:*
>>>>> user.cifs: disable
>>>>> cluster.server-quorum-ratio: 51%
>>>>
>>>>
>>>> Many Thanks, Alastair
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Users mailing listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Users mailing list
>>>> Users(a)ovirt.org
>>>> http://lists.ovirt.org/mailman/listinfo/users
>>>>
>>>>
>>>
>>>
>>
>>
>
9 years
Modules sanlock are not configured
by Jurriën Bloemen
--Apple-Mail=_B0F5D3E0-FE6C-44CC-9D86-DD009DD544F1
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=windows-1252
Hi all,
I have CentOS 7 running and I added the oVirt 3.5 repo to it. I open the =
oVirt Manager and added a new system to it.=20
The manager says installing and after that is fails to connect. Looking =
on the system I see:
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: vdsm: Running mkdirs
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: vdsm: Running =
configure_coredump
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: vdsm: Running =
configure_vdsm_logs
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: vdsm: Running =
wait_for_network
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: vdsm: Running run_init_hooks
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: vdsm: Running =
upgraded_version_check
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: vdsm: Running =
check_is_configured
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: Error:
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: One of the modules is not =
configured to work with VDSM.
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: To configure the module use =
the following:
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: 'vdsm-tool configure =
[--module module-name]'.
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: If all modules are not =
configured try to use:
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: 'vdsm-tool configure =
--force'
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: (The force flag will stop =
the module's service and start it
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: afterwards automatically to =
load the new configuration.)
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: libvirt is already =
configured for vdsm
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: Modules sanlock are not =
configured
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: vdsm: stopped during execute =
check_is_configured task (task returned with error code 1).
So I run vdsm-tool configure after I stop sanlock.=20
# vdsm-tool configure
Checking configuration status...
libvirt is already configured for vdsm
SUCCESS: ssl configured to true. No conflicts
Running configure...
Reconfiguration of sanlock is done.
Done configuring modules to VDSM.
But when I want to start vdsmd it still gives the error that sanlock is =
not configured.
Does somebody has a solution for this?=20
I am a bit lost on this=85 Google only tells me that there was a bug in =
3.4.=20
Thanks in advance,
Jurri=EBn=
--Apple-Mail=_B0F5D3E0-FE6C-44CC-9D86-DD009DD544F1
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=windows-1252
<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1252"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Hi =
all,<div><br></div><div>I have CentOS 7 running and I added the oVirt =
3.5 repo to it. I open the oVirt Manager and added a new system to =
it. </div><div>The manager says installing and after that is fails =
to connect. Looking on the system I see:</div><div><br></div><div><div =
style=3D"margin: 0px; font-family: 'Courier New'; color: rgb(245, 245, =
245); background-color: rgb(0, 0, 0);">Mar 30 =
21:09:37 vdsmd_init_common.sh[7106]: vdsm: Running mkdirs</div><div =
style=3D"margin: 0px; font-family: 'Courier New'; color: rgb(245, 245, =
245); background-color: rgb(0, 0, 0);">Mar 30 =
21:09:37 vdsmd_init_common.sh[7106]: vdsm: Running =
configure_coredump</div><div style=3D"margin: 0px; font-family: 'Courier =
New'; color: rgb(245, 245, 245); background-color: rgb(0, 0, 0);">Mar 30 =
21:09:37 vdsmd_init_common.sh[7106]: vdsm: Running =
configure_vdsm_logs</div><div style=3D"margin: 0px; font-family: =
'Courier New'; color: rgb(245, 245, 245); background-color: rgb(0, 0, =
0);">Mar 30 21:09:37 vdsmd_init_common.sh[7106]: vdsm: Running =
wait_for_network</div><div style=3D"margin: 0px; font-family: 'Courier =
New'; color: rgb(245, 245, 245); background-color: rgb(0, 0, 0);">Mar 30 =
21:09:37 vdsmd_init_common.sh[7106]: vdsm: Running =
run_init_hooks</div><div style=3D"margin: 0px; font-family: 'Courier =
New'; color: rgb(245, 245, 245); background-color: rgb(0, 0, 0);">Mar 30 =
21:09:37 vdsmd_init_common.sh[7106]: vdsm: Running =
upgraded_version_check</div><div style=3D"margin: 0px; font-family: =
'Courier New'; color: rgb(245, 245, 245); background-color: rgb(0, 0, =
0);">Mar 30 21:09:37 vdsmd_init_common.sh[7106]: vdsm: Running =
check_is_configured</div><div style=3D"margin: 0px; font-family: =
'Courier New'; color: rgb(245, 245, 245); background-color: rgb(0, 0, =
0);">Mar 30 21:09:37 vdsmd_init_common.sh[7106]: Error:</div><div =
style=3D"margin: 0px; font-family: 'Courier New'; color: rgb(245, 245, =
245); background-color: rgb(0, 0, 0);">Mar 30 =
21:09:37 vdsmd_init_common.sh[7106]: One of the modules is not =
configured to work with VDSM.</div><div style=3D"margin: 0px; =
font-family: 'Courier New'; color: rgb(245, 245, 245); background-color: =
rgb(0, 0, 0);">Mar 30 21:09:37 vdsmd_init_common.sh[7106]: To =
configure the module use the following:</div><div style=3D"margin: 0px; =
font-family: 'Courier New'; color: rgb(245, 245, 245); background-color: =
rgb(0, 0, 0);">Mar 30 21:09:37 vdsmd_init_common.sh[7106]: =
'vdsm-tool configure [--module module-name]'.</div><div style=3D"margin: =
0px; font-family: 'Courier New'; color: rgb(245, 245, 245); =
background-color: rgb(0, 0, 0);">Mar 30 =
21:09:37 vdsmd_init_common.sh[7106]: If all modules are not =
configured try to use:</div><div style=3D"margin: 0px; font-family: =
'Courier New'; color: rgb(245, 245, 245); background-color: rgb(0, 0, =
0);">Mar 30 21:09:37 vdsmd_init_common.sh[7106]: 'vdsm-tool =
configure --force'</div><div style=3D"margin: 0px; font-family: 'Courier =
New'; color: rgb(245, 245, 245); background-color: rgb(0, 0, 0);">Mar 30 =
21:09:37 vdsmd_init_common.sh[7106]: (The force flag will stop the =
module's service and start it</div><div style=3D"margin: 0px; =
font-family: 'Courier New'; color: rgb(245, 245, 245); background-color: =
rgb(0, 0, 0);">Mar 30 21:09:37 vdsmd_init_common.sh[7106]: =
afterwards automatically to load the new configuration.)</div><div =
style=3D"margin: 0px; font-family: 'Courier New'; color: rgb(245, 245, =
245); background-color: rgb(0, 0, 0);">Mar 30 =
21:09:37 vdsmd_init_common.sh[7106]: libvirt is already configured =
for vdsm</div><div style=3D"margin: 0px; font-family: 'Courier New'; =
color: rgb(245, 245, 245); background-color: rgb(0, 0, 0);">Mar 30 =
21:09:37 vdsmd_init_common.sh[7106]: Modules sanlock are not =
configured</div><div style=3D"margin: 0px; font-family: 'Courier New'; =
color: rgb(245, 245, 245); background-color: rgb(0, 0, 0);">Mar 30 =
21:09:37 vdsmd_init_common.sh[7106]: vdsm: stopped during execute =
check_is_configured task (task returned with error code =
1).</div></div><div><br></div><div>So I run vdsm-tool configure after I =
stop sanlock. </div><div><br></div><div><div style=3D"margin: 0px; =
font-family: 'Courier New'; color: rgb(245, 245, 245); background-color: =
rgb(0, 0, 0);"># vdsm-tool configure</div><div style=3D"margin: 0px; =
font-family: 'Courier New'; color: rgb(245, 245, 245); background-color: =
rgb(0, 0, 0); min-height: 14px;"><br></div><div style=3D"margin: 0px; =
font-family: 'Courier New'; color: rgb(245, 245, 245); background-color: =
rgb(0, 0, 0);">Checking configuration status...</div><div style=3D"margin:=
0px; font-family: 'Courier New'; color: rgb(245, 245, 245); =
background-color: rgb(0, 0, 0); min-height: 14px;"><br></div><div =
style=3D"margin: 0px; font-family: 'Courier New'; color: rgb(245, 245, =
245); background-color: rgb(0, 0, 0);">libvirt is already configured for =
vdsm</div><div style=3D"margin: 0px; font-family: 'Courier New'; color: =
rgb(245, 245, 245); background-color: rgb(0, 0, 0);">SUCCESS: ssl =
configured to true. No conflicts</div><div style=3D"margin: 0px; =
font-family: 'Courier New'; color: rgb(245, 245, 245); background-color: =
rgb(0, 0, 0); min-height: 14px;"><br></div><div style=3D"margin: 0px; =
font-family: 'Courier New'; color: rgb(245, 245, 245); background-color: =
rgb(0, 0, 0);">Running configure...</div><div style=3D"margin: 0px; =
font-family: 'Courier New'; color: rgb(245, 245, 245); background-color: =
rgb(0, 0, 0);">Reconfiguration of sanlock is done.</div><div =
style=3D"margin: 0px; font-family: 'Courier New'; color: rgb(245, 245, =
245); background-color: rgb(0, 0, 0); min-height: 14px;"><br></div><div =
style=3D"margin: 0px; font-family: 'Courier New'; color: rgb(245, 245, =
245); background-color: rgb(0, 0, 0);">Done configuring modules to =
VDSM.</div></div><div><br></div><div>But when I want to start vdsmd it =
still gives the error that sanlock is not =
configured.</div><div><br></div><div>Does somebody has a solution for =
this? </div><div><br></div><div>I am a bit lost on this=85 Google =
only tells me that there was a bug in =
3.4. </div><div><br></div><div>Thanks in =
advance,</div><div><br></div><div>Jurri=EBn</div></body></html>=
--Apple-Mail=_B0F5D3E0-FE6C-44CC-9D86-DD009DD544F1--
9 years
