I have a trace log now, although it does not appear to be the same trace log that generated the debug logs pasted in previous posts.
I see two odd things here. First, ten of the flushed dumps are listed with an orig-kb of 0. Amreport should be able to handle this situation, and should be tested for it, too. dd if=/path/to/holding/file bs=32k count=1 The second odd thing is that several of the dumps are logged with an orig-kb of -1, which leads to some very large, negative COMP% values. This is exactly the same set of DLEs that are producing the zero orig-kb above, but these are live dumps, not flushes. It looks like what's happening is that the dumps are failing, and as a result no orig-kb is being recorded. For live dumps, this means the driver's default value of -1 is still present; for flushes, this means that a default of zero is used. The latter is clearly a driver bug, but amreport should handle it gracefully (probably by assuming a negative orig-kb is zero). I still can't see any reason that your labels wouldn't come out. But as I mentioned above, I'm looking at a different trace log than you were when you started this thread. Did you try running the command I suggested? amreport MyConfig --ps=temp.ps Dustin -- Open Source Storage Engineer http://www.zmanda.com
