Malcolm V wrote:
I'm writing a program to calculate space lost to the difference between block
size and filesize (Surely this has been done before, but I couldn't find it
from a quick few googles).
It's actually a difficult task, and impossible to do in a
way that is portable between filesyste
On Wed, Apr 26, 2006 at 10:39:20AM +1000, Malcolm V wrote:
> Does anyone else get confused by the unclear usage of the term "block"?
Only all the time :-)
> Given that a *nix block is always 512 bytes (or is it?) and a disk block is a
> variety of sizes. Most documentation uses the generic term
On Wednesday 26 April 2006 09:59, Martin Pool wrote:
> On 23/04/2006, at 8:31 PM, Malcolm V wrote:
> > On an ext3 filesystem some files stat as being one disk block size
> > larger
> > then would seem necessary.
>
> This is because one block is used to store an "indirect block",
> containing poin
On 23/04/2006, at 8:31 PM, Malcolm V wrote:
I'm writing a program to calculate space lost to the difference
between block
size and filesize (Surely this has been done before, but I couldn't
find it
from a quick few googles).
Whilst doing this, I've encountered the below and I'm unsure why
I'm writing a program to calculate space lost to the difference between block
size and filesize (Surely this has been done before, but I couldn't find it
from a quick few googles).
Whilst doing this, I've encountered the below and I'm unsure why it is
happening to some files only.
On an ext3
