On Thu, Aug 03, 2006 at 11:09:10PM -0700, UZAIR LAKHANI wrote: ... > (1) Finding out the meanings of FIST_FILTER_SCA and The stackable filesystem changes the size of the data: for example, gzipfs takes n bytes and compresses them to m bytes. > FIST_FILTER_DATA Data gets transformed, but the size is the same: for example, rot13fs takes n bytes and runs them though rot13, the result is still n bytes. > (3) When I update some file in the actual fs e.g. a > file in the folder on ext3 file system, the changes > done there are not reflected on the same file on > wrapper fs but the vice versa is working correctly. That is an artifact of how the Linux VFS works. When you modify a file though wrapfs (or any other stackable file system) the wrapfs code gets called. It then calls the lower file system code on your behalf. When you modify the lower file directly, ext3 gets the called, but since Linux has no way for this change to be announced up the stack, wrapfs happily uses the old, cached data. If you have ideas about how to solve this, please share them - right now, there is a lot of work being done to get Unionfs (ours) and eCryptfs into the vanilla linux kernel. Jeff. -- Linux, n.: Generous programmers from around the world all join forces to help you shoot yourself in the foot for free. - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
