6.2(16): Nexus-7010-16-2-16# echo ; dir logflash: ; echo
50193 Aug 19 22:48:09 2018 accounting_log 250109 Aug 12 23:34:44 2018 accounting_log.1 4096 Nov 28 03:32:34 2013 core/ 4096 Nov 28 03:32:34 2013 debug/ 1068 May 03 05:50:16 2018 event_archive_1 25645 May 22 16:42:41 2016 forwarding_debug_data 4096 Nov 28 03:32:34 2013 generic/ 4096 Feb 12 04:29:44 2014 log/ Usage for logflash://sup-local 6916423680 bytes used 963309568 bytes free 7879733248 bytes total Nexus-7010-16-2-16# On 8/18/18, 5:22 PM, "Pavel Korovin" <p...@tristero.se> wrote: On 08/18, heasley wrote: > Fri, Aug 17, 2018 at 10:16:51PM +0300, Pavel Korovin: > > There are several issues with fluctuating data received from Cisco Nexus > > platform (55xx, 77xx): > > > > * if PAR_COUNT is > 1 (by default, it's 5) and rancid simultaneously runs > > "show version" in multiple VDCs on the same device, bootflash size > > slot0 too? or just bootflash? I don't have Nexus devices with slot0 size > 0, but I suppose it should be the same story. > > values hop between 0 and actual size, with each invocation producing cvs > > commits and change notifications. To reproduce, run "show ver" > > simultaneously on multiple VDCs. It seems that NX-OS requires exclusive > > access to hardware to determine the size of bootflash and fails during > > concurrent access. I cannot offer any better solution than just > > providing a knob to filter out bootflash size fluctuations by setting > > FILTER_OSC = ALL. > > - # Drop accounting.log > > - /\s+accounting\.log$/ && next; > > + # Drop accounting logs > > + /\s+accounting.log.*/ && next; > > was removal of the escape of the . intentional? Yes. I don't remember if earlier versions of NX-OS use accounting_log or accounting.log naming, so it will filter both. -- With best regards, Pavel Korovin _______________________________________________ Rancid-discuss mailing list Rancid-discuss@shrubbery.net http://www.shrubbery.net/mailman/listinfo/rancid-discuss