From: Ian Nartowicz Subject: =?utf-8?b?aW5saW5lX2RhdGE=?= feature Date: Wed, 22 Jan 2014 16:17:06 +0000 (UTC) Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: linux-ext4@vger.kernel.org Return-path: Received: from plane.gmane.org ([80.91.229.3]:33947 "EHLO plane.gmane.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752175AbaAVQUG (ORCPT ); Wed, 22 Jan 2014 11:20:06 -0500 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1W60X5-000504-Kt for linux-ext4@vger.kernel.org; Wed, 22 Jan 2014 17:20:03 +0100 Received: from cpc65391-bagu13-2-0-cust595.1-3.cable.virginmedia.com ([81.103.170.84]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 22 Jan 2014 17:20:03 +0100 Received: from claws by cpc65391-bagu13-2-0-cust595.1-3.cable.virginmedia.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 22 Jan 2014 17:20:03 +0100 Sender: linux-ext4-owner@vger.kernel.org List-ID: I have been trying to test the inline_data feature of EXT4. I am using kernel 3.9.5 and have compiled e2fsprogs from the pu branch. I am able to set the feature and apparently to use the filesystem, but I get a lot of warnings from the kernel and fsck reports several errors and then crashes. Typical kernel warnings from dmesg: EXT4-fs warning (device sda10): ext4_rmdir:2714: empty directory has too many links (9) EXT4-fs error (device sda10): empty_inline_dir:1650: inode #26263: block 1924: comm pool: bad entry in directory: directory entry across range - offset=40(40), inode=26270, rec_len=8020, name_len=2 EXT4-fs warning (device sda10): empty_inline_dir:1657: bad inline directory (dir #26263) - inode 26270, rec_len 8020, name_len 2inline size 60 Data does appear to be correctly written and read from the filesystem without corruption. Small directories appear with size 60 bytes or 132 bytes rather than 4.1kB so everything seems to work.