Re: [vdsm] Installing VDSM on an empty Fedora 16 machine?

2012-03-07 Thread Shu Ming 

It is seems the authentication get some problems.

You can use this link as a install reference to disable the 
authentication .

http://www.ovirt.org/wiki/Installing_VDSM_from_rpm

On 2012-3-8 0:33, Saša Tomić wrote:


On 03/07/2012 04:24 PM, Dan Kenigsberg wrote:

Time to debug further in... Clues in /var/log/libvirtd.log?
Do you see anything when you run libvirtd --listen from the command 
line?
Dan. 

We are getting closer now, it appears that some paths are broken...

[stomic@localhost ~]$ sudo tail /var/log/libvirtd.log
2012-03-07 15:42:58.129+: 1590: debug : virRegisterDriver:783 : 
driver=0x739960 name=QEMU
2012-03-07 15:42:58.129+: 1590: debug : virRegisterDriver:807 : 
registering QEMU as driver 10
2012-03-07 15:42:58.129+: 1590: debug : virRegisterDriver:783 : 
driver=0x739f60 name=LXC
2012-03-07 15:42:58.129+: 1590: debug : virRegisterDriver:807 : 
registering LXC as driver 11
2012-03-07 15:42:58.129+: 1590: debug : virRegisterDriver:783 : 
driver=0x73aa40 name=UML
2012-03-07 15:42:58.129+: 1590: debug : virRegisterDriver:807 : 
registering UML as driver 12
2012-03-07 15:42:58.131+: 1590: debug : virHookCheck:115 : No hook 
script /etc/libvirt/hooks/daemon
2012-03-07 15:42:58.131+: 1590: debug : virHookCheck:115 : No hook 
script /etc/libvirt/hooks/qemu
2012-03-07 15:42:58.131+: 1590: debug : virHookCheck:115 : No hook 
script /etc/libvirt/hooks/lxc
2012-03-07 15:42:58.134+: 1590: error : 
virNetTLSContextCheckCertBasicConstraints:166 : The certificate 
/etc/pki/vdsm/certs/vdsmcert.pem basic constraints show a CA, but we 
need one for a server



[stomic@localhost ~]$ libvirtd --listen
2012-03-07 16:26:00.931+: 4893: info : libvirt version: 0.9.6, 
package: 4.fc16 (Fedora Project, 2011-12-19-20:27:37, 
x86-01.phx2.fedoraproject.org)
2012-03-07 16:26:00.931+: 4893: error : 
virNetTLSContextCheckCertFile:92 : Cannot read CA certificate 
'/etc/pki/CA/cacert.pem': No such file or directory


[stomic@localhost ~]$ locate cacert.pem
/etc/pki/vdsm/certs/cacert.pem

[stomic@localhost pki]$ ls -l /etc/pki/vdsm/certs/cacert.pem
lrwxrwxrwx. 1 root root   32 Mar  6 18:15 
/etc/pki/vdsm/certs/cacert.pem -> /etc/pki/vdsm/certs/vdsmcert.pem


[stomic@localhost pki]$ ls -l /etc/pki/vdsm/certs/vdsmcert.pem
-rw---. 1 vdsm kvm 1188 Mar  6 18:15 /etc/pki/vdsm/certs/vdsmcert.pem




--
Shu Ming
IBM China Systems and Technology Laboratory


___
vdsm-devel mailing list
vdsm-devel@lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/vdsm-devel

Re: [vdsm] Installing VDSM on an empty Fedora 16 machine?

2012-03-07 Thread Saša Tomić 


On 03/07/2012 04:24 PM, Dan Kenigsberg wrote:

Time to debug further in... Clues in /var/log/libvirtd.log?
Do you see anything when you run libvirtd --listen from the command line?
Dan. 

We are getting closer now, it appears that some paths are broken...

[stomic@localhost ~]$ sudo tail /var/log/libvirtd.log
2012-03-07 15:42:58.129+: 1590: debug : virRegisterDriver:783 : 
driver=0x739960 name=QEMU
2012-03-07 15:42:58.129+: 1590: debug : virRegisterDriver:807 : 
registering QEMU as driver 10
2012-03-07 15:42:58.129+: 1590: debug : virRegisterDriver:783 : 
driver=0x739f60 name=LXC
2012-03-07 15:42:58.129+: 1590: debug : virRegisterDriver:807 : 
registering LXC as driver 11
2012-03-07 15:42:58.129+: 1590: debug : virRegisterDriver:783 : 
driver=0x73aa40 name=UML
2012-03-07 15:42:58.129+: 1590: debug : virRegisterDriver:807 : 
registering UML as driver 12
2012-03-07 15:42:58.131+: 1590: debug : virHookCheck:115 : No hook 
script /etc/libvirt/hooks/daemon
2012-03-07 15:42:58.131+: 1590: debug : virHookCheck:115 : No hook 
script /etc/libvirt/hooks/qemu
2012-03-07 15:42:58.131+: 1590: debug : virHookCheck:115 : No hook 
script /etc/libvirt/hooks/lxc
2012-03-07 15:42:58.134+: 1590: error : 
virNetTLSContextCheckCertBasicConstraints:166 : The certificate 
/etc/pki/vdsm/certs/vdsmcert.pem basic constraints show a CA, but we 
need one for a server



