On 07/04/14 at 10:53am, HATAYAMA, Daisuke wrote: > > There are things that make users to guess actual vmcore size; not only > compression but also additional meta-data, note data, header, bitmaps, of > vmcores. I think it important to stress that the actual dump size should be > larger than the number of pages displayed there so you (users) should care > about that enough. >
Yes, if dump is kdump compression user need know actual vmcore includes more. If only show number of dumpable page, the size should be very close to the elf vmcore size. But I think it's a good idea to tell user the difference. > For fail safe, it should address ENOSPC case more. Sadly, preparing too small > disks for vmcores is human error. In general, we cannot avoid this in real > world. It's important to make vmcore valid even in case of ENOSPC in the > sense that at least generated part of vmcore can correctly be analized by > crash. In this direction, I previously sent the patch to create 1st bitmap > first but this patch alone is still unsatisfactory to deal with the issue. > It's necessary to flush the 2nd bitmap and the data left in caches too. > Yes, it makes sense to me that generate part of vmcore even in case of ENOSPC, maybe later further attempt can be taken in this direction. > > -- > Thanks. > HATAYAMA, Daisuke > > > _______________________________________________ > kexec mailing list > [email protected] > http://lists.infradead.org/mailman/listinfo/kexec _______________________________________________ kexec mailing list [email protected] http://lists.infradead.org/mailman/listinfo/kexec
