Hi, Miriami wrote: > > I would like the fuse filesystem to automatically grow as new files > > are added in, just like how a SQLite database would grow as new > > records being inserted.
Tim Woodall wrote: > The nearest I can think of is growisofs. That's mainly a burn program for optical media. (I praise it for being first to offer free DVD and BD burning and for giving me code examples for the SCSI specs SPC and MMC when i developed support for these media types in libburn.) But it is not fuse based and i never could get it to work with a data file instead of an optical drive. My own program xorriso does better with data files as storage medium, but like growisofs it is not based on fuse. ISO 9660 is mountable only read-only. Files can be replaced by adding a session, but each file can only be replaced as a whole. Afterwards one would have to unmount and then mount again, whenever a new session was written. > But if, instead, what you want is the backing store to grow then use a > sparse file as the backing store. This idea reduces the search to filesystems which don't hop around and write without need to new random places on their storage medium. > # truncate -s 1T file > # mke2fs -t ext4 file > That's a 1T ext4 filesystem that is, when empty, using around 20M of disk space. Question is how its "du" size grows when you put a few files into it, overwrite their content, rename and copy them. Miriami wrote: > I have found quite a lot of projects seem to meet this function, but > seems that those projects are quite unmature. Would you mind to share a few project names and/or web links ? Have a nice day :) Thomas
