BETA: PowerArchiver 2023 - 22.10.02

[TBGBe]

Sorry, that was misleading.
There is something strange going on -
Create a test Folder containing filenames of different lengths
I used 7 files (98 chars to 105 chars).
Length of 103 was correct.
98 to 102 were corrupted to be 103 chars (4, 44, 444, 0444, 00444 was added to extension .txt)
104 and 105 were corrupted by addition of the string “0000002” to the extension (both files).
:eek:

So the result was
a) {longfilename}.txt00444
b) {longfilename1}.txt0444
…
…
c) {longer filename}.txt0000002
d) {longer filename1}.txt0000002
:confused:

[peterr]

@spwolf:

we have no idea what will it include until we start working on it :-).

I see 10.1 beta is out.

At this stage, do you know if 10.1 final will include the bug fixes for …

1. The filename extension problem as explained in this thread.

2. The “additional pathnames” bug/problem.

Also, thanks to Terry for doing some more testing. I was about to download a website backup toay, and then remembered about this filename extension problem with .tar.gz files. :(

[peterr]

The website backup was uncompressed to a local path, and there was a ‘mix’ of file extensions that ended in …

0000444
0000644

I went and checked on the website, and it does match the file permissions (Linux box as server), so if that is of any help ?

In one path that was uncompressed/extracted, I can see where the ‘limit’ is. The pathname is 110 chars, including the volume number and all backslashes, and the filename extension has only been changed for 3 files in that path. Here is an example of one file that has no change to the extension, and one file that has the extension changed, as follows:

daily_usage_200610.png –-> daily_usage_200610.png
hourly_usage_200610.png --> hourly_usage_200610.png0000644

The one extra character (the difference between ‘daily’ and hourly’) blew the limit.

The total size, of the file, at the “max” (daily_usage_200610.png), including full pathname is 132 bytes.

HTH

[peterr]

I just installed the latest PA, version 10.10.10 and this filename extension problem still exists. :mad:

I didn’t restart after the install, there was no message to do so.

[spwolf]

@peterr:

I just installed the latest PA, version 10.10.10 and this filename extension problem still exists. :mad:

I didn’t restart after the install, there was no message to do so.

yeah, this will take longer since we have to add support for longer file+path in tar files… we had some priority fixes for 10.1

[peterr]

@spwolf:

yeah, this will take longer since we have to add support for longer file+path in tar files

I wonder how 7-Zip does it, because from memory, it handled the longer file+path’s okay.

@spwolf:

… we had some priority fixes for 10.1

… and here I was, thinking that I would be top of the list. :D

[spwolf]

this will probably make it into 10.2, working on it now…

[peterr]

Thank you. :)

[spwolf]

And it did :-).

Please check with Beta 4:
http://www.powerarchiver.com/test/release10/powarc1020.exe

Please let us know if this fixes this issue as soon as you can.

thank you!

[peterr]

The filename extension problem still exists. :(

Also, when I extracted the archive, in addition to it creating the main pathname and all files and paths underneath that, it also created some other weird pathname, with 19 folders and no files when extracted.

The archive was large, PA is reporting 5032 files, 625 directories and 13,476,762 bytes.

[spwolf]

can you send us the archive so we have it for testing? Just compress it with 7zip (tar file itself) and upload it to some free uploads site? Is that ok?

That would be very helpful….

thanks!

[peterr]

@spwolf:

can you send us the archive so we have it for testing? Just compress it with 7zip (tar file itself) and upload it to some free uploads site? Is that ok?

Sorry, no can do, it’s a website backup and has a lot of confidential files in it.

I also used PACL to extract the same archive, guess what, same results, that is, lots of files created with the filename extension changed. This didn’t happen before with PACL, at least I don’t think so ??

I did a binary compare on the PA extract compared with the PACL extact, all files matched, but PA didn’t create a number of paths where there were no files, … sound familiar.

I may try some other archive tool tomorrow, on the archive.

Once again, the ‘pattern’ of the filename extensions is that the (cmod) permissions from the website, has been appended to the fiename extension.

Looking at one file that has had the extension changed, the pathname is 133 bytes, and the filename plus extension is 18 bytes, that makes 152 if we add the extra backslash.

The filename, plus extension is meant to be 11 bytes (modinfo.php), and there is another file in the same path that is a total of 10 bytes (index.html), which hasn’t had the extension name changed.

See attached screen dump of that path.

Also when I open the archive, PA seems to be showing the file extensions incorrectly, that is, the same as the screen dump.

[spwolf]

cant you compress non-confidential parts of the website and send them over? I am sure you can recreate same behaviour without using files that you dont want to send us… 1 file is enough.

thanks!

[peterr]

The archive is automatically created from cPanel, I just hit the “create full backup” button.

I will see about trying to create an archive of ‘parts’ of the site manually, but please don’t hold your breath. :D

[spwolf]

what about just deleting parts of the archive that are confidential and leaving few files that are fine? you can send it to us at support so it wont be for public viewing…

thanks

[peterr]

I’m not about to sort through 5032 files, and remove all the confidential ones.

As I said, …. it will take a while.

[peterr]

Have sent you a test archive. :)

[peterr]

Installed version 10.20.17 , and unfortunately, this problem is now worse. :confused:

Instead of just a few files that had the filename extension changed. there are now over 80 files (same archive used for testing), and the ‘filename’ (including the extension) has now been truncated. I checked 5 files, and they are all truncated at 145 bytes (includes full pathname and extension).

What is strange, is that when I shortened the length of the path used to extract, exactly the same problem occurred, that is, the same number of filenames are corrupt.

I would have thought decreasing the size of the (full) pathname, would have resulted in less errors found in the filename.

When I increased the size of the (full) pathname, and did the extract again, the filenames are now truncating at 151 bytes (145 + 6).

There don’t appear to be any filename extensions changed this time, just the truncation problem, but the problem is not consistant with the pathname length, and the same filename results, irregardless of the pathname length.

Here is an example, showing the correct filename, total size is 146 bytes …

F:\temp\powerachiver.…\class\smarty\internals\core.assemble_plugin_filepath.php

======
When the full pathname is increased in size by 8 bytes, the filename is truncated at 145 bytes …

F:\temp\powerachiver.…\class\smarty\internals\core.assemble_plugin_fil

When the full pathname is increased in size by 6 bytes, the filename is truncated at 151 bytes …

F:\temp\powerachiver.…\class\smarty\internals\core.assemble_plugin_fil

When the full pathname is decreased in size by 22 bytes, the filename is truncated at 129 bytes …

F:\temp\powerachiver\….\class\smarty\internals\core.assemble_plugin_fil

In all cases, the same filename results, a truncated name, and in all extracts, exactly the same number of errors have occurred (approx. 80 files with filenames truncated).

‘spwolf’ has the same test archive, and will be able to see what the extract is doing.

When the archive is being viewed, the filenames appear to be okay, it is just some weird problem with the extract. :confused:

[spwolf]

Please try with .21 from our website and see what happens.

thanks

[peterr]

Installed .21 , and ran the extract again, … same problems unfortunately.

Just extract the test archive I sent, and you will see where filenames have been truncated. :(