From: DervishD <lkml@dervishd.net>
To: Juergen Beisert <juergen127@kreuzholzen.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Wrong free clusters count on FAT32
Date: Thu, 19 Apr 2007 16:19:42 +0200 [thread overview]
Message-ID: <20070419141942.GF8287@DervishD> (raw)
In-Reply-To: <200704191352.06456.juergen127@kreuzholzen.de>
Hi Juergen :)
* Juergen Beisert <juergen127@kreuzholzen.de> dixit:
> On Thursday 19 April 2007 10:57, DervishD wrote:
> > I have a portable device with a FAT32 formatted hard disk in it, and
> > everytime I delete a file in the device *using the device itself to
> > do it* the device increases its count of free space and if I plug
> > the device in a Windows system, Windows agrees on the free space.
> > Linux doesn't. Linux believes that the files are still there
> > ocuppying space, and I have to run fsck.vfat to fix the problem.
>
> As I remember: It needs a large amount of time to calculate the free
> space on a big FAT32 system.
Big fat truth, I'm afraid. The thing is that I thought that Linux
did that from time to time to update the count. Obviously, doing it for
every statfs call would be very expensive :((
> So the last free sector count is also stored. When mounting this
> filesystem you don't need to walk through the whole FAT to calculate
> the available space, you can use this "cached" value instead. And this
> cached value seems not to be updated in your portable device.
It doesn't, certainly, but Windows doesn't care. Moreover, the
device doesn't seem to recalculate the value on every run (unless it
does it lightning fast!), so maybe the number is stored elsewhere (the
count can be stored in many places as far as I've read, but I don't know
the details).
A mount option to force walking the FAT and getting the real info
could be interesting. That way, it will be only done for certain devices
(small disks, for example).
Thanks for your answer :)
Raúl Núñez de Arenas Coronado
--
Linux Registered User 88736 | http://www.dervishd.net
It's my PC and I'll cry if I want to... RAmen!
next prev parent reply other threads:[~2007-04-19 14:17 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-19 8:57 Wrong free clusters count on FAT32 DervishD
2007-04-19 10:27 ` Boaz Harrosh
2007-04-19 14:23 ` DervishD
2007-04-19 11:52 ` Juergen Beisert
2007-04-19 14:19 ` DervishD [this message]
2007-04-21 22:42 ` OGAWA Hirofumi
2007-04-22 3:18 ` Andrew Morton
2007-04-22 4:26 ` OGAWA Hirofumi
2007-04-22 11:26 ` DervishD
2007-04-22 11:55 ` OGAWA Hirofumi
2007-04-22 20:08 ` DervishD
2007-04-23 2:27 ` OGAWA Hirofumi
2007-04-23 6:19 ` DervishD
2007-04-22 11:17 ` DervishD
2007-04-22 11:28 ` Juergen Beisert
[not found] <8bAF0-3Yj-29@gated-at.bofh.it>
[not found] ` <8bDta-8rc-31@gated-at.bofh.it>
[not found] ` <8bFEr-3B4-1@gated-at.bofh.it>
[not found] ` <8cwz8-2fE-13@gated-at.bofh.it>
2007-04-22 13:28 ` Bodo Eggert
2007-04-22 14:04 ` OGAWA Hirofumi
2007-04-22 14:29 ` OGAWA Hirofumi
2007-04-22 14:53 ` Andreas Schwab
2007-04-22 15:13 ` OGAWA Hirofumi
2007-04-22 21:46 ` Bodo Eggert
2007-04-23 2:20 ` OGAWA Hirofumi
2007-04-22 20:11 ` DervishD
[not found] ` <8cAMl-du-3@gated-at.bofh.it>
[not found] ` <8cBS7-1Qa-1@gated-at.bofh.it>
[not found] ` <8cIqE-3qZ-9@gated-at.bofh.it>
[not found] ` <8cITG-40H-5@gated-at.bofh.it>
2007-04-22 17:21 ` Bodo Eggert
2007-04-22 17:44 ` 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=20070419141942.GF8287@DervishD \
--to=lkml@dervishd.net \
--cc=juergen127@kreuzholzen.de \
--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