Very Computer

Quote:> FAT: bogus logical sector size 0

It is not a problem at all.

It happens if you compile fat in the Kernel and not as module. In this case
the fat-driver seems to check every partition for a fat-filesystem. When it
fails it gives you this message.

So you can
1. ignore these messages or
2. compile fat as a module.

greetings

Christian
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

It is a user interface error by the FAT coder, a serious one actually,
because it affects partitions that are not FAT.  Would be nice if it got
fixed.

Hans

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Quote:> > Machine booted ok and everything seemed to be ok, but i noticed a few
> > weird messages in boot messages right before mounting the root-partition:
> > FAT: bogus logical sector size 0
> > FAT: bogus logical sector size 0
> When the kernel is booting, it doesn't know the filesystem type of the
> root fs, so it tries to mount the root device using all of the compiled-in
> fs drivers, in the order they are listed in fs/Makefile.in.
> It appears that the fat driver doesn't even check for a magic when it
> starts trying to mount the filesystem, so it proceeds directly to

To be complete we should also apply this patch.

diff -urN linux/fs/fat/inode.c linux-new/fs/fat/inode.c
--- linux/fs/fat/inode.c        Thu Oct 25 09:02:26 2001

                CF_LE_W(get_unaligned((unsigned short *) &b->sector_size));
        if (!logical_sector_size
            || (logical_sector_size & (logical_sector_size - 1))) {
-               printk("FAT: bogus logical sector size %d\n",
+               if (!silent)
+                   printk("FAT: bogus logical sector size %d\n",
                       logical_sector_size);
                brelse(bh);

        sbi->cluster_size = b->cluster_size;
        if (!sbi->cluster_size
            || (sbi->cluster_size & (sbi->cluster_size - 1))) {
-               printk("FAT: bogus cluster size %d\n", sbi->cluster_size);
+               if (!silent)
+                   printk("FAT: bogus cluster size %d\n", sbi->cluster_size);
                brelse(bh);
                goto out_invalid;
        }
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

How about putting fat last in the list, and having it say something more
like "FAT: bogus cluster size, perhaps XXX is not a FAT partition"

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

| > > Machine booted ok and everything seemed to be ok, but i noticed a few
| > > weird messages in boot messages right before mounting the root-partition:
| > > FAT: bogus logical sector size 0
| > > FAT: bogus logical sector size 0
| > When the kernel is booting, it doesn't know the filesystem type of the
| > root fs, so it tries to mount the root device using all of the compiled-in
| > fs drivers, in the order they are listed in fs/Makefile.in.
| > It appears that the fat driver doesn't even check for a magic when it
| > starts trying to mount the filesystem, so it proceeds directly to
|
| To be complete we should also apply this patch.

To be totally honest I think this is the wrong way to go. Like masking
the symptoms instead of treating the disease. The problem is that the
FAT driver seems to not check f/s type before claiming a f/s as its own.
The better solution is to put in a check before going forward with using
the f/s as FAT.

--

  His first management concern is not solving the problem, but covering
his ass. If he lived in the middle ages he'd wear his codpiece backward.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Yes. You can't use the module before you mounted the root filesystem.
This is a reason for not seeing an error message.
--

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/