| To: | Zhi Yong Wu <zwu.kernel@xxxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH] xfs: fix an assertion failure |
| From: | Dave Chinner <david@xxxxxxxxxxxxx> |
| Date: | Fri, 26 Jul 2013 21:37:17 +1000 |
| Cc: | xfstests <xfs@xxxxxxxxxxx>, "linux-fsdevel@xxxxxxxxxxxxxxx" <linux-fsdevel@xxxxxxxxxxxxxxx>, linux-kernel mlist <linux-kernel@xxxxxxxxxxxxxxx>, Zhi Yong Wu <wuzhy@xxxxxxxxxxxxxxxxxx> |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <CAEH94LiXtG=DD+Qn4kbNT_Y_Qn65wVYrpYvHKXOob6wru3SeDw@xxxxxxxxxxxxxx> |
| References: | <1374759524-10061-1-git-send-email-zwu.kernel@xxxxxxxxx> <20130726020318.GD21982@dastard> <CAEH94LiXtG=DD+Qn4kbNT_Y_Qn65wVYrpYvHKXOob6wru3SeDw@xxxxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.21 (2010-09-15) |
On Fri, Jul 26, 2013 at 02:01:23PM +0800, Zhi Yong Wu wrote: > No, it still raised the same assertion as below: > > [ 521.715103] XFS: Assertion failed: !(bip->bli_item.li_flags & > XFS_LI_IN_AIL), file: fs/xfs/xfs_buf_item.c, line: 940 How are you reproducing it? Can you take an event trace with trace-cmd and attach the output of the report? Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH] xfs: introduce object readahead to log recovery, Dave Chinner |
|---|---|
| Next by Date: | Re: [PATCH v6 5/7] xfs: create internal eofblocks structure with kuid_t types, Brian Foster |
| Previous by Thread: | Re: [PATCH] xfs: fix an assertion failure, Zhi Yong Wu |
| Next by Thread: | Re: [PATCH] xfs: fix an assertion failure, Zhi Yong Wu |
| Indexes: | [Date] [Thread] [Top] [All Lists] |