On 03/17/2013 11:38 PM, Ryan Mitchell wrote:
Hi Scooter,
On 03/16/2013 07:59 AM, Scooter Morris wrote:
Hi all,
We got the backtrace again on kernel-2.6.32-358.2.1.el6:
Can I ask if you ran fsck on the filesystem after updating to the new
kernel? I'm wondering if there was some corruption from an earlier
event in the filesystem that has triggered after you updated.
We ran fsck on the filesystems after the upgrade to
kernel-2.6.32-358.0.1.el6 (i.e. after we first noticed the problem)
Bob, you mentioned bz 875753, but Steve mentioned bz 908398. Both of
those bugs are closed, so I can't determine if this they are different
bugs, or related in some way. Are both supposed to be fixed in
kernel-2.6.32-358.2.1.el6 or should I put in a ticket and ask for the
kernel with the fix for 908398?
Bz#875753 and bz#908398 are the same issue. The former is the master
bug where the issue was initially reported. The later is the z-stream
bug that is responsible for the fix getting into
kernel-2.6.32-358.2.1.el6
Got it -- thanks. That helps.
It would be great if you could raise a case and upload the vmcore to
Red Hat Support. I'd like to make sure we've resolved the issue
completely.
Already raised the case: 00806983
Regards,
Ryan Mitchell
Red Hat Global Support Services
Thanks!
-- scooter
--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster
