From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Ali Akcaagac <aliakc@web.de>
Cc: linux-kernel@vger.kernel.org, aebr@win.tue.nl
Subject: Re: [BUG] FAT broken in 2.6.7-bk15
Date: Mon, 05 Jul 2004 01:36:42 +0900 [thread overview]
Message-ID: <877jtjwwyt.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <1088951695.596.7.camel@localhost>
Ali Akcaagac <aliakc@web.de> writes:
> Ok after some further research I figured this out. My last working
> version of the Linux Kernel was 2.6.7 which worked with my rescue
> system. I now applied the bk* patches upwards to check which one caused
> the issue and I figured that this happened between bk3 to bk4 (so the
> problem occoured with the bk4 patch). The diskimage was created with
> mtools 3.9.9 and worked perfectly before.
Ah, my fault. I changed the handling of "codepage" options, but it wasn't
mentioned on changelog at all. (Sorry, I didn't notice this changes.)
Now, the codepage option recognizes only real NLS codepage module.
(It uses FAT_DEFAULT_CODEPAGE, not NLS_DEFAULT. And FAT_DEFAULT_CODEPAGE
only recognizes the numbers.)
Previously, it recognized/loaded all NLS modules via CONFIG_NLS_DEFAULT,
if it can't load the nls_cp437.ko or specified codepage.
But this is seriously wrong. For example, if fatfs using the
nls_utf8.ko for codepage, it will store the wrong 8.3-alias to
disk. (At least, windows can't read this. And several peoples reported
this problem.)
Anyway, could you please check FAT_DEFAULT_CODE/FAT_DEFAULT_IOCHARSET
and NLS_xxx in your .config.
Yes, this should be done automatically by config system. However...
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
next prev parent reply other threads:[~2004-07-04 16:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-04 14:34 [BUG] FAT broken in 2.6.7-bk15 Ali Akcaagac
2004-07-04 16:36 ` OGAWA Hirofumi [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-05 6:08 Ali Akcaagac
2004-07-05 4:50 Ali Akcaagac
2004-07-04 22:11 Ali Akcaagac
2004-07-04 22:17 ` Jesse Stockall
2004-07-05 5:02 ` OGAWA Hirofumi
2004-07-04 11:28 Ali Akcaagac
2004-07-04 12:18 ` Andries Brouwer
2004-07-04 13:44 ` Jesse Stockall
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=877jtjwwyt.fsf@devron.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=aebr@win.tue.nl \
--cc=aliakc@web.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