[prev in list] [next in list] [prev in thread] [next in thread] 

List:       jfs-discussion
Subject:    Re: [Jfs-discussion] jfs metadata corruptions, how to recover?
From:       Dave Kleikamp <shaggy () linux ! vnet ! ibm ! com>
Date:       2010-09-27 15:20:12
Message-ID: 1285600812.17411.17.camel () shaggy-w500
[Download RAW message or body]

On Mon, 2010-09-27 at 22:46 +0800, Samson Luk wrote:
> Hi Dave,
> 
>         I'm not sure what's wrong with the metadata, but if ls -lR
>         looks good,
>         then it's likely that you may be able to copy everything to
>         another
>         partition (or backup media) safely.  I'd recommend doing that
>         before
>         trying to fix the partition.
> 
>         Can you re-run fsck.jfs with the -d flag.  It's not
>         documented, but it's
>         a debug flag that should indicate a little more precisely what
>         it thinks
>         is wrong with the metadata.
> 
> I've jfs_fscklog saved earlier, is this the same as fsck.jfs -d?  

Yes, they give the same information.  Thanks.
> 
> I am in progress of copying the whole partition, so can't do fsck at
> the moment.

Unfortunately, the output doesn't really pinpoint exactly where the
problem is, so I'll have to dig through the code a bit to see what to
look for.

I'm not sure how much time I'll find to look at this, so don't wait for
me if you want to go ahead and reformat and repopulate the partition.

Thanks,
Shaggy

> # jfs_fscklog -- d fscklog.new
> jfs_fscklog version 1.1.14, 06-Apr-2009
> processing started: 9/26/2010 20.28.3 [xchkdsk.c:1445]
> The current device is: /dev/sda6 [xchkdsk.c:1520]
> Open(...READ/WRITE EXCLUSIVE...) returned rc = 0 [fsckpfs.c:3233]
> Primary superblock is valid. [fsckmeta.c:1551]
> The type of file system for the device is JFS. [xchkdsk.c:1537]
> Block size in bytes: 4096 [xchkdsk.c:1850]
> Filesystem size in blocks: 58107097 [xchkdsk.c:1857]
> **Phase 0 - Replay Journal Log [xchkdsk.c:1864]
> LOGREDO: Allocating for ReDoPage: (d) 4096 bytes [log_work.c:1783]
> LOGREDO: Allocating for NoDoFile: (d) 4096 bytes [log_work.c:1807]
> LOGREDO: Allocating for BMap: (d) 138224 bytes [log_map.c:366]
> LOGREDO: Allocating for IMap: (d) 18480 bytes [log_map.c:689]
> LOGREDO: Allocating for IMap: (d) 2048 bytes [log_map.c:893]
> LOGREDO: Allocating for IMap: (d) 2048 bytes [log_map.c:893]
> LOGREDO: Allocating for IMap: (d) 2048 bytes [log_map.c:893]
> LOGREDO: Allocating for IMap: (d) 2048 bytes [log_map.c:893]
> LOGREDO: Allocating for IMap: (d) 2048 bytes [log_map.c:893]
> LOGREDO: Address (0x01fffff4) of next log record is out of range.
> [logredo.c:633]
> logredo failed (rc=-245). fsck continuing. [xchkdsk.c:1894]
> **Phase 1 - Check Blocks, Files/Directories, and Directory Entries
> [xchkdsk.c:1989]
> Primary metadata inode A1 is corrupt. [fsckmeta.c:2549]
> Secondary metadata inode A1 is corrupt. [fsckmeta.c:2553]
> Errors detected in the Primary File/Directory Allocation Table.
> [fsckmeta.c:1890]
> Errors detected in the Secondary File/Directory Allocation Table.
> [fsckmeta.c:1895]
> CANNOT CONTINUE. [fsckmeta.c:1902]
> processing terminated: 9/26/2010 20:28:05 with return code: -10049
> exit code: 4. [xchkdsk.c:468]
> 
> 
> 
> 

-- 
Dave Kleikamp
IBM Linux Technology Center


------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Jfs-discussion mailing list
Jfs-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jfs-discussion
[prev in list] [next in list] [prev in thread] [next in thread]