If you calculated the Zip thing and the difference isnt big enough,
there is only the way i and Roland (but i missunderstodd him .. sorry) suggested.
Calculat the parity size for every smallets Unit you can and want to move (without destroying the organization of your files) and try to rearrange them.
What do i mean exactly .... Balancing of files ..
Making parity work by Xoring the data of one drive with the data of the others.
If you have 10 Bytes on each of your drives ... you get ??? ... 10 Bytes Parity
But if one of them have 20 Bytes ... you get 20 Bytes ... the missing 10 Bytes on the other drives are Padded with 0 ...
SO if you rearrange your Data so the biggest drive is as small as possibele you you can make your Parity smaller ...... BUT ....
It is possible that your biggest (most filld) drive isnt the biggest ...... Hää ... why ... ?
PaddingBytes ! ... example
Drive one ... The biggest 90% filled but with 25GB BluRay ISO ...
Drive two ... 85% filled but with mp3 ... it is smaller but if you add the paddingbytes its possible that the parity for this drive is much bigger than dive 1 ... its also possible that the parity is bigger than the total capacity of the drive ...
So calculate the Real Parity size for as example
The MP3/ROck FOlder on drive 1
The MP3/Pop FOlder on drive 1
The SeriesFolder on drive 2
The ... whatever your system is and your smallest unit you are willing to move is.
The size of your Unit in Byte + (Number of Files * 32768)
Ignore The metadata ... the size of metadata dont change, it depends on the Count of files.
Now you can try (on paper) to rearrange them until the biggest RealParitySumm is small enough to write it on your Parity drive.
If this even dont work ... then nobody can help you ... there is no way ...
Sorry ... much to explain ... so its longer ...
And ... all the calculation is statistical not the exact value ... but if calculation say it dont work ... the chance that it work in real is very small ...
And to correct what you wrote ...
>>LARGE number of files with the sort of "table of content"
Large number of files is correct .... but
Not the Table of content (MetaData) is the problem ... as wrote before it is someting like 100-300 Bytes depending on Pathlength per file ... so for 100.000 Files its only 15MB (i calculated with 150 Bytes per file)
But there is up to 64KB PaddingBytes per files ... which is 6GB in worst case for the same 100.000 Files.