We found and fixed this problem. It is included in version 1.0.14, which is available on our website.
Barry Arndt IBM Linux Technology Center JFS for Linux http://oss.software.ibm.com/jfs (512) 838-0723 t/l 678-0723 "Sean Gollschewsky" <[EMAIL PROTECTED]> @www-126.southbury.usf.ibm.com on 01-28-2002 10:48:14 AM Sent by: [EMAIL PROTECTED] To: <[EMAIL PROTECTED]> cc: Subject: [Jfs-discussion] Corrupted File System Hi all, I've had a minor disaster with one of my JFS partitions. It's only minor due to the nature of the data that I may have lost, not the actual incident... I had about 6 or 7 downloads writing to the file system, and I was watching a movie file (750mb) residing on the JFS partition shared with Samba. After a few seconds of watching the movie, my linux machine locked solid - the only thing that caused any response was the Magic Sysreq key which caused a reboot. The JFS file system wouldn't mount at boot, so I attempted a fsck. gollo:/# fsck -t jfs -nv /dev/hda4 fsck 1.25 (20-Sep-2001) fsck.jfs version 1.0.13, 25-Jan-2002 The current device is: /dev/hda4 (chklog) FSCK Open(...READONLY...) returned rc = 0 (chklog) FSCK Invalid filesystem size in the superblock (P). (chklog) FSCK Primary superblock is corrupt. (chklog) FSCK Invalid filesystem size in the superblock (S). (chklog) FSCK Secondary superblock is corrupt. Superblock is corrupt and cannot be repaired because both primary and secondary copies are corrupt. FSCK CANNOT CONTINUE. gollo:/# I had just upgraded to JFS 1.0.13 (from 1.0.9) on the previous boot of the machine. Running 2.4.18-pre7, with LVM 1.0.2 - the jfs filesystem is running on a logical volume. Is there any hope of recovery? TIA, Gollo. _______________________________________________ Jfs-discussion mailing list [EMAIL PROTECTED] http://www-124.ibm.com/developerworks/oss/mailman/listinfo/jfs-discussion _______________________________________________ Jfs-discussion mailing list [EMAIL PROTECTED] http://www-124.ibm.com/developerworks/oss/mailman/listinfo/jfs-discussion
