xfs
[Top] [All Lists]

sudden xfs errors with 2.6.10-rc1-bk19

To: linux-xfs@xxxxxxxxxxx
Subject: sudden xfs errors with 2.6.10-rc1-bk19
From: Christian <evilninja@xxxxxxx>
Date: Sat, 13 Nov 2004 19:11:29 +0100
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mozilla Thunderbird 0.6+ (Windows/20041008)
hi,

a few days ago i had to reboot the machine and i thought i could upgrade to a more recent kernel. i don't know if the following issue is related to this upgrade but as of now i can't mount my xfs fs any more. the hing is, i'm using loop-aes too and so xfs is on the loop device only:

$ losetup -F /dev/loop7
Password:
$ losetup -a
/dev/loop7: [0805]:389 (/dev/sdb1) encryption=twofish128 multi-key
$ mount -t xfs /dev/loop7 /data/Storage/
mount: wrong fs type, bad option, bad superblock on /dev/loop7,
       or too many mounted file systems

so i've checked with "xfs_check -v /dev/loop7", because without "-v" the xfs_check returned no output (errorcode 0, so i assume no errors occured). the output of "xfs_check -v" is saved in http://www.nerdbynature.de/bits/sheep/2.6.10-rc1-bk19/xfs_check-loop7.log.bz2
(will be available after the bzip2 finished, it's pretty large...)

xfs_repair did (sorry, long)

--------------------------
root@sheep:~# xfs_repair -v /dev/loop7
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
--------------------------

however, i am still not able to mount this thing.

this is all on debian/unstable (i386), xfsprogs-2.6.20.
do you need more infos about this things? xfsdump or sth. like this?
perhaps someone can give me a hint here what to do next.

thank you very much,
Christian.
--
BOFH excuse #293:

You must've hit the wrong any key.


<Prev in Thread] Current Thread [Next in Thread>