Thanks for this first reply. So how restart a VM create : with a CR job with the snapshot with memory and keep the backup chain healthy? For now, I'm using the "With memory" option because I think it's the best choice for reliably restoring VMs such as an AD or a SQL Server database. Am I wrong?

On the version question, 8.3 ships DRBD 9.2.18 right now (that's what kmod-drbd.spec says on the 8.3 branch), so you'd be asking for a single point bump rather than a big jump. That probably helps you. Of your two links though, I think the netlink crash fix is a 9.2.17 entry, which would mean it's already in what you're running. The 9.2.19 line that looks closest to your crash to me is the connection-teardown races one rather than the AB-BA deadlock, since a deadlock would hang rather than throw a GPF, but you've read these traces far more closely than I have so correct me if that's backwards. I can't request a build myself, that's a @Team-Storage call rather than mine, though your post #13 timeline next to those changelog lines is a stronger case than most version-bump requests turn up with.

@poddingue Oh yes (dumb me). Very good, we'll see if they respond (as now there's two @ refferences). Happy Day

Old thread but I'd like to add a follow-up on this. The issues continued with the new Minio instance but probably the storage is quite slow which I would guess caused the issues with listing and caused timeouts. After a lot of troubleshooting it seems to have been improved (so far) by increasing the socketTimeout for S3 from 10 minutes (600000) to 2 hours (7200000) in '@xen-orchestra/fs/dist/s3.js' I thought it could be good to know, possibly add a config option to adjust the timeout if needed if it doesn't exist already. I could not find one at least.