From: Alex Tomas <alex@clusterfs.com>
To: Valerie Clement <valerie.clement@bull.net>
Cc: Alex Tomas <alex@clusterfs.com>, linux-ext4@vger.kernel.org
Subject: Re: [RFC] ext4-locality-groups patch
Date: Wed, 13 Dec 2006 17:51:01 +0300 [thread overview]
Message-ID: <m3slfjzw6i.fsf@bzzz.home.net> (raw)
In-Reply-To: <45801018.1090001@bull.net> (Valerie Clement's message of "Wed\, 13 Dec 2006 15\:37\:12 +0100")
>>>>> Valerie Clement (VC) writes:
VC> Alex Tomas wrote:
>>>>>>> Valerie Clement (VC) writes:
>>
VC> Hi Alex,
VC> I did the following test:
VC> # mkfs /dev/sdc1
VC> # mount -t ext4dev -o extents,mballoc,delalloc /dev/sdc1 /test
VC> # dumpe2fs -h /dev/sdc1
VC> # cp linux.tar /test
VC> # tar xf /test/linux.tar
VC> # dumpe2fs -h /dev/sdc1
>>
VC> The "Free blocks" and "Free inodes" counters in the dumpe2fs output
VC> did not change after running the cp and tar commands.
>>
>> sync should help, I think.
VC> No, I've just tried, it does not change anything.
VC> Valérie
not sure ....
[root@tom ~]# mke2fs -m0 -j /dev/sda1 >&/dev/null
[root@tom ~]# mount -t ext4dev -o extents,mballoc,delalloc /dev/sda1 /test
[root@tom ~]# dumpe2fs /dev/sda1 >/tmp/before
dumpe2fs 1.39.cfs1 (29-May-2006)
[root@tom ~]# dd if=/dev/zero of=/test/f bs=1M count=20
20+0 records in
20+0 records out
[root@tom ~]# dumpe2fs /dev/sda1 >/tmp/after1
dumpe2fs 1.39.cfs1 (29-May-2006)
[root@tom ~]# sync
[root@tom ~]# dumpe2fs /dev/sda1 >/tmp/after2
dumpe2fs 1.39.cfs1 (29-May-2006)
[root@tom ~]# diff -pu /tmp/before /tmp/after1
--- /tmp/before 2006-12-13 14:39:42.541828787 +0300
+++ /tmp/after1 2006-12-13 14:39:59.602086138 +0300
@@ -45,9 +45,9 @@ Group 0: (Blocks 0-32767)
Reserved GDT blocks at 2-245
Block bitmap at 246 (+246), Inode bitmap at 247 (+247)
Inode table at 248-752 (+248)
- 15607 free blocks, 16149 free inodes, 2 directories
+ 15607 free blocks, 16148 free inodes, 2 directories
Free blocks: 17161-32767
- Free inodes: 12-16160
+ Free inodes: 13-16160
Group 1: (Blocks 32768-65535)
Backup superblock at 32768, Group descriptors at 32769-32769
Reserved GDT blocks at 32770-33013
[root@tom ~]# diff -pu /tmp/after1 /tmp/after2
--- /tmp/after1 2006-12-13 14:39:59.602086138 +0300
+++ /tmp/after2 2006-12-13 14:40:05.592176495 +0300
@@ -45,8 +45,8 @@ Group 0: (Blocks 0-32767)
Reserved GDT blocks at 2-245
Block bitmap at 246 (+246), Inode bitmap at 247 (+247)
Inode table at 248-752 (+248)
- 15607 free blocks, 16148 free inodes, 2 directories
- Free blocks: 17161-32767
+ 10487 free blocks, 16148 free inodes, 2 directories
+ Free blocks: 17161-22527, 27648-32767
Free inodes: 13-16160
Group 1: (Blocks 32768-65535)
Backup superblock at 32768, Group descriptors at 32769-32769
[root@tom ~]#
try to repeat with a single file?
thanks, Alex
next prev parent reply other threads:[~2006-12-13 14:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-30 23:56 [RFC] ext4-locality-groups patch Alex Tomas
2006-12-12 16:48 ` Valerie Clement
2006-12-12 16:58 ` Alex Tomas
2006-12-13 14:08 ` Valerie Clement
2006-12-13 14:21 ` Alex Tomas
2006-12-13 14:37 ` Valerie Clement
2006-12-13 14:51 ` Alex Tomas [this message]
2006-12-13 14:54 ` Alex Tomas
2006-12-13 15:02 ` Valerie Clement
2006-12-13 21:32 ` Andreas Dilger
2006-12-13 14:40 ` Eric Sandeen
2006-12-13 21:33 ` Andreas Dilger
2006-12-13 22:26 ` Eric Sandeen
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=m3slfjzw6i.fsf@bzzz.home.net \
--to=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;
as well as URLs for NNTP newsgroup(s).