On Thu 16 Nov 2006, hanj wrote: > > I'm getting the "No unexpired good images" message during expire. Now, I've > seen reference to this in the past stating that this is due to error message > written in the summary file in that particular vault. Looking at the vault, > I'm seeing 'SUCCESS', so not sure as to why it can't expire it. This is my > 'base' image, and is out dated.. so not sure what to do. I'll provide a > snapshot of the directory and file sizes along with the summary file in that > particular vault.
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. PS: please wordwrap at around column 70, that makes it easier to quote properly... > 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... To find out how much space is unique in each subdirectory, I usually do: du -h --max-depth=1 . Of course, you need GNU du, but you seem to have that as you also use -h. > Any ideas on what I need to do? I'm hoping that I don't have to start over > and re-init the vault. No, because you still have the one image that is declared successful. Paul Slootman _______________________________________________ Dirvish mailing list [email protected] http://www.dirvish.org/mailman/listinfo/dirvish
