public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: "Christian Bornträger" <linux-kernel@borntraeger.net>
Cc: Andreas Dilger <adilger@turbolabs.com>,
	chaffee@cs.berkeley.edu, linux-kernel@vger.kernel.org,
	Eric M <ground12@jippii.fi>
Subject: Re: 2.4.15-pre1:  "bogus" message with reiserfs root and other weirdness
Date: Thu, 22 Nov 2001 16:48:43 +0300	[thread overview]
Message-ID: <3BFD023B.7030307@namesys.com> (raw)
In-Reply-To: <6893478.1006329318464.JavaMail.ground12@jippii.fi> <20011121111811.P1308@lynx.no> <E166e8A-0000t2-00@mrvdom02.schlund.de>

Christian Bornträger wrote:

>>>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
>+++ linux-new/fs/fat/inode.c    Wed Nov 21 21:28:49 2001
>@@ -609,7 +609,8 @@
>                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);
>                goto out_invalid;
>@@ -618,7 +619,8 @@
>        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;
>        }
>
>
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"



  reply	other threads:[~2001-11-22 13:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-21  7:55 2.4.15-pre1: "bogus" message with reiserfs root and other weirdness Eric M
2001-11-21  9:43 ` Christian Bornträger
2001-11-21 13:39   ` Hans Reiser
2001-11-21 18:18 ` Andreas Dilger
2001-11-21 20:37   ` Christian Bornträger
2001-11-22 13:48     ` Hans Reiser [this message]
2001-11-26 14:56   ` bill davidsen
2001-11-26 16:17     ` OGAWA Hirofumi
2001-11-26 16:54       ` Bill Davidsen
2001-11-26 17:54         ` OGAWA Hirofumi
2001-11-26 18:15           ` David Ford
2001-11-26 18:44             ` OGAWA Hirofumi
2001-11-26 19:48           ` Bill Davidsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3BFD023B.7030307@namesys.com \
    --to=reiser@namesys.com \
    --cc=adilger@turbolabs.com \
    --cc=chaffee@cs.berkeley.edu \
    --cc=ground12@jippii.fi \
    --cc=linux-kernel@borntraeger.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox