From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs mailing list <xfs@oss.sgi.com>
Subject: xfs_repair 3.0.3 crash and abort
Date: Fri, 26 Mar 2010 12:57:37 +0100 [thread overview]
Message-ID: <201003261257.41233@zmi.at> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 4494 bytes --]
I tried a repair on one server, but it crashes:
# xfs_repair /dev/sharestore/public
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
- agno = 2
- agno = 3
- agno = 4
- agno = 5
- agno = 6
- agno = 7
- agno = 8
- agno = 9
- agno = 10
attr fork in regular inode 10790641420 claims used block 337609
bad attribute fork in inode 10790641420, clearing attr fork
clearing inode 10790641420 attributes
correcting nblocks for inode 10790641420, was 1147457 - counted 1147456
cleared inode 10790641420
- agno = 11
- agno = 12
inode 12926632060 - bad extent starting block number 3940649673949450,
offset 2942236164344
bad attribute fork in inode 12926632060, clearing attr fork
clearing inode 12926632060 attributes
correcting nblocks for inode 12926632060, was 1147457 - counted 1147456
cleared inode 12926632060
inode 12926632061 - bad extent starting block number 2867526325240071,
offset 3558442336524
bad attribute fork in inode 12926632061, clearing attr fork
clearing inode 12926632061 attributes
correcting nblocks for inode 12926632061, was 1147457 - counted 1147456
cleared inode 12926632061
- agno = 13
- agno = 14
data fork in regular inode 15032385909 claims used block 261
bad data fork in inode 15032385909
cleared inode 15032385909
- agno = 15
- process newly discovered inodes...
Phase 4 - check for duplicate blocks...
- setting up duplicate extent list...
- check for inodes claiming duplicate blocks...
- agno = 0
attr fork in ino 312 claims dup extent, off - 0, start - 337609, cnt 1
bad attribute fork in inode 312, clearing attr fork
clearing inode 312 attributes
correcting nblocks for inode 312, was 1 - counted 0
cleared inode 312
- agno = 1
entry "zmi_power2u.goelsen.net_old.tar.bz2" at block 0 offset 296 in
directory inode 1468243215 references free inode 15032385909
clearing inode number in entry at offset 296...
- agno = 2
- agno = 3
- agno = 4
- agno = 5
- agno = 6
- agno = 7
- agno = 8
- agno = 9
- agno = 10
data fork in inode 10790641420 claims metadata block 537051648
xfs_repair: dinode.c:2121: process_inode_data_fork: Zusicherung »err ==
0« nicht erfüllt.
Abgebrochen
What can I do?
--
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-03-26 11:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-26 11:57 Michael Monnerie [this message]
2010-03-26 12:33 ` xfs_repair 3.0.3 crash and abort Michael Monnerie
2010-03-26 12:59 ` 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=201003261257.41233@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 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.