Prev: Purchase cheap voltarol online without prescription
Next: Ubuntu 9.10 Keeps Freezing
From: Davorin Vlahovic on 23 Oct 2009 12:14
[Fri, 23 Oct 2009 10:08:39 -0500] F. Michael Orr je napisao/la:
> The simplest (though kludgy) solution is to create another directory,
> move many of your existing directories to the new directory, and replace
> them with symlinks in the old directory. Symlinks aren't hard, and thus
> aren't subject to the 32k limitation. This of course requires constant
> babysitting, but it will get around much of the problem.

create a directory for every beginning letter...

a/ -> aardvark, avokado...
b/ -> borg, babysitter....
c..
d..


--
You, you, and you: Panic. The rest of you, come with me.
From: P1 on 23 Oct 2009 12:26
J.O. Aho wrote:
> P1 wrote:
>> There is apparently a subdirectory limit of 32,000 on ext3 file systems.
>> How are people getting around this? I have a mail server that just
>> reached that number of users and I'm unable to create more.
>
> The subdirecotry limit is 31998, symlink limit is 32000 (per inode), and don't
> forget that ext3 also has inode limitations, which will cause trouble in a
> file system with a lot of files.
>
> Don't use ext3, there are quite many other options like reiserfs, reiser4,
> jfs, xfs. The two later are industry standard file systems and all of them
> don't have the inode problem as ext3 has.
>

XFS does seem promising, thanks for that suggestion, I'll have to try it
out.
From: P1 on 23 Oct 2009 12:28
F. Michael Orr wrote:
> On Fri, 23 Oct 2009 07:00:05 +0200, J.O. Aho wrote:
>
>> P1 wrote:
>>> There is apparently a subdirectory limit of 32,000 on ext3 file
>>> systems.
>>> How are people getting around this? I have a mail server that just
>>> reached that number of users and I'm unable to create more.
>> The subdirecotry limit is 31998, symlink limit is 32000 (per inode), and
>> don't forget that ext3 also has inode limitations, which will cause
>> trouble in a file system with a lot of files.
>>
>> Don't use ext3, there are quite many other options like reiserfs,
>> reiser4, jfs, xfs. The two later are industry standard file systems and
>> all of them don't have the inode problem as ext3 has.
>
> Actually, that's not entirely accurate. The actual limit is 32766
> (32K-2). All filesystems have a limit, though they vary. That of reiser
> is 64k, but it is a limit nonetheless. I don't know about xfs, but jfs
> is 32k as well (at least the AIX flavor). UFS on Solaris is 32k as
> well. The biggest I have found is WAFL on NetApp, which has a non-magic
> number limit of 100,000.
>
> The simplest (though kludgy) solution is to create another directory,
> move many of your existing directories to the new directory, and replace
> them with symlinks in the old directory. Symlinks aren't hard, and thus
> aren't subject to the 32k limitation. This of course requires constant
> babysitting, but it will get around much of the problem.

Thanks Mike, that is a good solution I think. At least in the interim,
it's quick and easy to implement. I'll still experiment with XFS as a
possible permanent solution, but this will get me back up and running
for a while.
First  |  Prev  | 
Pages: 1 2 3
Prev: Purchase cheap voltarol online without prescription
Next: Ubuntu 9.10 Keeps Freezing