It is great having access to features that are not fully production
ready, but it would be nice to know which Ceph features are ready and
which are not. Just like Ceph File System is well marked that it is
not yet fully ready for production, it would be nice if rbd-fuse could
be marked as not
On Wed, Jul 29, 2015 at 11:42 PM, pixelfairy pixelfa...@gmail.com wrote:
copied ceph.conf from the servers. hope this helps. should this be
concidered an unsupported feature?
# rbd-fuse /cmnt -c /etc/ceph/ceph.conf -d
FUSE library version: 2.9.2
nullpath_ok: 0
nopath: 0
utime_omit_ok: 0
copied ceph.conf from the servers. hope this helps. should this be
concidered an unsupported feature?
# rbd-fuse /cmnt -c /etc/ceph/ceph.conf -d
FUSE library version: 2.9.2
nullpath_ok: 0
nopath: 0
utime_omit_ok: 0
unique: 1,
opcode: INIT (26), nodeid: 0, insize: 56, pid: 0
INIT: 7.22
client debian wheezy, server ubuntu trusty. both running ceph 0.94.2
rbd-fuse seems to work, but cant access, saying Transport endpoint is
not connected when i try to ls the mount point.
on the ceph server, (a virtual machine, as its a test cluster)
root@c3:/etc/ceph# ceph -s
cluster
On Wed, Jul 29, 2015 at 2:52 PM, pixelfairy pixelfa...@gmail.com wrote:
client debian wheezy, server ubuntu trusty. both running ceph 0.94.2
rbd-fuse seems to work, but cant access, saying Transport endpoint is
not connected when i try to ls the mount point.
on the ceph server, (a virtual
