[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: "Too much files to mangle" error
From: |
Thomas Schmitt |
Subject: |
Re: "Too much files to mangle" error |
Date: |
Fri, 12 Jun 2020 09:19:33 +0200 |
Hi,
> https://drive.google.com
They want me to become a member. So i let the slow download go on.
It ended after about 6 hours.
Program "file" says about the download result:
gzip compressed data, max compression, from Unix
But after gunzip the file has surplus 96 bytes at the start
0d 00 00 00 00 00 00 00 6e 69 78 2d 61 72 63 68
69 76 65 2d 31 00 00 00 01 00 00 00 00 00 00 00
28 00 00 00 00 00 00 00 04 00 00 00 00 00 00 00
74 79 70 65 00 00 00 00 07 00 00 00 00 00 00 00
72 65 67 75 6c 61 72 00 08 00 00 00 00 00 00 00
63 6f 6e 74 65 6e 74 73 00 48 10 3b 01 00 00 00
As cleartext:
n i x - a r c h
i v e - 1
(
t y p e
r e g u l a r
c o n t e n t s H ;
and trailing 16 bytes at the end
01 00 00 00 00 00 00 00 29 00 00 00 00 00 00 00
This seems to be an extra wrapping around the ISO. But "file" just says
that it is "data".
I removed the prefixed bytes by creating a loop device with offset 96 and
copying its content to a new data file. This also stripped the trailing
16 bytes due to block alignment truncation.
Now i have a recognizable ISO of the size which its partition table tells:
10318244 + 5760 = 10324004 blocks of 512 = 5,285,890,048 bytes
Which program would i use regularly to unpack the ISO ?
---------------------------------------------------------------------------
Whatever, i can now reproduce the error message.
(There are 47 HFS+ name collisions reported as resolved by DEBUG verbosity.)
The size of the ISO and the speed of xorriso when compiled with -O0 will
cause quite long program runs.
So it may last a while until i found out what exactly goes wrong.
Have a nice day :)
Thomas