David Sterba dave at jikos.cz writes:
That's right. Inode represented as btrfs_inode_item does not contain any
xattr fields, they're stored independently as a btrfs_dir_item of type
BTRFS_FT_XATTR . Due to the way the b-tree keys are built, the xattr
item key should be stored near the inode
On Tue, Feb 28, 2012 at 11:30:26AM +, Alex wrote:
David Sterba dave at jikos.cz writes:
That's right. Inode represented as btrfs_inode_item does not contain any
xattr fields, they're stored independently as a btrfs_dir_item of type
BTRFS_FT_XATTR . Due to the way the b-tree keys
On Mon, Feb 27, 2012 at 10:18:55PM +, Alex wrote:
I've come across the 'gotcha' in XFS where the inode size defaults to 256 [1]
whereas for SELinux the attributes play better when you initialise it at
creation to 512.
A btrfs inode structure is 136 bytes in size. xattrs and any inline
On Mon, Feb 27, 2012 at 10:18:55PM +, Alex wrote:
From my reading of the btrfs specs [2] it doesn't look like you'll get caught
with that as the inodes will not contain embedded file data or extended
attribute data. These things are stored in other item types.
Have I read that right? I've
