Sponsored Content
Special Forums Hardware Filesystems, Disks and Memory Compressed Filesystem for Linux Post 302820887 by DGPickett on Thursday 13th of June 2013 03:10:13 PM
Old 06-13-2013
I wonder if you can achieve compressed backup with some sort of hybrid mirror, where files on one side are compressed once quiescent, and on the other side, are left uncompressed. Compression would occur in the background, not at write time.
 

10 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

Filesystem for Linux - Solaris

Do you know how I can find detailed information on filesystems on Linux and Solaris. And I mean not only for the OS but and how it(the OS) uses the hard drives! Thank you in advance!! Solid Snake;) ;) (3 Replies)
Discussion started by: SolidSnake
3 Replies

2. Linux

Linux filesystem

Hi all, Suppose i have a disk having three partitions (hda1,hda2,hda3) ,and are mounted all under /dev/ .. My question is where the / will be existing.which file system it wil be in? I am windows user new to linux/unix.Any help in learning internals would be appreciated . Thanks ,... (1 Reply)
Discussion started by: gkrishn
1 Replies

3. Tips and Tutorials

Linux Filesystem Hierarchy

Hi, Please have a look this: http://tldp.org/LDP/Linux-Filesystem-Hierarchy/Linux-Filesystem-Hierarchy.pdf I think this can be very useful for a beginner/intermediate level user to understand the filesystem hierarchy and as well as it can be used as a reference to various linux commands and... (0 Replies)
Discussion started by: tayyabq8
0 Replies

4. Programming

Uncompress on linux a UDP Payload compressed on win$ using closed source library

I am trying to uncompress a UDP packets payload. The data was compressed using "Xceed Version 4.3" which is a closed source windows program. I need to uncompress the data on a linux box. The technical support people at Xceed tell me that the data was compressed using "the Deflate compression method... (0 Replies)
Discussion started by: sysadmin9
0 Replies

5. UNIX for Advanced & Expert Users

Linux FileSystem Internal Buffer size:

I know that Univ FileSystem stores all file data in the form of first few direct nodes followed by indirect nodes. But internally some systems implement where , a single block of 4096 isnt allocated alone a single block basis on physical drive, rather a large chunk of data is allocated and no. of... (1 Reply)
Discussion started by: GloriousDaisy
1 Replies

6. UNIX for Dummies Questions & Answers

How can I check if I have raw filesystem on unix/linux

Hello again. Please can someone tell me how can i check if my filesystem is raw on unix/linux ? Is there some file to check or something like that to be sure ? also , when i do : $ ls -l /dev/rdisk i get among other things , this also(there resides are oracle related files) : ... (2 Replies)
Discussion started by: tonijel
2 Replies

7. SuSE

filesystem from unix 32 to linux 64

Hi all. Im migrating from a Unix 32 bit to a linux suse 10 64 bit and would like to know whats the best way to migrate the filesystems? cpio? tar? ftp? Could I make a backup in tape in the unix 32 and restore it in the linux 64? thanx (1 Reply)
Discussion started by: mrodrig
1 Replies

8. Linux

filesystem locking issue on linux

hi, we are getting filesystem locking issue very frequently. we are using linux rhel 5.5. our filesystem type is gfs2 where we are facing locking issue and unix admin team reboots server to over come with this issue. suddenly we used to face slowness on server and server gets hung. after that... (1 Reply)
Discussion started by: anshu ranjan
1 Replies

9. Linux

Partition of linux filesystem wit meaning

Cud some one pls help me wit some partitions of linux filesystem wit their meaning....urgent cos is an assignment (5 Replies)
Discussion started by: GODBLESSME
5 Replies

10. Shell Programming and Scripting

Is there any way to find the compressed size of a file without compressing it in linux

i need to backup a directory from one partition to another and and compress that directory after backing up, so i need to predict the compressed size of the directory with out actually compressing it, to check whether the space is available in the destination partition to accommodate the zipped... (2 Replies)
Discussion started by: Kesavan
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 09:51 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy