From: Paul Slootman <paul@wurtel.net>
To: xfs@oss.sgi.com
Subject: Re: XFS internal error XFS_WANT_CORRUPTED_GOTO
Date: Tue, 15 Aug 2006 13:54:42 +0200 [thread overview]
Message-ID: <20060815115442.GA9248@wurtel.net> (raw)
In-Reply-To: <20060814141731.GA9098@wurtel.net>
On Mon 14 Aug 2006, Paul Slootman wrote:
>
> kernel: 2.6.17.7 x86_64
> xfstools: 2.8.11 from CVS last week
>
> I'm now running the "standard" debian xfs_repair (version 2.6.20) for kicks,
> as the 2.8.11 version didn't really seem to help much. I'm now getting
> plenty of these errors:
[snip]
After all that, again, tonight:
Aug 15 01:11:57 boes kernel: Filesystem "md6": XFS internal error xfs_trans_cancel at line 1150 of file fs/xfs/xfs_trans.c. Caller 0xffffffff880577d3
Aug 15 01:11:57 boes kernel:
Aug 15 01:11:57 boes kernel: Call Trace: <ffffffff880501d0>{:xfs:xfs_trans_cancel+96}
Aug 15 01:11:57 boes kernel: <ffffffff880577d3>{:xfs:xfs_create+1587} <ffffffff88062381>{:xfs:xfs_vn_mknod+433}
Aug 15 01:11:57 boes kernel: <ffffffff8805076c>{:xfs:xfs_trans_unlocked_item+44}
Aug 15 01:11:57 boes kernel: <ffffffff8805e1ae>{:xfs:xfs_buf_rele+62} <ffffffff880260f1>{:xfs:xfs_da_brelse+129}
Aug 15 01:11:57 boes kernel: <ffffffff8802c24b>{:xfs:xfs_dir2_leaf_lookup_int+555}
Aug 15 01:11:57 boes kernel: <ffffffff8802bf93>{:xfs:xfs_dir2_leaf_lookup+35} <ffffffff8802842f>{:xfs:xfs_dir2_isleaf+31}
Aug 15 01:11:57 boes kernel: <ffffffff88027b9f>{:xfs:xfs_dir2_lookup+255} <ffffffff802892ef>{link_path_walk+415}
Aug 15 01:11:57 boes kernel: <ffffffff880560aa>{:xfs:xfs_access+74} <ffffffff80289e9e>{vfs_create+142}
Aug 15 01:11:57 boes kernel: <ffffffff8028a22f>{open_namei+383} <ffffffff80278ff7>{do_filp_open+39}
Aug 15 01:11:57 boes kernel: <ffffffff80279211>{get_unused_fd+113} <ffffffff80279406>{do_sys_open+70}
Aug 15 01:11:57 boes kernel: <ffffffff80209b5a>{system_call+126}
Aug 15 01:11:57 boes kernel: xfs_force_shutdown(md6,0x8) called from line 1151 of file fs/xfs/xfs_trans.c. Return address = 0xffffffff88065ba8
Aug 15 01:11:57 boes kernel: Filesystem "md6": Corruption of in-memory data detected. Shutting down filesystem: md6
Aug 15 01:11:57 boes kernel: Please umount the filesystem, and rectify the problem(s)
The only thing the (2.8.11) xfs_repair reported was, in phase 3:
data fork in ino 2995825682 claims free block 251664817
Paul Slootman
next prev parent reply other threads:[~2006-08-15 11:55 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-10 16:42 cache_purge: shake on cache 0x5880a0 left 8 nodes!? Paul Slootman
2006-08-11 1:30 ` Barry Naujok
2006-08-11 9:02 ` Paul Slootman
2006-08-12 9:14 ` Paul Slootman
2006-08-14 14:17 ` XFS internal error XFS_WANT_CORRUPTED_GOTO Paul Slootman
2006-08-15 11:54 ` Paul Slootman [this message]
2006-08-15 1:49 ` cache_purge: shake on cache 0x5880a0 left 8 nodes!? Barry Naujok
2006-08-15 11:55 ` Paul Slootman
2006-08-14 14:59 ` Chris Wedgwood
2006-08-14 15:55 ` Paul Slootman
-- strict thread matches above, loose matches on Subject: below --
2007-04-19 13:28 XFS internal error XFS_WANT_CORRUPTED_GOTO Burbidge, Simon A
2007-04-19 14:18 ` David Chinner
2007-04-19 14:36 ` Burbidge, Simon A
2007-04-19 22:10 ` David Chinner
2008-05-29 13:48 Louis-David Mitterrand
2009-06-24 11:56 Nitin Arora
2009-06-24 12:40 ` Michael Monnerie
2009-06-24 13:18 ` Nitin Arora
2009-06-24 13:23 ` Eric Sandeen
2009-06-25 10:06 ` Nitin Arora
2009-06-25 13:45 ` Eric Sandeen
2011-07-22 4:52 Amit Sahrawat
2011-07-22 5:23 ` Amit Sahrawat
2011-07-22 6:59 ` Amit Sahrawat
2011-07-22 8:34 ` Dave Chinner
2011-07-22 10:33 ` Amit Sahrawat
2011-07-24 1:34 ` Dave Chinner
2011-07-25 5:26 ` Amit Sahrawat
2011-07-26 3:33 ` Dave Chinner
2011-07-26 9:47 ` Ajeet Yadav
2011-07-26 10:27 ` Christoph Hellwig
2011-07-27 4:33 ` Amit Sahrawat
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=20060815115442.GA9248@wurtel.net \
--to=paul@wurtel.net \
--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.