Unfinished work: Difference between revisions
No edit summary |
No edit summary |
||
Line 17: | Line 17: | ||
There is a git tree on oss.sgi.com that implements NFSv4 ACLs for XFS. It is based on a SLES10 kernel tree which includes changes to the core kernel that are required to support NFSv4 ACLs [http://oss.sgi.com/cgi-bin/gitweb.cgi?p=v4acls-experimental/sles10sp2-expanded.git;a=summary] | There is a git tree on oss.sgi.com that implements NFSv4 ACLs for XFS. It is based on a SLES10 kernel tree which includes changes to the core kernel that are required to support NFSv4 ACLs [http://oss.sgi.com/cgi-bin/gitweb.cgi?p=v4acls-experimental/sles10sp2-expanded.git;a=summary] | ||
== Parent Pointers/Create+EA == | |||
Keeping track: http://thread.gmane.org/gmane.comp.file-systems.xfs.general/27772 |
Latest revision as of 18:26, 3 February 2009
This is a list of patches that haven't been merged because they haven't been fully completed.
Inline data in inodes[edit | edit source]
IWAMOTO Toshihiro had a rough patch implementing storing regular file data inside the inode data fork, similar to what we do for small directories or symlinks [1]. Needs more work, and xfs-cmds support.
The xfs_reno tool[edit | edit source]
The xfs_reno tool has been available for IRIX for a long time. It can be used to make sure all inodes fit into 32 bits which is required for many old applications on 32 bit systems. It also is one of the building blocks required to support filesystem shrinks. Two versions [2] [3] have been posted by Barry Naujok. The current version is enough for it's original usecase, but not yet enough for the shrink functionality. See the required additional steps here [4] for full shrink support.
Support for unicode / utf8 filesystems[edit | edit source]
For normal Unix filesystems the characterset does not matter because filenames are treated as opaque blobs with special treatment only for ".", "..", "/" and "\0". But for case insensitive filenames the case mapping depends on the locale. The best way to implement case insensitive filenames is thus to chose one locale and stick to it for the on disk format. Utf8 has the boadest coverage so it's the best choice if you only want to support one. Barry Naujok has worked on it and published various patches for this. The latestet unicode support patch for XFS is here [5] There is also a slightly older patch that can convert from different user charsets to unicode for the on disk format [6]
Support for NFSv4 ACLs[edit | edit source]
There is a git tree on oss.sgi.com that implements NFSv4 ACLs for XFS. It is based on a SLES10 kernel tree which includes changes to the core kernel that are required to support NFSv4 ACLs [7]
Parent Pointers/Create+EA[edit | edit source]
Keeping track: http://thread.gmane.org/gmane.comp.file-systems.xfs.general/27772