AJas

I think that 5923.7 GB wasted is the amount that cannot be assigned to Free GB because Parity Disk has not enough space to generate parity data for this. Currently everything is fine, because you don't use this space yet, but you clearly see that of that 14TB disk you can use only less than 8TB in total - otherwise you will run out of space on parity drive.

Hi, I've just started using SnapRAID plugin for OMV6 and can't find the answer for above question. As I understand from the manuals - SnapRAID creates parity file, and content files which are later used for checks and repairs. Parity file and checksums in content files must be updated according to changes in the data done by the user - otherwise these changes will be taken as errors that needs repairing. Okay, so now let check the scenario like this: Last check was done yesterday evening - todays...

[mssql] Column rename works incorrectly resulting in glitched column names.

I think it works for you because everything works for default schema, but generated code don't contain schema name definitely. I've just posted another ticket for foreign keys that are not being displayed for tables located in custom schemas (different than sys ?!?). I think exactly the same is here. Generated query don't put schema name on front of the table and is assumed it's good because was teste only on default schema where you don't need to put schema prefix and you can call table directl...

[mssql] No Foreign Keys displayed for different than default schema.

[Adminer4.7.7][Design] Schema select is a bit not handy to use.

[Adminer4.7.7][MSSQL] No server default collation can be applied on table creation

[Adminer4.7.7][Design] More than 3 logins don't fit inside container.