during initial tests we found some disks do not specify a serial number correctly, so we had to do that.
unfortunately this is not a small change, though it may look so; it is a lot of work, as it requires to update all the stored procedures and will require a database upgrade. So we won’t be able to do this soon. We have more urgent updates to make first. I will try to stick in the next bugfix release, but I can’t guarantee.
I understand a permanent fix can take a while, and this is obviously a minor thing so not a priority. I was referring to what you said here:
When the size changes, you must intervene manually on the database (howtos will follow)
About a manual intervention with the database. Since it’s not critical data I can put it on an external drive for now, so I just need a way to manually fix the database to point to the new drive if possible, thanks!