public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Arkadiusz Miśkiewicz" <arekm@maven.pl>
To: xfs@oss.sgi.com
Subject: Re: xfs_repair fails with corrupt dinode 17491441757, extent total = 1, nblocks = 0.  This is a bug.
Date: Sun, 6 Nov 2011 23:19:01 +0100	[thread overview]
Message-ID: <201111062319.01375.arekm@maven.pl> (raw)
In-Reply-To: <201110311156.20421.arekm@maven.pl>

On Monday 31 of October 2011, Arkadiusz Miśkiewicz wrote:
> xfs_repair version 3.1.6
> 
> disconnected inode 17491441754, moving to lost+found
> disconnected inode 17491441755, moving to lost+found
> disconnected inode 17491441756, moving to lost+found
> disconnected inode 17491441757, moving to lost+found
> corrupt dinode 17491441757, extent total = 1, nblocks = 0.  This is a bug.
> Please capture the filesystem metadata with xfs_metadump and
> report it to xfs@oss.sgi.com.
> cache_node_purge: refcount was 1, not zero (node=0x21450c90)
> 
> fatal error -- 117 - couldn't iget disconnected inode

> In meantime I'll probably make ugly hack by making "couldn't iget
> disconnected inode" non fatal, so repair will be able to finish.

With this one repair finished and then while repairing for second time
(this time without hack) I got glibc catching invalid free:

name create failed in ino 17873999459 (117), filesystem may be out of space
bad hash table for directory inode 17875023137 (brak wpisu danych): przebudowano
rebuilding directory inode 17875023137
*** glibc detected *** /sbin/xfs_repair: free(): invalid next size (normal): 0x00007f9ffcdc4c00 ***
======= Backtrace: =========
/lib64/libc.so.6(+0x758b6)[0x7fa146a6b8b6]
/lib64/libxfs.so.0(libxfs_getbufr+0x81)[0x7fa14738de81]
/lib64/libxfs.so.0(cache_node_get+0xca)[0x7fa14738a39a]
/lib64/libxfs.so.0(libxfs_getbuf+0x29)[0x7fa14738dfc9]
/sbin/xfs_repair[0x425cd0]
/sbin/xfs_repair[0x426aa6]
/lib64/libpthread.so.0(+0x7ed5)[0x7fa146d8ced5]
/lib64/libc.so.6(clone+0x6d)[0x7fa146acfe5d]
======= Memory map: ========
00400000-0043e000 r-xp 00000000 08:12 125854083                          /sbin/xfs_repair
0043f000-00440000 r--p 0003e000 08:12 125854083                          /sbin/xfs_repair
00440000-00441000 rw-p 0003f000 08:12 125854083                          /sbin/xfs_repair
00441000-2aa06000 rw-p 00000000 00:00 0                                  [heap]
7f9f00000000-7f9f01123000 rw-p 00000000 00:00 0
7f9f01123000-7f9f04000000 ---p 00000000 00:00 0
7f9f077ff000-7f9f07800000 ---p 00000000 00:00 0
7f9f07800000-7f9f08000000 rw-p 00000000 00:00 0
[...]

-- 
Arkadiusz Miśkiewicz        PLD/Linux Team
arekm / maven.pl            http://ftp.pld-linux.org/

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      parent reply	other threads:[~2011-11-06 22:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-31 10:56 xfs_repair fails with corrupt dinode 17491441757, extent total = 1, nblocks = 0. This is a bug Arkadiusz Miśkiewicz
2011-11-03 10:26 ` Christoph Hellwig
2011-11-03 10:40   ` Arkadiusz Miśkiewicz
2011-11-03 10:48     ` Christoph Hellwig
2011-11-03 10:57       ` Arkadiusz Miśkiewicz
2011-11-03 11:03         ` Christoph Hellwig
2011-11-03 11:54           ` Christoph Hellwig
2011-11-03 20:02             ` Arkadiusz Miśkiewicz
2011-11-03 20:21           ` Arkadiusz Miśkiewicz
2011-11-06 22:19 ` Arkadiusz Miśkiewicz [this message]

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=201111062319.01375.arekm@maven.pl \
    --to=arekm@maven.pl \
    --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