On Friday, 13.06.2003 at 12:49 +0200, Paul Bijnens wrote:

> >A stat of one of the files on the ncp filesystem looks like this:
> >
> >  File: "pm-net2.ini"
> >  Size: 14025           Blocks: 28         IO Block: -4611692065741340160 
> >  Regular File
> >Device: 15h/21d Inode: 1517        Links: 1    
> >Access: (0444/-r--r--r--)  Uid: (    0/    root)   Gid: (    0/    root)
> >Access: Wed Jun 11 00:00:00 2003
> >Modify: Wed Jun  4 12:08:00 2003
> >Change: Tue Jun  3 11:07:06 2003
> >
> >This file, according to its timestamp was changed at 12:08 on June 4th.
> 
> The mtime + the inode number are compared by gnutar.
> Maybe linux fakes inodes for ncpmounts and maybe they don't stay
> constant between mounts.
> Have a look at the files in gnutar-lists. They look like:
> 
> 35651587 423837 ./lant/lib
> 35651587 891648 ./lant24/var/spool/data/in
> 35651587 341248 ./lant24/Nl-Fr
> 35651587 522880 ./lant24/En-SN/lib
> 35651587 181633 ./lant/En-Es
> 
> The first number is the mtime (in seconds since epoch), the second 
> number is the inode number, followed by the filename.
> You find files named:  (in perl notation:)
>       $host . "_" . ($dir =~ s!/!_!g) . $level
> A e.g. host__0 for the level 0 backup of the root filesystem.
> A level 1 backup is compared to the status of the last level 0 backup.

Hmmm - the 'seconds since epoch' is clearly wrong for all the Netware
gnutar lists (it is showing 0, rather than something corresponding
approximately to 'this year').  Seems like the Netware mount is getting
a rogue timestamp which is making AMANDA think everything is new.

Your help has been useful - you may have directed me towards the real
problem.  Now all I need to do is figure out the right way to mount the
Netware filesystems ...

Thanks Paul,

Dave.
-- 
Dave Ewart
Dave.Ewart AT cancer.org DOT uk
Computing Manager, Epidemiology Unit, Oxford
Cancer Research UK
PGP: CC70 1883 BD92 E665 B840 118B 6E94 2CFD 694D E370