From: "Kevin Krieser" <kkrieser@lcisp.com>
To: <linux-kernel@vger.kernel.org>
Subject: RE: very large FAT16 partition not readable on 2.6.0-test11
Date: Tue, 9 Dec 2003 19:45:12 -0600 [thread overview]
Message-ID: <NDBBLFLJADKDMBPPNBALOEDBCLAB.kkrieser@lcisp.com> (raw)
In-Reply-To: <3FD65CCA.3000408@triphoenix.de>
Actually, there is an extension to 4GB that NT used in the 4.0 days (maybe
earlier?).
Don't know if the Linux driver supports it.
-----Original Message-----
From: linux-kernel-owner@vger.kernel.org
[mailto:linux-kernel-owner@vger.kernel.org]On Behalf Of Dennis
Bliefernicht
Sent: Tuesday, December 09, 2003 5:38 PM
To: linux-kernel@vger.kernel.org
Subject: Re: very large FAT16 partition not readable on 2.6.0-test11
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.
Well, according to my sources FAT16 cannot sustain any partition larger
than 2GiB, so 80GiB is probably a lot more than it can handle. Anyway,
sdb1 is lacking any type of header and sdb containt something, but not a
FAT header afaik. So probably theres just a partition table entry but
not formatted.
next prev parent reply other threads:[~2003-12-10 1:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <10Zjf-TI-11@gated-at.bofh.it>
2003-12-09 23:37 ` very large FAT16 partition not readable on 2.6.0-test11 Dennis Bliefernicht
2003-12-10 1:45 ` Kevin Krieser [this message]
2003-12-11 6:43 ` H. Peter Anvin
2003-12-09 23:03 Greg KH
2003-12-10 9:34 ` Andries Brouwer
2003-12-10 12:49 ` Rogier Wolff
2003-12-11 6:49 ` Greg KH
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=NDBBLFLJADKDMBPPNBALOEDBCLAB.kkrieser@lcisp.com \
--to=kkrieser@lcisp.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