From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 Date: Sat, 7 Jun 2014 21:39:29 +0100 Message-ID: From: Riddler To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=UTF-8 Subject: [9fans] Question about fossil Topicbox-Message-UUID: f7613ea0-ead8-11e9-9d60-3106f5b1d025 I'm thinking of turning my raspberry pi into a fossil/venti combination to store some files and I am curious about how fossil would handle a particular scenario. Some background; I have a 1.5TB HDD that I was planning on turning into a 64GB fossil partition and a ~1472GB venti partition. It is quite possible the active portion of the filesystem will exceed 64GB. Obviously that is not to say I expect to be changing 64GB of data between snapshots/archives, but I may want >64GB to be accessible. My understanding from reading the wiki and related man pages is that fossil will allow this because after a file is archived to venti its blocks on the fossil partition are freed up for re-use and a reference to the venti data is stored instead. Onto my question: What if I shrunk that fossil partition to, say, 1GB and then wrote either more than 1GB in small files or a single 2GB file. Will fossil error on the write that pushes it over the edge? Perhaps 'spill' the extra data over to venti? Something else entirely?