From: Bharata B R. <bh...@in...> - 2003-05-20 05:21:15
|
On Tue, May 20, 2003 at 02:07:05AM +0800, Feng, Fleming wrote: > Lkcdutils-netdump.patch: There is a bug in the netdump-server that make it impossible to rewind to the dump file header (When we update dump header, we need to rewind) I have reported this bug to the mailing list. This patch file fixes this bug. I used this patch against the current netdump-server present in cvs and still I can't get useful dumps. When I run 'lcrash -s /var/log/dump -d vmcore', I always get a dump.N file with zero size. A while back, when I was debugging this, I found that lcrash was expecting to find the dump header at offset KL_DUMP_HEADER_OFFSET. This is true for block device but for network dump, the dump starts from the beginning of vmcore file, hence the header is at offset 0. Even if this is fixed there is an other problem. While dumping, lkcd updates the header many times with latest information. I don't know if netdump server has logic to understand this. (I suspect netdump server just takes the pages and appends to the file) I have seen that the header in vmcore file will always have the information that was written for the 1st time and without any subsequent updates. I wonder if you haven't seen these problems. Regards, Bharata. |