| To: | Mike Gao <ygao.linux@xxxxxxxxx> |
|---|---|
| Subject: | Re: What should to do with ASSERT failed |
| From: | Dave Chinner <david@xxxxxxxxxxxxx> |
| Date: | Tue, 31 Aug 2010 10:30:51 +1000 |
| Cc: | Eric Sandeen <sandeen@xxxxxxxxxxx>, xfs@xxxxxxxxxxx |
| In-reply-to: | <AANLkTinXDQoo7ZU+w2V7N7zBrxdS=Tc71MNZ7M4R5A9w@xxxxxxxxxxxxxx> |
| References: | <AANLkTin-zf0chkk68pGfwDRt03QaKmNdsP3=goDEUS+p@xxxxxxxxxxxxxx> <4C7C26E8.9070308@xxxxxxxxxxx> <AANLkTinXDQoo7ZU+w2V7N7zBrxdS=Tc71MNZ7M4R5A9w@xxxxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.20 (2009-06-14) |
On Mon, Aug 30, 2010 at 05:56:07PM -0500, Mike Gao wrote: > Thanks very much for help. The kernel is pretty old, 2.6.19 but the xfs is > pretty new. > the block size is 512 and use mmap for test with write and read compare. > (xfstest 074). Can you reproduce it on a more recent kernel? The buffer flags are modified by code outside XFS which could be significantly different in 2.6.19 comapred to 2.6.34/35, so it may not be aproblem with the XFS code as such.... Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: What should to do with ASSERT failed, Eric Sandeen |
|---|---|
| Next by Date: | Re: XFS Quota Check OOM, Stefan Priebe - Profihost AG |
| Previous by Thread: | Re: What should to do with ASSERT failed, Eric Sandeen |
| Next by Thread: | Re: What should to do with ASSERT failed, Mike Gao |
| Indexes: | [Date] [Thread] [Top] [All Lists] |