Sponsored Content
Operating Systems AIX LTO5 Catridge 1.5 TB Natvie capactiy unable to hold 1.44TB data in one volume Post 302814131 by bakunin on Tuesday 28th of May 2013 06:43:15 PM
Old 05-28-2013
Quote:
Originally Posted by m_raheelahmed
But let me inform you our uncompressed total data size is 1350 GB & when we compress the the data files it will become around 200 GB. So with the the help of compress we are able to hold 5-6 days data in a 1400 GB filesystem which will be backed up on cartridge once in a week. It is also save our storage space for not holding uncompressed data which is huge in size.
Some things to clarify: you can compress a file only once. If you use the utility "compress" (or "gzip", "bzip2" or any other packing program), you have compressed it once, using some CPU time to do so. If you want to restore it you will need CPU time too to uncompress it.

If you use the hardware compression, on the other hand, you will still compress it (and about the same ratio as with "compress"), but use no CPU time to do so. The same, when you restore it.

The size data for the LTO5 tape are pure estimations. OK, 1500GB of uncompressed size is a fact, but "3000GB compressed" simply means: we estimate that our average packing rate will be 1:2, regardless of what is thrown in the drives way, so we say it has 1500 x 2 = 3000GB of compressed capacity. In reality the compression ratio one really achieves varies widely, depending on what a file contains. Picture data like bitmaps usually can easily be compressed by a factor of 1:10, the same with DB-files, while executable files give considerably lower ratios, typically ~1:2 with a LZ78-based algorithm.

That means: if you use solely hardware compression will put you in about the same situation as now or as using software compression (the "compress" utility) alone. Everything else is just a waste of resources, because in your current situation the software compression does all the work and the hardware compression achieves most likely absolutely nothing.

I hope this helps.

bakunin
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Playing with Volume of data

Quick problem statement: How to read/extract data from a big-big file. Details: We are having a big big problemo in the work we are working at. We are using solaris plarform E25. There is a very big file created somewhere around 200 million records anad the lenght of each record is more than... (3 Replies)
Discussion started by: darshanw
3 Replies

2. HP-UX

Unable To Extend the Size of a Logical Volume File System

Background: # uname -a HP-UX deedee B.11.23 U ia64 4294967295 unlimited-user license deedee.rsn.hp.com:/ # bdf /opt Filesystem kbytes used avail %used Mounted on /dev/vg00/lvol6 6553600 6394216 158144 98% /opt /opt is almost full... (3 Replies)
Discussion started by: Rob Sandifer
3 Replies

3. UNIX for Dummies Questions & Answers

Unable to deactivate a Volume Group

We want to deactivate a VG but failed, because one of the LVs created there is busy. When we are trying to unmount the LV, it is telling "not mounted" and if I execute mount command it will be informing us "already mounted". dmsetup info is indicating "Open Count = 1". Please help me, how we... (5 Replies)
Discussion started by: atanubanerji
5 Replies

4. UNIX for Dummies Questions & Answers

Unable to reduce the size of volume group?

My volume group of size 200 gb. out of which only 100 gb is used by 2 logical volumes /dev/vg00/lvol0 and /dev/vg00/lvol0 respectively (both are 50 gb each). Whenever i use vgreduce command to reduce the size of volume group i get below error. # vgreduce vg00 -a Physical volume... (16 Replies)
Discussion started by: pinga123
16 Replies

5. UNIX for Dummies Questions & Answers

Confusion Regarding Physical Volume,Volume Group,Logical Volume,Physical partition

Hi, I am new to unix. I am working on Red Hat Linux and side by side on AIX also. After reading the concepts of Storage, I am now really confused regarding the terminologies 1)Physical Volume 2)Volume Group 3)Logical Volume 4)Physical Partition Please help me to understand these concepts. (6 Replies)
Discussion started by: kashifsd17
6 Replies

6. Solaris

[SOLVED] How to initialize LTO5 Tape Drive?

Hi, We replaced one of our tape drives (attached to a SPARC Server) with an LTO5 one (external, attached vi SAS). Manually we check (using tar) that the OS can write data to the Tape Drive, however, the application backup is failing. Since the application takes its own backup, the apps team... (0 Replies)
Discussion started by: Mack1982
0 Replies

7. AIX

Slow listing of LTo5 tape contents

Hi, We are taking our filesystem backup having size of 1.3 TB on LTO5 catridges using the following command find * -print|backup -ivf '/dev/rmt0' '-U' i.e backup byname and it took about 6.5 Hours to complete When we are listing same tape contents using the following command restore... (1 Reply)
Discussion started by: m_raheelahmed
1 Replies

8. AIX

Unable to extend volume group(VG)

Would some help me on this below I am trying to extend file system on AIX and however unable to extend the file system. 0516-306 extendvg: Unable to find physical volume 20 in the Device Configuration Database. 0516-321 extendvg: Physical volume u01-lv is not configured. 0516-792... (15 Replies)
Discussion started by: murali969
15 Replies

9. AIX

/usr/sbin/extendvg: Unable to extend volume group

Dear Expret, Help me about my issue, I trying add new disk to volume Group but error: step add new disk to volume group. 1. ~Change a Volume Group Add a Physical Volume to a Volume Group Remove a Physical Volume from a Volume Group Reorganize a Volume Group... (6 Replies)
Discussion started by: williamen
6 Replies

10. Shell Programming and Scripting

Output large volume of data to CSV file

I have a program that output the ownership and permission on each directory and file on the server to a csv file. I am getting error message when I run the program. The program is not outputting to the csv file. Error: the file access permissions do not allow the specified action cannot... (2 Replies)
Discussion started by: dellanicholson
2 Replies
compress(1)							   User Commands						       compress(1)

NAME
compress, uncompress, zcat - compress, uncompress files or display expanded files SYNOPSIS
compress [-fv] [-b bits] [file...] compress [-cfv] [-b bits] [file] uncompress [-cfv] [file...] zcat [file...] DESCRIPTION
compress The compress utility will attempt to reduce the size of the named files by using adaptive Lempel-Ziv coding. Except when the output is to the standard output, each file will be replaced by one with the extension .Z, while keeping the same ownership modes, change times and mod- ification times. If appending the .Z to the file pathname would make the pathname exceed 1023 bytes, the command will fail. If no files are specified, the standard input will be compressed to the standard output. The amount of compression obtained depends on the size of the input, the number of bits per code, and the distribution of common sub- strings. Typically, text such as source code or English is reduced by 50-60%. Compression is generally much better than that achieved by Huffman coding (as used in pack(1)) and it takes less time to compute. The bits parameter specified during compression is encoded within the compressed file, along with a magic number to ensure that neither decompression of random data nor recompression of compressed data is subsequently allowed. uncompress The uncompress utility will restore files to their original state after they have been compressed using the compress utility. If no files are specified, the standard input will be uncompressed to the standard output. This utility supports the uncompressing of any files produced by compress. For files produced by compress on other systems, uncompress sup- ports 9- to 16-bit compression (see -b). zcat The zcat utility will write to standard output the uncompressed form of files that have been compressed using compress. It is the equiva- lent of uncompress -c. Input files are not affected. OPTIONS
The following options are supported: -c Writes to the standard output; no files are changed and no .Z files are created. The behavior of zcat is identical to that of `uncompress -c'. -f When compressing, forces compression of file, even if it does not actually reduce the size of the file, or if the corresponding file.Z file already exists. If the -f option is not given, and the process is not running in the background, prompts to verify whether an existing file.Z file should be overwritten. When uncompressing, does not prompt for overwriting files. If the -f option is not given, and the process is not running in the background, prompts to verify whether an existing file should be over- written. If the standard input is not a terminal and -f is not given, writes a diagnostic message to standard error and exits with a status greater than 0. -v Verbose. Writes to standard error messages concerning the percentage reduction or expansion of each file. -b bits Sets the upper limit (in bits) for common substring codes. bits must be between 9 and 16 (16 is the default). Lowering the number of bits will result in larger, less compressed files. OPERANDS
The following operand is supported: file A path name of a file to be compressed by compress, uncompressed by uncompress, or whose uncompressed form is written to standard out by zcat. If file is -, or if no file is specified, the standard input will be used. USAGE
See largefile(5) for the description of the behavior of compress, uncompress, and zcat when encountering files greater than or equal to 2 Gbyte ( 2**31 bytes). ENVIRONMENT VARIABLES
See environ(5) for descriptions of the following environment variables that affect the execution of compress, uncompress, and zcat: LANG, LC_ALL, LC_CTYPE, LC_MESSAGES, and NLSPATH. EXIT STATUS
The following error values are returned: 0 Successful completion. 1 An error occurred. 2 One or more files were not compressed because they would have increased in size (and the -f option was not specified). >2 An error occurred. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWesu | +-----------------------------+-----------------------------+ |CSI |Enabled | +-----------------------------+-----------------------------+ |Interface Stability |Standard | +-----------------------------+-----------------------------+ SEE ALSO
ln(1), pack(1), attributes(5), environ(5), largefile(5), standards(5) DIAGNOSTICS
Usage: compress [-fvc] [-b maxbits] [file... ] Invalid options were specified on the command line. Missing maxbits Maxbits must follow -b, or invalid maxbits, not a numeric value. file: not in compressed format The file specified to uncompress has not been compressed. file: compressed with xxbits, can only handle yybits file was compressed by a program that could deal with more bits than the compress code on this machine. Recompress the file with smaller bits. file: already has .Z suffix -- no change The file is assumed to be already compressed. Rename the file and try again. file: already exists; do you wish to overwrite (y or n)? Respond y if you want the output file to be replaced; n if not. uncompress: corrupt input A SIGSEGV violation was detected, which usually means that the input file is corrupted. Compression: xx.xx% Percentage of the input saved by compression. (Relevant only for -v.) - - not a regular file: unchanged When the input file is not a regular file, (such as a directory), it is left unaltered. - - has xx other links: unchanged The input file has links; it is left unchanged. See ln(1) for more information. - - file unchanged No savings are achieved by compression. The input remains uncompressed. filename too long to tack on .Z The path name is too long to append the .Z suffix. NOTES
Although compressed files are compatible between machines with large memory, -b 12 should be used for file transfer to architectures with a small process data space (64KB or less). compress should be more flexible about the existence of the .Z suffix. SunOS 5.10 9 Sep 1999 compress(1)
All times are GMT -4. The time now is 05:36 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy