On Sun, 2010-09-26 at 18:20 -0700, Samson Luk wrote: > Since I did not get any copy of my original post to the list or any reply > from the list so sorry for the resend... Is anybody still here or the list > already death?
Your original post was held up for moderation. The list isn't dead, but there's nobody working full-time on JFS these days, so I fall behind sometimes. > ---------- Forwarded message ---------- > samson...@date: Sat, Sep 25, 2010 at 9:24 PM > Subject: Errors detected in the Primary & Secondary File/Directory > Allocation Table > To: [email protected] > > Dear all, > > I don't knon why this happen... Please kindly advice if it is possible to > recover data from he following errors and how? Many thanks! 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. > # fsck.jfs -v -p /dev/sda6 > fsck.jfs version 1.1.11, 05-Jun-2006 > processing started: 9/25/2010 21.7.35 > The current device is: /dev/sda6 > Open(...READ/WRITE EXCLUSIVE...) returned rc = 0 > Primary superblock is valid. > The type of file system for the device is JFS. > Block size in bytes: 4096 > Filesystem size in blocks: 58107097 > **Phase 0 - Replay Journal Log > LOGREDO: Allocating for ReDoPage: (d) 4096 bytes > LOGREDO: Allocating for NoDoFile: (d) 4096 bytes > LOGREDO: Allocating for BMap: (d) 138224 bytes > LOGREDO: Allocating for IMap: (d) 18480 bytes > LOGREDO: Allocating for IMap: (d) 2048 bytes > LOGREDO: Allocating for IMap: (d) 2048 bytes > LOGREDO: Allocating for IMap: (d) 2048 bytes > LOGREDO: Allocating for IMap: (d) 2048 bytes > LOGREDO: Allocating for IMap: (d) 2048 bytes > LOGREDO: Address (0x01fffff4) of next log record is out of range. > logredo failed (rc=-245). fsck continuing. > **Phase 1 - Check Blocks, Files/Directories, and Directory Entries > Primary metadata inode A1 is corrupt. > Secondary metadata inode A1 is corrupt. > Errors detected in the Primary File/Directory Allocation Table. > Errors detected in the Secondary File/Directory Allocation Table. > CANNOT CONTINUE. > processing terminated: 9/25/2010 21:07:37 with return code: -10049 exit > code: 4. > > ==================================== > this morning I just tried a recovery on the partition after a complete dd > backup of the whole corrupted partition: > > # jfs_fsck -v --omit_journal_replay /dev/sdb2 > r...@hs-dhgl2b4:~# jfs_fsck -v > jfs_fsck version 1.1.11, 05-Jun-2006 > processing started: 9/27/2010 5.39.37 > Using default parameter: -p > The current device is: /dev/sdb2 > Open(...READ/WRITE EXCLUSIVE...) returned rc = 0 > Primary superblock is valid. > The type of file system for the device is JFS. > Block size in bytes: 4096 > Filesystem size in blocks: 58107097 > **Phase 1 - Check Blocks, Files/Directories, and Directory Entries > Primary metadata inode A1 is corrupt. > Secondary metadata inode A1 is corrupt. > Errors detected in the Primary File/Directory Allocation Table. > Errors detected in the Secondary File/Directory Allocation Table. > CANNOT CONTINUE. > processing terminated: 9/27/2010 5:39:38 with return code: -10049 exit > code: 4. > > Stiild couldn't continue.... However, the partition is able to mount Read > Only: > > ~# mount -o ro -t jfs ./dev/sdb2 /mnt/disk1 > > ls -lR shown everything seems alright, is it safe to copy as much as I can > to recover the files inside? How can I recover the jfs metadata if the > actual data are not corrupted. since this is a data partition and there > should be no disk read/write upon system reboot. 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. > Regards, > Samson > -- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/jfs-discussion
