On Thu, Jan 23, 2014 at 8:07 AM, Arne Wiebalck <Arne.Wiebalck@xxxxxxx> wrote: > > On Jan 23, 2014, at 4:18 PM, Gregory Farnum <greg@xxxxxxxxxxx> > wrote: > >> On Wed, Jan 22, 2014 at 3:23 PM, Karol Kozubal <Karol.Kozubal@xxxxxxxxx> wrote: >>> Hi Everyone, >>> >>> I have a few questions concerning mounting cephfs with ceph-fuse in fstab at >>> boot. I am currently successfully mounting cephfs using ceph-fuse on 6 >>> clients. I use the following command, where the ip is my mon address: >>> >>>> ceph-fuse –m 192.168.0.2:6789 –r /shared/files /root/shared >>> >>> This works correctly when I mount at run time. However I am running into >>> issues doing this at boot time through fstab with the following command, as >>> per the documentation on ceph.com I am passing cephfs root as a part of the >>> first argument in fstab: >>> >>> id=admin,r=/shared/files /root/shared fuse.ceph defaults 0 0 >>> >>> Am I passing the argument correctly? And should I include the m argument as >>> well? >> >> You aren't specifying a config file, nor a monitor address to mount. >> You'll need to include the IP somewhere or other, yes. >> -Greg >> Software Engineer #42 @ http://inktank.com | http://ceph.com > > > Greg, > > Is there an example of how an fstab entry for ceph-fuse should look like if the keyfile is in a separate place? http://ceph.com/docs/master/cephfs/fstab/#fuse discusses fstab generically. You specify the keyfile either in a config you point to, or as one of the arguments in fstab, just like normal. > Also: fuse mounting in general should work with entities other than admin, right? > If so, would the capabilities be different from the minimal ones used to mount with the kernel client? Yeah, it works with whoever, and there are no differences in perms between kernel and fuse clients. -Greg Software Engineer #42 @ http://inktank.com | http://ceph.com _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |