From: Valdis.Kletnieks@vt.edu
To: NamJae Jeon <linkinjeon@gmail.com>
Cc: hirofumi@mail.parknet.co.jp, linux-kernel@vger.kernel.org
Subject: Re: RFC : fat : default errors use FAT_ERRORS_CONT instead of FAT_ERRORS_RO.
Date: Wed, 12 Oct 2011 20:57:41 -0400 [thread overview]
Message-ID: <13498.1318467461@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Thu, 13 Oct 2011 09:24:52 +0900." <CAKYAXd9v_wFg2RQ_R+fYyCJnCbnuMs_VECujOen1GUSGXo3rHw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 722 bytes --]
On Thu, 13 Oct 2011 09:24:52 +0900, NamJae Jeon said:
> It said windows fat provide a chance that continuously access
> partition except corrupted file.
It also gives you a chance to make things worse by continuing to write to the
device. If you force it RO at the first sign of trouble, maybe you lose a few
blocks of one file. If you keep writing to it, creating new files, erasing
files, and so on, pretty soon your corrupted filesystem is even more corrupted.
> I suggest that the default errors of linux fat use FAT_ERRORS_CONT
> instead of FAT_ERRORS_RO.
And what user benefit does that give? If you keep going, they won't
realize their device is corrupted, and won't have any reason to *fix* the
filesystem.
[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2011-10-13 0:57 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 [this message]
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
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=13498.1318467461@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=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®