Nathan Stratton Treadway <[email protected]> wrote: > The point is that GNU tar doesn't know that the files you are trying to > back up are on an LVM volume, and thus doesn't do any special processing > like trying to look up LVM metadata for them.
On a system that is POSIX compliant, there is no need to know this. > Essentially, all tar does is request the "stat" information from the OS > for each file and directory it's processing, and then uses the device id > (and lots of other fields) taken out of that information. > > So it sounds like then HP/UX LVM 2.2 is used, the device id that gets > assigned to a volume is unusual in some way that causes trouble for > tar... but the issue ties back to the values returned by the standard > "stat" function call, and not to some attempt by tar to parse the LVM > metadata or whatever. As "TAR" is defined to archive dev_t values as unsigned values, the observed problem is a GNU tar specific problem that does not apply to tar. Jörg -- EMail:[email protected] (home) Jörg Schilling D-13353 Berlin [email protected] (uni) [email protected] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily
