On Wed, 2007-01-24 at 22:27 +0100, Simon Lundell wrote: > Simon Lundell skrev:
> > Hi again! > > > > I figured that it might have been the 12th field that I should have > > changed, instead of the 11th. Yeah. My mistake. I was playing around in jfs_debugfs and run the "s2p" command instead of "sup". It displays the superblock a little bit differently. Not a very useful command. > So this is what happens if i change the > > 12th field to 0xa: ... > > simons ~ # fsck -dvf /dev/vgmedia/media > > fsck 1.39 (29-May-2006) > > fsck.jfs version 1.1.11, 05-Jun-2006 > > processing started: 1/24/2007 22.20.25 > > The current device is: /dev/vgmedia/media [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: 102028288 [xchkdsk.c:1857] > > **Phase 0 - Replay Journal Log [xchkdsk.c:1864] > > LOGREDO: Beginning to recover File System Extend processing. > > [logredo.c:506] > > LOGREDO: File System Extend recovered and completed. [logredo.c:1676] > > LOGREDO: Done recovering File System Extend processing. [logredo.c:508] Well, it tried to recover. > > logredo returned rc = 0 [xchkdsk.c:1896] > > **Phase 1 - Check Blocks, Files/Directories, and Directory Entries > > [xchkdsk.c:1989] > > Primary metadata inode A2 is corrupt. [fsckmeta.c:3170] > > Duplicate reference to 12471 block(s) beginning at offset 16 found in > > file system object MA2. [fsckwsp.c:452] > > Inode A2 has references to cross linked blocks. [fsckwsp.c:1772] > > Secondary metadata inode A2 is corrupt. [fsckmeta.c:3174] > > 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] Not much help though. > Sorry for spamming the list but when I run fsck a second time it says > that the superblock is invalid: At this point, I think you'd be better off reformatting and restoring your backed-up data. I'm going to try to stress the resizing code, and possibly force it to fail at different phases to see if I can recreate the problem. I probably won't get to it right away, so I don't want to take up any more of your time right now. I really appreciate all the data you've been feeding me. Thanks, Shaggy -- David Kleikamp IBM Linux Technology Center ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Jfs-discussion mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jfs-discussion
