linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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:54:06 +0300	[thread overview]
Message-ID: <m3odq7zw1d.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.

ah, it's simple. you're looking at superblock counters.
we don't update them every time. this was changed years
ago. try the same with regular ext3

thanks, Alex

  parent reply	other threads:[~2006-12-13 14:54 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
2006-12-13 14:54       ` Alex Tomas [this message]
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=m3odq7zw1d.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).