> what would be helpful, and move the discussion forward, is if someone > could try to replicate this with unclean shutdowns after various file > operations. i suspect that it won't repeat. but either way, it > will move the discussion forward.
For what it's worth, unclean shutdowns resulted in lost data for me under both fossil and hjfs. In my experience unclean shutdowns never seemed to cause problems for cwfs64x. In the case of both fossil and hjfs it is sometimes possible to repair the damage. Other times it is not. Fossil has vocal supporters, while hjfs is still marked experimental (bugs are actually getting fixed). The problem for users is that when you boot the system and you can't access your files, it gets in the way of the reason you booted the system in the first place. Persistence of this condition is unacceptable. I ran fossil on both hardware and under different virtual machines and eventually experienced file corruption on every single install. Once I found out about cwfs I switched to that and had zero problems, ever. Okay, I said to myself, this is where I'll stay. Anecdotal? You betcha. But cwfs never lost data. We can argue about who misread what messages forever. The fact is that some of us had problems with fossil and then found ways around the problems. For some of us that meant patching fossil or changing the way we used fossil. For others, it meant finding some other filesystem. Saying "there is no problem" changes nothing. You can debate with the Grand Canyon for hours, but when you walk off the cliff you're still going to plummet to the ground. http://img.stanleylieber.com/src/15358/img/1370274020.jpg -sl
