From: Paulo Marques <pmarques@grupopie.com>
To: Hiroyuki Machida <machida@sm.sony.co.jp>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFD] FAT robustness
Date: Mon, 18 Jul 2005 12:57:05 +0100 [thread overview]
Message-ID: <42DB9911.9010106@grupopie.com> (raw)
In-Reply-To: <42D9FDAC.3010109@sm.sony.co.jp>
Hiroyuki Machida wrote:
> [...]
> Q3 : I'm not sure JBD can be used for FAT improvements. Do you
> have any comments ?
I might not be the best person to answer this, but this just seems so
obvious:
If you plan to let a recently hot-unplugged device to be used in another
OS that doesn't understand your journaling extensions, your disk will be
corrupted.
If this is supposed to work only on OS's that understand your journaling
extensions, then there are much better filesystems out there with
journaling already.
You might be able to reduce the size of the time window where hot
removing the media will cause problems, like writting all the data first
and update the metadata in as few operations as possible. But that just
reduces the probability of data corruption. It doesn't eliminate it at all.
--
Paulo Marques - www.grupopie.com
It is a mistake to think you can solve any major problems
just with potatoes.
Douglas Adams
next prev parent reply other threads:[~2005-07-18 11:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-17 6:41 [RFD] FAT robustness Hiroyuki Machida
2005-07-18 11:57 ` Paulo Marques [this message]
2005-07-20 18:03 ` Hiroyuki Machida
2005-07-21 14:56 ` OGAWA Hirofumi
2005-07-21 5:22 ` Pavel Machek
2005-07-19 14:54 ` OGAWA Hirofumi
2005-07-21 12:15 ` Hiroyuki Machida
-- strict thread matches above, loose matches on Subject: below --
2005-07-19 16:58 Etienne Lorrain
2005-07-19 21:53 ` Horst von Brand
2005-07-20 7:35 ` Denis Vlasenko
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=42DB9911.9010106@grupopie.com \
--to=pmarques@grupopie.com \
--cc=linux-kernel@vger.kernel.org \
--cc=machida@sm.sony.co.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