Re: 3.9.0: general protection fault

[Bernd Schubert <bernd.schubert@itwm.fraunhofer.de>]

Just an update here, the issue only came up once again on another system 
and I didn't have time for a couple of days to even save the collectl 
log file. I then increased the max number of rotated log files, but it 
didn't happen again ever since. So I don't have any logs about the state 
of the system at crash time so far.
However, I just got a captured file corruption:

> (squeeze)fslab3:~/fstests# cat /mnt/fhgfs//fslab4/ql-fstest/fstest13579.err
> File corruption in /mnt/fhgfs//fslab4/ql-fstest/fstest.13635/d040/d030/7ae214d1 (create time: Mon Jun  3 17:36:11 2013) around 246415360 [pattern = 7ae214d1]
> After n-checks: 3
> Expected: d1, got: 83 (pos = 247324600)
> Expected: 14, got: ec (pos = 247324601)
> Expected: e2, got: 30 (pos = 247324602)
> Expected: 7a, got: 48 (pos = 247324603)
> Expected: d1, got: 89 (pos = 247324604)
> Expected: 14, got: 5d (pos = 247324605)
> Expected: e2, got: e8 (pos = 247324606)
...
> Expected: 14, got: 84 (pos = 247324661)
> Expected: e2, got: b9 (pos = 247324662)
> Expected: 7a, got: 0 (pos = 247324663)

Hmm, exactly 64 bytes of corrupted data, the file itself has a size of 
512MiB.

I'm going to export single disks from the controller to use it with 
md-raid6 as this allows to do parity checks and to identify bad disks.


Cheers,
Bernd

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs