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
| ||
|
Date: Sun, 20 Nov 2011 15:08:23 +0800 From: Yongqiang Yang <xiaoqiangnk@...il.com> To: "Ted Ts'o" <tytso@....edu> Cc: linux-ext4@...r.kernel.org Subject: Re: [PATCH 1/2] dumpe2fs: dump blocks count used by super and GDT On Sun, Nov 20, 2011 at 12:43 PM, Ted Ts'o <tytso@....edu> wrote: > On Wed, Nov 16, 2011 at 09:02:07AM +0800, Yongqiang Yang wrote: >> Blocks count used by super and GDT is dumped so that users >> can know how many blocks are taken up by super and GDT. >> >> Signed-off-by: Yongqiang Yang <xiaoqiangnk@...il.com> > > I'm not convinced this is sufficiently useful to be worth adding to > dumpe2fs. How many users really need to know this? Some users are confused by static metadata blocks allocated by extN file systems. Blocks used as inode tables and bitmaps can be calculated by data from dumpe2fs. However, blocks taken up by super blocks and GDT can not be calculated. So this patch prints the number of blocks used by super blocks and GDT. IMHO, it is useful for some users who know little about extN. I met several users who ask why a fresh ext4 has used so many blocks compared to others. I know most of them are used as inode tables. Without this patch, we can explain the problem. I just think we can explain the problem with explicit numbers with the patch. Yongqiang. > > - Ted > -- Best Wishes Yongqiang Yang -- 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