On 10/10/2014 12:59, Roman Mamedov wrote:
On Fri, 10 Oct 2014 12:53:38 +0200
Bob Marley <bobmarley@xxxxxxxxxxxxx> wrote:
On 10/10/2014 03:58, Chris Murphy wrote:
* mount -o recovery
"Enable autorecovery attempts if a bad tree root is found at mount time."
I'm confused why it's not the default yet. Maybe it's continuing to evolve at a pace that suggests something could sneak in that makes things worse? It is almost an oxymoron in that I'm manually enabling an autorecovery
If true, maybe the closest indication we'd get of btrfs stablity is the default enabling of autorecovery.
No way!
I wouldn't want a default like that.
If you think at distributed transactions: suppose a sync was issued on
both sides of a distributed transaction, then power was lost on one
side
What distributed transactions? Btrfs is not a clustered filesystem[1], it does
not support and likely will never support being mounted from multiple hosts at
the same time.
[1]http://en.wikipedia.org/wiki/Clustered_file_system
This is not the only way to do a distributed transaction.
Databases can be hosted on the filesystem, and those can do distributed
transations.
Think of two bank accounts, one on btrfs fs1 here, and another bank
account on database on a whatever filesystem in another country. You
want to debit one account and credit the other one: the filesystems at
the two sides *must not rollback their state* !! (especially not
transparently without human intervention)
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
