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: Wed, 21 Oct 2009 12:44:34 -0500 [thread overview]
Message-ID: <4ADF4882.70106@sandeen.net> (raw)
In-Reply-To: <c2dcdfa40910211032y5b1d2cd8l418491327d24b87b@mail.gmail.com>
Amit Sahrawat wrote:
> Thanks Eric,
>
> Yes, I am able to get this for the same Inode and Block number.
>
> xfs_check reports error for dir inode 128 missing leaf entries..(exact
> string I m missing), will provide you the details.
>
> Using xfs_repair fixes the problem. But again the same operation leads
> to the crash.
> Even on a freshly formatted disk, I get this error.
>
> Please let me know from where I can get this patch to try whether it
> fixes for me or not.
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff_plain;h=ae23a5e87dbbf4657a82e1ff8ebc52ab50361c14
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-10-21 17:43 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 [this message]
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
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=4ADF4882.70106@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.