From: "H. Peter Anvin" <hpa@zytor.com>
To: Phillip Lougher <phil.lougher@gmail.com>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>,
linux-kernel@vger.kernel.org, phillip@lougher.demon.co.uk
Subject: Re: squashfs size in statfs
Date: Fri, 16 Jun 2006 15:38:04 -0700 [thread overview]
Message-ID: <449332CC.6070809@zytor.com> (raw)
In-Reply-To: <cce9e37e0606161511p5fc33a8dtb63432060f9e3784@mail.gmail.com>
Phillip Lougher wrote:
>> >
>> Yes, because CRAM does it that way, and maybe zisofs does it too:
>
> Zisofs doesn't (H. Peter Anvin should know as he wrote it :-) ).
>
> root@pierrot:/# ls -la dir.iso
> -rw-r--r-- 1 root root 366592 2006-06-16 22:41 dir.iso
> root@pierrot:/# mount -t iso9660 dir.iso /mnt -o loop
> root@pierrot:/# df /mnt
> Filesystem 1K-blocks Used Available Use% Mounted on
> /dir.iso 358 358 0 100% /mnt
> root@pierrot:/# ls -la /mnt
> total 13
> drwxr-xr-x 2 root root 2048 2006-06-16 22:41 .
> drwxr-xr-x 32 root root 4096 2006-06-16 22:56 ..
> -rw-r--r-- 1 root root 51200000 2006-06-16 22:40 zero
>
> Statfs should return the size of the filesystem, not the amount of
> data the filesystem represents. In this respect the behaviour of
> Squashfs and Zisofs is correct.
>
> This is analogous to performing stat on a gzipped file. The stat
> returns the size of the compressed file, not the uncompressed size.
>
A better analogy is it is like statting a sparse file on, say, an ext3 filesystem. stat
(ls -s) and statfs report the amount of storage consumed.
-hpa
next prev parent reply other threads:[~2006-06-16 22:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-05 10:43 squashfs size in statfs Jan Engelhardt
2006-06-05 22:57 ` H. Peter Anvin
2006-06-15 9:51 ` Jan Engelhardt
2006-06-16 22:11 ` Phillip Lougher
2006-06-16 22:38 ` H. Peter Anvin [this message]
2006-06-17 9:15 ` Jan Engelhardt
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=449332CC.6070809@zytor.com \
--to=hpa@zytor.com \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=phil.lougher@gmail.com \
--cc=phillip@lougher.demon.co.uk \
/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.