From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs-oss <xfs@oss.sgi.com>
Subject: xfs_repair 3.1.2 crashing
Date: Thu, 10 Jun 2010 13:06:07 +0200 [thread overview]
Message-ID: <201006101306.07587@zmi.at> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1815 bytes --]
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 1 - find and verify superblock...
Phase 2 - using internal log
- zero log...
- scan filesystem freespace and inode maps...
- found root inode chunk
Phase 3 - for each AG...
- scan and clear agi unlinked lists...
- process known inodes and perform inode discovery...
- agno = 0
- agno = 1
local inode 2267035928 attr too small (size = 3, min size = 4)
bad attribute fork in inode 2267035928, clearing attr fork
clearing inode 2267035928 attributes
cleared inode 2267035928
- agno = 2
- agno = 3
- agno = 4
- agno = 5
- agno = 6
- process newly discovered inodes...
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?
Before that, I had 3.0.3 installed, it found tons of errors before also
crashing. I'll send that log later.
--
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc
it-management Internet Services
http://proteger.at [gesprochen: Prot-e-schee]
Tel: 0660 / 415 65 31
// Wir haben im Moment zwei Häuser zu verkaufen:
// http://zmi.at/langegg/
// http://zmi.at/haus2009/
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2010-06-10 11:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-10 11:06 Michael Monnerie [this message]
2010-06-10 16:27 ` xfs_repair 3.1.2 crashing Eric Sandeen
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=201006101306.07587@zmi.at \
--to=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