Originally posted by RahulSundaram
View Post
Announcement
Collapse
No announcement yet.
OpenSUSE Looks To Switch To Btrfs For Next Release
Collapse
X
-
Originally posted by JS987 View PostIt should be possible to test most use cases, if there are one or more full time testers who will create new or use existing realistic tests for all common real world software like database server.
Which you can't, really.
Comment
-
Originally posted by JS987 View PostProper testing would still reduce number of bugs significantly.
Comment
-
Originally posted by GreatEmerald View PostThe article never claimed otherwise. "Next" does not necessarily mean 13.1.
from http://www.merriam-webster.com/dictionary/next
1next
adjective \ˈnekst\
: coming after this one : coming after the one that just came, happened, etc.
: any other
Full Definition of NEXT
1
: immediately adjacent (as in place, rank, or time)
2
: any other considered hypothetically <knew it as well as the next man>
Comment
-
BTRFS is still no where near ready... yet
BTRFS has a serious Achilles heel and... ironically its COW & snapshots...
Every time a snapshot is made, it?s b-tree changes, and when it changes, that forces the entire file system structure (b+tree) to be modified and duplicated on each file system snapshot.
So that creates an exponential degradation each and every time a snapshot is performed simply because its COW feature is working against it really badly.
So... the very benefit BTRFS has as its best feature its always defended for(snapshots) completely makes the file system into a ticking data-time-bomb until there?s an exponential metadata overload to the point of a grinding halt and system freeze, just because there are too many nodes created by the snapshots which cause that exponential b-tree node duplication.
This is a very serious reason to NOT USE BTRFS AS DEFAULT BECAUSE ALL BTRFS FILE SYSTEMS WILL NEED TO BE DESTROYED AND RECREATED IF/WHEN THIS PROBLEM IS EVER SOLVED.
Also, all the REAL databases like Postgres, Oracle, MSSQL and MySQL etc, have realized that the only true way to be consistent and able to not be insane after the end of an error frenzy, is to append to their transaction log, and they seem extremely separated with their internal structures etc so if anyone COULD have found a way to not use a single log to contend on, it would be them.
I really do apologize for caps but hasty use of BTRFS is a BAD IDEA still, please stick to EXT4 or XFS.
Comment
-
Originally posted by HeavensRevenge View PostBTRFS has a serious Achilles heel and... ironically its COW & snapshots...
Every time a snapshot is made, it?s b-tree changes, and when it changes, that forces the entire file system structure (b+tree) to be modified and duplicated on each file system snapshot.
So that creates an exponential degradation each and every time a snapshot is performed simply because its COW feature is working against it really badly.
So... the very benefit BTRFS has as its best feature its always defended for(snapshots) completely makes the file system into a ticking data-time-bomb until there?s an exponential metadata overload to the point of a grinding halt and system freeze, just because there are too many nodes created by the snapshots which cause that exponential b-tree node duplication.
This is a very serious reason to NOT USE BTRFS AS DEFAULT BECAUSE ALL BTRFS FILE SYSTEMS WILL NEED TO BE DESTROYED AND RECREATED IF/WHEN THIS PROBLEM IS EVER SOLVED.
Also, all the REAL databases like Postgres, Oracle, MSSQL and MySQL etc, have realized that the only true way to be consistent and able to not be insane after the end of an error frenzy, is to append to their transaction log, and they seem extremely separated with their internal structures etc so if anyone COULD have found a way to not use a single log to contend on, it would be them.
I really do apologize for caps but hasty use of BTRFS is a BAD IDEA still, please stick to EXT4 or XFS.
Comment
-
Originally posted by Luke_Wolf View PostActually yes it does, in terms of futures "Next" is a very specific term meaning "The one after the current one", and openSUSE.Release.Current = 12.3
Originally posted by HeavensRevenge View PostBTRFS has a serious Achilles heel and... ironically its COW & snapshots...
Comment
Comment