From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: NamJae Jeon <linkinjeon@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: RFC : fat : default errors use FAT_ERRORS_CONT instead of FAT_ERRORS_RO.
Date: Thu, 13 Oct 2011 14:01:32 +0900 [thread overview]
Message-ID: <87vcrtqyc3.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <CAKYAXd9v_wFg2RQ_R+fYyCJnCbnuMs_VECujOen1GUSGXo3rHw@mail.gmail.com> (NamJae Jeon's message of "Thu, 13 Oct 2011 09:24:52 +0900")
NamJae Jeon <linkinjeon@gmail.com> writes:
> Hi ogawa.
>
> I found different error exception between linux fat and windows fat.
>
> When fat is currputed by sudden unplug usb device formatted fat, fat
> does never change RO partition on windows.
>
> It said windows fat provide a chance that continuously access
> partition except corrupted file.
>
> Currently when access corrupted file, linux fat change RO parition
> from RW. So user no longer do open/write on linux fat.
>
> I suggest that the default errors of linux fat use FAT_ERRORS_CONT
> instead of FAT_ERRORS_RO.
>
> I want to know your opinion.
I think it is dangerous, and the default should be safer side.
If driver noticed the corruption, it means FS is not unknown state
anymore. Any files/directories are possibly corrupted.
Even if you change the file that seems to be uncorrupted, it may make FS
unrecoverable more. (e.g. lose all data in worst case)
Thanks.
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
next prev parent reply other threads:[~2011-10-13 5:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-13 0:24 NamJae Jeon
2011-10-13 0:57 ` Valdis.Kletnieks
2011-10-13 1:24 ` NamJae Jeon
2011-10-13 1:30 ` NamJae Jeon
2011-10-13 2:01 ` NamJae Jeon
2011-10-13 10:01 ` Alan Cox
2011-10-13 5:01 ` OGAWA Hirofumi [this message]
2011-10-13 7:35 ` NamJae Jeon
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=87vcrtqyc3.fsf@devron.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=linkinjeon@gmail.com \
--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
all inboxes | Powered by JetHome®