On 03/25/2013 06:03 AM, Dan van der Ster wrote: > Hi, > Apologies if this is already a known bug (though I didn't find it). > > If we try to map a device that doesn't exist, we get an immediate and > reproduceable kernel BUG (see the P.S.). We hit this by accident > because we forgot to add the --pool <ourpool>. > > This works: > > [root@afs245 /]# rbd map afs254-vicepa --pool afs --id afs --keyring > /etc/ceph/ceph.client.afs.keyring > [root@afs245 /]# rbd showmapped > id pool image snap device > 1 afs afs254-vicepa - /dev/rbd1 > > But this BUGS: > > [root@afs245 /]# rbd map afs254-vicepa > BUG... > > Any clue? Yes. You've found a bug in the kernel rbd client, and I've posted a fix for review. The reason you're hitting the bug is because your "map" command is not supplying the pool name for the image you want to map. You have no image named "afs254-vicepa" in the default pool (named "rbd"). To identify what you want to map you need to indicate which pool it's defined in, using "--pool=afs" (or "--pool afs"). The kernel bug is occurring because it wasn't properly handling the case where the image was not found. Thanks for calling attention to this, and I'm sorry you hit it. -Alex > Cheers, > Dan, CERN IT . . . _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |