On Mon, 23 Feb 2009, Jeff Gilchrist wrote:

On Mon, Feb 23, 2009 at 10:00 AM, Justin Piszcz <[email protected]> wrote:
Package: pbzip2
Version: 1.0.3-1

After the upgrade from 1.0.2-0 to 1.0.3-1, pbzip2 is broken when compressing
files over NFS.

The problem:
root:~# pbzip2 -9 -p4
 /nfs/backup/user/2009-02-23/user-root-2009-02-23.xfsdump
 *ERROR: Could not get file meta data from
[/nfs/backup/user/2009-02-23/user-root-2009-02-23.xfsdump]!  Skipping...
-------------------------------------------
root:~# pbzip2 -9 -p4
 /nfs/backup/user/2009-02-23/user-root-2009-02-23.xfsdump
root:~# pbzip2 /nfs/backup/user/2009-02-23/user-root-2009-02-23.xfsdump
 *ERROR: Could not get file meta data from
[/nfs/backup/user/2009-02-23/user-root-2009-02-23.xfsdump]!  Skipping...
-------------------------------------------

That is very strange.  There was a small change in a function to that
call but it shouldn't functionally be different.  It went from:

int getFileMetaData(char *fileName)
{
        int ret = 0;
        // get the file meta data and store it in the global structure
        ret = stat(fileName, &fileMetaData);
        return ret;
}

to

int getFileMetaData(char *fileName)
{
        // get the file meta data and store it in the global structure
        return stat(fileName, &fileMetaData);
}

When I try v1.0.3 it seems to be working for me with NFS mounts on
RedHat based distros.  The latest version is now 1.0.5
(http://compression.ca/pbzip2/) so you may want to try that.
Otherwise I'm not sure what to suggest unless there is some file/NFS
permission problems going on.

Jeff.


Hello, 1.0.5 works successfully!

Debian/System
root:~# pbzip2 -9 -p4 $filepath
 *ERROR: Could not get file meta data from 
[/nfs/backup/user/2009-02-23/user-root-2009-02-23.xfsdump]!  Skipping...

Version 1.0.5:

root:~# /vapp/bin/pbzip2 -9 -p4 $filepath
root:~# /vapp/bin/pbzip2 -V
Parallel BZIP2 v1.0.5 - by: Jeff Gilchrist [http://compression.ca]
[Jan. 08, 2009]             (uses libbzip2 by Julian Seward)

Justin.




--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to