Dave Ewart 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.
(or maybe you just have problems with accessing the gnutar-lists dir?)
Does anything look odd, apart from that?
Dave.
--
Paul Bijnens, Xplanation Tel +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUM Fax +32 16 397.512
http://www.xplanation.com/ email: Paul.Bijnens AT xplanation DOT com
***********************************************************************
* I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, *
* quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, *
* kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... *
* ... "Are you sure?" ... YES ... Phew ... I'm out *
***********************************************************************
|
