Re: timestamp(?) problems with incremental dumps

* Joerg Schilling writes:
> Lasse Kliemann <[email protected]> wrote:

> >    Type of this level 3  dump: full
> >    Date of this level 3  dump: Thu Sep 13 18:44:40 2007
> >    Date of last level 2  dump: Thu Sep 13 18:27:17 2007
> >    star: 14266 blocks + 0 bytes (total of 146083840 bytes = 142660.00k).

> > (...)
> >    var/log/debug: different size,data,mtime
> >       8568 -rw-r-----   1 root/adm Sep 13 18:27 2007 var/log/debug
> >       8160 -rw-r-----   1 root/adm Sep 13 18:11 2007 var/log/debug
> >
> > The version of 18:27 is from the snapshot and the version of 18:11 is from the 
> > restored version. Note that the level 2 dump is from 18:27:17 (see above).  
> > Theory: during the level 3 dump, the file appeared to star as being older than 
> > 18:27:17, which meant that it was already included in the level 2 dump (but it 
> > in fact was not). Hence it was not included in the level 3 dump and hence, on 
> > restore, the old version (from 18:11) was not updated.
> 
> How does the file look on the snapshot?
> 
> The problem may be that the filesystem does not sync meta data fast enough.
 
To determine this, I must take a look at the file in question on the snapshot 
which was used for the level 2 dump. I will do so in the next tests.

If this is the case, should a `sync' between touching the timestamp and 
creating the snapshot help? (Well, it depends on the sync implementation and 
the filesystem, I guess.)

 
> > This looks like typical behavior when the timestamp (later given to star with 
> > `dumpdate=') is made *after* the snapshot is created. But that's not how I do 
> > it. Maybe it has to do with accuracy? The times in /etc/tardumps seem to only 
> > have the accuracy of one second. Then, `sleep 1' between timestamp and snapshot 
> > should help. I am doing more tests; results are still to be expected.
> 
> The timestamp on /etc/tardumps is using a one microsecond granularity.
> 
> If your filesystem does not give a granularity better than one second, this is a
> problem of the filesystem.

The entries here look all like this:

root              13 1190157291.000000 Wed Sep 19 01:14:51 2007

It's always zeros after the period. I tried on Solaris, and there the time 
looks like: 1190194893.331676

Hence this seems to be Linux- (specifically ext3-)related.

_______________________________________________
Star-users mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/star-users

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)

iD8DBQFG8QhX1gObwed86AkRAieCAKDVCy3DY4EVAQOOWz1pfmLWcCEA/wCgnaaX
qYjhXnwxMVleQ6+tYQEdFNw=
=YF2c
-----END PGP SIGNATURE-----