| 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: Wed, 20 Jul 2011 10:28:57 -0400 From: Theodore Tso <tytso@....EDU> To: hao.bigrat@...il.com Cc: linux-ext4@...r.kernel.org, Robin Dong <sanbai@...bao.com> Subject: Re: [PATCH bigalloc] e2fsprogs: change root-inode to extent-mapped On Jul 20, 2011, at 1:38 AM, hao.bigrat@...il.com wrote: > From: Robin Dong <sanbai@...bao.com> > > After creating more than 1000 files in root directory on ext4 of bigalloc, > the kernel reports many error messages like: > > [181126.730911] EXT4-fs error (device sda4): ext4_ind_map_blocks:1015: inode #2: comm falloc: Can't allocate blocks for non-extent mapped inodes with bigalloc > [181126.735945] EXT4-fs error (device sda4): ext4_ind_map_blocks:1015: inode #2: comm falloc: Can't allocate blocks for non-extent mapped inodes with bigalloc > > because the root inode of a new ext4 filesystem is type of block-mapped > even use mke2fs with "-O extent,bigalloc". This is fixed already in the "next" branch of e2fsprogs http://git.kernel.org/?p=fs/ext2/e2fsprogs.git;a=commit;h=1afb468b9a80031b39eab37272709f45727fb221 This commit was checked in well over a month ago. If you're not using the latest next branch of e2fsprogs, you really should.... this wasn't the only bigalloc-related mke2fs bug that was fixed, and e2fsck should now be working as well with bigalloc. -- 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