Le jeudi 05 octobre 2017 à 21:52 +0200, Ilya Dryomov a écrit :
> On Thu, Oct 5, 2017 at 6:05 PM, Olivier Bonvalet <ceph.list@xxxxxxxxx
> > wrote:
> > Le jeudi 05 octobre 2017 à 17:03 +0200, Ilya Dryomov a écrit :
> > > When did you start seeing these errors? Can you correlate that
> > > to
> > > a ceph or kernel upgrade? If not, and if you don't see other
> > > issues,
> > > I'd write it off as faulty hardware.
> >
> > Well... I have one hypervisor (Xen 4.6 and kernel Linux 4.1.13),
> > which
>
> Is that 4.1.13 or 4.13.1?
>
Linux 4.1.13. The old Debian 8, with Xen 4.6 from upstream.
> > have the problem for a long time, at least since 1 month (I haven't
> > older logs).
> >
> > But, on others hypervisors (Xen 4.8 with Linux 4.9.x), I haven't
> > the
> > problem.
> > And it's when I upgraded thoses hypervisors to Linux 4.13.x, that
> > "bad
> > crc" errors appeared.
> >
> > Note : if I upgraded kernels on Xen 4.8 hypervisors, it's because
> > some
> > DISCARD commands over RBD were blocking ("fstrim" works, but not
> > "lvremove" with discard enabled). After upgrading to Linux 4.13.3,
> > DISCARD works again on Xen 4.8.
>
> Which kernel did you upgrade from to 4.13.3 exactly?
>
>
4.9.47 or 4.9.52, I don't have more precise data about this.
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
