mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michael Scondo <michael.scondo@arcor.de>
To: linux-kernel@vger.kernel.org
Subject: Re: vfat bug - solved
Date: Fri, 17 Sep 2004 12:30:07 +0200	[thread overview]
Message-ID: <200409171230.07524.michael.scondo@arcor.de> (raw)
In-Reply-To: <20040917020405.GB2573@MAIL.13thfloor.at>

Am Freitag, 17. September 2004 04:04 schrieb Herbert Poetzl:
> On Fri, Sep 17, 2004 at 12:13:20AM +0200, Michael Scondo wrote:
> > Hello..
> > I've just compiled a new kernel ( 2.6.8.1 ), and now I'm not able to
> > mount my fat32 partitions anymore.
> >
> > mount /dev/hda7 /mnt
> > mount: wrong fs type, bad option, bad superblock on /dev/hda7,
> >        or too many mounted file systems
> >
> > :-(
> >
> > Every works still fine with 2.6.4, but I'm not sure, whether this occurs
> > due to a bug in the kernel or because a wrong build process.
> > Therefore I'm posting this to the list.
>
> check the kernel ring buffer (dmesg) for codepages which
> are requested but not found (or other strange messages)
> which appear when you 'try' to mount the filesystem
>
> HTH,
> Herbert

Yes, the module fat wasn´t able to find cp437 as well as the charset 
iso8859-1. ( both configured as default )
If I pass the options "-o codepage=850,iocharset=iso8859-15" to mount, 
everything works fine.
Maybe, I should have been a little bit more watchful while configuring.
But weren't it sensible to provide a mechanism, which prevent's such a silly 
configuration ?

Thanks a lot 
Micha




      reply	other threads:[~2004-09-17 10:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-16 22:13 vfat bug Michael Scondo
2004-09-17  2:04 ` Herbert Poetzl
2004-09-17 10:30   ` Michael Scondo [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=200409171230.07524.michael.scondo@arcor.de \
    --to=michael.scondo@arcor.de \
    --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

Powered by JetHome