Re: mke2fs & capacity (where did it go!?)
matthew tebbens <matthew@tebbens.com> writes:
> > > Here is what 'df' says about the drives:
> > > Filesystem 1024-blocks Used Available Capacity Mounted on
> > > /dev/hdb1 705433 485054 183942 73% /
> > > /dev/sda1 4253289 509553 3523648 13% /var/sda1
> > > /dev/sdb1 4253289 13 4033188 0% /var/sdb1
> > > /dev/sdc1 4253289 13 4033188 0% /var/sdc1
> > > /dev/sdd1 4253289 13 4033188 0% /var/sdd1
> > >
> > > This says I have 4,033,188 to play with plus 220,088 for reserved.
> > > Now, if I add those together I get 4,253,276.
> > > This is not even close to the stated formatted capacity of 4.51gigs.
> > >
> > > What am I missing here ??
> >
> > 4,033,188 + 220,088 + 13 = 4,253,289 so that's all right then.
> > But that's not what's at issue.
> > What's relevant is the 4,401,778 blocks which becomes 4,507,420,672 bytes.
> > That looks better. But even that is only looking at the first partition
> > (sda1, sdb1 etc.)
>
> But I don't have 4,401,778 blocks, I only have a total of 4,253,289 blocks
> which becomes aprox 4,355,367,000 bytes.
>
> How does it get from 4,401,778 blocks to 4,253,289 blocks ?
> Somewhere along the line I lost about 250,000 blocks... ??
There are also the superblocks and inodes, and probably other
overhead. The default ext2 fs uses 1 inode for 3KB, and it looks like
inodes are probably 128 bytes. I figure that at about 190 MB for a
4.5GB disk for inodes alone.
--
Carl Johnson carlj@peak.org
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-user-request@lists.debian.org .
Trouble? e-mail to templin@bucknell.edu .
Reply to: