No Space Left on Device

Re:No Space Left on Device by cyberferret on Tuesday September 06, 2016 @02:43AM (#12434022)

Brings back memories of the old DOS days, when there was quite a low limit on the number of files that you could store in the root directory. I can't remember the exact numbers, but it lead to my early habits of creating a new sub directory for every little thing so nowadays (over 3 decades later) nearly everything I need is at least 5 levels deep! ;)

NB: My current working folders are now in Google Drive, but is essentially the same folder structure as I started on our Novell server about 25 years ago...

[ Parent | on HN ]

Re:No Space Left on Device by jaredsohn on Tuesday September 06, 2016 @02:53AM (#12434058)

> when there was quite a low limit on the number of files that you could store in the root directory. I can't remember the exact numbers

512?

https://en.wikipedia.org/wiki/File_Allocation_Table#Final_FA... (see the last paragraph.)

[ Parent | on HN ]

Re:No Space Left on Device by cyberferret on Tuesday September 06, 2016 @02:56AM (#12434073)

That sounds about right. It was a ridiculously low number, and even back in the days of 10MB hard drives, it was easy to bust that number with just batch and text files...

[ Parent | on HN ]

Re:No Space Left on Device by pjc50 on Tuesday September 06, 2016 @04:28AM (#12434402)

.. aided by CHKDSK, which would find orphaned allocation units and create files for them in the root directory. Could quite easily fill up your root directory on its own.

[ Parent | on HN ]

Re:No Space Left on Device by cyberferret on Tuesday September 06, 2016 @07:34AM (#12435205)

YES! That's right... all those FILEnnnn.CHK files exploding all over your root directory! Ah, those were the days!

[ Parent | on HN ]