Hi, I just mentioned this recently on this list. They have to be in the FStab file with a non-zero number in the second to last field. The problem is probably two-fold: a.) Supporting JFS hasn't seemeda huge priority to Redhat, they chose ext3 as their main supported filesystem (correct me if I am wrong...). b.) ext3 replays the journal on any mount attempt. You have to actually run fsck on a JFS drive to replay the journal. If you try to mount a non-checked dirty jfs partition, it just fails. This means that even if fedora doesn't run an fsck on an ext3 partiton, it is simply replayed when mounted. If it doesn't run a check on a JFS partition, it fails to mount at all. -- noah On Fri, 3 Dec 2004, gslink wrote: > Ever since IBM wrote the jfs drivers there has always been the problem > that drives are not checked unless they have to be there. I use jfs on > both fixed and removable drives. These get checked in FC3 without > manual intervention but only if they are listed as drives that must be > there for the system to run. If one of these jfs drives isn't there > then the system won't boot. This is true even if the jfs drive has > nothing to do with the system. If the drive is removable and is not > required to be there then you will need to run any checks manually or > use OS/2. > > -- > fedora-test-list mailing list > fedora-test-list@xxxxxxxxxx > To unsubscribe: > http://www.redhat.com/mailman/listinfo/fedora-test-list >