Sponsored Content
Operating Systems Linux Red Hat RHEL 5.6 Slow rsync to NFS array Post 302501876 by lori_lin on Saturday 5th of March 2011 09:52:01 AM
Old 03-05-2011
why use the parameter -z ?
It will do compress by -z ,and its the reason for what u want .
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

ls -l over NFS slow

I have an HP-UX server with a Network Appliance Filer attached over Gigabit Ethernet. I am noticing very slow response time when using "ls -l" on one directory on one of the several NFS mounted filesystems. The "ls" command by itself does not seem to be a problem. Typically I get a response within... (3 Replies)
Discussion started by: keelba
3 Replies

2. UNIX for Dummies Questions & Answers

Remote server mount slow - NFS

Hi, Following my last post I've mounted the remote server on my local server. However copying files from this mounted server is increadbily slow. If I copy files using rcp it's very fast so I assume there must be a setting somewhere? Any help appreicated. Thanks (2 Replies)
Discussion started by: AngryBunny
2 Replies

3. Red Hat

NFS writing so slow

Hi, I facing an NFS problem. I have machine1, which has diskA and diskB, and machine2, both are Mandriva 2009 Linux. When I am on machine2 and NFS mount both diskA and diskB of machine1. Writing to diskA is very fast, but writing to diskB is very slow. I tried different mount rsize and wsize... (2 Replies)
Discussion started by: hiepng
2 Replies

4. Red Hat

file writing over nfs very slow

Hi guys, I am trying something. I wrote a simple shell program to test something where continuous while loop writes on a file over the nfs. The time taken to write "hello" 3000 times take about 10 sec which is not right. Ideally it should take fraction of seconds. If I write on the local disk, it... (1 Reply)
Discussion started by: abhig
1 Replies

5. Red Hat

cannot ssh (use NFS) on RHEL box, but can mount external & ssh out of RHEL box

Ok, Im trying to get NFS working on my RHEL 5 box, apparently i can use the box as a client, but not as a server. If it helps i cant ssh into the box (server), but as a client ssh works fine. Ive configured server: /etc/hosts.allow: all : all all :all@all setup my /etc/exports file... (4 Replies)
Discussion started by: drs.grid
4 Replies

6. AIX

Slow NFS when cio/dio enabled

Hi, I have a bit of a NFS problem on AiX 6.1 : When I set the mount to cio and dio - needed for a database app - Everything slows down. The following is copying 700mb, top one is a normal mount bottom one is a mount with the cio/dio option enabled : # ./a.sh Wed Jan 11 11:41:24 GMT 2012... (5 Replies)
Discussion started by: AJCG1976
5 Replies

7. UNIX for Dummies Questions & Answers

Rsync Can I delete .NFS and .fuse files

Hello, I have some files in a local directory and perform an rsync command with the files in a remote directory, Now when I checked the files in the local and the remote directory, I found some strange filetypes such as this: .nfs0000000001d0c8e000002ff2 , .fuse_hidden000014da00000001 etc etc,... (3 Replies)
Discussion started by: ajayram
3 Replies

8. Red Hat

RHEL 7.1 autofs permissions do not match NFS servers

RHEL 7.1 client using autofs to mount a NIS map of home directories being exported by a Solaris 10x86 nfs server. The owner and group are correct on the NFS server, but on the RHEL client, the owner and group end up being nobody nobody. The USERS and GROUPS are NIS maps as well. They are... (2 Replies)
Discussion started by: mrmurdock
2 Replies

9. Solaris

RHEL NFS share on Solaris 11.3 vers=4

NFS server: RHEL:6 /nfsdb 192.168.8.10/28(rw,sync,no_root_squash) 192.168.7.10/28(rw,sync,no_root_squash) Client: Solaris 11.3 vfstab entry : 192.168.8.9:/nfsdbarch - /archive_data nfs - yes rw,soft,vers=4 # ls -ld /archive_data drwxr-xr-x 4 root root... (3 Replies)
Discussion started by: Shirishlnx
3 Replies

10. Solaris

Rsync quite slow (using very little cpu): how to improve its speed?

I have "inherited" a OmniOS (illumos based) server. I noticed rsync is significantly slower in respect to my reference, FreeBSD 12-CURRENT, running on exactly same hardware. Using same hardware, same command with same source and target disks, OmniOS r151026 gives: test@omniosce:~# time... (11 Replies)
Discussion started by: priyadarshan
11 Replies
COMPRESS(1)						    BSD General Commands Manual 					       COMPRESS(1)

NAME
compress, uncompress -- compress and expand data SYNOPSIS
compress [-cdfv] [-b bits] [file ...] uncompress [-cdfv] [file ...] DESCRIPTION
compress reduces the size of the named files using adaptive Lempel-Ziv coding. Each file is renamed to the same name plus the extension ``.Z''. As many of the modification time, access time, file flags, file mode, user ID, and group ID as allowed by permissions are retained in the new file. If compression would not reduce the size of a file, the file is ignored. uncompress restores the compressed files to their original form, renaming the files by deleting the ``.Z'' extension. If renaming the files would cause files to be overwritten and the standard input device is a terminal, the user is prompted (on the standard error output) for confirmation. If prompting is not possible or confirmation is not received, the files are not overwritten. If no files are specified, the standard input is compressed or uncompressed to the standard output. If either the input and output files are not regular files, the checks for reduction in size and file overwriting are not performed, the input file is not removed, and the attributes of the input file are not retained. The options are as follows: -b Specify the bits code limit (see below). -c Compressed or uncompressed output is written to the standard output. No files are modified. -d Force decompression. -f Force compression of file, even if it is not actually reduced in size. Additionally, files are overwritten without prompting for confirmation. -v Print the percentage reduction of each file. compress uses a modified Lempel-Ziv algorithm. Common substrings in the file are first replaced by 9-bit codes 257 and up. When code 512 is reached, the algorithm switches to 10-bit codes and continues to use more bits until the limit specified by the -b flag is reached (the default is 16). Bits must be between 9 and 16. After the bits limit is reached, compress periodically checks the compression ratio. If it is increasing, compress continues to use the existing code dictionary. However, if the compression ratio decreases, compress discards the table of substrings and rebuilds it from scratch. This allows the algorithm to adapt to the next "block" of the file. The -b flag is omitted for uncompress since the bits parameter specified during compression is encoded within the output, along with a magic number to ensure that neither decompression of random data nor recompression of compressed data is attempted. The amount of compression obtained depends on the size of the input, the number of bits per code, and the distribution of common substrings. Typically, text such as source code or English is reduced by 50-60%. Compression is generally much better than that achieved by Huffman cod- ing (as used in the historical command pack), or adaptive Huffman coding (as used in the historical command compact), and takes less time to compute. The compress utility exits 0 on success, and >0 if an error occurs. SEE ALSO
zcat(1) Welch, Terry A., "A Technique for High Performance Data Compression", IEEE Computer, 17:6, pp. 8-19, June, 1984. HISTORY
The compress command appeared in 4.3BSD. BSD
January 23, 2003 BSD
All times are GMT -4. The time now is 11:50 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy