Originally posted by kebabbert
View Post
from the paper:
Second, to remedy the problem of failure handling diffusion, we develop
amodified
ext3 that unifies all failure handling in a Centralized Failure Handler (CFH).
We then showcase the power of centralized failure handling in ext3c, a modified
IRON version of ext3 that uses CFH by demonstrating its support for flexible,
consistent,
and fine-grained policies. By carefully separating policy from mechanism,
ext3c demonstrates how a file system can provide a thorough, comprehensive, and
easily understandable failure-handling policy.
amodified
ext3 that unifies all failure handling in a Centralized Failure Handler (CFH).
We then showcase the power of centralized failure handling in ext3c, a modified
IRON version of ext3 that uses CFH by demonstrating its support for flexible,
consistent,
and fine-grained policies. By carefully separating policy from mechanism,
ext3c demonstrates how a file system can provide a thorough, comprehensive, and
easily understandable failure-handling policy.
Thanks, I think most of the ext4 developers have already read these papers.
They are definitely of interest, and reducing e2fsck time is a very important
area of development these days.
We have already implemented the IRON FS journal checksumming feature, and
this will go into ext4 shortly. There is lots of work needed in order to
implement checksumming for the rest of the filesystem, so if you are
interested to work on this please let us know.
They are definitely of interest, and reducing e2fsck time is a very important
area of development these days.
We have already implemented the IRON FS journal checksumming feature, and
this will go into ext4 shortly. There is lots of work needed in order to
implement checksumming for the rest of the filesystem, so if you are
interested to work on this please let us know.
Of course it is not credible to post to blogs. But if the blog links to research papers then you can post to that blog. Or if the blog links to for instance, official benchmarks. It is not necessary to link directly to the research paper or the official benchmark.
Jesus Kraftman, we had this discussion before. Earlier I posted to a Sun blog with links to official SAP benchmarks (Solaris wins over Linux) on www.sap.com,
but you said something like: the SAP benchmarks where FUD and created by Sun. You said that SAP have partnership with Sun and therefore SAP favours Solaris in official benchmarks. I showed you links that SAP have partnership with several Linux companies - so why did SAP not favour all Linux companies? Jesus Kraftman.
When Linux wins, everything is good. It does not matter if Linux uses gcc v4.xx 64bit vs OpenSolaris uses different gcc v3.xx 32 bit - you think that are good benchmarks and dont complain. But when Solaris wins, that is bad offical benchmark published by SAP and you say companies favour Sun and it is FUD benchmark. Unbelievable logic.
Jesus Kraftman. If you had read my posts, then you would have seen those research papers. I do not FUD. Read this post again if you want to see some research papers. I have more research papers about data corruption that I can post if anyone asks me.
http://www.phoronix.com/forums/showp...1&postcount=44
http://www.phoronix.com/forums/showp...1&postcount=44
Fine. I understand I FUDs a lot, in your reality. But, you on the other hand have never linked to any research papers or almost no credible links at all. And you have CONFESSED you do FUD. So, really, I dont really understand how you can accuse me of FUDing? (But, there are lots of things I dont understand about you). So it is ok if you think I FUD, especially as you can not prove that I FUD or lie. It is just more FUD from you, about me.
But I can prove that you FUD, I just link to the post where you confess you are a FUDer. Done. Kraftman = FUD and lies.
Comment