xfs
[Top] [All Lists]

bad magic and dubious inode

To: xfs@xxxxxxxxxxx
Subject: bad magic and dubious inode
From: "KE Liew" <ke.liew@xxxxxxxxx>
Date: Sat, 3 Feb 2007 18:59:29 +0100
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=rVl4bE434eUJ7CPil5AxpkChzeGkK/bFcw8Bsa1OTsc3xN/l8tFxCmNFs5iZk1JmiW8W23Va3NOpwShC8EHyzF9WHfaS5GqCyjsPKxalAVT514i3MCVp53VLKmHPOxOBG9G6bhCHeJb0m+7BOB8mBWemcmXB3HSyumn70WGvXQY=
Sender: xfs-bounce@xxxxxxxxxxx
Hello,

It's been a great day, and this is the situation. Files were being
transfered from one hdd to another, SATA to IDE, and BANG and error
occured, can't remember exactly what, but I had to umount it.
Successful, and ran xfs_check

====================
eXiStEnCe:~# xfs_check -s /dev/hdb
bad magic # 0 in inobt block 15/916145
====================

Doesn't look good at all. I attempted the famous xfs_repair :)

====================
eXiStEnCe:~# xfs_repair -n /dev/hdb
Phase 1 - find and verify superblock...
Phase 2 - using internal log
       - scan filesystem freespace and inode maps...
bad magic # 0 in inobt block 15/916145
dubious inode btree block header 15/916145
       - found root inode chunk
Phase 3 - for each AG...
       - scan (but don't 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...
       - 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
No modify flag set, skipping phase 5
Inode allocation btrees are too corrupted, skipping phases 6 and 7
No modify flag set, skipping filesystem flush and exiting.
====================

As you can see, it's almost dead? I haven't mount it yet, so I hope
it's all safe and cool. What should be the next step for me to take?



Kwang


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