On 09/02/2010 14:04, Sambit Nayak wrote: > Hi Robert, > > In case you are still at this problem and want to look at older CMM > trace messages : > > cmm_dbg_buf is the CMM trace buffer, and it wraps around as you > already noted. > The buffer structure holds the previous snapshot of the trace buffer > (before the wraparound), apart from the current view after the > wraparound. > Try checking : > > *(cmm_dbg_buf+8)+1/s <--- gives you the older part, before the > wraparound > instead of > > *cmm_dbg_buf/s <--- gives you the current buffer after the wraparound > > If the messages you are looking for are even older, then you can't see > them in the trace buffer. :( > >
Thank you! This might be handy one day. Unfortunately it's already too late... btw: is there a way to get a date of events in cmm dbg buffer? is it the tm fields? (but it's not a unix timestamp...) However I still haven't found the root-cause and because the corruption happend also to some data within ZFS pool... anyway despite writing much more data and running zfs scrub several times no new corruption happened which indicates it was a temporary problem - which is really bad as we can't be sure if/when it will happen again. The only suspicious thing I can see is er_other_discard=17 on a brocade switch on a port where one of the nodes is connected to - but I can't see any other errors on the node itself. -- Robert Milkowski http://milek.blogspot.com
