From: Eric Sandeen <sandeen@sandeen.net>
To: Michael Monnerie <michael.monnerie@is.it-management.at>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: xfs_repair 3.1.2 crashing
Date: Thu, 10 Jun 2010 11:27:40 -0500 [thread overview]
Message-ID: <4C11127C.3030907@sandeen.net> (raw)
In-Reply-To: <201006101306.07587@zmi.at>
Michael Monnerie wrote:
> Dear devs, I have a massive problem with a filesystem in our internal
> server. We've had an overheating problem with the RAID controller CPU,
> as it's very hot here and aircondition was turn off... the system "just"
> stopped working. This is a XenServer with some Linuxen on it, and one of
> them (of course our main server :-) reports this on xfs_repair:
>
...
> Phase 4 - check for duplicate blocks...
> - setting up duplicate extent list...
> - check for inodes claiming duplicate blocks...
> - agno = 0
> - agno = 2
> - agno = 1
> data fork in regular inode 2267035928 claims used block 537158068
> xfs_repair: dinode.c:2101: process_inode_data_fork: Assertion `err == 0'
> failed.
>
> Any ideas?
It'd be great to at least capture the issue by creating an xfs_metadump
image for analysis...
-Eric
> Before that, I had 3.0.3 installed, it found tons of errors before also
> crashing. I'll send that log later.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-06-10 16:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-10 11:06 xfs_repair 3.1.2 crashing Michael Monnerie
2010-06-10 16:27 ` Eric Sandeen [this message]
2010-06-11 23:38 ` Michael Monnerie
2010-06-12 1:38 ` Eric Sandeen
2010-06-12 10:41 ` Michael Monnerie
2010-06-23 18:32 ` Michael Monnerie
2010-06-12 13:33 ` Michael Monnerie
2010-06-14 12:47 ` Michael Monnerie
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=4C11127C.3030907@sandeen.net \
--to=sandeen@sandeen.net \
--cc=michael.monnerie@is.it-management.at \
--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