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 21:37:21 -0500 [thread overview]
Message-ID: <4AE116E1.5050008@sandeen.net> (raw)
In-Reply-To: <c2dcdfa40910220955q586bdcabn268ddbc30d9b785d@mail.gmail.com>
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.
-eric
> Thanks & Regards,
> Amit Sahrawat
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-10-23 2:35 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
2009-10-22 16:55 ` Amit Sahrawat
2009-10-23 2:37 ` Eric Sandeen [this message]
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=4AE116E1.5050008@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.