From: Ted Ts'o <tytso@mit.edu>
To: Ivan Shmakov <oneingray@gmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: a (documented) way to get the Ext2+ filesystem size?
Date: Wed, 17 Aug 2011 14:31:01 -0400 [thread overview]
Message-ID: <20110817183101.GC6901@thunk.org> (raw)
In-Reply-To: <86aab94mfg.fsf@gray.siamics.net>
On Tue, Aug 16, 2011 at 06:37:23PM +0700, Ivan Shmakov wrote:
> How do I get the Ext2+ filesystem size (in blocks)?
I assume you need the exact numbers, so you can't use statfs(2)? What
are you using it for?
- Ted
next prev parent reply other threads:[~2011-08-17 18:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-16 11:37 a (documented) way to get the Ext2+ filesystem size? Ivan Shmakov
2011-08-16 14:21 ` Jan Kara
2011-08-17 18:31 ` Ted Ts'o [this message]
2011-08-17 18:50 ` Ivan Shmakov
2011-08-17 22:09 ` Ted Ts'o
2011-08-18 2:34 ` Steven Liu
2011-08-18 4:25 ` e2dis example usage pattern Ivan Shmakov
2011-08-18 3:49 ` a (documented) way to get the Ext2+ filesystem size? Ivan Shmakov
2011-08-18 21:03 ` Ted Ts'o
2011-08-19 4:34 ` Ivan Shmakov
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=20110817183101.GC6901@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=oneingray@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).