On Tue, Jul 28, 2015 at 9:17 AM, van <chaofanyu@xxxxxxxxxxx> wrote: > Hi, list, > > I found on the ceph FAQ that, ceph kernel client should not run on > machines belong to ceph cluster. > As ceph FAQ metioned, “In older kernels, Ceph can deadlock if you try to > mount CephFS or RBD client services on the same host that runs your test > Ceph cluster. This is not a Ceph-related issue.” > Here it says that there will be deadlock if using old kernel version. > I wonder if anyone knows which new kernel version solve this loopback > mount deadlock. > It will be a great help since I do need to use rbd kernel client on the > ceph cluster. Note that doing this is *not* recommended. That said, if you don't push your system to its knees too hard, it should work. I'm not sure what exactly constitutes and older kernel as per that FAQ (as you haven't even linked it), but even if I knew, I'd still suggest 4.1. > > As I search more informations, I found two articals > https://lwn.net/Articles/595652/ and https://lwn.net/Articles/596618/ talk > about supporting nfs loopback mount，it seems they do effort not on memory > management only, but also on nfs related codes, I wonder if ceph has also so > some effort on kernel client to solve this problem. If ceph did, could > anyone help provide the kernel version with the patch? There wasn't any specific effort on the ceph side, but we do try not to break it: sometime around 3.18 a ceph patch was merged that made it impossible to do co-locate kernel client with OSDs; once we realized that, the culprit patch was reverted and the revert was backported. So the bottom line is we don't recommend it, but we try not to break your ability to do it ;) Thanks, Ilya _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |