Sponsored Content
Full Discussion: doubt regarding bzip2
Operating Systems Solaris doubt regarding bzip2 Post 302340038 by rogerben on Sunday 2nd of August 2009 04:15:11 AM
Old 08-02-2009
doubt regarding bzip2


I tried to upload the crash dump files unix.0 and vmcore.0 ..bzip2 is working fine for unix.0 but for vmcore.0 its not working and it shows the below error. Is there any size limit or file type for bzip2. current vmcore.0 file size -- 2326372352 kb

# file vmcore.0
vmcore.0: SunOS 5.8 Generic_117350-47 64-bit crash dump from 'tktpfclu1'

"bzip2: Input file vmcore.0 doesn't exist, skipping."

3 More Discussions You Might Find Interesting

1. AIX

bzip2 on AIX 5.3

Hi. I have the bzip2 version 1.0.2 installed on AIX 5.3 (RPM package). The documentation (www.bzip.org) says that this version can compress files >2Gb, but is not working. On AIX, bzip2 is working well just for files less than 2Gb. I have the bzip2 (same version) installed on Linux box. The... (0 Replies)
Discussion started by: Livio
0 Replies

2. UNIX for Dummies Questions & Answers


I have a DVD that has a 2gigabit bzip2 file. How do I unzip it. Please excuse my ignorance I am to old and stupid to be trying this. Help would sure be appreciated. Love, jerryandjerry could you email me at jerrylowery2@msn.com (1 Reply)
Discussion started by: jerryandjerry
1 Replies

3. Shell Programming and Scripting

zip files using bzip2

Hi all, Say I've got a file /tmp/tempfile.txt which contains a list of files with full path. Now I would wish to take all filenames in that tempfile as arguments and zip them in a single archived file. So how could I archive this? Seems like I need to use the xargs command? Thanks (5 Replies)
Discussion started by: isaacniu
5 Replies
savecore(1M)						  System Administration Commands					      savecore(1M)

savecore - save a crash dump of the operating system SYNOPSIS
/usr/bin/savecore [-Lvd] [-f dumpfile] [directory] DESCRIPTION
The savecore utility saves a crash dump of the kernel (assuming that one was made) and writes a reboot message in the shutdown log. It is invoked by the dumpadm service each time the system boots. savecore saves the crash dump data in the file directory/vmcore.n and the kernel's namelist in directory/unix.n. The trailing .n in the pathnames is replaced by a number which grows every time savecore is run in that directory. Before writing out a crash dump, savecore reads a number from the file directory/minfree. This is the minimum number of kilobytes that must remain free on the file system containing directory. If after saving the crash dump the file system containing directory would have less free space the number of kilobytes specified in minfree, the crash dump is not saved. if the minfree file does not exist, savecore assumes a minfree value of 1 megabyte. The savecore utility also logs a reboot message using facility LOG_AUTH (see syslog(3C)). If the system crashed as a result of a panic, savecore logs the panic string too. OPTIONS
The following options are supported: -d Disregard dump header valid flag. Force savecore to attempt to save a crash dump even if the header information stored on the dump device indicates the dump has already been saved. -f dumpfile Attempt to save a crash dump from the specified file instead of from the system's current dump device. This option may be useful if the information stored on the dump device has been copied to an on-disk file by means of the dd(1M) command. -L Save a crash dump of the live running Solaris system, without actually rebooting or altering the system in any way. This option forces savecore to save a live snapshot of the system to the dump device, and then immediately to retrieve the data and to write it out to a new set of crash dump files in the specified directory. Live system crash dumps can only be per- formed if you have configured your system to have a dedicated dump device using dumpadm(1M). savecore -L does not suspend the system, so the contents of memory continue to change while the dump is saved. This means that live crash dumps are not fully self-consistent. -v Verbose. Enables verbose error messages from savecore. OPERANDS
The following operands are supported: directory Save the crash dump files to the specified directory. If directory is not specified, savecore saves the crash dump files to the default savecore directory, configured by dumpadm(1M). FILES
directory/vmcore.n directory/unix.n directory/bounds directory/minfree /var/crash/'uname -n' default crash dump directory ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ SEE ALSO
adb(1), mdb(1), svcs(1), dd(1M), dumpadm(1M), svcadm(1M), syslog(3C), attributes(5), smf(5) NOTES
The system crash dump service is managed by the service management facility, smf(5), under the service identifier: svc:/system/dumpadm:default Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M). The ser- vice's status can be queried using the svcs(1) command. If the dump device is also being used as a swap device, you must run savecore very soon after booting, before the swap space containing the crash dump is overwritten by programs currently running. SunOS 5.10 25 Sep 2004 savecore(1M)

Featured Tech Videos

All times are GMT -4. The time now is 09:54 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy