linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Drake <dsd@laptop.org>
To: Eric Sandeen <sandeen@redhat.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Determining if an ext4 fs uses the whole partition
Date: Mon, 30 Apr 2012 12:18:48 -0600	[thread overview]
Message-ID: <CAMLZHHQUQKK10XQ2WZdgoMO9PPTmP2tNYL5xN2aQirD+TLSzbA@mail.gmail.com> (raw)
In-Reply-To: <4F9ECC0E.8020201@redhat.com>

On Mon, Apr 30, 2012 at 11:29 AM, Eric Sandeen <sandeen@redhat.com> wrote:
> For starters, use fdisk -u to get 512-byte sector units,
> otherwise it's just inscrutable CHS magic.
>
> i.e.:
>
> # fdisk -lu /dev/sda2
>
> Disk /dev/sda2: 526 MB, 526417920 bytes
> 255 heads, 63 sectors/track, 64 cylinders, total 1028160 sectors
> Units = sectors of 1 * 512 = 512 bytes
>
> so 1028160 512-byte sectors.
>
> # dumpe2fs -h /dev/sda2 | grep "Block count\|Block size"
> dumpe2fs 1.42.2 (27-Mar-2012)
> Block count:              514080
> Block size:               1024
>
> so 514080 1k blocks, or 1028160 512-byte sectors, so bingo, it's full.

Hmm yes, following the same process I can get the same results. I must
have misread/miscalculated something when I looked earlier.
User error :)

> Or, FWIW, it's harmless to invoke resize2fs if the fs already fills the
> partition; it should just exit with a no-op.

Thanks for pointing this out - its probably my best option, coming to
think of it.

>> One easy solution, if possible, would be to find out the number of the
>> last sector used by the filesystem. I could then very easily compare
>> this to the "end" information found in sysfs for the partition. Then I
>> can make the decision on whether to grow or not.
>
> dumpe2fs should certainly be able to tell you.  Mounting the fs, and
> doing statfs would, as well (f_blocks).  There should also be libext2fs
> functions you could use if you want to do it in C...

Trying the statfs approach (the fs in question is already mounted):

# dumpe2fs -h /dev/mmcblk0p2 | grep "Block count\|Block size"
dumpe2fs 1.42 (29-Nov-2011)
Block count:              949248
Block size:               4096

# stat -f /
  File: "/"
    ID: f09a7645207bdd68 Namelen: 255     Type: ext2/ext3
Block size: 4096       Fundamental block size: 4096
Blocks: Total: 934935     Free: 198205     Available: 188947
Inodes: Total: 227824     Free: 133103

The numbers don't agree.

(Not a big deal, since I can use the other 2 approaches you mentioned,
just wanted to point it out)

Thanks
Daniel
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2012-04-30 18:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-30 17:19 Determining if an ext4 fs uses the whole partition Daniel Drake
2012-04-30 17:29 ` Eric Sandeen
2012-04-30 17:37   ` Jeff Moyer
2012-04-30 19:01     ` Ted Ts'o
2012-04-30 18:18   ` Daniel Drake [this message]
2012-04-30 18:26     ` Eric Sandeen
2012-04-30 17:33 ` djwong

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=CAMLZHHQUQKK10XQ2WZdgoMO9PPTmP2tNYL5xN2aQirD+TLSzbA@mail.gmail.com \
    --to=dsd@laptop.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=sandeen@redhat.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).