Two extraction issues (1.13.25 and 1.14)

View: New views
4 Messages — Rating Filter:   Alert me  

Two extraction issues (1.13.25 and 1.14)

by David Shochat-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

We are seeing a couple of problems, seemingly intermittently,
extracting as root from a roughly 3.2 Gb (uncompressed) tar file on
HP-UX 11i, into an NFS-mounted file system. The first involves a few
subtrees ending up owned by root after extraction, even though they
were owned by an ordinary user when the archive was created. The
listing of the tar file shows the correct ownership. In fact, almost
all of the 60,000 line listing shows this same owner and, except for a
few places, everything ends up with the correct ownership.
Furthermore, several levels into this incorrectly-extracted subtree
there are some symlinks (which again look fine in the listing) which
end up not as symlinks at all, but as 0-length ordinary files. We have
done some experiments extracting not as root, but as the
above-mentioned user. Obviously, nothing ends up owned by root now,
but we still see some strangeness with certain symlinks. These
symlinks are created by the development system we use (Rational Apex)
and each one points (using a full pathname) to the directory that it
is contained in. Sometimes these also end up as 0-length ordinary
files instead of the symlinks they were supposed to be.
If any of this sounds to anyone like a known bug which might have been
fixed since 1.14, this would be very valuable information. It would
obviously strengthen the argument for upgrading to a newer version
(e.g. 1.22).
-- David



Re: Two extraction issues (1.13.25 and 1.14)

by Sergey Poznyakoff-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

David Shochat <david.shochat@...> ha escrit:

> If any of this sounds to anyone like a known bug which might have been
> fixed since 1.14, this would be very valuable information. It would
> obviously strengthen the argument for upgrading to a newer version
> (e.g. 1.22).

Looks like both bugs were fixed. I'd suggest to try 1.22.

Regards,
Sergey



Re: Two extraction issues (1.13.25 and 1.14)

by David Shochat-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Sat, Aug 29, 2009 at 10:52 AM, Sergey Poznyakoff<gray@...> wrote:
>
> Looks like both bugs were fixed. I'd suggest to try 1.22.
>
Thank you. That is very helpful information. By any chance do you
remember what version or versions they were fixed in? I had tried
looking through the change logs but did not spot anything.
-- David



Re: Two extraction issues (1.13.25 and 1.14)

by Sergey Poznyakoff-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

David Shochat <david.shochat@...> ha escrit:

> Thank you. That is very helpful information. By any chance do you
> remember what version or versions they were fixed in?

No, I do not. Since 1.14, there were more than 50 commits affecting only
the extracting code, which constitute almost a rewrite of it. I'll need to
scan through all these to answer this question.

Regards,
Sergey