public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Matt_Domsch@Dell.com
To: linux-ia64@vger.kernel.org
Subject: RE: [Linux-ia64] FAT32 file system not mounting on IA-64
Date: Sat, 18 Nov 2000 02:06:20 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590678205747@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205745@msgid-missing>

Chris, thanks for investigating further.  Glad to hear you can reproduce the
problem there.

w/o the -F 32, it makes a FAT16 file system, which supports long file names
and the vfat type, just as Windows NT FAT16 file systems support long file
names.   If you mount with:  mount -ofat\x16  or with -ofat2, you'll see it
force the choice, and then you can see if the kernel thinks it's a FAT16 or
FAT32.

Thanks,
Matt


-----Original Message-----
From: Ahna, Christopher J [mailto:christopher.j.ahna@intel.com]
Sent: Friday, November 17, 2000 7:25 PM
Subject: RE: [Linux-ia64] FAT32 file system not mounting on IA-64


Matt,

I looked a little more and think you're probably onto something.  I believe
there is a problem with 'mkdosfs -F 32'.  I ran this program on a 100MB file
I built with dd and got the errors you reported when I tried to mount it.
Doing the same thing without the '-F 32' switch built a mountable filesystem
which looks for all the world like FAT32 (for example, it doesn't have a
problem with arbitrarily long filenames and mounted successfully with 'mount
-t vfat').

Somebody might want to look into this if they have time.  Thanks,

Chris



      parent reply	other threads:[~2000-11-18  2:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-17 23:40 [Linux-ia64] FAT32 file system not mounting on IA-64 Matt_Domsch
2000-11-18  0:17 ` Ahna, Christopher J
2000-11-18  2:06 ` Matt_Domsch [this message]

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=marc-linux-ia64-105590678205747@msgid-missing \
    --to=matt_domsch@dell.com \
    --cc=linux-ia64@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