Forget what I told you do to fix this. I was confused on which inode fsck is complaining about. It is fileset inode 1, not aggregate inode 1 that is the problem. You should be able to fix this with jfs_debugfs as follows. Please ignore my previous instructions.
Run "jfs_debugfs /dev/hdg6". From the command prompt, type "xt 1". On a good filesystem it should look like this: > xt 1 Root X-Tree Node of inode 1 [1] flag 0x83 BT_ROOT BT_LEAF [2] nextindex 2 [5] self.addr1 0x00 [3] maxentry 18 [6] self.addr2 0x00000000 [4] self.len 0x000000 self.addr 0 xtree: [m]odify, or e[x]it: >From here, you can use the "m" sub-command to change any incorrect field to the right value. i.e. "m 1 0x83", "m 2 2", "m 3 18", etc. On Fri, 2004-09-17 at 16:44, David Kleikamp wrote: > But now, to try to fix your filesystem... > > Running "jfs_debugfs /dev/hdg6" should give you a command prompt. From > here, type "in 1 a". On a good file system, you should see something > like this: > > <Bad advise deleted> _______________________________________________ Jfs-discussion mailing list [EMAIL PROTECTED] http://www-124.ibm.com/developerworks/oss/mailman/listinfo/jfs-discussion
