I expected that to at least get by the superblock check. Can you run fsck.jfs again with the -v flag? You can also use jfs_debug to see if the superblock looks somewhat sane.
On Thu, 2005-01-27 at 13:51 -0600, Sean Murphy wrote: > I tried copying in the fresh superblock and ended up with this. > Anything else? > It about 10 days worth of computing on there, so I'm only spending > another few hours > on it before we just regenerate it all. > > [EMAIL PROTECTED] ~]# fsck.jfs -f /dev/VolGroup00/lvol0 fsck.jfs version > 1.1.7, 22-Jul-2004 > processing started: 1/27/2005 13.49.9 > The current device is: /dev/VolGroup00/lvol0 > Superblock is corrupt and cannot be repaired > since both primary and secondary copies are corrupt. > > CANNOT CONTINUE. -- David Kleikamp IBM Linux Technology Center _______________________________________________ Jfs-discussion mailing list [email protected] http://www-124.ibm.com/developerworks/oss/mailman/listinfo/jfs-discussion
