From: Emmanuel Florac <eflorac@intellique.com>
To: xfs@oss.sgi.com
Subject: xfs_repair has been running for a very long time, no disk IO.
Date: Tue, 9 Apr 2013 12:17:26 +0200 [thread overview]
Message-ID: <20130409121726.6342519e@harpe.intellique.com> (raw)
On a quite badly mangled filesystem, xfs_repair (v. 3.1.4) seems to
never end. It has run for 16 hours with absolutely no disk activity.
Usually xfs_repair takes much less than one hour on a similar (9 TB)
filesystem.
I know I should try the latest version. What else can be wrong?
What should I try?
Last lines of output of the still running xfs_repair where it has
been stuck since yesterday night:
entry "Panel-2333" at block 3 offset 2464 in directory inode 2190114192 references non-existent inode 60238299
clearing inode number in entry at offset 2464...
entry "Panel-2316" at block 3 offset 2512 in directory inode 2190114192 references non-existent inode 60238300
clearing inode number in entry at offset 2512...
entry "Panel-2309" at block 3 offset 2560 in directory inode 2190114192 references non-existent inode 60238301
clearing inode number in entry at offset 2560...
entry "Panel-2292" at block 3 offset 2608 in directory inode 2190114192 references non-existent inode 60238302
clearing inode number in entry at offset 2608...
entry "Panel-2290" at block 3 offset 2656 in directory inode 2190114192 references non-existent inode 60238303
clearing inode number in entry at offset 2656...
bad attribute format 1 in inode 2190120814, resetting value
- agno = 2
- agno = 3
- agno = 4
- agno = 5
- agno = 6
- agno = 7
- agno = 8
- agno = 9
- agno = 10
- agno = 11
- agno = 12
- agno = 13
- agno = 14
- agno = 15
- agno = 16
- agno = 17
- agno = 18
- agno = 19
- agno = 20
- agno = 21
- agno = 22
- agno = 23
- agno = 24
- agno = 25
- agno = 26
- agno = 27
- agno = 28
- agno = 29
- agno = 30
- agno = 31
Phase 5 - rebuild AG headers and trees...
- reset superblock...
Phase 6 - check inode connectivity...
- resetting contents of realtime bitmap and summary inodes
- traversing filesystem ...
--
------------------------------------------------------------------------
Emmanuel Florac | Direction technique
| Intellique
| <eflorac@intellique.com>
| +33 1 78 94 84 02
------------------------------------------------------------------------
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2013-04-09 10:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-09 10:17 Emmanuel Florac [this message]
2013-04-09 12:02 ` xfs_repair has been running for a very long time, no disk IO Dave Chinner
2013-04-09 12:30 ` Emmanuel Florac
2013-04-09 12:54 ` Dave Chinner
2013-04-09 17:51 ` Emmanuel Florac
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=20130409121726.6342519e@harpe.intellique.com \
--to=eflorac@intellique.com \
--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