Comments on: Warning: mkdir [function.mkdir]: Too many links in … on line … http://www.intelliot.com/tech/2007/10/17/warning-mkdir-functionmkdir-too-many-links-in-on-line.html Making technology work Fri, 29 Aug 2008 21:58:10 +0000 http://wordpress.org/?v=2.5.1 By: Ryan http://www.intelliot.com/tech/2007/10/17/warning-mkdir-functionmkdir-too-many-links-in-on-line.html#comment-90 Ryan Mon, 22 Oct 2007 04:52:56 +0000 http://www.intelliot.com/tech/2007/10/17/warning-mkdir-functionmkdir-too-many-links-in-on-line.html#comment-90 I use the folder hash method with sha1. Speed was not really a concern since this hash is only found once, and I never needed it again. Right now, I only take the first letter of the hash. I've been using only the first letter, but I think I'm going to switch to the first and second. I use the folder hash method with sha1. Speed was not really a concern since this hash is only found once, and I never needed it again. Right now, I only take the first letter of the hash. I’ve been using only the first letter, but I think I’m going to switch to the first and second.

]]> By: Kenny http://www.intelliot.com/tech/2007/10/17/warning-mkdir-functionmkdir-too-many-links-in-on-line.html#comment-88 Kenny Sun, 21 Oct 2007 17:57:49 +0000 http://www.intelliot.com/tech/2007/10/17/warning-mkdir-functionmkdir-too-many-links-in-on-line.html#comment-88 Check out this post from 37 signals on how they implement something similar: http://www.37signals.com/svn/archives2/id_partitioning.php Check out this post from 37 signals on how they implement something similar: http://www.37signals.com/svn/archives2/id_partitioning.php

]]> By: Topbit http://www.intelliot.com/tech/2007/10/17/warning-mkdir-functionmkdir-too-many-links-in-on-line.html#comment-73 Topbit Wed, 17 Oct 2007 23:30:51 +0000 http://www.intelliot.com/tech/2007/10/17/warning-mkdir-functionmkdir-too-many-links-in-on-line.html#comment-73 Clarification: The 10-15% referred to the Linux IO Wait time (visible in `top`) caused by having to traverse a list of thousands of names. For this particular application, our files were already relatively random, a long string of digits. We took off the extension (.jpg) and then used the last four characters (being the most 'random'), in two groups - so 123456(78)(90) mapped to a file ./90/78/1234567890.jpg. Clarification: The 10-15% referred to the Linux IO Wait time (visible in `top`) caused by having to traverse a list of thousands of names.

For this particular application, our files were already relatively random, a long string of digits. We took off the extension (.jpg) and then used the last four characters (being the most ‘random’), in two groups - so 123456(78)(90) mapped to a file ./90/78/1234567890.jpg.

]]>