* session lost, hunting for new mon @ 2012-05-19 5:22 Stefan Priebe 2012-05-19 6:08 ` Josh Durgin 0 siblings, 1 reply; 6+ messages in thread From: Stefan Priebe @ 2012-05-19 5:22 UTC (permalink / raw) To: ceph-devel Hi, while doing my first tests with ceph i'm always struggling about these kernel messages: [ 273.332472] libceph: client0 fsid d3aa8d88-3aa8-4f74-bb87-aa8de4975a84 [ 273.351025] libceph: mon1 10.0.255.101:6789 session established [ 459.830296] libceph: mon1 10.0.255.101:6789 socket closed [ 459.847044] libceph: mon1 10.0.255.101:6789 session lost, hunting for new mon [ 472.226073] libceph: mon0 10.0.255.100:6789 session established Always while stress testing the session to the mon's got lost. Any ideas? Stefan ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: session lost, hunting for new mon 2012-05-19 5:22 session lost, hunting for new mon Stefan Priebe @ 2012-05-19 6:08 ` Josh Durgin 2012-05-19 8:13 ` Stefan Priebe 2012-05-20 4:33 ` qemu-rdb questions Alexandre DERUMIER 0 siblings, 2 replies; 6+ messages in thread From: Josh Durgin @ 2012-05-19 6:08 UTC (permalink / raw) To: Stefan Priebe; +Cc: ceph-devel On 05/18/2012 10:22 PM, Stefan Priebe wrote: > Hi, > > while doing my first tests with ceph i'm always struggling about these > kernel messages: > > [ 273.332472] libceph: client0 fsid d3aa8d88-3aa8-4f74-bb87-aa8de4975a84 > [ 273.351025] libceph: mon1 10.0.255.101:6789 session established > [ 459.830296] libceph: mon1 10.0.255.101:6789 socket closed > [ 459.847044] libceph: mon1 10.0.255.101:6789 session lost, hunting for > new mon > [ 472.226073] libceph: mon0 10.0.255.100:6789 session established > > Always while stress testing the session to the mon's got lost. Any ideas? These aren't a problem - it's just the connection to a monitor being lost, and the client connecting to another one. ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: session lost, hunting for new mon 2012-05-19 6:08 ` Josh Durgin @ 2012-05-19 8:13 ` Stefan Priebe 2012-05-20 4:33 ` qemu-rdb questions Alexandre DERUMIER 1 sibling, 0 replies; 6+ messages in thread From: Stefan Priebe @ 2012-05-19 8:13 UTC (permalink / raw) To: Josh Durgin; +Cc: ceph-devel Am 19.05.2012 08:08, schrieb Josh Durgin: > On 05/18/2012 10:22 PM, Stefan Priebe wrote: >> Hi, >> >> while doing my first tests with ceph i'm always struggling about these >> kernel messages: >> >> [ 273.332472] libceph: client0 fsid d3aa8d88-3aa8-4f74-bb87-aa8de4975a84 >> [ 273.351025] libceph: mon1 10.0.255.101:6789 session established >> [ 459.830296] libceph: mon1 10.0.255.101:6789 socket closed >> [ 459.847044] libceph: mon1 10.0.255.101:6789 session lost, hunting for >> new mon >> [ 472.226073] libceph: mon0 10.0.255.100:6789 session established >> >> Always while stress testing the session to the mon's got lost. Any ideas? > > These aren't a problem - it's just the connection to a monitor being > lost, and the client connecting to another one. But what is causing this? I'm also seeing: [ 623.554698] ceph: mds0 caps stale [ 650.190504] ceph: mds0 caps renewed My biggest problem is that random reads and writes are awfully slow. Stefan ^ permalink raw reply [flat|nested] 6+ messages in thread
* qemu-rdb questions 2012-05-19 6:08 ` Josh Durgin 2012-05-19 8:13 ` Stefan Priebe @ 2012-05-20 4:33 ` Alexandre DERUMIER 2012-05-21 6:07 ` Josh Durgin 1 sibling, 1 reply; 6+ messages in thread From: Alexandre DERUMIER @ 2012-05-20 4:33 UTC (permalink / raw) To: ceph-devel Hi, i'm planning to do rdb integration in proxmox2 kvm distribution (not using libvirt). I found some doc here http://ceph.com/wiki/QEMU-RBD and also in libvirt mailing list. some questions: qemu drive command line : ------------------------- -drive file=rbd:pool/image:id=myname:key=QVFDVm41aE82SHpGQWhBQXEwTkN2OGp0SmNJY0UrSE9CbE1RMUE=:auth_supported=cephx none:mon_host=mon1.example.org\:6321\;mon2.example.org\:6322\;mon3.example.org\:6322,if=virtio,format=raw is it the right syntax ? for image management, what is the best way ? qemu-img or rdb ? rdb creation with qemu-img: ---------------------------- qemu-img create -f rbd rbd:data/foo 10G how to specify monitor, authentification,.... ? rdb delete/resize with qemu-img? -------------------------------- don't find any infos. rdb commands ------------ Is the rdb kernel module require to use rdb command ? Also,I would like to not have any /dev/rdbx device on my client. Regards, -Alexandre ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: qemu-rdb questions 2012-05-20 4:33 ` qemu-rdb questions Alexandre DERUMIER @ 2012-05-21 6:07 ` Josh Durgin 2012-05-21 8:52 ` Alexandre DERUMIER 0 siblings, 1 reply; 6+ messages in thread From: Josh Durgin @ 2012-05-21 6:07 UTC (permalink / raw) To: Alexandre DERUMIER; +Cc: ceph-devel On 05/19/2012 09:33 PM, Alexandre DERUMIER wrote: > Hi, > i'm planning to do rdb integration in proxmox2 kvm distribution (not using libvirt). > > I found some doc here > http://ceph.com/wiki/QEMU-RBD > and also in libvirt mailing list. > > > some questions: > > qemu drive command line : > ------------------------- > -drive file=rbd:pool/image:id=myname:key=QVFDVm41aE82SHpGQWhBQXEwTkN2OGp0SmNJY0UrSE9CbE1RMUE=:auth_supported=cephx none:mon_host=mon1.example.org\:6321\;mon2.example.org\:6322\;mon3.example.org\:6322,if=virtio,format=raw > > is it the right syntax ? Newer qemu doesn't like the space in auth_supported, so you'll want to use a semicolon instead: -drive file=rbd:pool/image:id=myname:key=QVFDVm41aE82SHpGQWhBQXEwTkN2OGp0SmNJY0UrSE9CbE1RMUE=:auth_supported=cephx;none:mon_host=mon1.example.org\:6321\;mon2.example.org\:6322\;mon3.example.org\:6322,if=virtio,format=raw The key/value pairs separated by colons are Ceph configuration options. The above drive line is equivalent the following settings: /path/to/myname.keyring containing the keyring for myname, as shown by 'ceph auth list'. /etc/ceph/ceph.conf containing: [client.myname] keyring = /path/to/myname.keyring auth supported = cephx none mon host = mon1.example.org:6321;mon2.example.org:6322;mon3.example.org:6322 And a drive line like: -drive file=rbd:pool/image:id=myname,if=virtio,format=raw Qemu reads the from the ceph.conf file if it exists. Any extra options you add override those from the configuration file. You can have it read from another file by adding ':conf=/path/to/file'. > > > for image management, what is the best way ? qemu-img or rdb ? > > rdb creation with qemu-img: > ---------------------------- > qemu-img create -f rbd rbd:data/foo 10G > > how to specify monitor, authentification,.... ? > > rdb delete/resize with qemu-img? > -------------------------------- > don't find any infos. The rbd tool has more features. As you noticed, qemu doesn't know how to delete images. It also can't rename them. I'm not sure if qemu-img lets you resize them. The monitor and auth options for qemu-img are the same as for qemu's -drive syntax. You can configure them in /etc/ceph/ceph.conf, or on the command line. For the rbd tool, if you don't want to use a configuration file, the options would be: rbd --mon-host 'mon1.example.org:6321;mon2.example.org:6322;mon3.example.org:6322' --keyring /path/to/keyring --id myname --auth-supported 'cephx;none' These are generic ceph options, and work with any ceph command. They can also be set in the CEPH_ARGS environment variable. > > > rdb commands > ------------ > Is the rdb kernel module require to use rdb command ? Nope, it's only needed if you want to have /dev/rbd devices on your hosts. > Also,I would like to not have any /dev/rdbx device on my client. qemu goes directly through the userspace librbd to access rbd images. The rbd kernel module isn't involved at all, and no devices appear on the host. The guest does not know it's using rbd; it sees a block device, just as if you were using e.g. a qcow2 file. Josh ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: qemu-rdb questions 2012-05-21 6:07 ` Josh Durgin @ 2012-05-21 8:52 ` Alexandre DERUMIER 0 siblings, 0 replies; 6+ messages in thread From: Alexandre DERUMIER @ 2012-05-21 8:52 UTC (permalink / raw) To: Josh Durgin; +Cc: ceph-devel Thanks Josh, this is very clear ! ----- Mail original ----- De: "Josh Durgin" <josh.durgin@inktank.com> À: "Alexandre DERUMIER" <aderumier@odiso.com> Cc: ceph-devel@vger.kernel.org Envoyé: Lundi 21 Mai 2012 08:07:59 Objet: Re: qemu-rdb questions On 05/19/2012 09:33 PM, Alexandre DERUMIER wrote: > Hi, > i'm planning to do rdb integration in proxmox2 kvm distribution (not using libvirt). > > I found some doc here > http://ceph.com/wiki/QEMU-RBD > and also in libvirt mailing list. > > > some questions: > > qemu drive command line : > ------------------------- > -drive file=rbd:pool/image:id=myname:key=QVFDVm41aE82SHpGQWhBQXEwTkN2OGp0SmNJY0UrSE9CbE1RMUE=:auth_supported=cephx none:mon_host=mon1.example.org\:6321\;mon2.example.org\:6322\;mon3.example.org\:6322,if=virtio,format=raw > > is it the right syntax ? Newer qemu doesn't like the space in auth_supported, so you'll want to use a semicolon instead: -drive file=rbd:pool/image:id=myname:key=QVFDVm41aE82SHpGQWhBQXEwTkN2OGp0SmNJY0UrSE9CbE1RMUE=:auth_supported=cephx;none:mon_host=mon1.example.org\:6321\;mon2.example.org\:6322\;mon3.example.org\:6322,if=virtio,format=raw The key/value pairs separated by colons are Ceph configuration options. The above drive line is equivalent the following settings: /path/to/myname.keyring containing the keyring for myname, as shown by 'ceph auth list'. /etc/ceph/ceph.conf containing: [client.myname] keyring = /path/to/myname.keyring auth supported = cephx none mon host = mon1.example.org:6321;mon2.example.org:6322;mon3.example.org:6322 And a drive line like: -drive file=rbd:pool/image:id=myname,if=virtio,format=raw Qemu reads the from the ceph.conf file if it exists. Any extra options you add override those from the configuration file. You can have it read from another file by adding ':conf=/path/to/file'. > > > for image management, what is the best way ? qemu-img or rdb ? > > rdb creation with qemu-img: > ---------------------------- > qemu-img create -f rbd rbd:data/foo 10G > > how to specify monitor, authentification,.... ? > > rdb delete/resize with qemu-img? > -------------------------------- > don't find any infos. The rbd tool has more features. As you noticed, qemu doesn't know how to delete images. It also can't rename them. I'm not sure if qemu-img lets you resize them. The monitor and auth options for qemu-img are the same as for qemu's -drive syntax. You can configure them in /etc/ceph/ceph.conf, or on the command line. For the rbd tool, if you don't want to use a configuration file, the options would be: rbd --mon-host 'mon1.example.org:6321;mon2.example.org:6322;mon3.example.org:6322' --keyring /path/to/keyring --id myname --auth-supported 'cephx;none' These are generic ceph options, and work with any ceph command. They can also be set in the CEPH_ARGS environment variable. > > > rdb commands > ------------ > Is the rdb kernel module require to use rdb command ? Nope, it's only needed if you want to have /dev/rbd devices on your hosts. > Also,I would like to not have any /dev/rdbx device on my client. qemu goes directly through the userspace librbd to access rbd images. The rbd kernel module isn't involved at all, and no devices appear on the host. The guest does not know it's using rbd; it sees a block device, just as if you were using e.g. a qcow2 file. Josh -- -- Alexandre D erumier Ingénieur Système Fixe : 03 20 68 88 90 Fax : 03 20 68 90 81 45 Bvd du Général Leclerc 59100 Roubaix - France 12 rue Marivaux 75002 Paris - France -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2012-05-21 8:53 UTC | newest] Thread overview: 6+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2012-05-19 5:22 session lost, hunting for new mon Stefan Priebe 2012-05-19 6:08 ` Josh Durgin 2012-05-19 8:13 ` Stefan Priebe 2012-05-20 4:33 ` qemu-rdb questions Alexandre DERUMIER 2012-05-21 6:07 ` Josh Durgin 2012-05-21 8:52 ` Alexandre DERUMIER
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.