From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Subject: xfs_repair 3.1.1 doesnt repair broken filesystem
Date: Tue, 18 May 2010 09:53:47 +0200 [thread overview]
Message-ID: <201005180953.51892@zmi.at> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 15266 bytes --]
I do a repair on a broken filesystem, which reports no problems. Then I
mount and "ls -l", and you can easily see all those broken entries,
which should be directories. They are not repaired. What could I do?
# xfs_repair -v /dev/bigbak/bigbak
Phase 1 - find and verify superblock...
- block cache size set to 8536 entries
Phase 2 - using internal log
- zero log...
XFS: totally zeroed log
zero_log: head block 0 tail block 0
- 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
- 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
- process newly discovered inodes...
Phase 4 - check for duplicate blocks...
- setting up duplicate extent list...
- check for inodes claiming duplicate blocks...
- agno = 0
- agno = 1
- 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...
- agno = 0
- agno = 1
- 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
- reset superblock...
Phase 6 - check inode connectivity...
- resetting contents of realtime bitmap and summary inodes
- traversing filesystem ...
- agno = 0
- agno = 1
- 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
- traversal finished ...
- moving disconnected inodes to lost+found ...
Phase 7 - verify and correct link counts...
XFS_REPAIR Summary Tue May 18 09:50:35 2010
Phase Start End Duration
Phase 1: 05/18 09:48:12 05/18 09:48:12
Phase 2: 05/18 09:48:12 05/18 09:48:44 32 seconds
Phase 3: 05/18 09:48:44 05/18 09:49:39 55 seconds
Phase 4: 05/18 09:49:39 05/18 09:49:54 15 seconds
Phase 5: 05/18 09:49:54 05/18 09:49:54
Phase 6: 05/18 09:49:54 05/18 09:50:35 41 seconds
Phase 7: 05/18 09:50:35 05/18 09:50:35
Total run time: 2 minutes, 23 seconds
done
# mount /dev/bigbak/bigbak /disks/bigbak/
# l /disks/bigbak/
ls: Zugriff auf /disks/bigbak/lama nicht möglich: Das Argument ist
ungültig
ls: Zugriff auf /disks/bigbak/maza nicht möglich: Das Argument ist
ungültig
ls: Zugriff auf /disks/bigbak/paan nicht möglich: Das Argument ist
ungültig
ls: Zugriff auf /disks/bigbak/public nicht möglich: Das Argument ist
ungültig
ls: Zugriff auf /disks/bigbak/tmp nicht möglich: Das Argument ist
ungültig
ls: Zugriff auf /disks/bigbak/upload nicht möglich: Das Argument ist
ungültig
ls: Zugriff auf /disks/bigbak/vop nicht möglich: Das Argument ist
ungültig
ls: Zugriff auf /disks/bigbak/zmi nicht möglich: Das Argument ist
ungültig
insgesamt 20
drwxrwx--- 14 root 1000 4096 12. Mai 09:36 ./
drwxr-xr-x 7 root root 184 17. Mai 12:40 ../
drwx------ 6 1007 nogroup 4096 9. Jan 15:51 anse/
-rw-r--r-- 1 root root 155 12. Mai 09:42 du.20100512
-rwx------ 1 root root 141 26. Mär 14:51 find-inode.sh*
drwx------ 2 1006 nogroup 68 23. Nov 15:15 hope/
drwxrwxr-x+ 4 1007 nogroup 49 29. Nov 12:32 itm/
drwx------ 2 1002 nogroup 68 23. Nov 15:14 jog/
??????????? ? ? ? ? ? lama
??????????? ? ? ? ? ? maza
??????????? ? ? ? ? ? paan
??????????? ? ? ? ? ? public
??????????? ? ? ? ? ? tmp
??????????? ? ? ? ? ? upload
??????????? ? ? ? ? ? vop
??????????? ? ? ? ? ? zmi
--
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-05-18 7:51 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-05-18 7:53 Michael Monnerie [this message] 2010-05-18 10:16 ` xfs_repair 3.1.1 doesnt repair broken filesystem Emmanuel Florac 2010-05-18 11:01 ` Default User 2010-05-18 11:42 ` xfs_repair 3.1.1 doesnt repair broken filesystem [solved] 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=201005180953.51892@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.