-
• Hashed directories do not currently work. Be sure to keep the CONFIG_EXT3COW_INDEX flag undefined (for the time being).
-
• There is only rudimentary failure code for versioning. If your disk fails or computer crashes mid-write, there is no guarantee of file system consistency.
-
• Similarly, there are no fsck or other file system tools for ext3cow.
-
• There is no way to delete old versions. Although, this once existed in the 2.4 version, so will eventually make its way to 2.6.
-
• There is no way to backup or copy an entire version chain. A cool feature might be to have a cpv (copy with version) that will copy and entire version chain within the file system. This is tricky to implement for many reasons.
-
• The ls file@ to get a version listing needs to be updated for 2.6
-
• There should be a way to make certain files unversionable. The flag exists, but there is no user-land mechanism to turn it on/off.
-
• “Fake” or “Temporal” inodes get allocated in a stupid way, which will cause problems for long-running systems.