I believe this is a result of how we used the kernel interfaces (allocating a major device ID for each RBD volume), and some kernel limits (only 8 bits for storing major device IDs, and some used for other purposes). See http://tracker.ceph.com/issues/5048 I believe we have discussed not using a major device ID for each mounted RBD volume, but I don't remember the details as they involved kernel-fu beyond what I'm familiar with. -Greg Software Engineer #42 @ http://inktank.com | http://ceph.com On Tue, Oct 8, 2013 at 10:19 AM, Gaylord Holder <gholder@xxxxxxxxxxxxx> wrote: > I'm testing how many rbds I can map on a single server. > > I've created 10,000 rbds in the rbd pool, but I can only actually map 230. > > Mapping the 230th one fails with: > rbd: add failed: (16) Device or resource busy > > Is there a way to bump this up? > > -Gaylord > > _______________________________________________ > ceph-users mailing list > ceph-users@xxxxxxxxxxxxxx > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |