02-12-2010
Quote:
Originally Posted by
digitalrg
We have an application which is expected to create 12000 files per day. We have to archive files only after 6 days. As i know that maximum limit for files/directories to be created are 32K.
Can you provide a link supporting that limitation ? Performance definitely degrades with large number of files in a directory under UFS, but I'm not aware of any hardcoded limit.
Quote:
What is that option/variable in Soalris to change this limit from 32K to 64K or any other value?
Store these files on ZFS and there will be no limit you can ever reach.
9 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi I am going to migrate our datawarehouse system from HP Tru 64 Unix to the Red Hat Linux.
Inside the box, it is running around 40 cron jobs; inside each cron job, it is calling other shell script files, and the shell script files may again call other shell script files or ctl files(for... (1 Reply)
Discussion started by: franksubramania
1 Replies
2. Shell Programming and Scripting
Hi,
Could someone please assist on a quick way of How to extract data from indexed files (ISAM files) maintained in an UNIX(AIX) server.The file data needs to be extracted in flat text file or CSV or excel format .
Usually we have programs in microfocus COBOL to extract data, but would like... (2 Replies)
Discussion started by: devina
2 Replies
3. UNIX for Dummies Questions & Answers
the sorting is based on name of file,
file size
modification time stamps o f file
it should dislay the output in the following format
"." and ".." enteries should be ignored
please give some idea how to do it (1 Reply)
Discussion started by: pappu kumar jha
1 Replies
4. Shell Programming and Scripting
Hi,
I am new to shell scripting.Please help me on this.I am using solaris 10 OS and shell i am using is
# echo $0
-sh
My requirement is i have source file say makefile.I need to extract files with extensions (.c |.cxx |.h |.hxx |.sc) from the makefile.after doing so i need to check whether... (13 Replies)
Discussion started by: muraliinfy04
13 Replies
5. Shell Programming and Scripting
I need a script file for backup (zip or tar or gz) of old log files in our unix server (causing the space problem). Could you please help me to create the zip or gz files for each log files in current directory and sub-directories also?
I found one command which is to create gz file for the... (4 Replies)
Discussion started by: Mallikgm
4 Replies
6. UNIX for Advanced & Expert Users
Find all files in the current directory only excluding hidden directories and files.
For the below command, though it's not deleting hidden files.. it is traversing through the hidden directories and listing normal which should be avoided.
`find . \( ! -name ".*" -prune \) -mtime +${n_days}... (7 Replies)
Discussion started by: ksailesh1
7 Replies
7. Shell Programming and Scripting
Hii,
Could someone help me to append string to the starting of all the filenames inside a directory but it should exclude .zip files and subdirectories.
Eg.
file1: test1.log
file2: test2.log
file3 test.zip
After running the script
file1: string_test1.log
file2: string_test2.log
file3:... (4 Replies)
Discussion started by: Ravi Kishore
4 Replies
8. Shell Programming and Scripting
Hi,
Very good wishes to all!
Please help to provide the shell script for generating the record counts in filed wise from the .csv file
My question:
Source file:
Field1 Field2 Field3
abc 12f sLm
1234 hjd 12d
Hyd 34
Chn
My target file should generate the .csv file with the... (14 Replies)
Discussion started by: Kirands
14 Replies
9. UNIX for Beginners Questions & Answers
i use the split command to split a one terabyte backup file into 10 chunks of 100 GB each. The files are split one after the other. While the files is being split, I will like to scp the files one after the other as soon as the previous one completes, from server A to Server B. Then on server B ,... (2 Replies)
Discussion started by: malaika
2 Replies
nfile(5) File Formats Manual nfile(5)
NAME
nfile - maximum number of open files (system-wide)
VALUES
Failsafe
Default
The default value for is (zero). The value of zero means that the system limit usually enforced by will be disabled (that is, the number
of system-wide open files is limited only by available memory).
Allowed values
The allowed values for are either (zero) or values between the minimum and maximum (inclusive). The minimum value is The maximum value is
the maximum 32-bit signed integer value that can be represented in the system. The value is further constrained in that it must be greater
than or equal to two times the per-process open file hard limit (that is,
Specify a positive integer value.
DESCRIPTION
This tunable is now private and deprecated. It should no longer be used. The system open file table was restructured in 11iV3 to remove
the architectural limitations on this value, and, therefore, is no longer needed. The recommended way to regulate the maximum number of
open files on the system is to set the values of and appropriately; the theoretical system maximum can be assumed to be *
The tunable defines the maximum number of slots in the system open file table. This number limits the cumulative number of open files by
all processes in the system. In addition to named files (regular files, directories, links, device files, and so on), other objects that
consume slots in the system open file table include pipes, FIFOs, sockets, and streams. Be aware that the and system calls consume entries
in the per-process file tables but do not consume new slots in the system open file table.
Who Is Expected to Change This Tunable?
This tunable is not expected to be changed.
Restrictions on Changing
This tunable is dynamic; tuning will take effect immediately on the running system. When the value of is dynamically tuned it cannot be
set to a value lower than the number of current open files in the running kernel. To allow an unlimited number of system-wide open files,
the value should be set to the default.
When Should the Value of This Tunable Be Raised?
This tunable should only be set to a non-zero value to enforce a limit on the number of open files.
What Are the Side Effects of Raising the Value?
By setting this tunable to a positive, non-zero value, the system wide limit will be enforced. By requiring the system to enforce a global
limit, performance of the system call and other related system calls may be impaired.
When Should the Value of This Tunable Be Lowered?
The value of rarely needs to be lowered. The value may be lowered to limit the number of open files on a system, and this may reduce mem-
ory consumption.
What Are the Side Effects of Lowering the Value?
A lower limit may restrict an application's ability to allocate a new file descriptor or open a named file.
What Other Tunable Values Should Be Changed at the Same Time?
must be equal to or greater than two times the value of Kernel checks during tunable setting ensure this.
WARNINGS
This tunable is obsolete and will be removed in a future release of HP-UX.
All HP-UX kernel tunable parameters are release specific. This parameter may be removed or have its meaning changed in future releases of
HP-UX.
Installation of optional kernel software, from HP or other vendors, may cause changes to tunable parameter values. After installation,
some tunable parameters may no longer be at the default or recommended values. For information about the effects of installation on tun-
able values, consult the documentation for the kernel software being installed. For information about optional kernel software that was
factory installed on your system, see at
AUTHOR
was developed by HP.
SEE ALSO
kctune(1M), sam(1M), dup(2), dup2(2), gettune(2), open(2), settune(2), maxfiles(5), maxfiles_lim(5), nproc(5).
OBSOLETE
Tunable Kernel Parameters nfile(5)