| 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
| ||
|
Message-ID: <20090724223201.GA6832@mit.edu> Date: Fri, 24 Jul 2009 18:32:01 -0400 From: Theodore Tso <tytso@....edu> To: Andreas Dilger <adilger@....com> Cc: Eric Sandeen <sandeen@...hat.com>, linux-ext4@...r.kernel.org Subject: Re: [PATCH] e2freefrag utility On Thu, Jul 23, 2009 at 11:07:59AM -0600, Andreas Dilger wrote: > > I like the printing of the total blocks in each section and the > percent of blocks... Attached is an incremental patch that adds > the same to e2freefrag. Thanks, applied. One question --- right now the chunksize (as specified by -c) only affects these lines printed by e2freefrag, right? Chunksize: 1048576 bytes (256 blocks) Total chunks: 71681 Free chunks: 21657 (30.2%) They are a little confusing since "chunk" as used here is different from "chunk" used in the next part of the output: Min free chunk: 4 KB Max free chunk: 568232 KB Avg free chunk: 188 KB How useful is it to print the "total chunks / free chunks" in the general case? I'm guessing this relates to Lutsre's chunking and chunksize? Would it make sense to only print the "Chunksize / Total chunks / Free Chunks" if a chunksize is specified explicitly via the -c option, and to do a s/chunk/extent/ in the next part of the output, i.e.: Min free extent: 4 KB Max free extent: 568232 KB Avg free extent size: 188 KB - Ted -- 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
Powered by blists - more mailing lists