- Original Message -
From: Yuval M yuva...@gmail.com
To: Dan Kenigsberg dan...@redhat.com
Cc: users@ovirt.org, Nezer Zaidenberg nzaidenb...@mac.com
Sent: Friday, March 29, 2013 2:19:43 PM
Subject: Re: [Users] VM crashes and doesn't recover
Any ideas on what can cause that storage
Can you attach the sanlock log and the full vdsm log? (compress it if it's too
big and not xz yet)
Thanks.
- Original Message -
Any ideas on what can cause that storage crash?
could it be related to using a SSD?
Thanks,
Yuval Meir
On Wed, Mar 27, 2013 at 6:08 PM, Yuval M
Any ideas on what can cause that storage crash?
could it be related to using a SSD?
Thanks,
Yuval Meir
On Wed, Mar 27, 2013 at 6:08 PM, Yuval M yuva...@gmail.com wrote:
Still getting crashes with the patch:
# rpm -q vdsm
vdsm-4.10.3-0.281.git97db188.fc18.x86_64
attached excerpts from
Concerning the following error in dmesg:
[ 2235.638814] device-mapper: table: 253:0: multipath: error getting device
[ 2235.638816] device-mapper: ioctl: error adding target to table
I tried to debug it but mutipath gives me some problems
[wil@bufferoverflow vdsm]$ sudo multipath -l
Mar 28
On Sun, Mar 24, 2013 at 09:50:02PM +0200, Yuval M wrote:
I am running vdsm from packages as my interest is in developing for the
engine and not vdsm.
I updated the vdsm package in an attempt to solve this, now I have:
# rpm -q vdsm
vdsm-4.10.3-10.fc18.x86_64
I'm afraid that this build still
From the VDSM log, it seems that the master storage domain was not
responding.
Thread-23::DEBUG::2013-03-22
18:50:20,263::domainMonitor::216::Storage.DomainMonitorThread::(_monitorDomain)
Domain 1083422e-a5db-41b6-b667-b9ef1ef244f0 changed its status to Invalid
Traceback (most recent call
sanlock is at the latest version (this solved another problem we had a few
days ago):
$ rpm -q sanlock
sanlock-2.6-7.fc18.x86_64
the storage is on the same machine as the engine and vdsm.
iptables is up but there is a rule to allow all localhost traffic.
On Sun, Mar 24, 2013 at 11:34 AM, Maor
https://bugzilla.redhat.com/show_bug.cgi?id=890365
try restarting the vdsm service.
you had a problem with the storage and the vdsm did not recover properly.
On 03/24/2013 11:40 AM, Yuval M wrote:
sanlock is at the latest version (this solved another problem we had a
few days ago):
$ rpm
On Fri, Mar 22, 2013 at 08:24:35PM +0200, Limor Gavish wrote:
Hello,
I am using Ovirt 3.2 on Fedora 18:
[wil@bufferoverflow ~]$ rpm -q vdsm
vdsm-4.10.3-7.fc18.x86_64
(the engine is built from sources).
I seem to have hit this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=922515
I am running vdsm from packages as my interest is in developing for the
engine and not vdsm.
I updated the vdsm package in an attempt to solve this, now I have:
# rpm -q vdsm
vdsm-4.10.3-10.fc18.x86_64
I noticed that when the storage domain crashes I can't even do df -h
(hangs)
I'm also getting
10 matches
Mail list logo