ssible suggestions:
>
> - scarier option names, like
> - a separate config option that allows any experimental option
> - enumerate experiemntal options we want to enable
> Other ideas?
A separate config file for experimental options:
/etc/ceph/danger-danger.conf
--
D
date, but to try not to deal with now. Maybe the
bind mount of /dev/rbd/rbd will do for now.
--
David Champion • d...@uchicago.edu • University of Chicago
Enrico Fermi Institute • Computation Institute • USATLAS Midwest Tier 2
OSG Connect • CI Connect
__
an set this directly in ceph.conf,
though, right? This is the advice I've seen before. Is a restart of
ceph-mds sufficient to make that work, or would something need to be
recreated?
--
David Champion • d...@uchicago.edu • University of Chicago
Enrico Fermi Institute • Computation In
;m looking at a bind/loopback mount of
> > /dev/rbd/rbd into the user-visible namespace?
>
> No, definitely no mapping of RBD into CephFS. It's a completely
> different data format.
OK, thanks. I thought there might be a logical layer that allows
mapping the raw blocks as se
the CephFS mount to users, but not
/dev. Is there a way to map the RBD as a pseudo-file within the CephFS
mount? If not, then perhaps I'm looking at a bind/loopback mount of
/dev/rbd/rbd into the user-visible namespace?
Thanks for information and suggestions.
--
David Champion • d..