[stomic@localhost ~]$ libvirtd --listen
2012-03-07 16:26:00.931+: 4893: info : libvirt version: 0.9.6, 
package: 4.fc16 (Fedora Project, 2011-12-19-20:27:37, 
x86-01.phx2.fedoraproject.org)
2012-03-07 16:26:00.931+: 4893: error : 
virNetTLSContextCheckCertFile:92 : Cannot read CA certificate 
'/etc/pki/CA/cacert.pem': No such file or directory


[stomic@localhost ~]$ locate cacert.pem
/etc/pki/vdsm/certs/cacert.pem

[stomic@localhost pki]$ ls -l /etc/pki/vdsm/certs/cacert.pem
lrwxrwxrwx. 1 root root   32 Mar  6 18:15 /etc/pki/vdsm/certs/cacert.pem 
-> /etc/pki/vdsm/certs/vdsmcert.pem


[stomic@localhost pki]$ ls -l /etc/pki/vdsm/certs/vdsmcert.pem
-rw---. 1 vdsm kvm 1188 Mar  6 18:15 /etc/pki/vdsm/certs/vdsmcert.pem

--
best regards,
Saša

___
vdsm-devel mailing list
vdsm-devel@lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/vdsm-devel

Re: [vdsm] Installing VDSM on an empty Fedora 16 machine?

2012-03-07 Thread Dan Kenigsberg 
On Wed, Mar 07, 2012 at 04:03:33PM +0100, Saša Tomić wrote:
> On 03/07/2012 03:41 PM, Dan Kenigsberg wrote:
> >That's empty because in Fedora vdsm uses the now-standard systemd
> >/lib/systemd/system/vdsmd.service
> >
> >which for some reason fails to start.  Is libvirtd running?
> >systemctl status libvirtd.service
> 
> Appears not...
> 
> [root@localhost ~]# systemctl status libvirtd.service
> libvirtd.service - LSB: daemon for libvirt virtualization API
>   Loaded: loaded (/etc/rc.d/init.d/libvirtd)
>   Active: failed since Wed, 07 Mar 2012 14:25:12 +0100; 1h 28min ago
>   CGroup: name=systemd:/system/libvirtd.service

Time to debug further in...
Clues in /var/log/libvirtd.log?

Do you see anything when you run

libvirtd --listen

from the command line?

Dan.
___
vdsm-devel mailing list
vdsm-devel@lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/vdsm-devel

Re: [vdsm] Installing VDSM on an empty Fedora 16 machine?

2012-03-07 Thread Saša Tomić 

On 03/07/2012 03:41 PM, Dan Kenigsberg wrote:

That's empty because in Fedora vdsm uses the now-standard systemd
/lib/systemd/system/vdsmd.service

which for some reason fails to start.  Is libvirtd running?
systemctl status libvirtd.service


Appears not...

[root@localhost ~]# systemctl status libvirtd.service
libvirtd.service - LSB: daemon for libvirt virtualization API
  Loaded: loaded (/etc/rc.d/init.d/libvirtd)
  Active: failed since Wed, 07 Mar 2012 14:25:12 +0100; 1h 28min ago
  CGroup: name=systemd:/system/libvirtd.service


and the rest of dependencies listed in
Requires=multipathd.service libvirtd.service ntpd.service network.service




--
best regards,
Saša

___
vdsm-devel mailing list
vdsm-devel@lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/vdsm-devel

Re: [vdsm] Installing VDSM on an empty Fedora 16 machine?

2012-03-07 Thread Saša Tomić 


On 03/07/2012 03:20 PM, Itamar Heim wrote:

On 03/07/2012 03:38 PM, Saša Tomić wrote:

Hi to all,

Does anybody have step-by-step instructions how to install vdsm on an
empty Fedora 16 machine?
I need a git version of vdsm (to compile from source), so the binary
rpms will not do the work.


add host via engine with rpm's, then replace them?



Is this the recommended approach, or just a workaround?
Can I be sure that a "make install" will copy all the files to right 
places, and that I will not get crashes in the future because of the 
incomplete installation of vdsm?


How do you guys do it?

--
best regards,
Saša

___
vdsm-devel mailing list
vdsm-devel@lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/vdsm-devel

Re: [vdsm] Installing VDSM on an empty Fedora 16 machine?

2012-03-07 Thread Dan Kenigsberg 
On Wed, Mar 07, 2012 at 03:07:32PM +0100, Saša Tomić wrote:
> 
> On 03/07/2012 02:43 PM, Shu Ming wrote:
> >On 2012-3-7 21:38, Saša Tomić wrote:
> >>
> >>vdsClient -s 0 getVdsCaps
> >
> >Does "vdsClient  0 getVdsCaps" without '-s" work? "-s" means
> >secure connection.
> >
> yep, exactly the same...
> 
> Further:
> >[root@localhost log]# ls -lR /var/log/vdsm*
> >/var/log/vdsm:
> >total 4
> >drwxr-xr-x. 2 vdsm kvm 4096 Mar  6 16:26 backup
> >
> >/var/log/vdsm/backup:
> >total 0
> >
> >/var/log/vdsm-reg:
> >total 0
> 
> And
> >[root@localhost log]# grep vdsm /var/log/messages | tail
> >Mar  7 11:20:58 localhost yum[2306]: Installed:
> >vdsm-cli-4.9.4-0.91.git90795dd.fc16.noarch
> >Mar  7 14:25:12 localhost systemd[1]: Job vdsmd.service/start
> >failed with result 'dependency'.
> >Mar  7 14:25:14 localhost systemd-vdsmd[759]: vdsm: libvirt
> >already configured for vdsm [  OK  ]
> >Mar  7 14:25:14 localhost systemd-vdsmd[759]: Configuring sysctl
> >for vdsm...
> >Mar  7 14:25:14 localhost systemd-vdsmd[759]:
> >/proc/sys/net/bridge/bridge-nf-call-ip6tables: No such file or
> >directory
> >Mar  7 14:25:14 localhost systemd-vdsmd[759]:
> >/proc/sys/net/bridge/bridge-nf-call-iptables: No such file or
> >directory
> >Mar  7 14:25:14 localhost systemd-vdsmd[759]:
> >/proc/sys/net/bridge/bridge-nf-call-arptables: No such file or
> >directory
> >Mar  7 14:25:14 localhost systemd-vdsmd[759]: vdsm: failed to
> >reconfigure libvirt[FAILED]
> >Mar  7 14:25:14 localhost systemd[1]: vdsmd.service: control
> >process exited, code=exited status=255
> >Mar  7 14:25:14 localhost systemd[1]: Unit vdsmd.service entered
> >failed state.
> And
> >[root@localhost log]# ls -l /etc/init.d/vdsm*
> >ls: cannot access /etc/init.d/vdsm*: No such file or directory

That's empty because in Fedora vdsm uses the now-standard systemd
/lib/systemd/system/vdsmd.service

which for some reason fails to start.  Is libvirtd running?
systemctl status libvirtd.service
and the rest of dependencies listed in
Requires=multipathd.service libvirtd.service ntpd.service network.service

___
vdsm-devel mailing list
vdsm-devel@lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/vdsm-devel

Re: [vdsm] Installing VDSM on an empty Fedora 16 machine?

2012-03-07 Thread Itamar Heim 

On 03/07/2012 03:38 PM, Saša Tomić wrote:

Hi to all,

Does anybody have step-by-step instructions how to install vdsm on an
empty Fedora 16 machine?
I need a git version of vdsm (to compile from source), so the binary
rpms will not do the work.


add host via engine with rpm's, then replace them?



What I have so far is:
# for resolving the sanlock bug
sudo yum update --enablerepo=updates-testing
# installing additional packages for devel
sudo yum install @development-tools
sudo yum install fedora-packager
sudo yum install git autoconf automake gcc gcc-c++ pyflakes rpm-build
git clone http://gerrit.ovirt.org/p/vdsm.git
cd vdsm
./autogen.sh --system && make rpm
sudo yum -y install /home/stomic/rpmbuild/RPMS/x86_64/vdsm-*.rpm
/home/stomic/rpmbuild/RPMS/noarch/vdsm-cli*.rpm
vdsClient -s 0 getVdsCaps
#This should show you Vdsm's response about its capabilities, but returns:
# Connection to 0:54321 refused
sudo vdsClient -s 0 getVdsStats
# If I try as root, nothing changes:
# Connection to root@localhost.localdomain:54321 refused


Thank you in advance!
Sasha


___
vdsm-devel mailing list
vdsm-devel@lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/vdsm-devel


___
vdsm-devel mailing list
vdsm-devel@lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/vdsm-devel

Re: [vdsm] Installing VDSM on an empty Fedora 16 machine?

2012-03-07 Thread Saša Tomić 


On 03/07/2012 02:43 PM, Shu Ming wrote:

On 2012-3-7 21:38, Saša Tomić wrote:


vdsClient -s 0 getVdsCaps


Does "vdsClient  0 getVdsCaps" without '-s" work? "-s" means secure 
connection.



yep, exactly the same...

Further:

[root@localhost log]# ls -lR /var/log/vdsm*
/var/log/vdsm:
total 4
drwxr-xr-x. 2 vdsm kvm 4096 Mar  6 16:26 backup

/var/log/vdsm/backup:
total 0

/var/log/vdsm-reg:
total 0


And

[root@localhost log]# grep vdsm /var/log/messages | tail
Mar  7 11:20:58 localhost yum[2306]: Installed: 
vdsm-cli-4.9.4-0.91.git90795dd.fc16.noarch
Mar  7 14:25:12 localhost systemd[1]: Job vdsmd.service/start failed 
with result 'dependency'.
Mar  7 14:25:14 localhost systemd-vdsmd[759]: vdsm: libvirt already 
configured for vdsm [  OK  ]
Mar  7 14:25:14 localhost systemd-vdsmd[759]: Configuring sysctl for 
vdsm...
Mar  7 14:25:14 localhost systemd-vdsmd[759]: 
/proc/sys/net/bridge/bridge-nf-call-ip6tables: No such file or directory
Mar  7 14:25:14 localhost systemd-vdsmd[759]: 
/proc/sys/net/bridge/bridge-nf-call-iptables: No such file or directory
Mar  7 14:25:14 localhost systemd-vdsmd[759]: 
/proc/sys/net/bridge/bridge-nf-call-arptables: No such file or directory
Mar  7 14:25:14 localhost systemd-vdsmd[759]: vdsm: failed to 
reconfigure libvirt[FAILED]
Mar  7 14:25:14 localhost systemd[1]: vdsmd.service: control process 
exited, code=exited status=255
Mar  7 14:25:14 localhost systemd[1]: Unit vdsmd.service entered 
failed state.

And

[root@localhost log]# ls -l /etc/init.d/vdsm*
ls: cannot access /etc/init.d/vdsm*: No such file or directory


Any hints?

--
best regards,
Saša

___
vdsm-devel mailing list
vdsm-devel@lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/vdsm-devel

Re: [vdsm] safelease source location ?

2012-03-07 Thread Deepak C Shetty 

On 03/07/2012 07:19 PM, Deepak C Shetty wrote:

Hi,
I could not find the source for `/usr/libexec/vdsm/safelease` in 
the vdsm git.. which git / repo

do i need to look for ? thanks in advance.


My bad, thanks to ill formed search string ;-)
Got it under storage/protect/ dir of vdsm git.

___
vdsm-devel mailing list
vdsm-devel@lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/vdsm-devel


___
vdsm-devel mailing list
vdsm-devel@lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/vdsm-devel

[vdsm] safelease source location ?

2012-03-07 Thread Deepak C Shetty 

Hi,
I could not find the source for `/usr/libexec/vdsm/safelease` in 
the vdsm git.. which git / repo

do i need to look for ? thanks in advance.

___
vdsm-devel mailing list
vdsm-devel@lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/vdsm-devel

Re: [vdsm] Installing VDSM on an empty Fedora 16 machine?

2012-03-07 Thread Shu Ming 

On 2012-3-7 21:38, Saša Tomić wrote:

Hi to all,

Does anybody have step-by-step instructions how to install vdsm on an 
empty Fedora 16 machine?
I need a git version of vdsm (to compile from source), so the binary 
rpms will not do the work.


What I have so far is:
# for resolving the sanlock bug
sudo yum update --enablerepo=updates-testing
# installing additional packages for devel
sudo yum install @development-tools
sudo yum install fedora-packager
sudo yum install git autoconf automake gcc gcc-c++ pyflakes rpm-build
git clone http://gerrit.ovirt.org/p/vdsm.git
cd vdsm
./autogen.sh --system && make rpm
sudo yum -y install /home/stomic/rpmbuild/RPMS/x86_64/vdsm-*.rpm 
/home/stomic/rpmbuild/RPMS/noarch/vdsm-cli*.rpm

vdsClient -s 0 getVdsCaps


Does "vdsClient  0 getVdsCaps" without '-s" work? "-s" means secure 
connection.


  #This should show you Vdsm's response about its capabilities, but 
returns:

  # Connection to 0:54321 refused
sudo vdsClient -s 0 getVdsStats
  # If I try as root, nothing changes:
  # Connection to root@localhost.localdomain:54321 refused


Thank you in advance!
Sasha


___
vdsm-devel mailing list
vdsm-devel@lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/vdsm-devel



--
Shu Ming
IBM China Systems and Technology Laboratory


___
vdsm-devel mailing list
vdsm-devel@lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/vdsm-devel

[vdsm] Installing VDSM on an empty Fedora 16 machine?

2012-03-07 Thread Saša Tomić 

Hi to all,

Does anybody have step-by-step instructions how to install vdsm on an 
empty Fedora 16 machine?
I need a git version of vdsm (to compile from source), so the binary 
rpms will not do the work.


What I have so far is:
# for resolving the sanlock bug
sudo yum update --enablerepo=updates-testing
# installing additional packages for devel
sudo yum install @development-tools
sudo yum install fedora-packager
sudo yum install git autoconf automake gcc gcc-c++ pyflakes rpm-build
git clone http://gerrit.ovirt.org/p/vdsm.git
cd vdsm
./autogen.sh --system && make rpm
sudo yum -y install /home/stomic/rpmbuild/RPMS/x86_64/vdsm-*.rpm 
/home/stomic/rpmbuild/RPMS/noarch/vdsm-cli*.rpm

vdsClient -s 0 getVdsCaps
  #This should show you Vdsm's response about its capabilities, but 
returns:

  # Connection to 0:54321 refused
