Hi there, with FhGFS we may use extended attributes to store file meta data and with ext3/ext4 that also works very well and the rate to create files and to write those EAs (create() + fsetxattr() is
Currently XFS uses synchronous transactions when retiring inodes with xattrs on them. So far I've not actually found a good reason for that, so I suspect we can remove it. I'll do another audit of it
The patch below should help with the performance of deleting files that have external attributes. But I still wonder why you see attributes outside the inode if you are using 512 byte inodes and arou
On 08/16/2011 06:13 PM, Christoph Hellwig wrote: The patch below should help with the performance of deleting files that have external attributes. But I still wonder why you see attributes outside th
It means that you are having an extent spanning 8 blocks for xattr storage, that map to physical blocks 92304 to 9231 in the filesystem. It sounds to me like your workload has a lot more than 256 byt
On 08/17/2011 07:02 PM, Christoph Hellwig wrote: On Wed, Aug 17, 2011 at 03:05:28PM +0200, Bernd Schubert wrote: (squeeze-x86_64)fslab2:~# xfs_bmap -a /mnt/xfs/Bonnie.29243/00000/00000027faJxifNb0n /
XFS directory algorithms are significantly more complex than ext4. They trade off CPU usage for significantly better layout and scalability at large sizes. i.e. CPU costs less than IO so we burn more
It is neither of these. Ok, I've reproduced it on a 3.0-rc2 kernel with attr=2 and 2k inodes. An attribute of 254 bytes stays in line: .... u = (empty) a.sfattr.hdr.totsize = 270 a.sfattr.hdr.count =
Btw, one interesting thing I noticed is that xfs_attr_leaf_create always zeroes and logs whe whole attr block. I'll need to audit this a bit more, but from the highlevel POV I don't see why we can't