Search results

Has anyone found a solution to this yet? I am running into the same thing... I am getting ready to boot into a live ubuntu environment and nuke the drives containing the conflicting rpool (in my case I don't need to keep the other one), but it seems like this is a very heavy-handed approach...

What?? I DO take into account the probabilities... I specifically said "in rare circumstances" that is a probability. You made statements that were "absolute" and I was correcting that your assumptions of "prevention" were not guaranteed, the way you thought they were. And yes, you...

I don't understand your point here... Guaranteed Data Integrity comes at the cost of performance. Period. Always will. Whether that tradeoff is worth it (to you) for a "normal" windows VM is your choice... to anyone who can't bear to lose any data, it certainly wouldn't be "unreasonable"...

Yes, you are correct. The DB transaction log is another level of "journaling", and it necessary to ensure "atomic" commits. The more layers of protection, the better. Ultimately, plan on losing your data at some point (because you will, eventually) and have backups. Offsite. Multiple copies...

There are still some very dangerous misconceptions here. Yes, journaling helps avoid filesystem corruption* (by default). No, it is not *perfect* and you can still get a corrupted filesystem under certain (very rare) conditions... however, that is not what I am talking about. I'm talking...

As the risk of being strung up and skinned alive for a resurrecting an old thread... I thought it was worth replying to clarify one point that I think may be causing some confusion. When you say "bare metal", you are implying that is the standard, the bar to aim for in terms of data safety...