On Wed, Dec 4, 2013 at 8:11 PM, Miguel Oliveira <m.a.oliveira@xxxxxxxxxxx> wrote: > > >> On 4 Dec 2013, at 04:37, "Yan, Zheng" <ukernel@xxxxxxxxx> wrote: >> >> On Tue, Dec 3, 2013 at 4:00 PM, Miguel Afonso Oliveira >> <m.a.oliveira@xxxxxxxxxxx> wrote: >>> >>>> If your issue is caused by the bug I presume, you need to use the >>>> newest client (0.72 ceph-fuse or 3.12 kernel) >>>> >>>> Regards >>>> Yan, Zheng >>> >>> >>> Hi, >>> >>> We are running 0.72-1 throughout the cluster but on kernel >>> 2.6.32-358.6.2.el6.x86_64... This is a big deployment (~10000 cores), not so >>> easy to update kernel has it has too many implications... >>> >>> Is there any way I can help iron out this bug? >> >> 2.6.32 kernel is too old, it's not easy to back port fixes to it. > > We will have a maintenance stop soon so I guess updating the kernel will be top priority but I'm not sure we can do the 3 kernel series... > >> how >> about using 0.72 ceph-fuse? > > Not quite sure I follow, we already have 0.72-1 > > [root@compute-1-1 ~]# rpm -qa | grep ceph > ceph-0.72.1-0.el6.x86_64 > libcephfs1-0.72.1-0.el6.x86_64 > ceph-fuse-0.72.1-0.el6.x86_64 > python-ceph-0.72.1-0.el6.x86_64 > > > Does this mean we are having some other bug? > How do you mount cephfs, use ceph-fuse or kernel driver? Regards Yan, Zheng > Cheers, > > MAO > >> >> Regards >> Yan, Zheng >> >>> >>> Cheers, >>> >>> MAO >>> >>>> >>>> >>>>> Cheers, >>>>> >>>>> MAO >>>>> >>>>> >>>>> >>> _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |