On Tue, Apr 12, 2016 at 12:21 PM, Simon Ferber
<ferber@xxxxxxxxxxxxxxxxxxxxxxxx> wrote:
> Am 12.04.2016 um 12:09 schrieb Florian Haas:
>> On Tue, Apr 12, 2016 at 11:53 AM, Simon Ferber
>> <ferber@xxxxxxxxxxxxxxxxxxxxxxxx> wrote:
>>> Thank you! That's it. I have installed the Kernel from the Jessie
>>> backport. Now the crashes are gone.
>>> How often do these things happen? It would be a worst case scenario, if
>>> a system update breaks a productive system.
>>
>> For what it's worth, what you saw is kernel (i.e. client) side
>> breakage. You didn't mess up your Ceph cluster, nor your CephFS
>> metadata, nor any data. Also, anything you do in CephFS using a
>> release before Jewel must be considered experimental, and while things
>> will generally not break even on the client, you shouldn't be
>> surprised if they do. Thirdly, my recommendation for any Ceph
>> client-side kernel functionality (both rbd.ko and CephFS) would be to
>> use nothing older than a 4.x kernel.
>
> Thank you for clarification, Florian.
Florian is correct. I'd like to add that this (i.e. breaking an
already released kernel) happened maybe once before in many years.
It was truly an accident - a commit that wasn't explicitly set to be
backported to 3.16.* got backported semi-automatically.
Thanks,
Ilya
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
