On Thu, 16 Nov 2006 17:35:18 +0100 Paul Slootman <[EMAIL PROTECTED]> wrote:
> You're looking at that particular vault, and seeing "SUCCESS". > That's exactly what dirvish is also doing. However, dirvish apparently > can't find any *NEWER* images that are also successful, so it's leaving > the last known good image intact. *That* is what the message is telling > you. So, take a look at the newer summary files. Thanks for pointing that out. I see that I'm getting the following status on all the other images: Status: warning (24) -- file vanished on sender I'm not sure how to pin what file(s) has vanished. There is no rsync_error file in any of the vaults. I'll manually change a summary to success to see if that gets me past 20060920. > PS: please wordwrap at around column 70, that makes it easier to quote > properly... Sorry about that. > > comp zeus # du -sh * > > 5.1G 20060920 > > 1000M 20061012 > > 338M 20061013 > > 349M 20061014 > > That's a bit curious, as du -sh * will usually count each argument > separately without taking into account hardlinks (that's only done > within each argument). Now it looks like each next image was pretty > incomplete, which of course would indicate that those images were in > fact unsuccessful... It appears that those images are successful (besides the vanish message). I thought that is showing the 'changed' files in each of those vaults. I tried Johannes command.. and this is a snippet of what I got: du -csh * 5.1G 20060920 1021M 20061013 349M 20061014 804M 20061015 So same result. I forgot to mention that the I did the disk usage yesterday.. that's why 20061012 is no longer there now. Thanks! hanji _______________________________________________ Dirvish mailing list [email protected] http://www.dirvish.org/mailman/listinfo/dirvish
