Sponsored Content
Full Discussion: MAX file size limited to 2GB
Top Forums UNIX for Dummies Questions & Answers MAX file size limited to 2GB Post 302183742 by mhbd on Thursday 10th of April 2008 12:50:19 AM
Old 04-10-2008
MAX file size limited to 2GB

Hi All,

We are running HP rp7400 box with hpux 11iv1.

Recently, we changed 3 kernel parameters

a) msgseg from 32560 to 32767
b) msgmnb from 65536 to 65535
c) msgssz from 128 to 256

Then we noticed that all application debug file size increase upto 2GB then it stops. So far we did not find any error in application despite debug file is incomplete.

Is the debug file size limited to 2GB size due to any of the 3 kernel parameters value change? If not, how to find out the problem?

Any suggestion will help us greatly.

Thanks in advance
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

File size exceeding 2GB

I am working on HP-Unix. I have a 600 MB file in compressed form. During decompression, when file size reaches 2GB, decompression aborts. What should be done? (3 Replies)
Discussion started by: Nadeem Mistry
3 Replies

2. Shell Programming and Scripting

setting max log file size...

Hello all! I have found a new home, this place is great! I have been searching for days to find a way to set a max size for a log.txt file using a cron job exicuting a shell script. Is it possible for a script to remove older entries in a log file to maintain a limited file size? If so,... (5 Replies)
Discussion started by: v-rod
5 Replies

3. Programming

Max file size can't exceed 2 GB

