blob: 9e173e7e0b86f1005adb839537a1c8a273f627ed (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
|
Motivation
----------
Yes, I know what happens if you store files in a database (in respect to
drop of efficiency and incremental backups for instance). :-)
Nevertheless, there are special situations, where a filesystem in a database
is usefull. With FUSE this is also rather simple to write.
The reason I wrote one was a projects with lots of data on a ReiserFS, which
was more or less immutable and should be efficiently stored away (almost in
an archive mode). Backup is no issue there (as the files are more or less
static after an initial load), but space efficiency is an issue.
Most other projects try to map an existing database structure somehow as
files. This here should strictly deal with files/dirs as the only model.
Other projects
--------------
Pgfs: store a filesystem in Postgres, expose it as NFS server, rather old
and I was unable to find the sources
mysqlfs: the blueprint I used and got inspired from.
References
----------
http://www.cs.hmc.edu/~geoff/classes/hmc.cs135.201109/homework/fuse/fuse_doc.html
http://www.postgresql.org/docs/8.3/static/libpq-example.html
http://www.postgresql.org/docs/8.0/static/libpq-example.html
http://fuse.sourceforge.net/doxygen/structfuse__operations.html#dc6dc71274f185de72217e38d62142c4
|
