public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rogier Wolff <R.E.Wolff@BitWizard.nl>
To: Andries Brouwer <aebr@win.tue.nl>
Cc: Greg KH <greg@kroah.com>, linux-kernel@vger.kernel.org
Subject: Re: very large FAT16 partition not readable on 2.6.0-test11
Date: Wed, 10 Dec 2003 13:49:44 +0100	[thread overview]
Message-ID: <20031210124944.GA25182@bitwizard.nl> (raw)
In-Reply-To: <20031210093446.GB10321@win.tue.nl>

On Wed, Dec 10, 2003 at 10:34:46AM +0100, Andries Brouwer wrote:
> On Tue, Dec 09, 2003 at 03:03:33PM -0800, Greg KH wrote:
> 
> > I just bought a new USB/Firewire external drive.  It comes pre-formatted
> > as FAT16 (or so shows fdisk) as one big 80Gb partition.  Unfortunately,
> > Linux can't seem to mount this partition, and I get the following dmesg
> > output when trying to mount the partition:
> > 	FAT: bogus number of reserved sectors
> > 	VFS: Can't find a valid FAT filesystem on dev sdb1.

May I make a programming style suggestion? When you find a parameter
out-of-range, don't just print that it's out of range, but print the
actual value as well. This message would have become:

	FAT: Number of reserved sectors (0) out of range. 

Even better would be to print the range as well:

	FAT: Number of reserved sectors (0) out of range (1..16). 

(I just made the number up, I haven't looked in the code what the
valid range actually is...).


		Roger. 

-- 
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2600998 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
**** "Linux is like a wigwam -  no windows, no gates, apache inside!" ****

  reply	other threads:[~2003-12-10 12:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-09 23:03 very large FAT16 partition not readable on 2.6.0-test11 Greg KH
2003-12-10  9:34 ` Andries Brouwer
2003-12-10 12:49   ` Rogier Wolff [this message]
2003-12-11  6:49   ` Greg KH
     [not found] <10Zjf-TI-11@gated-at.bofh.it>
2003-12-09 23:37 ` Dennis Bliefernicht
2003-12-10  1:45   ` Kevin Krieser
2003-12-11  6:43     ` H. Peter Anvin

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=20031210124944.GA25182@bitwizard.nl \
    --to=r.e.wolff@bitwizard.nl \
    --cc=aebr@win.tue.nl \
    --cc=greg@kroah.com \
    --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