[Ocfs2-users] Free space oddities on OCFS2

[Sunil Mushran]

Once a cluster is allocated to be used for inodes, it is then only used
for inodes. As in, one will not see the freespace increase even after those
inodes are deleted. However, those "freed" blocks will be reused when
new inodes are created.

Try using 2K blocksize.

Robinson Maureira Castillo wrote:
>
> Thanks for the info, but I still don't understand if this is a normal 
> behaviour or not.
>
> For me, at least, it's not very useful if the global bitmap is 6 times 
> larger than the data I'm putting on it, and after deleting everything, 
> this bitmap doesn't decrease in size.
>
> Regards,
>
>
> -----Original Message-----
> From: Sunil Mushran [mailto:Sunil.Mushran at oracle.com]
> Sent: Wed 8/2/2006 8:19 PM
> To: Robinson Maureira Castillo
> Cc: ocfs2-users at oss.oracle.com
> Subject: Re: [Ocfs2-users] Free space oddities on OCFS2
>
> 1. The global bitmap in ocfs2 maps all the clusters on the disk. That
> includes,
> the space used by the super block, root dir, system dir, system files, 
> etc.
> Hence the usage on a clean fs. Most of this space is being used by the
> journals.
> # echo "stat //journal:0000" | debugfs.ocfs2 -n /dev/sdX
>
> 2. ocfs2 does not preallocate space for inodes. It allocates space on
> demand.
> You can view the space allocated to inodes for slot 0 as follows:
> # echo "stat //inode_alloc:0000" | debugfs.ocfs2 -n /dev/sdX
>
> 3. du does not reflect space used by filesystem metadata.
>