From: Matt_Domsch@Dell.com
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] FAT32 file system not mounting on IA-64
Date: Fri, 17 Nov 2000 23:40:12 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205745@msgid-missing> (raw)
Has anyone tried using a FAT32 file system on an IA-64 Linux box? While
this works on my IA-32 system (kernel 2.4.0-test9), this fails on my IA-64
system (same kernel).
(use fdisk to make one big sdb1 partition, 18GB or so)
mkdosfs -F 32 /dev/sdb1
mount /dev/sdb1 /mnt/fat32-1
On IA-64, I get the following error:
Directory 1: bad FAT (from linux/fs/fat/inode.c)
File system panic (dev 08:11)
FAT error (from linux/fs/fat/misc.c)
File system has been set read-only.
If the file system previously existed, after the (read-only) mount, I can
only see garbage. I suspect that the on-disk data structures as defined in
the kernel are not 64-bit clean, but that's just a guess. Any pointers are
appreciated.
Thanks,
Matt Domsch
Dell Enterprise Systems Group
Linux Development Team
next reply other threads:[~2000-11-17 23:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-17 23:40 Matt_Domsch [this message]
2000-11-18 0:17 ` [Linux-ia64] FAT32 file system not mounting on IA-64 Ahna, Christopher J
2000-11-18 2:06 ` Matt_Domsch
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-105590678205745@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