|To:||xfs@xxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, linux-raid@xxxxxxxxxxxxxxx|
|Subject:||2.6.31: xfs or md/raid1 bug in 2.6.31?|
|From:||Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>|
|Date:||Fri, 16 Oct 2009 08:37:03 -0400 (EDT)|
|Cc:||Alan Piszcz <ap@xxxxxxxxxxxxx>|
|User-agent:||Alpine 2.00 (DEB 1167 2008-08-23)|
Hi all, Does anyone recall if there was a serious xfs bug in 2.6.31?I saw xfsbufd/pdflush etc locked up and local file system access hung whenever I tried to write a file to the filesystem, I ran a sysrq-t but could not capture the output nor did I see anything obvious.
System runs a md/raid1+xfs. Upgraded to 184.108.40.206, will have to see if it happens again.Was curious though if anyone recalled problems with this kernel release/combination?
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||Re: XFS mount failuer on RAID5, Justin Piszcz|
|Next by Date:||Re: XFS mount failuer on RAID5, Eric Sandeen|
|Previous by Thread:||XFS mount failuer on RAID5, hank peng|
|Next by Thread:||2.6.31+220.127.116.11: XFS - All I/O locks up to D-state after 24-48 hours (sysrq-t+w available), Justin Piszcz|
|Indexes:||[Date] [Thread] [Top] [All Lists]|