[Bug-tar] Re: gtar --listed-incremental silently failing again

[Dat Head]

On 5/8/07, Sergey Poznyakoff <address@hidden> wrote:
> Please try the CVS version, or at least the latest stable, which is
> 1.16.1.  There were several incremental-related fixes recently.

tried stable 1.16.1 and tar-1.16.2-20070123 (from alpha.gnu) and
neither work, none of the files in the 8.5 million file fs get picked
up at all still.

orig message below:

On 5/7/07, Dat Head <address@hidden> wrote:
> i thought this bug was squashed in tar-1.15.92 (-20060707), we had
> the problem before that and special patches were put into that version
> that made the issue go away at that time;  however, as time has one
> on and more files have been added to filesystem the bug is again back
> and *silently* it just does not back up *any* files in that file system.
>
> the original bug (and i'm sure this one)  is due to the number of
> files (see below,
> about 8.5 million inodes now) and something wrong with --listed-incremental
> processing (because it does not happen w/o that flag, but we need it).  it
> has to do with more than just the number of files though as we found before
> that changing the placement of where in the order of fs's would sometimes make
> it work (or not),  if we just backup this problem one and two others
> it works ok,
> but somehow the below combination does not
>
> /usr/local/bin/gtar --version
> tar (GNU tar) 1.15.92
>
> executing "/usr/local/bin/gtar -c -f address@hidden:/dev/sdlt27nr -b 256 -v -
> -one-file-system --ignore-failed-read --totals --listed-incremental
> /usr/local/adm/etc/bck
> incremental.xray  ./ /home /usr/local /usr/LOCAL /ftp /vol1 /tools /ftp/data/2 "
>
> Filesystem           1K-blocks      Used Available Use% Mounted on
> /dev/sda1              9898580   4228320   5167428  46% /
> /dev/sda2              9898612   1512032   7883748  17% /home
> /dev/sdc1              9400448   6558612   2364308  74% /usr/local
> /dev/sda5              4040000    169556   3665216   5% /usr/LOCAL
> /dev/sdc2             19243772   1873880  16392340  11% /ftp
> /dev/sdb2             10301792   5590436   4711356  55% /vol1
> /dev/sdc3             28170276   5099804  21639484  20% /tools
> /dev/sdc4            231548312  20971700 198814624  10% /ftp/data/2
>
> Filesystem            Inodes   IUsed   IFree IUse% Mounted on
> /dev/sda1            1259104  102907 1156197    9% /
> /dev/sda2            1259104   12894 1246210    2% /home
> /dev/sdc1            1196032   53668 1142364    5% /usr/local
> /dev/sda5             514048    2711  511337    1% /usr/LOCAL
> /dev/sdc2            2448000   93584 2354416    4% /ftp
> /dev/sdb2            1310720  272486 1038234   21% /vol1
> /dev/sdc3            3581088   18604 3562484    1% /tools
> /dev/sdc4            29409280 8786224 20623056   30% /ftp/data/2
>
> it sees that it is new (previous listed incremental file removed
> before this run to kick in a full backup), and sticks on mount point but that 
> is it:
>
> /usr/local/bin/gtar: /ftp/data/2: Directory is new
> /ftp/data/2/