Messages in this thread |  | | Date | Wed, 4 Sep 2002 16:49:38 +0200 | From | Lars Marowsky-Bree <> | Subject | Re: writing OOPS/panic info to nvram? |
| |
On 2002-09-04T16:41:54, "J.A. Magallon" <jamagallon@able.es> said:
> Ah, ther is no way to write raw blocks at a very low level to disk...??
Not reliably; you _know_ your infrastructure has crashed, otherwise you wouldn't be inside the crash dump handler ;), so you can't possibly trust the normal block layer to write the crash dump (and not write it over your salary and customer database).
Parts of this could probably be circumvented by a checksum of the code which is computed at boot time and checked before the crashdump takes place, but this doesn't deal with a crashed SCSI driver.
A network dump is much safer, though I would suggest running it over a dedicated card / driver combo and on a special ethernet protocol, because you might have lost your IP configuration...
Sincerely, Lars Marowsky-Brée <lmb@suse.de>
-- Immortality is an adequate definition of high availability for me. --- Gregory F. Pfister
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |