From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Sancho Dauskardt <sda@bdit.de>,
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Cc: linux-kernel@vger.kernel.org
Subject: Re: FAT statfs loop abort on read-error
Date: Sun, 6 Jul 2003 10:24:10 -0700 [thread overview]
Message-ID: <20030706102410.2becd137.rddunlap@osdl.org> (raw)
In-Reply-To: <5.0.2.1.2.20030704123653.03140b70@pop.puretec.de>
On Fri, 04 Jul 2003 13:57:19 +0200 Sancho Dauskardt <sda@bdit.de> wrote:
| Hi all,
|
| i've written to the current FAT maintainer (Gordon Chaffee) about this,
| but he's no longer active, so:
|
| While working in the usb-sotrage area (mostly with removeable media, eg.
| CompactFlash in USB-Readers), i've come across a litte odd behaviour:
|
| when calling statfs on a volume that has been removed (without umount)
| fat_statfs() will attempt to read all sectors of the fat table quite a few
| times (depending on the fat type, eg. FAT16 --> 256 times).
|
| eg:
| 1. mount /dev/sda1 /mnt/cf
| 2. remove card
| 3. df
|
| on my system, for a 16 MB CompactFlash formated with FAT-16 this takes 47
| seconds.
|
| Possible solution:
| 1. let default_fat_access return something like -2 on 'can't read' error.
| 2. Abort stafs loop on error.
| 3. return -EIO
|
| This would break mode fat_access calls. I could make a patch, but I don't
| know what's going on with those cvf extensions (which seem to replace
| fat_access). Is dmsdos dead / can we ignore it ?
| Somewhere in the list archives, I found comments about the cvf stuff being
| completely removed ?
Try asking OGAWA Hirofumi (cc-ed). He's the de facto FAT maintainter.
(I asked him to add a patch to MAINTAINTERS...)
--
~Randy
| http://developer.osdl.org/rddunlap/ | http://www.xenotime.net/linux/ |
next prev parent reply other threads:[~2003-07-06 17:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-04 11:57 FAT statfs loop abort on read-error Sancho Dauskardt
2003-07-06 17:24 ` Randy.Dunlap [this message]
2003-07-07 15:54 ` OGAWA Hirofumi
2003-07-07 16:24 ` Christoph Hellwig
2003-07-08 12:18 ` OGAWA Hirofumi
2003-07-08 12:33 ` Christoph Hellwig
2003-07-08 14:56 ` OGAWA Hirofumi
2003-07-07 16:38 ` Jeff Garzik
2003-07-08 12:29 ` Sancho Dauskardt
2003-07-08 14:46 ` OGAWA Hirofumi
2003-09-11 20:47 ` Sancho Dauskardt
2003-09-12 17:12 ` OGAWA Hirofumi
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=20030706102410.2becd137.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=hirofumi@mail.parknet.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=sda@bdit.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.