Am 28.02.2018 um 16:09 schrieb Patrick Donnelly:
> On Tue, Feb 27, 2018 at 3:27 PM, Oliver Freyermuth
> wrote:
>> As you can see:
>> - Name collision for admin socket, since the helper is already running.
>
> You can change the admin socket path using the `admin socket` config
> variable. Use met
On Tue, Feb 27, 2018 at 3:27 PM, Oliver Freyermuth
wrote:
> As you can see:
> - Name collision for admin socket, since the helper is already running.
You can change the admin socket path using the `admin socket` config
variable. Use metavariables [1] to make the path unique.
> - A second helper
Am 28.02.2018 um 15:18 schrieb David Turner:
> If you run your container in privileged mode you can mount ceph-fuse inside
> of the VMs instead of from the shared resource on the host. I used a
> configuration like this to test multi-tenency speed tests of CephFS using
> ceph-fuse. The more moun
If you run your container in privileged mode you can mount ceph-fuse inside
of the VMs instead of from the shared resource on the host. I used a
configuration like this to test multi-tenency speed tests of CephFS using
ceph-fuse. The more mount points I used 1 per container, the more bandwidth
I wa
Dear Cephalopodians,
continuing a bit on the point raised in the other thread ( "CephFS very
unstable with many small files" )
concerning the potentially unexpected behaviour of the ceph-fuse client with
regard to mount namespaces I did a first small experiment.
First off: I did not see any ba
