|To:||Amit Sahrawat <amit.sahrawat83@xxxxxxxxx>|
|Subject:||Re: XFS internal error xfs_da_do_buf(1) at line 1992 of file fs/xfs/xfs_da_btree.c|
|From:||Eric Sandeen <sandeen@xxxxxxxxxxx>|
|Date:||Thu, 22 Oct 2009 21:37:21 -0500|
|References:||<c2dcdfa40910202307m77a9d7c5lf18e278a9ebae08e@xxxxxxxxxxxxxx> <4ADF2EE8.6010700@xxxxxxxxxxx> <c2dcdfa40910211032y5b1d2cd8l418491327d24b87b@xxxxxxxxxxxxxx> <4ADF4882.70106@xxxxxxxxxxx> <c2dcdfa40910220209v781f6a76u31e349ea461bc10a@xxxxxxxxxxxxxx> <4AE06BAE.8090706@xxxxxxxxxxx> <c2dcdfa40910220930l19a8dab0y88e80630a2453b39@xxxxxxxxxxxxxx> <4AE08AED.1020702@xxxxxxxxxxx> <c2dcdfa40910220955q586bdcabn268ddbc30d9b785d@xxxxxxxxxxxxxx>|
|User-agent:||Thunderbird 188.8.131.52 (Macintosh/20090812)|
Amit Sahrawat wrote:
that means it highely unlikey to get a fix for this issue :(Yes, backporting just doest not suits for me. I am trying to dig into the code, but really dont know if that's going to be that easy. Thanks Eric for all the help.W'll you know if I am able to fix this.
One other thought on the backporting side; RHEL5.4 now has xfs merged into a 2.6.18-ish kernel. There are still some other supporting bits in that kernel, it's hardly vanilla 2.6.18, but if you want to try a backport route it might be one option.
Testing an upstream kernel w/ your testcase in an emulator would also be a reasonable thing to do, I think.
Thanks & Regards, Amit Sahrawat
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||Re: 2.6.31+184.108.40.206: XFS - All I/O locks up to D-state after 24-48 hours (sysrq-t+w available), Dave Chinner|
|Next by Date:||Gewinnanspruch !, LA PRIMITIVA PROGRAM|
|Previous by Thread:||Re: XFS internal error xfs_da_do_buf(1) at line 1992 of file fs/xfs/xfs_da_btree.c, Amit Sahrawat|
|Next by Thread:||Re: XFS internal error xfs_da_do_buf(1) at line 1992 of file fs/xfs/xfs_da_btree.c, Amit Sahrawat|
|Indexes:||[Date] [Thread] [Top] [All Lists]|