Hello,
discuss the quincy/dashboard-v3 backports? was tabled from 11/1
https://github.com/ceph/ceph/pull/54252
agreement is to not backport breaking features to stable branches.
18.2.1
LRC upgrade affected by https://tracker.ceph.com/issues/62570#note-4 https://ceph-storage.slack.com/archives/C1HFJ4VTN/p1700575544548809
Figure out the reproducer and add tests
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ce0d5bd3a6c176f9a3bf867624a07119dd4d0878 is the trigger on the kernel client side?
Clients with that patch should work with the server-side code that broke older ones
Suggestion to introduce a matrix of pre-built "older" kernels into the fs suite
etherpad history lost
need a way to recover from DB or find another way to back things up
need a way to recover from DB or find another way to back things up
discuss the quincy/dashboard-v3 backports? was tabled from 11/1
https://github.com/ceph/ceph/pull/54252
agreement is to not backport breaking features to stable branches.
18.2.1
LRC upgrade affected by https://tracker.ceph.com/issues/62570#note-4 https://ceph-storage.slack.com/archives/C1HFJ4VTN/p1700575544548809
Figure out the reproducer and add tests
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ce0d5bd3a6c176f9a3bf867624a07119dd4d0878 is the trigger on the kernel client side?
Clients with that patch should work with the server-side code that broke older ones
Suggestion to introduce a matrix of pre-built "older" kernels into the fs suite
gibba vs LRC upgrades
LRC shouldn't be updated often, it should act more like a production cluster
LRC shouldn't be updated often, it should act more like a production cluster
RCs for reef, quincy and pacific
for next week when there is more time to discuss
for next week when there is more time to discuss
Regards,
-- _______________________________________________ Dev mailing list -- dev@xxxxxxx To unsubscribe send an email to dev-leave@xxxxxxx
