[sos-devel] [PATCH] sosreport: Add support for new ppc64-diag elog format

[Vasant Hegde]

On 04/30/2014 01:55 AM, Bryn M. Reeves wrote:
> On Tue, Apr 29, 2014 at 05:06:48PM +0530, Vasant Hegde wrote:
>> Did you get a chance to look into this one ?
>
> Hi Vasant,

Bryn,

>
> I've applied this as commit 98231d1:
>

Thanks a lot..

>    sosreport: Add support for new ppc64-diag elog format
>
>    Reviewed-by: Vasant Hegde <hegdevasant at linux.vnet.ibm.com>
>    Signed-off-by: Samuel Mendoza-Jonas <samjc.mj at gmail.com>
>
>    Minor fixups for missing comas and to apply to the current tree.
>

Thanks for the fix.

>    Signed-off-by: Bryn M. Reeves <bmr at redhat.com>
>
>    https://github.com/sosreport/sos/commit/98231d1
>
> I'm curious about the expected files under /var/log/opal-elog though - I
> couldn't find much information on the directory structure (most hits
> seem to discuss the /sys interface). If these can get large it would be
> good to add the path using a reasonable default size limit to keep the
> report size sane.


Sorry.. We should have written better description..

Power System reports platform related logs in PEL format..

On pSeries system we have rtas_errd daemon (part of ppc64-diag package) which 
captures these
information and stores in /var/log/platform..

On PowerNV system we have opal_errd (ppc64-diag package) which captures these 
information and
creates individual files per log under /var/log/opal-elog directory.. Hence we 
want to capture entire
directory..

These logs are pretty small (average 2K per log with max 16K).. Also we have log 
rotators inside opal_errd to remove old logs.  So this directory won't grow more 
than few MBs.

Also proper debugging we need all the logs...Hence we want to capture entire 
directory here.

Let me know if you have any more questions.

-Vasant