sudo vdsClient -s 0 getVdsStats
  # If I try as root, nothing changes:
  # Connection to root@localhost.localdomain:54321 refused


Thank you in advance!
Sasha


___
vdsm-devel mailing list
vdsm-devel@lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/vdsm-devel

Re: [vdsm] Kernel crash on FC16

2012-03-07 Thread Roi Dayan 
Tried it now with sudo to run the commands.
everything is ok.

I tried with vdsm again and here is what I see in vdsm.log
I did the cut after multiple call to lvcreate for outbox,leases,.. etc
last one is master, then there is a call to chown and mkfs.
from here mkfs did fail and kernel crashed.


--
Thread-154::DEBUG::2012-03-07
11:00:14,560::lvm::956::Storage.Misc.excCmd::(createLV) '/usr/bin/sudo -n
/bin/chown vdsm:qemu /dev/18706999-9fab-45ab-9d29-75f2eaa225aa/master' (cwd
None)
Thread-154::DEBUG::2012-03-07
11:00:14,577::lvm::956::Storage.Misc.excCmd::(createLV) SUCCESS:  =
'';  = 0
Thread-154::DEBUG::2012-03-07
11:00:14,578::blockSD::1036::Storage.Misc.excCmd::(_createVMSfs)
'/usr/bin/sudo -n /sbin/mkfs -q -j -E nodiscard
/dev/18706999-9fab-45ab-9d29-75f2eaa225aa/master' (cwd None)
Thread-154::DEBUG::2012-03-07
11:00:15,112::blockSD::1036::Storage.Misc.excCmd::(_createVMSfs) FAILED:
 = '';  = 139
Thread-154::ERROR::2012-03-07
11:00:15,113::task::853::TaskManager.Task::(_setError)
Task=`349abfb0-1838-4a6f-9b95-6521ad880cb2`::Unexpected error
Traceback (most recent call last):
  File "/usr/share/vdsm/storage/task.py", line 861, in _run
return fn(*args, **kargs)
  File "/usr/share/vdsm/logUtils.py", line 38, in wrapper
res = f(*args, **kwargs)
  File "/usr/share/vdsm/storage/hsm.py", line 2072, in createStorageDomain
domClass, typeSpecificArg, storageType, domVersion)
  File "/usr/share/vdsm/storage/blockSD.py", line 357, in create
_createVMSfs(os.path.join("/dev", vgName, MASTERLV))
  File "/usr/share/vdsm/storage/blockSD.py", line 1038, in _createVMSfs
raise se.MkfsError(dev)
MkfsError: Cannot create filesystem on device:
('/dev/18706999-9fab-45ab-9d29-75f2eaa225aa/master',)
Thread-154::DEBUG::2012-03-07
11:00:15,120::task::872::TaskManager.Task::(_run)
Task=`349abfb0-1838-4a6f-9b95-6521ad880cb2`::Task._run:
349abfb0-1838-4a6f-9b95-6521ad880cb2 (3,
'18706999-9fab-45ab-9d29-75f2eaa225aa', 'xx',
'hkDKBq-XAjX-qE1A-WCi7-Sttt-Lmos-uzVqR7', 1, '2') {} failed - stopping task
Thread-154::DEBUG::2012-03-07
11:00:15,120::task::1199::TaskManager.Task::(stop)
Task=`349abfb0-1838-4a6f-9b95-6521ad880cb2`::stopping in state preparing
(force False)
Thread-154::DEBUG::2012-03-07
11:00:15,120::task::978::TaskManager.Task::(_decref)
Task=`349abfb0-1838-4a6f-9b95-6521ad880cb2`::ref 1 aborting True
Thread-154::INFO::2012-03-07
11:00:15,121::task::1157::TaskManager.Task::(prepare)
Task=`349abfb0-1838-4a6f-9b95-6521ad880cb2`::aborting: Task is aborted:
'Cannot create filesystem on device' - code 608
Thread-154::DEBUG::2012-03-07
11:00:15,121::task::1162::TaskManager.Task::(prepare)
Task=`349abfb0-1838-4a6f-9b95-6521ad880cb2`::Prepare: aborted: Cannot
create filesystem on device
Thread-154::DEBUG::2012-03-07
11:00:15,122::task::978::TaskManager.Task::(_decref)
Task=`349abfb0-1838-4a6f-9b95-6521ad880cb2`::ref 0 aborting True
Thread-154::DEBUG::2012-03-07
11:00:15,122::task::913::TaskManager.Task::(_doAbort)
Task=`349abfb0-1838-4a6f-9b95-6521ad880cb2`::Task._doAbort: force False
Thread-154::DEBUG::2012-03-07
11:00:15,123::resourceManager::844::ResourceManager.Owner::(cancelAll)
Owner.cancelAll requests {}
Thread-154::DEBUG::2012-03-07
11:00:15,123::task::588::TaskManager.Task::(_updateState)
Task=`349abfb0-1838-4a6f-9b95-6521ad880cb2`::moving from state preparing ->
state aborting
Thread-154::DEBUG::2012-03-07
11:00:15,123::task::537::TaskManager.Task::(__state_aborting)
Task=`349abfb0-1838-4a6f-9b95-6521ad880cb2`::_aborting: recover policy none
Thread-154::DEBUG::2012-03-07
11:00:15,124::task::588::TaskManager.Task::(_updateState)
Task=`349abfb0-1838-4a6f-9b95-6521ad880cb2`::moving from state aborting ->
state failed
Thread-154::DEBUG::2012-03-07
11:00:15,124::resourceManager::809::ResourceManager.Owner::(releaseAll)
Owner.releaseAll requests {} resources {}
Thread-154::DEBUG::2012-03-07
11:00:15,125::resourceManager::844::ResourceManager.Owner::(cancelAll)
Owner.cancelAll requests {}
Thread-154::ERROR::2012-03-07
11:00:15,125::dispatcher::90::Storage.Dispatcher.Protect::(run) {'status':
{'message': "Cannot create filesystem on device:
('/dev/18706999-9fab-45ab-9d29-75f2eaa225aa/master',)", 'code': 608}}
Thread-157::DEBUG::2012-03-07
11:00:18,916::task::588::TaskManager.Task::(_updateState)
Task=`55a87a6e-6d63-4b40-94a5-1244cd7eb2aa`::moving from state init ->
state preparing
Thread-157::INFO::2012-03-07
11:00:18,917::logUtils::37::dispatcher::(wrapper) Run and protect:
repoStats(options=None)
Thread-157::INFO::2012-03-07
11:00:18,918::logUtils::39::dispatcher::(wrapper) Run and protect:
repoStats, Return response: {}
Thread-157::DEBUG::2012-03-07
11:00:18,918::task::1172::TaskManager.Task::(prepare)
Task=`55a87a6e-6d63-4b40-94a5-1244cd7eb2aa`::finished: {}
Thread-157::DEBUG::2012-03-07
11:00:18,919::task::588::TaskManager.Task::(_updateState)
Task=`55a87a6e-6d63-4b40-94a5-1244cd7eb2aa`::moving from state preparing ->
state finished
Thread-157::DEBUG::2012-03-07
11:00:18,919::resourceManager::809::Resource

Re: [vdsm] Kernel crash on FC16

2012-03-07 Thread Deepak C Shetty 

On 03/07/2012 01:35 PM, Roi Dayan wrote:

tried it.
I don't have any problems.



Wondering if trying as user vdsm will reproduce ? Might be worth trying.
su - vdsm -s /bin/bash





On Wed, Mar 7, 2012 at 12:14 AM, Saggi Mizrahi > wrote:


Could you try and run:
`mkfs.ext2 -q -j -E nodiscard /dev/lun`
where lun is a lun on said target.
If nothing crashes.
Could you please create a VG and an LV on a lun and run the same
command on the LV.

I assume one of these will reproduce the crash.

- Original Message -
> From: "Roi Dayan" mailto:roi.da...@gmail.com>>
> To: "Saggi Mizrahi" mailto:smizr...@redhat.com>>
> Cc: "Or Gerlitz" mailto:ogerl...@mellanox.com>>, "Itzik Brown"
mailto:itz...@mellanox.com>>,
vdsm-devel@lists.fedorahosted.org

> Sent: Tuesday, March 6, 2012 4:17:45 PM
> Subject: Re: [vdsm] Kernel crash on FC16
>
>
>
> Yes happens all the time.
> It's a normal iscsi target over 1GbE
>
> Roi
>
> On 6 במרץ 2012, at 23:14, Saggi Mizrahi < smizr...@redhat.com
 >
> wrote:
>
>
>
>
>
> Is it reproducible?
>
> - Original Message -
>
>
> From: "Roi Dayan" < roi.da...@gmail.com
 >
>
>
> To: vdsm-devel@lists.fedorahosted.org

>
>
> Cc: "Or Gerlitz" < ogerl...@mellanox.com
 >, "Itzik Brown" <
> itz...@mellanox.com  >
>
>
> Sent: Tuesday, March 6, 2012 11:09:15 AM
>
>
> Subject: [vdsm] Kernel crash on FC16
>
>
>
>
>
>
>
>
>
>
>
> Hi,
>
>
>
>
>
>
>
>
> After discovery I select a LUN and give it a name, I click OK and I
>
>
> get a kernel crash.
>
>
> The kernel version is 3.1.0-7
>
>
> I pasted the log below.
>
>
> Any idea?
>
>
>
>
>
>
>
>
> Thanks,
>
>
> Roi
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Mar 6 18:00:55 xena018 kernel: [ 339.762969] [ cut here
>
>
> ]
>
>
>
>
>
> Mar 6 18:00:55 xena018 kernel: [ 339.763233] kernel BUG at
>
>
> block/blk-flush.c:323!
>
>
>
>
>
> Mar 6 18:00:55 xena018 kernel: [ 339.763496] invalid opcode: 
>
>
> [#1] SMP
>
>
>
>
>
> Mar 6 18:00:55 xena018 kernel: [ 339.763839] CPU 6
>
>
>
>
>
> Mar 6 18:00:55 xena018 kernel: [ 339.763885] Modules linked in:
>
>
> ebtable_nat ebtables 8021q garp bonding lockd bridge stp llc
>
>
> be2iscsi iscsi_boot_sysfs bnx2i cnic uio cxgb4i cxgb4 cxgb3i
>
>
> libcxgbi cxgb3 mdio iscsi_tcp libiscsi_tcp libiscsi
>
>
> scsi_transport_iscsi ib_ipoib rdma_ucm xt_multiport ib_ucm ib_uverbs
>
>
> ib_umad rdma_cm ib_cm ip6t_REJECT iw_cm nf_conntrack_ipv6
>
>
> nf_defrag_ipv6 xt_state ib_addr nf_conntrack ip6table_filter ib_sa
>
>
> ip6_tables dm_round_robin dm_multipath mlx4_ib ib_mad ib_core sunrpc
>
>
> vhost_net igb i7core_edac edac_core i2c_i801 ioatdma macvtap macvlan
>
>
> tun virtio_net iTCO_wdt i2c_core kvm_intel iTCO_vendor_support dca
>
>
> kvm joydev mlx4_core serio_raw microcode uinput [last unloaded:
>
>
> ib_iser]
>
>
>
>
>
> Mar 6 18:00:55 xena018 kernel: [ 339.769133]
>
>
>
>
>
> Mar 6 18:00:55 xena018 kernel: [ 339.769387] Pid: 3217, comm:
>
>
> mkfs.ext2 Not tainted 3.1.0-7.fc16.x86_64 #1 Supermicro X8DTU/X8DTU
>
>
>
>
>
> Mar 6 18:00:55 xena018 kernel: [ 339.77] RIP:
>
>
> 0010:[] []
>
>
> blk_insert_flush+0x84/0x101
>
>
>
>
>
> Mar 6 18:00:55 xena018 kernel: [ 339.770529] RSP:
>
>
> 0018:880629ab3c28 EFLAGS: 00010046
>
>
>
>
>
> Mar 6 18:00:55 xena018 kernel: [ 339.770785] RAX: 
>
>
> RBX: 880319410e30 RCX: 08018215
>
>
>
>
>
> Mar 6 18:00:55 xena018 kernel: [ 339.771050] RDX: 
>
>
> RSI: 0001 RDI: 8806291cd008
>
>
>
>
>
> Mar 6 18:00:55 xena018 kernel: [ 339.771314] RBP: 880629ab3c38
>
>
> R08: 8806291cd008 R09: 0001
>
>
>
>
>
> Mar 6 18:00:55 xena018 kernel: [ 339.771571] R10: 0001
>
>
> R11: 880622982378 R12: 880319410e30
>
>
>
>
>

Re: [vdsm] Kernel crash on FC16

2012-03-07 Thread Roi Dayan 
tried it.
I don't have any problems.



On Wed, Mar 7, 2012 at 12:14 AM, Saggi Mizrahi  wrote:

> Could you try and run:
> `mkfs.ext2 -q -j -E nodiscard /dev/lun`
> where lun is a lun on said target.
> If nothing crashes.
> Could you please create a VG and an LV on a lun and run the same command
> on the LV.
>
> I assume one of these will reproduce the crash.
>
> - Original Message -
> > From: "Roi Dayan" 
> > To: "Saggi Mizrahi" 
> > Cc: "Or Gerlitz" , "Itzik Brown" <
> itz...@mellanox.com>, vdsm-devel@lists.fedorahosted.org
> > Sent: Tuesday, March 6, 2012 4:17:45 PM
> > Subject: Re: [vdsm] Kernel crash on FC16
> >
> >
> >
> > Yes happens all the time.
> > It's a normal iscsi target over 1GbE
> >
> > Roi
> >
> > On 6 במרץ 2012, at 23:14, Saggi Mizrahi < smizr...@redhat.com >
> > wrote:
> >
> >
> >
> >
> >
> > Is it reproducible?
> >
> > - Original Message -
> >
> >
> > From: "Roi Dayan" < roi.da...@gmail.com >
> >
> >
> > To: vdsm-devel@lists.fedorahosted.org
> >
> >
> > Cc: "Or Gerlitz" < ogerl...@mellanox.com >, "Itzik Brown" <
> > itz...@mellanox.com >
> >
> >
> > Sent: Tuesday, March 6, 2012 11:09:15 AM
> >
> >
> > Subject: [vdsm] Kernel crash on FC16
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Hi,
> >
> >
> >
> >
> >
> >
> >
> >
> > After discovery I select a LUN and give it a name, I click OK and I
> >
> >
> > get a kernel crash.
> >
> >
> > The kernel version is 3.1.0-7
> >
> >
> > I pasted the log below.
> >
> >
> > Any idea?
> >
> >
> >
> >
> >
> >
> >
> >
> > Thanks,
> >
> >
> > Roi
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Mar 6 18:00:55 xena018 kernel: [ 339.762969] [ cut here
> >
> >
> > ]
> >
> >
> >
> >
> >
> > Mar 6 18:00:55 xena018 kernel: [ 339.763233] kernel BUG at
> >
> >
> > block/blk-flush.c:323!
> >
> >
> >
> >
> >
> > Mar 6 18:00:55 xena018 kernel: [ 339.763496] invalid opcode: 
> >
> >
> > [#1] SMP
> >
> >
> >
> >
> >
> > Mar 6 18:00:55 xena018 kernel: [ 339.763839] CPU 6
> >
> >
> >
> >
> >
> > Mar 6 18:00:55 xena018 kernel: [ 339.763885] Modules linked in:
> >
> >
> > ebtable_nat ebtables 8021q garp bonding lockd bridge stp llc
> >
> >
> > be2iscsi iscsi_boot_sysfs bnx2i cnic uio cxgb4i cxgb4 cxgb3i
> >
> >
> > libcxgbi cxgb3 mdio iscsi_tcp libiscsi_tcp libiscsi
> >
> >
> > scsi_transport_iscsi ib_ipoib rdma_ucm xt_multiport ib_ucm ib_uverbs
> >
> >
> > ib_umad rdma_cm ib_cm ip6t_REJECT iw_cm nf_conntrack_ipv6
> >
> >
> > nf_defrag_ipv6 xt_state ib_addr nf_conntrack ip6table_filter ib_sa
> >
> >
> > ip6_tables dm_round_robin dm_multipath mlx4_ib ib_mad ib_core sunrpc
> >
> >
> > vhost_net igb i7core_edac edac_core i2c_i801 ioatdma macvtap macvlan
> >
> >
> > tun virtio_net iTCO_wdt i2c_core kvm_intel iTCO_vendor_support dca
> >
> >
> > kvm joydev mlx4_core serio_raw microcode uinput [last unloaded:
> >
> >
> > ib_iser]
> >
> >
> >
> >
> >
> > Mar 6 18:00:55 xena018 kernel: [ 339.769133]
> >
> >
> >
> >
> >
> > Mar 6 18:00:55 xena018 kernel: [ 339.769387] Pid: 3217, comm:
> >
> >
> > mkfs.ext2 Not tainted 3.1.0-7.fc16.x86_64 #1 Supermicro X8DTU/X8DTU
> >
> >
> >
> >
> >
> > Mar 6 18:00:55 xena018 kernel: [ 339.77] RIP:
> >
> >
> > 0010:[] []
> >
> >
> > blk_insert_flush+0x84/0x101
> >
> >
> >
> >
> >
> > Mar 6 18:00:55 xena018 kernel: [ 339.770529] RSP:
> >
> >
> > 0018:880629ab3c28 EFLAGS: 00010046
> >
> >
> >
> >
> >
> > Mar 6 18:00:55 xena018 kernel: [ 339.770785] RAX: 
> >
> >
> > RBX: 880319410e30 RCX: 08018215
> >
> >
> >
> >
> >
> > Mar 6 18:00:55 xena018 kernel: [ 339.771050] RDX: 
> >
> >
> > RSI: 0001 RDI: 8806291cd008
> >
> >
> >
> >
> >
> > Mar 6 18:00:55 xena018 kernel: [ 339.771314] RBP: 880629ab3c38
> >
> >
> > R08: 8806291cd008 R09: 0001
> >
> >
> >
> >
> >
> > Mar 6 18:00:55 xena018 kernel: [ 339.771571] R10: 0001
> >
> >
> > R11: 880622982378 R12: 880319410e30
> >
> >
> >
> >
> >
> > Mar 6 18:00:55 xena018 kernel: [ 339.771827] R13: 0046
> >
> >
> > R14: 0005 R15: 88061f0c4c00
> >
> >
> >
> >
> >
> > Mar 6 18:00:55 xena018 kernel: [ 339.772085] FS:
> >
> >
> > 7fedacb44780() GS:88063fc0()
> >
> >
> > knlGS:
> >
> >
> >
> >
> >
> > Mar 6 18:00:55 xena018 kernel: [ 339.772542] CS: 0010 DS:  ES:
> >
> >
> >  CR0: 80050033
> >
> >
> >
> >
> >
> > Mar 6 18:00:55 xena018 kernel: [ 339.772794] CR2: 017f4e70
> >
> >
> > CR3: 000628c25000 CR4: 06e0
> >
> >
> >
> >
> >
> > Mar 6 18:00:55 xena018 kernel: [ 339.773056] DR0: 
> >
> >
> > DR1:  DR2: 
> >
> >
> >
> >
> >
> > Mar 6 18:00:55 xena018 kernel: [ 339.773316] DR3: 
> >
> >
> > DR6: 0ff0 DR7: 0400
> >
> >
> >
> >
> >
> > Mar 6 18:00:55 xena018 kernel: [ 339.773573] Process mkfs.ext2 (pid:
> >
> >
> > 3217, threadinfo 880629ab2000,