From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christopher Nielsen To: 9fans@cse.psu.edu Message-ID: <20030723192342.GF63873@cassie.foobarbaz.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.3i Subject: [9fans] Fossil Questions Date: Wed, 23 Jul 2003 12:23:42 -0700 Topicbox-Message-UUID: 01cfd430-eacc-11e9-9e20-41e7f4b1d025 Is it just me or does fossil not clear the write buffer after 'snap -a' is performed? I am in the process of archiving my music collection to fossil+venti, executing 'snap -a' when the write buffer gets close to full. I was expecting to be able to just start writing to the buffer once the archival snapshot finished. Instead, it seems that I have to 'flfmt -v ...' the write buffer and restart fossil. This is a bit cumbersome when you have a fileserver that boots from fossil+venti. Also, from what I have experinced so far, fossil gets very cranky and does not recover gracefully when the write buffer is filled. I know people are on vacation and such, and I am more than happy to dive into the code to address this. Before I do, I want to make sure the behavior I am seeing is accurate and the behavior I expect is desired. That said, I must say the system is quite robust from a data safety standpoint. I've been through repeated crashes and have not lost any data that was archived to venti. Very nice work guys. -- Christopher Nielsen "They who can give up essential liberty for temporary safety, deserve neither liberty nor safety." --Benjamin Franklin