Unfinished work: Difference between revisions
add xfs_reno |
duh |
||
| Line 8: | Line 8: | ||
== The xfs_reno tool == | == The xfs_reno tool == | ||
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 [http://marc.info/?l=linux-xfs&m=119130906204596&w=2] [http://marc.info/?l=linux-xfs&m=119147190705051&w=2] 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 [ | 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 [http://marc.info/?l=linux-xfs&m=119130906204596&w=2] [http://marc.info/?l=linux-xfs&m=119147190705051&w=2] 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 [http://marc.info/?l=linux-xfs&m=119131697224361&w=2] for full shrink support. | ||
Revision as of 18:01, 21 December 2008
This is a list of patches that haven't been merged because they haven't been fully completed.
Inline data in inodes
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
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.