From: "Avuton Olrich" <avuton@gmail.com>
To: "Nathan Scott" <nathans@sgi.com>
Cc: linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: XFS crashed twice, once in 2.6.16.20, next in 2.6.17, reproducable
Date: Mon, 19 Jun 2006 23:40:34 -0700 [thread overview]
Message-ID: <3aa654a40606192340l67d0353fj875767d33d8bd493@mail.gmail.com> (raw)
In-Reply-To: <20060620161006.C1079661@wobbly.melbourne.sgi.com>
On 6/19/06, Nathan Scott <nathans@sgi.com> wrote:
> How reproducible is it? Is it reproducible even after xfs_repair?
It happens everytime I try to delete the directory.
Also, forgot to mention I ran xfs_check on it and it gave me more
information than I had before:
More information, ran xfs_check and got the following:
missing free index for data block 0 in dir ino 1507133580
missing free index for data block 2 in dir ino 1507133580
missing free index for data block 3 in dir ino 1507133580
missing free index for data block 4 in dir ino 1507133580
missing free index for data block 5 in dir ino 1507133580
missing free index for data block 6 in dir ino 1507133580
missing free index for data block 7 in dir ino 1507133580
missing free index for data block 8 in dir ino 1507133580
missing free index for data block 9 in dir ino 1507133580
--
avuton
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
next prev parent reply other threads:[~2006-06-20 6:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-19 7:44 Avuton Olrich
2006-06-19 10:35 ` daniel+devel.linux.lkml
2006-06-20 6:10 ` Nathan Scott
2006-06-20 6:38 ` Avuton Olrich
2006-06-20 6:43 ` Nathan Scott
2006-06-20 6:50 ` Avuton Olrich
2006-06-20 6:52 ` Nathan Scott
2006-06-20 8:20 ` Avuton Olrich
2006-06-20 8:39 ` Duncan Sands
2006-06-22 2:56 ` Nathan Scott
2006-06-25 10:09 ` Duncan Sands
2006-06-25 13:55 ` Duncan Sands
2006-06-20 6:40 ` Avuton Olrich [this message]
2006-06-20 8:57 ` Justin Piszcz
2006-06-20 17:01 ` Avuton Olrich
2006-06-20 17:15 ` Justin Piszcz
2006-06-20 17:21 ` Avuton Olrich
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=3aa654a40606192340l67d0353fj875767d33d8bd493@mail.gmail.com \
--to=avuton@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nathans@sgi.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
all inboxes | Powered by JetHome®