On 2013-01-07 13:04 (GMT-0500) Liam R E Quin composed:
On Mon, 2013-01-07 at 12:54 -0500, Felix Miata wrote:
On 2013-01-07 15:15 (GMT+0200) Anssi Hannula composed:
$ df /disks/esata
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sdb1 969063752 942471244 26592508 98% /disks/esata
Do total space in df & du output exclude inode blocks?
Yes, and indirect blocks that may be needed, depending on the file
system, and also the size of any filesystem journal. Th du command
doesn't know about such things, and can't in general (e.g. not all file
systems have ways to report it). The df command looks at total available
space, which will be reduced by inode blocks; df -i gives some
information about inode usage.
So the OP questions remain:
1-how can the free block count be identical before and after adding
37,925,705K bytes in 7 files to that journal-free, 0 reserved for root
filesystem?
2-how can I find out how much the free space really is, before adding enough
files to reduce it to 0?
--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
