Whoops. I noticed retroactively that the level stated for sabre:/biff
in the "after start degraded mode" schedule is level 7. There is a "0"
in that row and looking too quickly I mistook that for the dump level
column. I noticed this after discovering that the file created on the
holding disk for that dump was "sabre._biff.7". I learned this from
grepping for "biff" in the entire amdump log file:
setting up estimates for sabre:/biff
setup_estimate: sabre:/biff: command 0, options:
got result for host sabre disk /biff: 0 -> 3390062K, 6 ->
3300252K, 7 -> 519K
8: sabre /biff
pondering sabre:/biff... next_level0 2 last_level 6 (not due for a
full dump, picking an incr level)
sabre /biff pri 1 lev 7 size 519
promote: moving sabre:/biff up, total_lev0 3390062, total_size
3574492
sabre /biff 1 0 1970:1:1:0:0:0 3390062 3104 7 2001:8:10:18:36:32
519 0
sabre /biff lv 0 t 3104 s 3390094 p 1
sabre /biff lv 7 t 0 s 551 p 1
driver: send-cmd time 237.289 to dumper0: FILE-DUMP 00-00001
/hea_holding_disk/new/20010813/sabre._biff.7 sabre /biff 7
2001:8:10:18:36:32 1073741824 DUMP 608 |;bsd-auth;index;
So why did amstatus report it as level 0? If I had let the amdump
finish, I would be curious to know what level would have actually been
performed and what the final report would have stated.
Notice the "not due for a full dump, picking an incr level"
paranthetical statement. Also note the "promote: moving
sabre:/biff up, total_lev0"
Paul
