Re: Infernalis => Jewel: ceph-fuse regression concerning the automatic mount at boot?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Jun 1, 2016 at 10:23 AM, Francois Lafont <flafdivers@xxxxxxx> wrote:
> Hi,
>
> I have a Jewel Ceph cluster in OK state and I have a "ceph-fuse" Ubuntu
> Trusty client with ceph Infernalis. The cephfs is mounted automatically
> and perfectly during the boot via ceph-fuse and this line in /etc/fstab :
>
> ~# grep ceph /etc/fstab
> id=cephfs,keyring=/etc/ceph/ceph.client.cephfs.keyring,client_mountpoint=/  /mnt/  fuse.ceph  noatime,nonempty,defaults,_netdev  0  0
>
> I change my sources.list to install the Jewel version. I install the Jewel
> packages via a simple "apt-get update && apt-get upgrade". Now, the Jewel
> version is installed.
>
> So I reboot the machine. But now the automatic mount of cephfs at boot works
> no longer. After the reboot, I have:
>
> ~# mountpoint /mnt/
> /mnt/ is not a mountpoint
>
> ~# tail /var/log/upstart/mountall.log
> [...]
> 2016-06-01 19:00:55.234594 7f29301dbe80 -1 init, newargv = 0x7f29397b8fd0 newargc=13
> ceph-fuse[362]: starting ceph client
> ceph-fuse[362]: ceph mount failed with (1) Operation not permitted
> ceph-fuse[319]: mount failed: (1) Operation not permitted  <====================== Here!
> mountall: mount /mnt [306] terminated with status 255
> mountall: Disconnected from Plymouth
>
> The error is very curious because I have absolutely no problem to mount the
> cephfs manually:
>
> ~# mount /mnt/
> ceph-fuse[1279]: starting ceph client
> 2016-06-01 19:06:23.660419 7f174e336e80 -1 init, newargv = 0x7f1758c4afd0 newargc=13
> ceph-fuse[1279]: starting fuse
>
> ~# mountpoint /mnt/
> /mnt/ is a mountpoint
>
> ~# df /mnt/
> Filesystem     1K-blocks   Used Available Use% Mounted on
> ceph-fuse       21983232 172032  21811200   1% /mnt
>
> The machine is an updated and basic Ubuntu Trusty. I can reproduce the
> problem *systematically*. Indeed, the machine is a VM with a snapshot in
> Infernalis state where all is OK and after the upgrade the problem happens
> systematically. I have tried several reboot and the cephfs is *never*
> mounted automatically (but the manual mount is completely OK).
>
> Is it a little "Infernalis => Jewel" regression concerning ceph-fuse or
> have I forgotten a new mount option or something like that?
>
> I can reproduce the problem and provide any log if needed.
> Thanks in advance for your help.

This isn't something we test so just general logs, probably.

But if I were to guess: the default ownership of files changed in
Jewel (from root to "ceph"), and I believe it applies those permission
changes. Whatever's invoking mount might not have the right access
permissions on the files, or be rejecting them based on their own
security status or something.
-Greg
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com



[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux