> if you want to use cwfs as your boot filesystem. could you send me the diffs offline. this may be a good solution for laptops. kfs is nice, but history is a lot to give up. venti+fossil seems too dangerous.
> the disadvantage is using cwfs vs fossil is that you cant have > themporary snapshots and here is no temporary flag (chmod -t) per > file. so you have to create your users /tmp in the "other" fs wich > does not get dumped. using ken's fs directly, this has not been a problem at coraid. we have 75 users on the worm and have been doing our best to fill it up since 2004 and yet have <500gb on the worm. 80% of the worm is email from before the migration to nupas. 10% is log files (we never delete or rotate them). the balance is Actual Work. in fact, the real advantage of venti is the ability to back up non-plan 9 systems with no native dump reasonablly efficiently. unfortunately this advantage costs a fair bit of complexity. > filesystem limitations like filename length and maximum file size is > fixed once you created your filesystem. the maximum filename length > is smaller than fossils, so you may want change that in the > configuration and recompile before creating your filesystem. we've set our filename length to 56 characters. we don't allow spaces. neither of these limitations has been a problem yet. even in hosting apt-get repos and other stuff. the maximum filesize is now argued in the moot court. the minium maximum file size (4k blocks) is ~275TB. i just don't see that as being a problem as that's 68750x bigger than our largest file at coraid. (/sys/log/ipboot) we use 8k blocks, so we run the risk of having trouble in 6*2*68750 years. i suppose by then i'll just break down and use 16k blocks. supposing you have made a mistake (seems unlikely) or an old 32-bit fs, you can use the history mechanism outlined in “A Portable History,” http://www.quanstro.net/plan9/history.pdf. i have used this to migrate from 32-bit to 64-bit filesystems twice. and once to migrate between compatable systems. i can send anyone interested all the scripts. in fact, i've had some trouble with venti and large storage arrays (like 10-20TB). venti seems to get a little confused in the set up of various filters and caches. - erik
