NTFS Disable 8dot3name

Node Operators getting started
21

Maybe so, but when I run the command

fsutil 8dot3name strip /l w:\storagenode5\8dot3_removal-2024-03-28.log /s /v w:

I saw:

...
AR3E79~1.V1     0xa6000000006587      "W:\storagenode5\orders\archive\archived-orders-121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6-1711069200000000000-1711078653858529000-ACCEPTED.v1"
ARA98E~1.V1     0xad0000000072e3      "W:\storagenode5\orders\archive\archived-orders-121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6-1711072800000000000-1711082245234998100-ACCEPTED.v1"
...

so…

22

Yeah, who knows what Microsoft does under the hood. The guide guys say something and coders do something else.

23

Just checked my Windows Server 2022 for the 8dot3name thing. Found it disabled for all drives but the system drive. I did never care about so this seems to be the default.

1 Like
24

It could be possible, that it’s because my disks are too old and I still use the old Windows version (but seems until it would stop to receive updates…), so this is why it was enabled on all my disks, not only system one.

25

I think the 8dot3 thing was a red herring from what I’ve read since posting this. Like others said, it’s disabled by default so this would only help if you have your Storj folder on your OS drive (hopefully nobody does).

10 days later I’m finally moved from the broken ReFS volume to NTFS. First time a chkdsk took 24 minutes, crazy how many files are on this thing.

Checking file system on E:
Volume label is EXOS-X14_10TB_NTFS.

Stage 1: Examining basic file system structure ...
  17633024 file records processed.                                                         File verification completed.
 Phase duration (File record verification): 6.19 minutes.
  206 large file records processed.                                     Phase duration (Orphan file record recovery): 22.19 milliseconds.
  0 bad file records processed.                                       Phase duration (Bad file record checking): 7.42 milliseconds.

Stage 2: Examining file name linkage ...
  5 reparse records processed.                                         17645364 index entries processed.                                                        Index verification completed.
 Phase duration (Index verification): 18.02 minutes.

 Phase duration (Orphan reconnection): 2.95 seconds.

 Phase duration (Orphan recovery to lost and found): 32.50 milliseconds.
  5 reparse records processed.                                        Phase duration (Reparse point and Object ID verification): 86.61 milliseconds.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
 Phase duration (Security descriptor verification): 25.29 milliseconds.
  6170 data files processed.                                             Phase duration (Data attribute verification): 5.73 milliseconds.

Windows has scanned the file system and found no problems.
No further action is required.

   9537533 MB total disk space.
   4380594 MB in 17626518 files.
   7271316 KB in 6172 indexes.
  17999427 KB in use by the system.
     65536 KB occupied by the log file.
   5132260 MB available on disk.

      4096 bytes in each allocation unit.
2441608703 total allocation units on disk.
1313858727 allocation units available on disk.
Total duration: 24.27 minutes (1456429 ms).
26

Those numbers seems off… if your drive is X14 10 TB, why there it sais 18 TB used by the system?

27

17999427 KB = 18 GB :wink:

1 Like
28

:man_facepalming:t2: ignore me… to early for math :sweat_smile:

29

  1. sooo does anyone can confirm, does it really makes disk faster for Storj case?
    by how much?

  2. if i plug in a full storj disk, (created under win 10 pro, were “8dot3name” was always enabled), to a system like windows server where its disabled, will my storj files get corrupted or smth?

30

8.3 name is disabled in windows by default on non-os drives.
You can fsutil query any volume to ensure that it’s off:

3 Likes
31

funny, and i checked and all my storj drives has 8dot3 name creation enabled,
now 14TB and 60milion small files later, to undo that with

fsutil 8dot3name strip /f /s D:

looks like will take 2x infinity, judging by the speed on my 4TB right now,
(read speed on d: after above command is going like 60KB/s write speed 240KB/s)
@AtomicInternet how long does it took You please?

EDIT:
okay that speed isn’t translate to real speed on disk.
its just speed on index or something.
In fact it did striped me a 150GB storj’s blob folder in 2,5h

Also this topic might be the solution for SLOW FILEWALKING, at least on Windows nodes,
first You check if Your disk has 8dot3name enabled:
In CMD under Admin rights type:
fsutil 8dot3name query d:

d: is a drive letter here, change for Yours specific.
it will show You if its enabled or disabled

If enabled, dissable it with:
fsutil 8dot3name set d: 1

or for storj folder only:
fsutil 8dot3name set d:\storj 1

This will prevent new files being slow down.
Now You need to stripe all existing files, to speed up the read

fsutil 8dot3name strip /s /v d:\storj

/s -parameter is for all the subdirectories
/v - is for cmd screen to show You the progress work flow

the speed is around 38MB/s on my baremetal 16TB SATA disk
So If You have 14TB of files it might take 250h but looks like it’s a must IF You had that enabled all the time.

Thank You @AtomicInternet and @pangolin
This topic should be pined for every Windows SNO for a revision.
here’s just some journal of my test with it and “how it changed my life” lol