From: Eric Sandeen <sandeen@sandeen.net>
To: Amit Sahrawat <amit.sahrawat83@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: XFS internal error xfs_da_do_buf(1) at line 1992 of file fs/xfs/xfs_da_btree.c
Date: Thu, 22 Oct 2009 11:40:13 -0500 [thread overview]
Message-ID: <4AE08AED.1020702@sandeen.net> (raw)
In-Reply-To: <c2dcdfa40910220930l19a8dab0y88e80630a2453b39@mail.gmail.com>
Amit Sahrawat wrote:
> I am already using that patch.
> Other than using higher XFS version, can I try any other thing?
>
> I cannot directly use higher XFS version, I will have to backport the
> changes for higher to the kernel I am using because of dependencies.
>
backporting xfs would be hard; I was hoping that perhaps you could just
boot a newer kernel, though I know w/ vendor arm kernels that can be tough.
There are drawbacks to not getting machine support upstream... :)
I don't really have other things for you to try, and don't have a lot of
time to debug 3 year old kernels either... :(
You could try your arm testcase in a qemu emulator on a new kernel; if
that shows the same problem I'll be much more interested & motivated...
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-10-22 16:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-21 6:07 XFS internal error xfs_da_do_buf(1) at line 1992 of file fs/xfs/xfs_da_btree.c Amit Sahrawat
2009-10-21 15:55 ` Eric Sandeen
2009-10-21 17:32 ` Amit Sahrawat
2009-10-21 17:44 ` Eric Sandeen
2009-10-22 9:09 ` Amit Sahrawat
2009-10-22 14:26 ` Eric Sandeen
2009-10-22 16:30 ` Amit Sahrawat
2009-10-22 16:40 ` Eric Sandeen [this message]
2009-10-22 16:55 ` Amit Sahrawat
2009-10-23 2:37 ` Eric Sandeen
2009-10-24 8:28 ` Amit Sahrawat
2009-10-24 14:45 ` Eric Sandeen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AE08AED.1020702@sandeen.net \
--to=sandeen@sandeen.net \
--cc=amit.sahrawat83@gmail.com \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox