this post was submitted on 27 Jul 2023
455 points (89.0% liked)

Technology

59438 readers
4322 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 1 year ago
MODERATORS
 

As a full time desktop Linux user since 1999 (the actual year of the Linux desktop, I swear) I wish all you Windows folks the best of luck on the next clean install ๐Ÿ‘

...and Happy 30th Birthday "New Technology" File System!

you are viewing a single comment's thread
view the rest of the comments
[โ€“] d3Xt3r@lemmy.world 16 points 1 year ago

Not OP, but I occasionally come across this issue at work, where some user complains they they are unable to access a file/folder because of the limit. You often find this in medium-large organisations with many regions and divisions and departments etc. Usually they would create a shortcut to their team/project's folder space so they don't have to manually navigate to it each time. The folder structure might be quite nested, but it's organized logically, it makes sense. Better than dumping millions of files into a single folder.

Anyways, this isn't actually an NTFS limit, but a Windows API limit. There's even a registry value[1] you can change to lift the limit, but the problem is that it can crash legacy programs or lead to unexpected behavior, so large organisations (like ours) shy away from the change.

  1. https://learn.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=registry