On Mon, May 06, 2013 at 02:47:31PM +0200, Bernd Schubert wrote: > On 05/06/2013 02:28 PM, Dave Chinner wrote: > >On Mon, May 06, 2013 at 10:14:22AM +0200, Bernd Schubert wrote: > >>And anpther protection fault, this time with 3.9.0. Always happens > >>on one of the servers. Its ECC memory, so I don't suspect a faulty > >>memory bank. Going to fsck now- > > > >http://xfs.org/index.php/XFS_FAQ#Q:_What_information_should_I_include_when_reporting_a_problem.3F > > Isn't that a bit overhead? And I can't provide /proc/meminfo and > others, as this issue causes a kernel panic a few traces later. Provide what information you can. Without knowing a single thing about your hardware, storage config and workload, I can't help you at all. You're asking me to find a needle in a haystack blindfolded and with both hands tied behind my back.... Stuff like /proc/meminfo doesn't have to be provided from exactly the time of the crash - it's just the simplest way to find out how much RAM you have in the machine, so a dump from whenever the machine is up and running the workload is fine. Other information we ask for (e.g. capturing the output of `vmstat 5` as suggested in the FAQ) gives us the runtime variation of memory usage and easy to capture right up to the failure point.... Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx _______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