We have Sun OS 5.9 we are doing a backup process (ProC program) that uses the function... fprintf(fp,"%s;%s;%s;%s;%s;%ld;%ld;%ld;%ld;%s;%s;%s;%d;%s;%s;%s;%ld;%s;%s;%s;%ld;%ld;%s;%ld;%s;%ld;%s;%s;%c%c",x_contrno, x_subno, x_b_subno,x_transdate,x_last_traffic_date,BillAmt_s, x_billamount_int,... (10 Replies)
Discussion started by: atiato
10 Replies

4. Solaris

SUN Solaris 9 - Is there a 2GB file size limit?

Hi I am using SUN/Solaris 9 and I was told that some unix versions have 2GB size limit. Does this applies to SUN/Solaris 9? Thanks. (2 Replies)
Discussion started by: GMMike
2 Replies

5. UNIX for Advanced & Expert Users

How to determine the max file size

Does anyone know a way to determine the maximum filesize on a file system on Solaris, HP-UX, AIX, Linux, and OSF1 using the command line? TIA (2 Replies)
Discussion started by: dknight
2 Replies

6. Solaris

max. size of file

I wants to ask that what is the max size of file that we can create in the unix file system. (2 Replies)
Discussion started by: sameerghogre
2 Replies

7. UNIX for Advanced & Expert Users

Max. file size

i want to know what is the maximum file size supported by linux with ext3 file system. (1 Reply)
Discussion started by: nagalenoj
1 Replies

8. UNIX for Dummies Questions & Answers

Restrict Max file size

Hello All, I am working on an issue, where I need to check the max file size of a file. If the file size exceeds 2 GB, then I need to generate an error message. Since the file system does not allow a file to be created larger than 2 GB, I am planning to use named pipes & AWK file to acheive my... (6 Replies)
Discussion started by: puru2121
6 Replies

9. HP-UX

2GB file size limit

Greetings, I'm attempting to dump a filesystem from a RHEL5 Linux server to a VXFS filesystem on an HP-UX server. The VXFS filesystem is large file enabled and I've confirmed that I can copy/scp a file >2GB to the filesystem. # fsadm -F vxfs /os_dumps largefiles # mkfs -F vxfs -m... (12 Replies)
Discussion started by: bkimura
12 Replies

10. Solaris

Clamd max file size Solaris 10

Hi, I've compiled a 64-bit version of ClamAV 0.98.7 on my Solaris 10 SPARC server. I have a selection of files all containing the eicar signature but clamd is only picking up the signature in the files <2GB. I have the following set in clamd.conf, to remove file size checking: MaxScanSize 0... (4 Replies)
Discussion started by: Troutfest
4 Replies
kdump-config(8) 					Linux System Administrator's Manual					   kdump-config(8)

NAME
kdump-config - configure kdump, check status, or save a vmcore file SYNOPSIS
kdump-config { help | test | show | status | load | unload | savecore } DESCRIPTION
kdump-config manages the kdump feature of the Linux kernel. When a kdump enabled kernel panics, it immediately boots into a clean kernel called the kdump kernel. The memory image of the panicked kernel will be presented in /proc/vmcore while the kdump kernel (or "capture kernel") is running. kdump-config loads the kdump kernel into the current kernel and after a kdump, captures the vmcore image via kdump kernel. kdump-config can take advantage of the linux-image-$(uname -r)-dbg package and will try to use makedumpfile to capture the vmcore. The crash tool can then be used to analyze the vmcore at a later time. kdump-config exits with 0 on success and 1 on failure. COMMANDS
help Print a usage summary. test Determine the parameters that would be used to load the kdump kernel, but do not load the kdump kernel. Useful for evaluating your configuration settings. show Show current parameters and the saved kexec command from the last kdump-config load. status Evaluate /sys/kernel/kexec_crash_loaded and print a corresponding message. load Load the kdump kernel. unload Unload the kdump kernel. savecore If /proc/vmcore exists, save it using makedumpfile. FILES
/etc/init.d/kdump-tools init script to automatically load a kdump kernel, or save a vmcore and reboot. /etc/default/kdump-tools configuration file /var/crash/kernel_link a link to the current debug kernel /var/crash/kexec_cmd the last kexec_cmd executed by kdump-config DIAGNOSTICS
USE_KDUMP is not set or zero The variable USE_KDUMP in the file /etc/default/kdump-tools is 0. To use kdump, edit the file and change the value to 1. kdump is not supported by this kernel The file /sys/kernel/kexec_crash_loaded does not exist. This means that the currently running kernel either was not configured to support kdump, or that a crashkernel= commandline parameter was not used when the currently running kernel booted. no crashkernel= parameter in the kernel cmdline a crashkernel= commandline parameter was not used when the currently running kernel booted. You will need to add a crashkernel= parameter to your /etc/lilo.conf, /etc/elilo.conf or grub /boot/grub/menu.lst file and reboot, before kdump will work. See installed READMEs for suggestions. could not find an installed debug vmlinux image and DEBUG_KERNEL is not specified in /etc/default/kdump-tools Warning: makedumpfile will be limited to -d 1. A debug version of the currently booted kernel could not be found. KDUMP_KERNEL does not exist: $KDUMP_KERNEL A KDUMP_KERNEL was specified in /etc/default/kdump-tools, but it cannot be found. KDUMP_INITRD does not exist: $KDUMP_INITRD A KDUMP_INITRD was specified in /etc/default/kdump-tools, but it cannot be found. no KDUMP_KERNEL in $KDUMP_DEFAULTS and can't find a kdump package directory in /usr/lib no kdump kernel could be found. found a linux-kdump package in $KDUMP_PKG_DIR but can't find a kdump kernel in $KDUMP_PKG_DIR this indicates a broken linux-kdump package installation. no kdump initrd image: $KDUMP_INITRD an initrd will not be used this indicates that although a kdump kernel was found, a corresponding initrd was not found. kdump kernel relocation address does not match crashkernel= parameter For non-relocatable architectures, the kdump kernel must be built with a predetermined start address. This message indicates that the start address of the kdump kernel and the start address in the crashkernel= parameter do not match. failed to load kdump kernel kexec reported that it could not load the kdump kernel. failed to unload kdump kernel kexec reported that it could not unload the kdump kernel. Run 'kexec -u' directly for more detail. makedumpfile failed, falling back to 'cp' this message is printed if the kdump-tools init script attempts to save a /proc/vmcore file using makedumpfile and the save fails. failed to save vmcore in $KDUMP_STAMPDIR this message indicates that makedumpfile and the fallback method of using cp has failed. This usually occurs if pathnames are wrong or if the disk is full. SEE ALSO
/usr/share/doc/kdump-tools/README /usr/share/doc/kdump-tools/README.Debian kdump-tools(5), kexec(8), crash(8), gdb(1), makedumpfile(8) AUTHOR
Terry Loftin <terry.loftin@hp.com> kdump-tools v1.1.3 April 2007 kdump-config(8)
All times are GMT -4. The time now is 08:03 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy