From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Yokota Hiroshi <yokota@netlab.is.tsukuba.ac.jp>
Cc: linux-kernel@vger.kernel.org
Subject: Re: FAT fs sanity check patch
Date: Sun, 14 Dec 2003 04:03:47 +0900 [thread overview]
Message-ID: <87fzfofsks.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <20031214031630A.yokota@netlab.is.tsukuba.ac.jp>
Yokota Hiroshi <yokota@netlab.is.tsukuba.ac.jp> writes:
> From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
> Subject: Re: FAT fs sanity check patch
> Date: Wed, 03 Dec 2003 22:17:15 +0900
>
> > > Because some MS windows based FAT filesystem disk formatter generetes
> > > wrong super bloacks.
>
> > BTW, did this happen in MS windows of which version?
>
> I tested on Windows 95 and Windows Me.
> But I think it can happen on all version of MS-Windows.
Nope, win2k didn't this at least.
> I found why MS-Windows uses wrong numbers.
>
> Usually, MO-disk uses "super floppy" format. And all "super floppy" format
> disk contains wrong numbers. But "plain (Fixed disk)" format disk contains
> correct number.
>
> In "super floppy" format, boot sector's media number is 0xf0 (== 1.44MB 2HD
> IBM-PC floppy format).
> And FAT entry's media number is 0xf8 (== Fixed disk).
>
> Media number can takes 0xf0-0xff.
> Other media number values are used for other format disks.
> For example, 1.2MB 2HC NEC-PC9801 floppy format uses 0xf9.
I know.
> Usually, these two values must be same. But "super floppy" format
> disk uses different value.
>
> Why this format uses different value?
> I think MS-Windows changes disk cache's caching strategy based on
> boot sector's media ID value.
>
> Because any removeable media can eject any time, so disk cache
> (espeially write cache) is not usable for removeable disks.
So?
> MO disk can treat as Fixed disk, except disk caching strategy.
> Because MO disk is removeable.
>
> Anyway, this bad hack is not useful for Linux. Linux uses
> mount/unmount command to flush disk cache.
Bad hack? Why? Do you know how mount operation is dangerous and it's
difficult for fatfs? Do you want to handle the any format as FAT?
This is completely unrelated to handling the cache.
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
next prev parent reply other threads:[~2003-12-13 19:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-02 22:22 FAT fs sanity check patch Yokota Hiroshi
2003-12-03 13:17 ` OGAWA Hirofumi
2003-12-13 18:16 ` Yokota Hiroshi
2003-12-13 19:03 ` OGAWA Hirofumi [this message]
2003-12-13 20:23 ` Maciej Zenczykowski
2003-12-14 14:33 ` OGAWA Hirofumi
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=87fzfofsks.fsf@devron.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=yokota@netlab.is.tsukuba.ac.jp \
/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