I get odd things orphaned occasionally too, even without failing drives. Backups that failed halfway, and then were retried successfully, I think (never really looked). I tend to see them months later, and delete them, since amanda no longer recognizes them.
Deb Baddorf Fermilab On Oct 30, 2015, at 1:47 PM, Chris Nighswonger <cnighswon...@foundations.edu> wrote: > Hi Jean-Louis, > > On Fri, Oct 30, 2015 at 1:24 PM, Jean-Louis Martineau > <martin...@zmanda.com> wrote: >> Chris, >> >> You can use the following command to list all amanda dump in holding disk: >> $ amadmin CONFIG holding list -l >> >> What's in the holding (with the 'ls' command), it looks you have a lot of >> files not recognized by amanda. > > backup@scriptor:/storage/campus$ amadmin campus holding list -l > size (kB) lv outd dump specification > > So it looks like Amanda thinks there is nothing there. However, > between your suggestion and Debra's, I took a look at my holding disk > (I should have done this already) and found quite a large collection > of (very) old dumps. After cleaning up the holding disk, the flush > notice in the amreport is gone. > > I'm not sure what all may have transpired to result in these orphaned > dumps, but it probably had to do with the failing tape library we > replaced last month. > > Thanks to you and Debra for pointing me in the right direction! > > Kind regards, > Chris
