Skip to contentSkip to conversation

Wrapfs a stackable file system

DISCUSSION David Chow 5 participants 5 messages Sep 21, 2001

lore
Share & tools
lore

David Chow

author
#0 lore raw

I am rewriting he wrapfs from the fist project and is now in a debugging stage, it is now quite ready for experimental tests.

The idea is orinigally from FiST, a stackable file system. But the FiST owner Erez seems given up to maintain the project. At the time I receive the code, it is so buggy, even unusable, lots of segmentation fault problems. I have debugging the fs for quite a while. Now it is useful in just use as a file system wrapper. It is useful in chroot environments and hardlinks aren't available. It wraps a directory and mount to another directory on tops of any filesystems. I wish to maintain this file system development since FiST's idea is good. It allow to use this base wrapfs as a template and then you can do encryption and other operations on it with fast development time. If any kernel file system maintainer is interested, please contact me .. I would like to get help to finish up my debugging work. The result will be GPL'ed. I will also package it with the fistgen package as a file system development tool. Thanks.

regards.

David Chow

#1 lore raw

* [ David Chow]

Quoted 7 lines

The idea is orinigally from FiST, a stackable file system. But the FiST owner Erez seems given up to maintain the project. At the time I receive the code, it is so buggy, even unusable, lots of segmentation fault problems. I have debugging the fs for quite a while. Now it is useful in just use as a file system wrapper. It is useful in chroot environments and hardlinks aren't available. It wraps a directory and mount to another directory on tops of any filesystems.

Is this not essentially what we already have with mount --bind in 2.4?

Oystein

Signature · 1 line
When in doubt: Think again.
#2 lore raw
Quoted 11 lines · Oystein Viggen

* [ David Chow]

Quoted 7 lines

The idea is orinigally from FiST, a stackable file system. But the FiST owner Erez seems given up to maintain the project. At the time I receive the code, it is so buggy, even unusable, lots of segmentation fault problems. I have debugging the fs for quite a while. Now it is useful in just use as a file system wrapper. It is useful in chroot environments and hardlinks aren't available. It wraps a directory and mount to another directory on tops of any filesystems.

Is this not essentially what we already have with mount --bind in 2.4?

Bindings can be used to get the same result, but underlying mechanics is different. Wrapfs is not the most interesting application of FiST, so it's hardly a surprise...

#3 lore raw
Quoted 14 lines · Alexander Viro
Quoted 10 lines · Oystein Viggen

* [ David Chow]

Quoted 7 lines

The idea is orinigally from FiST, a stackable file system. But the FiST owner Erez seems given up to maintain the project. At the time I receive the code, it is so buggy, even unusable, lots of segmentation fault problems. I have debugging the fs for quite a while. Now it is useful in just use as a file system wrapper. It is useful in chroot environments and hardlinks aren't available. It wraps a directory and mount to another directory on tops of any filesystems.

Quoted 6 lines
Quoted 1 line

Is this not essentially what we already have with mount --bind in 2.4?

Bindings can be used to get the same result, but underlying mechanics is different. Wrapfs is not the most interesting application of FiST, so it's hardly a surprise...

I think you people didn't understand what is wrapfs, if is only a template for FiST. The aim is to provide a properly maintained stackable template under linux, and so that people can use FiST to develop their own filesystem. Currently the wrapfs template is so buggy, I spend weeks to fix all the bugs and even rewriting some of the code to make it more efficient. This dosn't means --bind, it means it also fix up tons of FS'es that is previously produced by using the old buggy FiST template, FiST is good for developing new stackable file system, the current problem is that the templates are buggy.... you got it??? If you know something is good but it is not properly maintained, why not give it a hand and do all the people a flavour?

regards,

David

#4 lore raw

Some docs about stackable fs (aka wrapfs):
http://www.isi.edu/~johnh/WORK/ucla.html
and:
http://www.isi.edu/~johnh/PAPERS/index.html

Quoted 37 lines · David Chow
Quoted 14 lines · Alexander Viro
Quoted 10 lines · Oystein Viggen

* [ David Chow]

Quoted 7 lines

The idea is orinigally from FiST, a stackable file system. But the FiST owner Erez seems given up to maintain the project. At the time I receive the code, it is so buggy, even unusable, lots of segmentation fault problems. I have debugging the fs for quite a while. Now it is useful in just use as a file system wrapper. It is useful in chroot environments and hardlinks aren't available. It wraps a directory and mount to another directory on tops of any filesystems.

Quoted 6 lines
Quoted 1 line

Is this not essentially what we already have with mount --bind in 2.4?

Bindings can be used to get the same result, but underlying mechanics is different. Wrapfs is not the most interesting application of FiST, so it's hardly a surprise...

I think you people didn't understand what is wrapfs, if is only a template for FiST. The aim is to provide a properly maintained stackable template under linux, and so that people can use FiST to develop their own filesystem. Currently the wrapfs template is so buggy, I spend weeks to fix all the bugs and even rewriting some of the code to make it more efficient. This dosn't means --bind, it means it also fix up tons of FS'es that is previously produced by using the old buggy FiST template, FiST is good for developing new stackable file system, the current problem is that the templates are buggy.... you got it??? If you know something is good but it is not properly maintained, why not give it a hand and do all the people a flavour?

regards,

Quoted 8 lines

David

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com