Use Flush(True) and FlushFileBuffers both?












1















I want to write to a file and flush to disk immediately.



Other questions on SO pointed out that Flush(True) isn't reliable on .NET 4.0. I am indeed using .NET 4.0 and can't upgrade any time soon.



Is FlushFileBuffers reliable? or is it known to have a bug too?



Is there an option that I can use or should I use both and hope for the best?










share|improve this question























  • Other questions on SO A link to those questions may get you more answers.

    – mjwills
    Nov 15 '18 at 23:07
















1















I want to write to a file and flush to disk immediately.



Other questions on SO pointed out that Flush(True) isn't reliable on .NET 4.0. I am indeed using .NET 4.0 and can't upgrade any time soon.



Is FlushFileBuffers reliable? or is it known to have a bug too?



Is there an option that I can use or should I use both and hope for the best?










share|improve this question























  • Other questions on SO A link to those questions may get you more answers.

    – mjwills
    Nov 15 '18 at 23:07














1












1








1








I want to write to a file and flush to disk immediately.



Other questions on SO pointed out that Flush(True) isn't reliable on .NET 4.0. I am indeed using .NET 4.0 and can't upgrade any time soon.



Is FlushFileBuffers reliable? or is it known to have a bug too?



Is there an option that I can use or should I use both and hope for the best?










share|improve this question














I want to write to a file and flush to disk immediately.



Other questions on SO pointed out that Flush(True) isn't reliable on .NET 4.0. I am indeed using .NET 4.0 and can't upgrade any time soon.



Is FlushFileBuffers reliable? or is it known to have a bug too?



Is there an option that I can use or should I use both and hope for the best?







c# .net filesystems filestream flush






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 15 '18 at 23:06









user1071840user1071840

1,58853255




1,58853255













  • Other questions on SO A link to those questions may get you more answers.

    – mjwills
    Nov 15 '18 at 23:07



















  • Other questions on SO A link to those questions may get you more answers.

    – mjwills
    Nov 15 '18 at 23:07

















Other questions on SO A link to those questions may get you more answers.

– mjwills
Nov 15 '18 at 23:07





Other questions on SO A link to those questions may get you more answers.

– mjwills
Nov 15 '18 at 23:07












1 Answer
1






active

oldest

votes


















0














I guess the "bug" you are talking about is this one:




.NET Framework 4.0 introduced the new FileStream.Flush(bool flushToDisk) overload.
If flushToDisk is set to true, it should commit the changes to disk.



However, in many cases (if internal buffer pointer is 0) the changes are not committed to disk, and the Flush(true) call does absolutely nothing.



If applications rely on FileStream.Flush(true) working as described, it could lead to data corruption issues.




but according to Is there an official fix (aka KB) for the FileStream.Flush bug introduced in .Net 4 it has been fixed with 4.0.3:




...As far as I can tell it is fixed in .NET Framework Update 4.0.3 even though it's not mentioned in the KB.







share|improve this answer























    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53329126%2fuse-flushtrue-and-flushfilebuffers-both%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    I guess the "bug" you are talking about is this one:




    .NET Framework 4.0 introduced the new FileStream.Flush(bool flushToDisk) overload.
    If flushToDisk is set to true, it should commit the changes to disk.



    However, in many cases (if internal buffer pointer is 0) the changes are not committed to disk, and the Flush(true) call does absolutely nothing.



    If applications rely on FileStream.Flush(true) working as described, it could lead to data corruption issues.




    but according to Is there an official fix (aka KB) for the FileStream.Flush bug introduced in .Net 4 it has been fixed with 4.0.3:




    ...As far as I can tell it is fixed in .NET Framework Update 4.0.3 even though it's not mentioned in the KB.







    share|improve this answer




























      0














      I guess the "bug" you are talking about is this one:




      .NET Framework 4.0 introduced the new FileStream.Flush(bool flushToDisk) overload.
      If flushToDisk is set to true, it should commit the changes to disk.



      However, in many cases (if internal buffer pointer is 0) the changes are not committed to disk, and the Flush(true) call does absolutely nothing.



      If applications rely on FileStream.Flush(true) working as described, it could lead to data corruption issues.




      but according to Is there an official fix (aka KB) for the FileStream.Flush bug introduced in .Net 4 it has been fixed with 4.0.3:




      ...As far as I can tell it is fixed in .NET Framework Update 4.0.3 even though it's not mentioned in the KB.







      share|improve this answer


























        0












        0








        0







        I guess the "bug" you are talking about is this one:




        .NET Framework 4.0 introduced the new FileStream.Flush(bool flushToDisk) overload.
        If flushToDisk is set to true, it should commit the changes to disk.



        However, in many cases (if internal buffer pointer is 0) the changes are not committed to disk, and the Flush(true) call does absolutely nothing.



        If applications rely on FileStream.Flush(true) working as described, it could lead to data corruption issues.




        but according to Is there an official fix (aka KB) for the FileStream.Flush bug introduced in .Net 4 it has been fixed with 4.0.3:




        ...As far as I can tell it is fixed in .NET Framework Update 4.0.3 even though it's not mentioned in the KB.







        share|improve this answer













        I guess the "bug" you are talking about is this one:




        .NET Framework 4.0 introduced the new FileStream.Flush(bool flushToDisk) overload.
        If flushToDisk is set to true, it should commit the changes to disk.



        However, in many cases (if internal buffer pointer is 0) the changes are not committed to disk, and the Flush(true) call does absolutely nothing.



        If applications rely on FileStream.Flush(true) working as described, it could lead to data corruption issues.




        but according to Is there an official fix (aka KB) for the FileStream.Flush bug introduced in .Net 4 it has been fixed with 4.0.3:




        ...As far as I can tell it is fixed in .NET Framework Update 4.0.3 even though it's not mentioned in the KB.








        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 16 '18 at 1:14









        Markus SafarMarkus Safar

        4,76241938




        4,76241938
































            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53329126%2fuse-flushtrue-and-flushfilebuffers-both%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Bressuire

            Vorschmack

            Quarantine