Booting Suse 7.2 I get everytime and again a failed message on the screen. Looking for the reason I found that "fatfs bogus cluster size is " is the start of a search for a fruitless search. Linux is trying to do something with a "dev 16:41 " device. How can I get rid of the failure message and of the bogus cluster size (whatever that may be ;-))
Constant Brouerius van Nidek wrote:
Booting Suse 7.2 I get everytime and again a failed message on the screen. Looking for the reason I found that "fatfs bogus cluster size is " is the start of a search for a fruitless search. Linux is trying to do something with a "dev 16:41 " device.
How can I get rid of the failure message and of the bogus cluster size
1. Use a 2.2 kernel, or 2. Edit /usr/src/linux/fs/fat/inode.c and delete the line that prints the message, then recompile, or 3. Don't mount any vfat filesystems during boot.
(whatever that may be ;-))
You can safely ignore the message. The explanation (from inode.c) is given below. JDL * The DOS3 partition size limit is *not* 32M as many people think. * Instead, it is 64K sectors (with the usual sector size being * 512 bytes, leading to a 32M limit). * * DOS 3 partition managers got around this problem by faking a * larger sector size, ie treating multiple physical sectors as * a single logical sector. * * We can accommodate this scheme by adjusting our cluster size, * fat_start, and data_start by an appropriate value.
Hi, When the kernel tries to mount a partition that's marked 'auto' in /etc/fstab, it will try various file system types as it tries. fat is tried before reiser, and that is what you're seeing. The kernel tries to mount it as fat, fails, and moves on to the next file system type. I get the message for all my reiserfs partitions. The next line should be something like kernel: VFS: Can't find a valid MSDOS filesystem on dev 03:43. and then messages about reiser Anders On Friday 31 August 2001 17.18, Constant Brouerius van Nidek wrote:
Booting Suse 7.2 I get everytime and again a failed message on the screen. Looking for the reason I found that "fatfs bogus cluster size is " is the start of a search for a fruitless search. Linux is trying to do something with a "dev 16:41 " device.
How can I get rid of the failure message and of the bogus cluster size (whatever that may be ;-))
participants (3)
-
Anders Johansson -
Constant Brouerius van Nidek -
John D Lamb