From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Hiroyuki Machida <machida@sm.sony.co.jp>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFD] FAT robustness
Date: Tue, 19 Jul 2005 23:54:52 +0900 [thread overview]
Message-ID: <87fyuaq20z.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <42D9FDAC.3010109@sm.sony.co.jp> (Hiroyuki Machida's message of "Sun, 17 Jul 2005 15:41:48 +0900")
Hiroyuki Machida <machida@sm.sony.co.jp> writes:
> We currently plan to add following features to address FAT corruption.
>
> - Utilize standard 2.6 features as much as possible
> - Implement as options of fat, vfat and uvfat
What is the uvfat? typo (xvfat)? Why is this an option (does it have
the big demerit)?
> - Utilize noop elevator to cancel unexpected operation reordering
Why don't you use the barrier?
> - Coordinate order of operations so that update data first, meta
> data later with transaction control
Is this meaning the SoftUpdates? What does this guarantee? How does
this handle the rename(), and cyclic dependency of updates?
> - With O_SYNC, close() make flush all related data and
> meta-data, then wait completion of I/O
What is this meaning? Why does O_SYNC only flush at close()?
Almost things in your email is needing the detail.
I'm thinking the SoftUpdates is best solution for now. Could you tell
the detail of your solution?
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
next prev parent reply other threads:[~2005-07-19 14:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-17 6:41 Hiroyuki Machida
2005-07-18 11:57 ` Paulo Marques
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 [this message]
2005-07-21 12:15 ` Hiroyuki Machida
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=87fyuaq20z.fsf@devron.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--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
all inboxes | Powered by JetHome®