maximum number of dirs

[uri_1]

hi,

there seems to be a limit of about 50000 directories that can reside under a single subdirectory.

could it be increased? is there a patch or something?

(the sad thing is that i actually need it.... changing poor programming is harder than installing a patch)

[Uday_S_Ankolekar]

I think you need a patch that will take care of your problem

From Knowlsedge base: (Check for new patches:)


System Error (mkdir): Too many links. Problem in directory frag DocId: KBRC00007018 Updated: 5/31/01 2:59:00 PM

PROBLEM
problem: system call from the application is mkdir and the exact error
is "SYSTEM ERROR (mkdir): Too many links. Problem in directory fragment"
CONFIGURATION
V2600
11.0

RESOLUTION
To verify, count the number of subdirectories:

$ ls -l |wc -l
32766

This is hitting the LINK_MAX limit.

install PHKL_21210 (requires reboot) and the dependency PHKL_18543

PHKL_21210 information:

The number of subdirectories which can be created for VxFS is limitted to
LINK_MAX

The patch introduced a new tunable for the Vertias filesystem (vx_maxlink)
which can be used to override the MAXLINK value which governs the ceiling
of subdirectory creation.

A new VxFS tunable (vx_maxlink) has been added which allows this limit to
be changed to any value between LINK_MAX and INT_MAX (See limits(5)).

INT_MAX Max decimal value of an 2147483647 +
int
LINK_MAX Max number of links to a 32767 +*
single file

Special Installation Instructions: After patch is installed the vx_maxlink
tunable can be set in /stand/system. At that time the system needs to be
rebuilt and rebooted.

Since you are at the LINK_MAX limit you will need to build a new kernel
after the patch is installed which specifies the value of vx_maxlink kernel
tunable to a value less than 2147483647.


-USA..

[KCS_1]

hi,

i am posting this, just copy and paste this by written someone.

anyway..have a look at this

There are no limits to the number of inodes in a VxFS filesystem.

The maximum number of directories in a VxFS filesystem has been limited to 32,767. This can be increased to a maximum of 2,147,483,647 [the maxiumum integer size] by tuning the 'vx_maxlink' kernel parameter. Patch PHKL_24201 implements this parameter.


In a vxfs filesystem inode allocation will be dynamically increased if you run out of inodes. Thus, the limitation is actually on total space. If the filesystem runs out of space, therte will be no room to allocate new inodes (or to write a new file, for that matter).


have a good day!

[Jeff Schussele]

Hi uri,

Just a further note to add to USA's great answer....

Be VERY, VERY careful with the PHKL_18543 patch - lovingly termed the "patch from hell".
DO NOT reinstall it for any reason, it will immediately BREAK your system & send you scurying for your latest make_tape_recovery volume.

Be advised that it's already on every system out there & does NOT need to be included in any current patch install bundles. Well.....I'll qualify that....IF you have one of the FIRST 11.00 systems out there & have NEVER patched - not once, then.......

Cheers,
Jeff

[Dietmar Konermann]

Since setting vx_maxlink to larger values than 64k-2 breaks compatibility e.g. with the stat() system call, the tunable no longer allows to be set up to MAXINT.

Be advised NOT to set vx_maxlink to something larger than 64k-2. Otherwise you could get into trouble in the future.

Latest:
11.00 PHKL_28105
11.11 PHKL_28185

Best regards...
Dietmar.

[uri_1]

many thanx. you guyz are good.