Smart chkdsk



  • From my latest chkdsk run:

    More than one CLIENT~1.XML in C:\BOINC. Renamed to CLIENT~1.XM0.
    More than one CLIENT~1.XML in C:\BOINC. Renamed to CLIENT~1.XM0.
    


  • @badpazzword said:

    From my latest chkdsk run:

    More than one CLIENT~1.XML in C:\BOINC. Renamed to CLIENT~1.XM0.
    More than one CLIENT~1.XML in C:\BOINC. Renamed to CLIENT~1.XM0.

    Next time you run chkdsk, it'll say:

    More than one CLIENT~1.XMO in C:\BOINC. Renamed to CLIENT~1.XMP.
    More than one CLIENT~1.XMO in C:\BOINC. Renamed to CLIENT~1.XMP.


  • @boolean said:

    @badpazzword said:
    From my latest chkdsk run:
    More than one CLIENT~1.XML in C:\BOINC. Renamed to CLIENT~1.XM0.
    More than one CLIENT~1.XML in C:\BOINC. Renamed to CLIENT~1.XM0.

    Next time you run chkdsk, it'll say:

    More than one CLIENT~1.XMO in C:\BOINC. Renamed to CLIENT~1.XMP.
    More than one CLIENT~1.XMO in C:\BOINC. Renamed to CLIENT~1.XMP.

    More like this:

    More than one CLIENT~1.XM0 in C:\BOINC. Renamed to CLIENT~1.XM1.
    More than one CLIENT~1.XM0 in C:\BOINC. Renamed to CLIENT~1.XM1.

    Yes it's probably hard to tell with the editor font, but on the post font it was obvious that it was "XM(zero)" not "XM(oh)".

    Still pretty WTFy but it sounds to me like this is a fat32 filesystem, and iirc it shouldn't fk up the LFN, so it'd be a simple question to find the two files and rename them to some dummy name and back.

    (Another WTF is this forum fks up whitespace in a PRE tag where whitespace is supposed to be left AS IS.)



  • It sounds to me like this is a fat32 filesystem

    Correct. Also notice that M and N are between L and O; so it wouldn't be P but R.




  • @aquanight said:

    @boolean said:
    @badpazzword said:
    From my latest chkdsk run:
    More than one CLIENT~1.XML in C:\BOINC. Renamed to CLIENT~1.XM0.
    More than one CLIENT~1.XML in C:\BOINC. Renamed to CLIENT~1.XM0.

    Next time you run chkdsk, it'll say:

    More than one CLIENT~1.XMO in C:\BOINC. Renamed to CLIENT~1.XMP.
    More than one CLIENT~1.XMO in C:\BOINC. Renamed to CLIENT~1.XMP.

    More like this:

    More than one CLIENT~1.XM0 in C:\BOINC. Renamed to CLIENT~1.XM1.
    More than one CLIENT~1.XM0 in C:\BOINC. Renamed to CLIENT~1.XM1.

    Yes it's probably hard to tell with the editor font, but on the post font it was obvious that it was "XM(zero)" not "XM(oh)".

    Still pretty WTFy but it sounds to me like this is a fat32 filesystem, and iirc it shouldn't fk up the LFN, so it'd be a simple question to find the two files and rename them to some dummy name and back.

    (Another WTF is this forum fks up whitespace in a PRE tag where whitespace is supposed to be left AS IS.)

    I suspect that this was actually caused by having three identically named files, resulting in the first one being unchanged and the second two being renamed. If that is the case, running chkdsk again will probably only rename one of them to CLIENT~1.XM1, resulting in the problem being fixed.

    So while it is a bit of a WTF that whoever wrote chkdsk didn't consider the possibility of more than two identically named files (although seeing as chkdsk has a very long heritage, it may not have been possible when it was written), it's probably not quite that bad.


Log in to reply
 

Looks like your connection to What the Daily WTF? was lost, please wait while we try to reconnect.