public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Valerie Clement <valerie.clement@bull.net>
Cc: ext4 development <linux-ext4@vger.kernel.org>,
	Alex Tomas <alex@clusterfs.com>,
	Andreas Dilger <adilger@clusterfs.com>
Subject: Re: problem with delayed allocation option
Date: Fri, 26 Oct 2007 20:27:03 +0530	[thread overview]
Message-ID: <4722003F.4020009@linux.vnet.ibm.com> (raw)
In-Reply-To: <4721DD74.20806@bull.net>



Valerie Clement wrote:
> Hi all,
> 
> I ran a small test which creates one directory and 2O 8-KB size files in 
> it.
> 
> When the filesystem is mounted without the delalloc option, here is the
> output of the command dumpe2fs for the group in which the directory and 
> the files are created:
> 
> Group 532 : (Blocks 17432576-17465343)
>   Block bitmap at 17432576 (+0), Inode bitmap at 17432577 (+1)
>   Inode table at 17432578-17433089 (+2)
>   32213 free blocks, 16363 free inodes, 1 directories
>   Free blocks : 17433090-17459199, 17459241-17465343
>   Free inodes : 8716310-8732672
> 
> 
> When the filesystem is mounted with the delalloc option, the same test
> gives a different result:
> 
> Group 395 : (Blocks 12943360-12976127)
>   Block bitmap at 12943360 (+0), Inode bitmap at 12943361 (+1)
>   Inode table at 12943362-12943873 (+2)
>   32213 free blocks, 16363 free inodes, 1 directories
>   Free blocks : 12943874-12955647, 12955650-12955655, 12955658-12955663, 
> 12955666-12955671, 12955674-12955679, 12955682-12955687, 
> 12955690-12955695, 12955698-12955703, 12955706-12955711, 
> 12955714-12955719, 12955722-12955727, 12955730-12955735, 
> 12955738-12955743, 12955746-12955751, 12955754-12955759, 
> 12955762-12955767, 12955770-12955775, 12955778-12955783, 
> 12955786-12955791, 12955794-12955799, 12955802-12961791, 12961793-12976127
>   Free inodes : 6471702-6488064
> 


I am finding both the case to be equally distributed. Tried
-o mballoc,delalloc and -o nomballoc,nodelalloc and ext3

for i in 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20; do dd if=/dev/zero of=mytest$i bs=1024 count=8; done


nodelalloc,nomballoc
---------------
Free blocks: 25017-25088, 25097-25600, 25609-26112, 26121-26624, 26633-27136, 27145-27648, 27657-28160, 28169-28672, 28682-29184, 29201-29696, 29713-30208, 30225-30720, 30737-31232, 31241-31744, 31753-32256, 32265-32768

delalloc,mballoc
-----------
Free blocks: 16624-16896, 16905-17408, 17417-17920, 17929-18432, 18441-18944, 18954-19456, 19465-19968, 19985-20480, 20497-20992, 21009-21504, 21521-22016, 22025-22528, 22537-23040, 23049-23552, 23561-24064, 24073-24576

with ext3
--------
Free blocks: 25017-25088, 25097-25600, 25609-26112, 26121-26624, 26633-27136, 27145-27648, 27658-28160, 28169-28672, 28689-29184, 29201-29696, 29713-30208, 30225-30720, 30729-31232, 31241-31744, 31753-32256, 32265-32768

  reply	other threads:[~2007-10-26 15:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-26 12:28 problem with delayed allocation option Valerie Clement
2007-10-26 14:57 ` Aneesh Kumar K.V [this message]
2007-10-26 17:58 ` Mingming Cao

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=4722003F.4020009@linux.vnet.ibm.com \
    --to=aneesh.kumar@linux.vnet.ibm.com \
    --cc=adilger@clusterfs.com \
    --cc=alex@clusterfs.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=valerie.clement@bull.net \
    /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