On Tue, Mar 27, 2018 at 6:54 AM, Rishabh Dave <ridave@xxxxxxxxxx> wrote: > On 27 March 2018 at 19:13, John Spray <jspray@xxxxxxxxxx> wrote:> >> I don't think the client_unmount_on_blacklist behaviour is going to be >> a good idea in practice -- if someone has a workload writing files out >> to a mounted /mnt/cephfs, and it gets auto-unmounted, they'll start >> writing data out to their root filesystem instead! We need to leave >> the actual unmounting to the administrator so that they can stop >> whatever workloads were using the mount point as well. > > So, would it preferable to just get rid of it or to set it to false by default? John raises a good point. I think instead just have the CephFS Client clean up its state such that umount(2) succeeds. -- Patrick Donnelly -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
