From: DervishD <lkml@dervishd.net>
To: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Juergen Beisert <juergen127@kreuzholzen.de>,
linux-kernel@vger.kernel.org
Subject: Re: Wrong free clusters count on FAT32
Date: Mon, 23 Apr 2007 08:19:27 +0200 [thread overview]
Message-ID: <20070423061927.GA2428@DervishD> (raw)
In-Reply-To: <87ps5vq0yw.fsf@duaron.myhome.or.jp>
Hi Ogawa :)
* OGAWA Hirofumi <hirofumi@mail.parknet.co.jp> dixit:
> DervishD <lkml@dervishd.net> writes:
> >> It would add the limitation to following simple usage,
> >>
> >> # mount -t vfat /dev/sda1 /mnt
> >> # cp -a * /mnt
> >> # umount
> >>
> >> if /dev/sda1 was the large and slow device, "mount" will need several
> >> minutes to counts free clusters. I think the user will be hard to
> >> accept the several minutes at "mount".
> >
> > I can carry some tests, but if Windows does that tasks lightning
> > fast, Linux surely does it faster ;) I don't think, anyway, that having
> > a huge USB disk is a common practice when using "modest" machines.
> >
> > If you want, I can perform a couple of tests. I have a 80GB disk
> > that I can connect using an USB adapter and my machine is AMD Athlon XP
> > 1900+ with 1GB of RAM, which looks pretty slow nowadays O:)
>
> Yes, I think it's not common practice too. But I don't see why do you
> want to scanning at the mount.
Just because I was thinking that, otherwise, the scanning would need
to be done at each statfs call, but I was wrong: once the scanning is
done and the count is right, it is written at free_clusters and used
afterwards.
I thought the mount was the best point in time for doing this.
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-23 6: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
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 [this message]
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=20070423061927.GA2428@DervishD \
--to=lkml@dervishd.net \
--cc=akpm@linux-foundation.org \
--cc=hirofumi@mail.parknet.co.jp \
--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