| To: | evilninja <evilninja@xxxxxxx> |
|---|---|
| Subject: | Re: XFS: can't read superblock |
| From: | Mathieu GOMBAULT <qwerty@xxxxxxxxx> |
| Date: | Sat, 20 Nov 2004 12:17:11 +0100 |
| Cc: | linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <419F1896.6020501@gmx.net> |
| References: | <419F1985.9010603@minet.net> <419F1896.6020501@gmx.net> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mozilla Thunderbird 0.9 (Windows/20041103) |
evilninja wrote: Mathieu GOMBAULT wrote: xfs_repair takes 2 seconds for a disk of 160 GB. I have xfs_repair version 2.6.20 here are all the logs I made: qwerty@Pegasus:~$;-) sudo xfs_repair -v /dev/hdd1
Phase 1 - find and verify superblock...
Phase 2 - using internal log
- zero log...
zero_log: head block 2 tail block 2
- 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
- process newly discovered inodes...
Phase 4 - check for duplicate blocks...
- setting up duplicate extent list...
- clear lost+found (if it exists) ...
- clearing existing "lost+found" inode
- marking entry "lost+found" to be deleted
- 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
Phase 5 - rebuild AG headers and trees...
- reset superblock...
Phase 6 - check inode connectivity...
- resetting contents of realtime bitmap and summary inodes
- ensuring existence of lost+found directory
- traversing filesystem starting at / ...
rebuilding directory inode 128
- traversal finished ...
- traversing all unattached subtrees ...
- traversals finished ...
- moving disconnected inodes to lost+found ...
Phase 7 - verify and correct link counts...
done
3 0 80043264 hda 3 1 16033 hda1 3 2 498015 hda2 3 3 498015 hda3 3 4 1 hda4 3 5 6000246 hda5 3 6 2000061 hda6 3 7 71023333 hda7 22 64 160086528 hdd 22 65 159993460 hdd1
Device Boot Start End Blocks Id System /dev/hdd1 * 2 19920 159993460 83 Linux I made only one partition with xfs when I created it
qwerty@Pegasus:~$;-) sudo mount -t xfs /dev/hdd1 /mnt/ mount: /dev/hdd1: can't read superblock qwerty@Pegasus:~$;-) dmesg | tail I/O error in filesystem ("hdd1") meta-data dev hdd1 block 0x1314ff7f ("xfs_read_buf") error 5 buf count 512 XFS: size check 2 failed attempt to access beyond end of device hdd1: rw=0, want=320143232, limit=319986920 I/O error in filesystem ("hdd1") meta-data dev hdd1 block 0x1314ff7f ("xfs_read_buf") error 5 buf count 512 XFS: size check 2 failed attempt to access beyond end of device hdd1: rw=0, want=320143232, limit=319986920 I/O error in filesystem ("hdd1") meta-data dev hdd1 block 0x1314ff7f ("xfs_read_buf") error 5 buf count 512 XFS: size check 2 failed
Regards Math |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: XFS: can't read superblock, evilninja |
|---|---|
| Next by Date: | Re: XFS: can't read superblock, evilninja |
| Previous by Thread: | Re: XFS: can't read superblock, evilninja |
| Next by Thread: | Re: XFS: can't read superblock, evilninja |
| Indexes: | [Date] [Thread] [Top] [All Lists] |