Sponsored Content
Special Forums Hardware Filesystems, Disks and Memory Compressed Filesystem for Linux Post 302820925 by DGPickett on Thursday 13th of June 2013 04:35:04 PM
Old 06-13-2013
Sending it over compressed can save time, too. Variations on zip allow the compression locally and the storage remote.
This User Gave Thanks to DGPickett For This Post:
 

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
Z(1)							      General Commands Manual							      Z(1)

NAME
comprez - safely (un)tar and (de)feather files and directories SYNOPSIS
comprez [ -t | -T ] [ -v | -V ] [ -l | -L ] [ -gz | -z | -I | -lz | -Z | -zip | -jar ] [ -# ] [ -s suffix ] [ -m mode ] [ -p | -P ] [ -h ] [ -- ] file ... DESCRIPTION
Comprez is a simple, safe and convenient front-end for the compress(1), uncompress(1), gzip(1), bzip2(1), lzip(1), tar(1), zip(1) and unzip(1) utilities for compressing and uncompressing files and directories. It processes each of its arguments according to the type of the file or directory given: If the argument is a plain file, then the file is compressed, ie, feathered. If the argument is a compressed file with a name ending in .Z, .gz, .z, .bz2, .lz, .zip or .jar, then the file is uncompressed, ie, defeathered. If the argument is a directory, then the directory is archived into one tar or zip file which is then compressed, ie, tarred and feathered. If the argument is a compressed tar or zip archive with a name ending in .{tar.,tar,ta,t}{Z,gz,z,bz2,lz} or .{zip,jar}, then the archive is uncompressed and untarred, ie, untarred and defeathered. The new compressed or uncompressed version will be in the same directory as the original. A compressed file is always uncompressed into a file with the same name sans the feather suffix. A compressed tar or zip archive is always unpacked into a subdirectory with the same name as the archive sans the tar and feather suffix, even if the archive did not itself contain such a subdirectory. OPTIONS
-- Interprets all following arguments as files instead of options. -# Where # is a digit from 1 through 9. This option is passed on to gzip(1), bzip2(1), lzip(1) and zip(1) when feathering with them. --fast may be used instead of -1 and --best instead of -9. -gz Uses gzip(1) and a .gz compression suffix when feathering. -h Prints a helpful usage message. -I Uses bzip2(1) and a .bz2 compression suffix when feathering. -l Lists the file or directory name created resulting from each argument. -L Does not report created files or directories. Default. -lz Uses lzip(1) and a .lz compression suffix when feathering. -m mode Apply the given chmod(1) mode argument to any created tar and feather files. Before this argument is applied, the files have the same read and write permissions as the directories from which they were created. For security, the default argument is go-rwx. If the mode is -, then no argument is applied. See chmod(1) for all other allowable formats of this argument. -p Preserves modes when untarring by giving the p flag to tar(1). Default. -P Doesn't preserve modes when untarring by not giving the p flag to tar(1). This option may be necessary on systems where ordinary users are allowed to run chown(2). -s suffix Creates tar and feather files using the given suffix style. The default suffix style is .tar.Z. Note that the suffix style does not dictate the program used for feathering nor the compression suffix. -t Only lists the table of contents of the given files. Does not make any changes. -T (Un)tars and (de)feathers the given files according to their type. Default. -v Verbose output. For example, reports compression ratios when feathering. -V Non-verbose output. Does not report compression ratios. Default. -q is a synonym. -z Uses gzip(1) and a .z compression suffix when feathering. -Z Uses compress(1) and a .Z compression suffix when feathering. Default. -zip, -jar Uses zip(1) and a .zip or .jar compression suffix when tarring and/or feathering. The zip format combines tarring and feather- ing. WARNING: zip does not preserve complete Unix filesystem information for the files it archives, such as links, some permis- sions, etc. A tar(1)-based format should be used if this is required. ENVIRONMENT VARIABLES
ZOPTS This variable may be set to a string of the above options to supersede the default settings. They may still be overridden by options given on the command line. GZIP This environment variable for gzip(1) is not passed on by comprez so that gzip's behavior is standard and predictable. ZIPOPT, UNZIP These environment variables for zip(1) and unzip(1) are not passed on by comprez so that their behavior is standard and pre- dictable. BUGS
There should be an option to allow the use of another directory for temporary files needed during the (un)tarring and (de)feathering pro- cesses. This would make comprez more useful when the quota or disk is nearly full. There should be -k and -K options for keeping the original input files or not. CAVEATS
Comprez is written to work with gzip versions 1.2.3 and 1.2.4, bzip2 versions 0.9.0 and 1.0.0, Unix zip version 2.0.1 and Unix unzip ver- sion 5.12. Other versions will probably work safely, too, but should still be checked for compatibility. Every effort has been made to assure that the use of this program will not lead to the inappropriate deletion or corruption of any files. However, there are never any guarantees, so please use at your own risk. VERSION
2.6.1 AUTHOR
Steve Kinzler, kinzler@cs.indiana.edu, May 89/Jun 93/Aug 99/Dec 00 URL
http://www.cs.indiana.edu/~kinzler/z SEE ALSO
compress(1), uncompress(1), gzip(1), bzip2(1), lzip(1), tar(1), zip(1), unzip(1) 2.6.1 Z(1)
All times are GMT -4. The time now is 09:39 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy