Originally posted by LinuxID10T
View Post
Announcement
Collapse
No announcement yet.
Where The Btrfs Performance Is At Today
Collapse
X
-
Originally posted by devius View PostSo it's probably a good idea to stay away from BTRFS for web/email/database servers. Everything else seems fine.
Comment
-
Originally posted by kebabbert View Post
Comment
-
Originally posted by LinuxID10T View PostCan we please get a filesystem benchmark using a mechanical drive? Everything here is tested using SSDs which is extremely flawed.
Comment
-
Originally posted by kebabbert View PostI didnt understand that sentence. Could you please rephrase?
Comment
-
Originally posted by kraftman View PostThe guy you linked is a damn troll. He compares Linux file systems
I hope you dont claim that PhD thesis and research papers are "damn troll"? If it was false and lies, then that research would never have passed the PhD trials. He got his PhD title, that research is valid. If it is not valid, then please mail his professor and point out the errors, then his PhD title will be withdrawn and he loose his diploma. You will instead soon get a PhD thesis if you find errors in current research and can improve it. If you can not point out the errors, then please be more careful before you accuse someone of Trolling. As we know, you are very quick to call people Troll, however you have admitted yourself that you have Trolled earlier.
Originally posted by kraftman View PostHe mentions ZFS, just because it will be available in os x. As you didn't link to a paper like you probably never did, but to some idiot then stop spreading FUD.
Here is a research paper documenting the research on ZFS. If you see some errors, please produce a paper how to improve research, and quite soon you will have a PhD thesis, you too.
Comment
-
Originally posted by voyager_biel View Postdata integrity in case of power outage, power cut or blackout....because journal is not persisted to disk... if write I/O corrupts your data or fs, then it doesn't matther which mount options you used...because corruption will be successfuly writen to fs. Only backup or old snapshot can help then to get integrity back...
This means that ALL changes was written to disc, or no changes was written to disc. I can not happen that only half of the changes where written to disc, and the other half of the changes got lost. No corruption. The state is always correct.
If power is cut before the pointer points to the new data, all old data is left intact and no corruption has occured.
Comment
Comment