[Bug 809221] Re: unable to mount ceph root at boot due to stripping of trailing slashes

[Dan Mick]

Seems to me that the filesystem-specific mount and/or the filesystem
module should get the 'device' path unmodified, and deal with it how it
will.  (For instance, as noted, nfs mounts can also contain a trailing
path, and nfsserv:/ should work unsurprisingly).

nfs currently works because it doesn't try to validate that '/' exists; mount.nfs requires a :, and passes on a 
potentially-empty path to the kernel mount function.  Ceph's kernel module could accept that as well, but the
fact remains that mountall really should not be removing the trailing /.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/809221

Title:
  unable to mount ceph root at boot due to stripping of trailing slashes

Status in “mountall” package in Ubuntu:
  Triaged

Bug description:
  When the mount device doesn't start with UUID= or LABEL= update_mount
  will strip the trailing slashes from the mount device name. For most
  situations this is fine but with Ceph it's quite possible that, for
  example, 192.168.0.15:/ would be an acceptable mount device but mount
  at boot fails since it passes 192.168.0.15: to mount.ceph, which then
  complains about an invalid device.

  I have attached a patch that resolves this issue. I don't know if it
  is the best way to do it but it works for me okay and shouldn't have
  an impact anywhere else.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/809221/+subscriptions