[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Bug#294206: stat(1) unclear about block size
From: |
Jim Meyering |
Subject: |
Re: Bug#294206: stat(1) unclear about block size |
Date: |
Tue, 08 Feb 2005 17:43:08 +0100 |
Jeroen van Wolffelaar <address@hidden> wrote:
> I've done a bit more reading and googling, and I found statvfs(2):
>
> struct statvfs {
> unsigned long f_bsize; /* file system block size */
> unsigned long f_frsize; /* fragment size */
> fsblkcnt_t f_blocks; /* size of fs in f_frsize units */
> fsblkcnt_t f_bfree; /* # free blocks */
> fsblkcnt_t f_bavail; /* # free blocks for non-root */
...
> So, since statfs seems deprecated, and statvfs more informative (it
> actually carries the units in which free and total size of filesystems
> is written), I think it would be useful for stat to support statvfs,
> which provides a superset of the functionality of statfs(2).
Does stat's --file-system (-f) option do what you want?
$ stat -f /
File: "/"
ID: 0 Namelen: 255 Type: ext2/ext3
Blocks: Total: 1032080 Free: 887328 Available: 834894 Size: 4096
Inodes: Total: 525312 Free: 490241
Message not available
- Message not available
- Re: Bug#294206: stat(1) unclear about block size, Paul Eggert, 2005/02/08
- Re: Bug#294206: stat(1) unclear about block size, Michael Stone, 2005/02/08
- Re: Bug#294206: stat(1) unclear about block size, Jeroen van Wolffelaar, 2005/02/08
- Re: Bug#294206: stat(1) unclear about block size, James Youngman, 2005/02/09
- Re: Bug#294206: stat(1) unclear about block size, Paul Eggert, 2005/02/09
- Re: Bug#294206: stat(1) unclear about block size, Paul Eggert, 2005/02/09