On Sat, Feb 03, 2007 at 06:59:29PM +0100, KE Liew wrote:
> 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.
Can you look in your syslog for the forced shutdown messages?
> 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 :)
You ran "xfs_repair -n" which means it didn't fix anything;
it just told you about errors it found.
> 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?
No, it's not dead - xfs-repair should be able to fix the problem
if you let it.
> 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?
run xfs_repair without the -n flag.
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
|