On Thu, 6 Dec 2001 at 2:19pm, Dan Garthwaite wrote > Of course. Joshua Baker-LePain sent some suggestions to the list on this as > well. I'm searching through the archives now, without capturing the output > to/from PLANNER the source code isn't revealing me anything.
I've been digging through it a bit too. I think one thing to do may be to stick some 'printf's in driver.c and see exactly which field in the planner output is generating the syntax error. From the amdump.3 you sent, line 10 looks like: amanda.mtg.saic.com //gagnona/F$ 11661 0 1970:1:1:0:0:0 0 0 1818845508 I *think* it's that last field that is the issue. It is supposed to be a date field for a degraded mode dump, followed by the degraded size and time estimates. (All three fields need not exist, but if the date does, then the other two must as well) It's worth noting that this host did *not* return an estimate for this disk. That doesn't explain where that number comes from though -- for that you may need to get some debbuging output from planner. Hmmm... There looks to be only *one* other line like that in amdump.3, and that's the next one after //gagnona/F$: amanda.mtg.saic.com //isis_temp/F$ 11661 0 1970:1:1:0:0:0 0 0 1818845508 *Are* there F drives on those boxes? Also, you were trying 4 filesystems on both those boxes -- maybe you overwhelmed the server side sharing (blame Windoze -- I like it!). But that still doesn't excuess the errant entry in planner's output. Not much help here, just thoughts, rambling, and more WAGs. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
