From: Pavel Machek <pavel@ucw.cz>
To: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Karpov Denis.2 (EXT-Teleca/Helsinki)"
<ext-denis.2.karpov@nokia.com>,
"axboe@kernel.dk" <axboe@kernel.dk>,
"hirofumi@mail.parknet.co.jp" <hirofumi@mail.parknet.co.jp>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Hunter Adrian (Nokia-D/Helsinki)" <adrian.hunter@nokia.com>
Subject: Re: [PATCH 0/4] FS: userspace notification of errors
Date: Wed, 10 Jun 2009 23:05:07 +0200 [thread overview]
Message-ID: <20090610210507.GF1381@ucw.cz> (raw)
In-Reply-To: <4A276266.8000409@nokia.com>
On Thu 2009-06-04 08:57:58, Artem Bityutskiy wrote:
> Andrew Morton wrote:
>> hm, I'm uncertain on the desirability or otherwise of the overall feature.
>>
>> Are there users or distros or device manufacturers asking for this?
>> Where did the requirement come from?
>>
>> What downstream application will handle the uevent messages? Do you
>> have some userspace design/plan in mind?
>>
>> IOW, it would be useful if we were told more about all of this, rather
>> than just staring at a kernel patch!
>
> As the original idea came from me, while whole implementation
> and design was done by Denis, I'll comment on this.
>
> Our use-case is about hand-held devices. We are particularly
> working with large FAT volumes on MMC. Do not question please
> why it is FAT and not something else :-) Anyway, FAT is very
> unreliable, and often hits errors, in which case it simply
> switches to read-only mode, and usually prints something to
> the printk ring buffer.
So fsck the mmc card on card insertion...? fsck.vfat on flash is
pretty fast operation (as it onl needs to read directories +
FATs). Android 1.5 implements this.
...otherwise you will loose data on two files sharing clusters, will
never recover lost clusters, etc.
Perhaps it would be feasible to permit read-only mount of unclean
VFAT, run fsck in background, and buffer any changes in memory until
fsck finishes?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2009-06-10 21:05 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-03 15:05 [PATCH 0/4] FS: userspace notification of errors Denis Karpov
2009-06-03 15:05 ` [PATCH 1/4] FS: filesystem corruption notification Denis Karpov
2009-06-03 15:05 ` [PATCH 2/4] FAT: generalize errors and warning printing Denis Karpov
2009-06-03 15:05 ` [PATCH 3/4] FAT: add 'notify' mount option Denis Karpov
2009-06-03 15:05 ` [PATCH 4/4] EXT2: " Denis Karpov
2009-06-03 19:00 ` Andrew Morton
2009-06-10 21:03 ` Pavel Machek
2009-06-03 18:59 ` [PATCH 3/4] FAT: " Andrew Morton
2009-06-03 18:58 ` [PATCH 1/4] FS: filesystem corruption notification Andrew Morton
2009-06-03 15:36 ` [PATCH 0/4] FS: userspace notification of errors Eric Sandeen
2009-06-03 18:56 ` Andrew Morton
2009-06-04 1:59 ` Jamie Lokier
2009-06-04 5:57 ` Artem Bityutskiy
2009-06-04 14:27 ` Denis Karpov
2009-06-10 21:05 ` Pavel Machek [this message]
2009-06-04 12:53 ` Kay Sievers
2009-06-04 14:29 ` Russell Cattelan
2009-06-05 7:25 ` Jon Masters
2009-06-05 11:07 ` Artem Bityutskiy
2009-06-05 11:51 ` Denis Karpov
2009-06-05 13:06 ` Kay Sievers
[not found] ` <ac3eb2510906050606u7527654dv789364549b36f3e7@mail.gmail.com>
2009-06-09 13:49 ` Jan Kara
2009-06-03 22:30 ` Jan Kara
2009-06-04 6:10 ` Artem Bityutskiy
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=20090610210507.GF1381@ucw.cz \
--to=pavel@ucw.cz \
--cc=Artem.Bityutskiy@nokia.com \
--cc=adrian.hunter@nokia.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=ext-denis.2.karpov@nokia.com \
--cc=hirofumi@mail.parknet.co.jp \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).