Hello everyone,
I've been using PBS on NFS storage (on several installations) for some time now, and I'm used to some kind of performance.
For example, a full SSD datastore (on the NFS datastore) I know takes 2 hours for a full garbage collect, etc. (datastore from 25 to 300 Tbytes).
This was always the case until release 2.3-2.
After the upgrade to 2.3-3 something changed (ok also to kernel 5.15-85) the same datastore that used to be completed in 2 hours, now after 3 days is 95% in marked mode.
Something does not add up for me (datastore side has not been touched a comma), ditto for PBS configuration.
Downgrade via dpkg from 2.3-3 to 2.3-2 (and change kernel to 6.1) and works very fast, as usually.
I don't know if the problem is in the kernel or in the 2.3-3 package, but this way it works as it should.
The system is in production, so I can't do too many tests and reboots...
I was exasperated by the slowness, so I made two changes at once (I know that diagnostically it's the worst solution, but not having time or a way to give too much disruption I couldn't do one test at a time).
Very thanks
Luca
I've been using PBS on NFS storage (on several installations) for some time now, and I'm used to some kind of performance.
For example, a full SSD datastore (on the NFS datastore) I know takes 2 hours for a full garbage collect, etc. (datastore from 25 to 300 Tbytes).
This was always the case until release 2.3-2.
After the upgrade to 2.3-3 something changed (ok also to kernel 5.15-85) the same datastore that used to be completed in 2 hours, now after 3 days is 95% in marked mode.
Something does not add up for me (datastore side has not been touched a comma), ditto for PBS configuration.
Downgrade via dpkg from 2.3-3 to 2.3-2 (and change kernel to 6.1) and works very fast, as usually.
I don't know if the problem is in the kernel or in the 2.3-3 package, but this way it works as it should.
The system is in production, so I can't do too many tests and reboots...
I was exasperated by the slowness, so I made two changes at once (I know that diagnostically it's the worst solution, but not having time or a way to give too much disruption I couldn't do one test at a time).
Very thanks
Luca