linux-ext4 - Re: [RFC] ext4-locality-groups patch

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <458010CE.6020402@redhat.com>
Date:	Wed, 13 Dec 2006 08:40:14 -0600
From:	Eric Sandeen <sandeen@...hat.com>
To:	Alex Tomas <alex@...sterfs.com>
CC:	Valerie Clement <valerie.clement@...l.net>,
	linux-ext4@...r.kernel.org
Subject: Re: [RFC] ext4-locality-groups patch

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.

This is probably a discrepancy that comes from reading the block device 
directly, right?  Which is not necessarily in sync with the address 
space for the filesystem.

-Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html