Hi folks, I believe we've been hitting the same issue that Gabriel Barazer reported in 2.6.28.9 on the 22nd of July on our NFS server for our HPC Linux clusters. Here is the backtrace we got this mor
Oops - I meant to also attach our kernel config! Here it is.. cheers, Chris -- Christopher Samuel - (03) 9925 4751 - Systems Manager The Victorian Partnership for Advanced Computing P.O. Box 201, Car
... I'll take a look. The reason for the objdump was to try to work out where in xfs_rename we were erroring out, but in your case: xfs_rename+0x5ac/0x5af I guess it's the trans_cancel at the very en
Hi Eric, Thanks for the speedy response! Thanks for that. Happy to do that, though we won't be able to reboot into it until another crash fails (the impact on the HPC jobs is too large I'm afraid :-(
Unfortunately we had another failure on Saturday and after getting some feedback from users we've had to regress to the Debian 2.6.26-4 kernel (we avoided that initially because of a separate issue,
Hi all, this may be a bit off topic but i want to point out that included xfs_objdump seems to be corrupted. I think there are too many branches and calls and no other instructions. i couldn't see al
... Just for the record, Chris let me know offline that he tried ext4 and got an error: so he got IO errors to sector 1430524111 and sector 63 (!) the question may now be whether xfs got an IO error
Umm, I think you've mixed me up with another Chris, we've never run ext4 on that system! -- Christopher Samuel - (03) 9925 4751 - Systems Manager The Victorian Partnership for Advanced Computing P.O.