linux-ext4 - Re: delalloc fragmenting files?

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: <472F66EA.9080908@redhat.com>
Date:	Mon, 05 Nov 2007 12:54:34 -0600
From:	Eric Sandeen <sandeen@...hat.com>
To:	Eric Sandeen <sandeen@...hat.com>,
	Alex Tomas <bzzz.tomas@...il.com>,
	ext4 development <linux-ext4@...r.kernel.org>,
	Kalpak Shah <Kalpak.Shah@....COM>
Subject: Re: delalloc fragmenting files?

Andreas Dilger wrote:

> On a related note - the FIEMAP patches to filefrag also include a new
> output format that is much more useful, IMHO.  The new format is like:
> 
> {filename}
> ext: [logical start.. end kB]: phys start..end kB    :           kB:lun: flags
>   0: [         0..     30207]:     401416..    522251:       120828: 0 :
>   1: [     30208..     60927]:     532480..    655359:       122880: 0 :
>   2: [     60928..    121855]:     790536..    916484:       125948: 0 :
> 
> Hopefully Kalpak will be able to post the updated patches here soon.

yep, I hacked existing filefrag to do something like this, the existing
format is pretty hard to glance over :)

One thing I like about xfs_bmap is that it can tell you which Allocation
Group the blocks are in; most filesystems have some concept of
sub-regions of the filesystem, such as BGs or resource groups or whatnot
- do you think there is room for this in the FIEMAP interface?  Hm, or
should this just be calculated from knowing the size of the sub-regions...

-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