> Tony Dziedzic wrote:
>
> We ran into an interesting error with lcrash when saving a crash dump.
> While copying the crash dump lcrash ran into an error and displayed the
> message "Error: dump flags in dumpdev page index invalid". On each
> subsequent reboot lcrash would again attempt to copy the crash dump, and
> would also encounter the same error. Each attempt would write some number
> of blocks and increment the bounds file contents, resulting in a continual
> series of less-than-useful crash dump files.
>
> In this particular error __kl_dump_retrieve returns a status of 0 (line 247
> of kl_savedump.c), which prevents the caller (kl_dump_retrieve) from erasing
> the dump. Every other failure case returns a status of 1, which seems more
> appropriate. It's probably advisable to modify this line to return a status
> of 1 to be consistent and to allow the crash dump to be erased.
Corrected. If you're using the CVS tree, grab the latest copy from
there. Thanks, Tony. :)
--Matt
> FYI,
> Tony Dziedzic
> Storigen Systems
|