From: Gunter Ohrner <G.Ohrner@post.rwth-aachen.de>
To: linux-kernel@vger.kernel.org
Cc: debian-devel@lists.debian.org
Subject: Re: gtkpod and Filesystem
Date: Sat, 17 Dec 2005 01:26:09 +0100 [thread overview]
Message-ID: <dnvlut$5rm$2@sea.gmane.org> (raw)
In-Reply-To: Pine.LNX.4.61.0512162329320.24996@yvahk01.tjqt.qr
Jan Engelhardt wrote:
>>Mh, what's "more gracefully" in the light of fs corruption?
> return -EIO;
In this case you wouldn't even be able to read data from the disk which is
not affected by the inconsistencies. If the FS driver switches to readonly
mode, that's possible at least. Personally I like such a kind of "Best
effort" behaviour. Well, but I'm not the vfat32 driver developer, so who am
I to argue? :-)
Greetings,
Gunter
next prev parent reply other threads:[~2005-12-17 0:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-16 14:56 gtkpod and Filesystem Alejandro Bonilla
2005-12-16 15:07 ` Gunter Ohrner
2005-12-16 22:12 ` Jan Engelhardt
2005-12-16 22:20 ` Gunter Ohrner
2005-12-16 22:33 ` Jan Engelhardt
2005-12-17 0:26 ` Gunter Ohrner [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-12-16 17:19 Bonilla, Alejandro
2005-12-16 18:09 ` Gunter Ohrner
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='dnvlut$5rm$2@sea.gmane.org' \
--to=g.ohrner@post.rwth-aachen.de \
--cc=debian-devel@lists.debian.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