[Bug-tar] Tar vs later linux kernels

[Gene Heskett]

Greetings;

Recently, a patch was applied to the linux kernel tree which had the 
effect of changing the Device: line of a 'stat' report on a file.

The inode did not change, nor did the timestamps, only the Device: first 
pair of values.

Device: ee00h/60928d <-all other data is identical regardless of the 
kernel booted.

This has the effect that tar, when asked to give a listed-incremental list 
and fed the reference file so it can obtain the timestamps and determine 
if the file is new, would ascertain that the whole 50GB of a 160GB drive 
that was used, was new, and drove amanda crazy trying to get caught up.

This patch needs to be applied to the kernel for good reasons as it moves 
the device-mapped stuff out of an area that is reserved for experimental 
usage.

What I looking for, is a good reason why tar is in fact sensitive to this 
particular piece of info.

And of course, would it be possible to make tar immune to this change, as 
I, with my relative lack of information, consider this to be a bug. If 
its not fixed, tar users such as myself using amanda, are in for a very 
rude surprise when the upgrade their kernels to something newer than 
2.6.20.3.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Zoe: "Sir, I think you have a problem with your brain being missing."
                                --Episode #2, "The Train Job"