public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Maciej Zenczykowski <maze@cela.pl>
Cc: Yokota Hiroshi <yokota@netlab.is.tsukuba.ac.jp>,
	<linux-kernel@vger.kernel.org>
Subject: Re: FAT fs sanity check patch
Date: Sun, 14 Dec 2003 23:33:40 +0900	[thread overview]
Message-ID: <87ad5vfozf.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <Pine.LNX.4.44.0312132122020.6211-100000@gaia.cela.pl>

Maciej Zenczykowski <maze@cela.pl> writes:

> > 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.
> 
> How about not playing around with fat detection and instead implement a 
> force mount flag for FAT, which would ignore all (most?) detection errors.  
> Of course if errors occured later you'd end up with a R/O filesystem.  And if 
> you forced something that wasn't FAT, you'd be screwed... but that's to be 
> expected...

Yes, this flag would be one of candidates... However the scandisk/chkdisk
of windows fixed this bad format. Such a fsck may be best solution, I think.

Well, since the number of blacklists is three, I would like to wait
the more report before doing anything.

Thanks.
-- 
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>

      reply	other threads:[~2003-12-14 14:34 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
2003-12-13 20:23       ` Maciej Zenczykowski
2003-12-14 14:33         ` OGAWA Hirofumi [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=87ad5vfozf.fsf@devron.myhome.or.jp \
    --to=hirofumi@mail.parknet.co.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maze@cela.pl \
    --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