[Top] [All Lists]

Re: tar xfs problem ? was: Re: xfs_fsr broken again?

To: linux-xfs@xxxxxxxxxxx
Subject: Re: tar xfs problem ? was: Re: xfs_fsr broken again?
From: Christian Guggenberger <christian.guggenberger@xxxxxxxxxxxxxxxxxxxxxxxx>
Date: Tue, 8 Oct 2002 16:05:48 +0200
Cc: nathans@xxxxxxx
In-reply-to: <20021008134737.A8760@xxxxxxxxxxxxxxxxxxxxxxxx>; from christian.guggenberger@xxxxxxxxxxxxxxxxxxxxxxxx on Tue, Oct 08, 2002 at 13:47:37 +0200
References: <20021008065719.GA999@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <20021008094316.A4351@xxxxxxxxxxxxxxxxxxxxxxxx> <20021008181533.A254596@xxxxxxxxxxxxxxxxxxxxxxxx> <20021008134737.A8760@xxxxxxxxxxxxxxxxxxxxxxxx>
Sender: linux-xfs-bounce@xxxxxxxxxxx
On 08 Oct 2002 13:47:37 Christian Guggenberger wrote:
On 08 Oct 2002 10:15:33 Nathan Scott wrote:
On Tue, Oct 08, 2002 at 09:43:16AM +0200, Christian Guggenberger wrote:
> Hi,
> I have the same problems here on my debian/unstable box. According to
> Nathan Scott the builds are fine on his box... maybe Nathan should
> again?!
> ...
> But you can use the latest xfsprogs, xfsdump and attr binary packages
> debian/unstable, they contain the fixes Eric checked in last week.

*cough* -- those would be the packages I built on my (debian/unstable)
laptop just yesterday, right? ;-)

It seems to be a problem, when building those debian packages on a xfs-Partition... the Problem seems to be in tar... I get proper builds on an ext3 filesystem...


i just checked again on a system running CVS Kernel of September, 2nd; this machine has no Problems with "false" symlink names in a tarred archive. My previous tests (which showed those symlink problems in tar archives) had been run on today's CVS Kernel ...


<Prev in Thread] Current Thread [Next in Thread>