mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Avuton Olrich" <avuton@gmail.com>
To: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	linux-xfs@oss.sgi.com
Subject: XFS crashed twice, once in 2.6.16.20, next in 2.6.17, reproducable
Date: Mon, 19 Jun 2006 00:44:58 -0700	[thread overview]
Message-ID: <3aa654a40606190044q43dca571qdc06ee13d82d979@mail.gmail.com> (raw)

Didn't make it to the linux-xfs list, it's not working so I'll try by
sending it both to the LKML and linux-xfs again.

Hello, when trying to recursively delete a directory (same directory
twice) from my 500gb hard drive I get a problem. It crashed first in
2.6.16.20, then I upgraded to try to get rid of the issue. This one is
from 2.6.17:

xfs_da_do_buf: bno 16777216
dir: inode 1507133580
Filesystem "sda1": XFS internal error xfs_da_do_buf(1) at line 2119 of
file /usr/src/linux-stable-cold/fs/xfs/xfs_da_btree.c.  Caller 0xb01
d9b63
 <b01d9720> xfs_da_do_buf+0x40e/0x7c7  <b01d9b63> xfs_da_read_buf+0x30/0x35
 <b01e43d5> xfs_dir2_leafn_lookup_int+0x2f3/0x453  <b01d9b63>
xfs_da_read_buf+0x30/0x35
 <b01e2ba5> xfs_dir2_node_removename+0x288/0x47f  <b01e2ba5>
xfs_dir2_node_removename+0x288/0x47f
 <b01ddbd3> xfs_dir2_removename+0xce/0xd5  <b020ff5d> kmem_zone_alloc+0x4d/0x98
 <b020d0ef> xfs_remove+0x2ac/0x444  <b0215e7f> xfs_vn_unlink+0x17/0x3b
 <b020a32b> xfs_lookup+0x6e/0x78  <b011e734> __capable+0xc/0x1f
 <b0155827> generic_permission+0x93/0xcc  <b01558f8> permission+0x98/0xa4
 <b0155da0> may_delete+0x32/0xe9  <b0156243> vfs_unlink+0x6d/0xa3
 <b0157c7a> do_unlinkat+0x92/0x125  <b0159a0d> sys_getdents64+0x9c/0xa6
 <b0102b67> sysenter_past_esp+0x54/0x75
Filesystem "sda1": XFS internal error xfs_trans_cancel at line 1150 of
file /usr/src/linux-stable-cold/fs/xfs/xfs_trans.c.  Caller 0xb020d2
5e
 <b0204b48> xfs_trans_cancel+0x59/0xe5  <b020d25e> xfs_remove+0x41b/0x444
 <b020d25e> xfs_remove+0x41b/0x444  <b0215e7f> xfs_vn_unlink+0x17/0x3b
 <b020a32b> xfs_lookup+0x6e/0x78  <b011e734> __capable+0xc/0x1f
 <b0155827> generic_permission+0x93/0xcc  <b01558f8> permission+0x98/0xa4
 <b0155da0> may_delete+0x32/0xe9  <b0156243> vfs_unlink+0x6d/0xa3
 <b0157c7a> do_unlinkat+0x92/0x125  <b0159a0d> sys_getdents64+0x9c/0xa6
 <b0102b67> sysenter_past_esp+0x54/0x75
xfs_force_shutdown(sda1,0x8) called from line 1151 of file
/usr/src/linux-stable-cold/fs/xfs/xfs_trans.c.  Return address =
0xb0218b68
Filesystem "sda1": Corruption of in-memory data detected.  Shutting
down filesystem: sda1

While trying to xfs_repair I get the following:
fatal error -- can't read block 16777216 for directory inode 1507133580

Badblocks has been run on this machine and it was sucessful.

I did find an old thread with this, but no solution:
http://oss.sgi.com/archives/xfs/2005-02/msg00067.html

config:
http://olricha.homelinux.net:8080/config.gz

Thanks for any help. If I can help at all please let me know.
-- 
avuton
--
 Anyone who quotes me in their sig is an idiot. -- Rusty Russell.

             reply	other threads:[~2006-06-19  7:45 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-19  7:44 Avuton Olrich [this message]
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
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=3aa654a40606190044q43dca571qdc06ee13d82d979@mail.gmail.com \
    --to=avuton@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-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

Powered by JetHome