public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arkadiusz Miskiewicz <a.miskiewicz@gmail.com>
To: David Newall <davidn@davidnewall.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: df -h shows ~10 times bigger size when umounting pendrive
Date: Sun, 22 Mar 2009 11:25:16 +0100	[thread overview]
Message-ID: <200903221125.16860.a.miskiewicz@gmail.com> (raw)
In-Reply-To: <49C5DEE5.6090205@davidnewall.com>

On Sunday 22 of March 2009, David Newall wrote:
> Arkadiusz Miskiewicz wrote:
> > While umount was running and data were synced on the
> > pendrive df -h showed:
> >
> > [arekm@t400 ~]$ df -h
> > System plik�w         rozm. u�yte dost. %u�. zamont. na
> > /dev/sda3             9,6G  4,2G  5,5G  44% /
> > /dev/sdb1             9,6G  4,2G  5,5G  44% /media/floppy
>
> This looks to me like a race between umount and df.  By the time df had
> read mtab (to find the mounted filesystem), the pen drive had already
> been unmounted; but umount hadn't yet updated mtab.  It's a pretty
> trivial sort of fault, and not worth worrying about.

It's not that. umounting takes more than 15 seconds (syncing 650MB of data 
takes some time) and in that ~15 seconds I reliably get such results:

/etc/mtab contains:

/dev/sdb1 /media/floppy vfat rw 0 0

statfs() returns:

statfs("/media/floppy", {f_type=0x58465342, f_bsize=4096, f_blocks=2497555, 
f_bfree=1410716, f_bavail=1410716, f_files=10000448, f_ffree=9842679, 
f_fsid={2051, 0}, f_namelen=255, f_frsize=4096}) = 0

which is:

/dev/sdb1             9,6G  4,2G  5,4G  44% /media/floppy

So why statfs() lies on a being unmounted filesystem?

-- 
Arkadiusz Miśkiewicz        PLD/Linux Team
arekm / maven.pl            http://ftp.pld-linux.org/


  reply	other threads:[~2009-03-22 10:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-22  0:50 df -h shows ~10 times bigger size when umounting pendrive Arkadiusz Miskiewicz
2009-03-22  6:47 ` David Newall
2009-03-22 10:25   ` Arkadiusz Miskiewicz [this message]
2009-03-22 14:52     ` David Newall

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=200903221125.16860.a.miskiewicz@gmail.com \
    --to=a.miskiewicz@gmail.com \
    --cc=davidn@davidnewall.com \
    --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