Sponsored Content
Special Forums Hardware Filesystems, Disks and Memory Faster way: SAN hd to SAN hd copying Post 303007689 by Corona688 on Monday 20th of November 2017 10:30:52 AM
Old 11-20-2017
There's nothing particularly slow about tar, either.

In the end it's 15 tb of data, transferring it will take time.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

what is SAN

Hello all, I have looked at the entire posting that have SAN in it and I'm still fuzzy on how SAN works. I understand that every disk array can be access from any server that needs it, but is there software that is install or NFS mount type situation. One post stated that if your format command... (7 Replies)
Discussion started by: larry
7 Replies

2. AIX

San:

hi We have 2 AIX nodes running with HACMP and all of them connected to SAN, Our shared storage is shark; I need to create shared volume group and I need the HACMP take a ware of it. Regards (1 Reply)
Discussion started by: h2aix
1 Replies

3. HP-UX

SAN migration

Hi, I'm going to be involved in a migration of SAN islands to one big SAN. I've not worked with SANs before and I'm not sure how to approach this. I suspect the disk devices on the HP servers are going to change, when the EVA's and servers are plugged into this new Cisco 9509 switch. Any... (0 Replies)
Discussion started by: Hils
0 Replies

4. Solaris

Connecting to SAN

I am about to attempt to connect my sun 280R boxes to a EMC SAN. I have Qlogic cards that came from Sun. I am going to load traffic manager, navisphere client. what else do i need, sun foundation suite ro somehting? This is the first time ive ever connected to a SAN. any help would be... (3 Replies)
Discussion started by: BG_JrAdmin
3 Replies

5. Solaris

Thoughts/experiences of SAN attaching V880 to EMC SAN

Hi everyone, I wonder if I can canvas any opinions or thoughts (good or bad) on SAN attaching a SUN V880/490 to an EMC Clarion SAN? At the moment the 880 is using 12 internal FC-AL disks as a db server and seems to be doing a pretty good job. It is not I/O, CPU or Memory constrained and the... (2 Replies)
Discussion started by: si_linux
2 Replies

6. AIX

SAN error

Dera all I have error repeating for two day, when I checked the error log by errpt command: ------------------------------------------------------------------------ LABEL: SC_DISK_ERR2 IDENTIFIER: 79B0DF89 Date/Time: Wed Oct 31 02:41:36 SAUS Sequence Number: 9000... (1 Reply)
Discussion started by: magasem
1 Replies

7. Linux

Linux on SAN

Hello everyone. I was wondering if there is a way to increase the size on the LUN on a SAN and make the Linux kernel understand the changes without restarting? In the past it has always been rebooted to see the new values but im sure that there is a way now for the lvm to see the Free PE in... (8 Replies)
Discussion started by: d_ark
8 Replies

8. UNIX for Dummies Questions & Answers

Storage from SAN

hi guys I installed Centos 5.5 (local disk). I am using 2 HBAs Now I mapped 5 LUNs from a Storage. I will be using LVM just to test I assigned a LUN I've read I have to use multipath to avoid my Centos see the LUN twice I enabled mdmpd and multipathd... something else I should do? ... (8 Replies)
Discussion started by: kopper
8 Replies

9. AIX

New to San Storage

Can anyone recommend a good book on san storage basics and how it communicates with an AIX server? (1 Reply)
Discussion started by: NycUnxer
1 Replies

10. AIX

IBM SAN TO SAN Mirroring

Has anyone tried SAN to SAN mirroring on IBM DS SAN Storage. DS5020 mentions Enhanced Remote Mirror to multi-LUN applications I wonder if Oracle High availibility can be setup using Remote Mirror option of SAN ? (1 Reply)
Discussion started by: filosophizer
1 Replies
deb(5)								      Debian								    deb(5)

NAME
deb - Debian binary package format SYNOPSIS
filename.deb DESCRIPTION
The .deb format is the Debian binary package file format. It is understood by dpkg 0.93.76 and later, and is generated by default by all versions of dpkg since 1.2.0 and all i386/ELF versions since 1.1.1elf. The format described here is used since Debian 0.93; details of the old format are described in deb-old(5). FORMAT
The file is an ar archive with a magic value of !<arch>. The file names might contain a trailing slash. The tar archives currently allowed are, the old-style (v7) format, the pre-POSIX ustar format, a subset of the GNU format (only the new style long pathnames and long linknames, supported since dpkg 1.4.1.17), and the POSIX ustar format (long names supported since dpkg 1.15.0). Unrecognized tar typeflags are considered an error. The first member is named debian-binary and contains a series of lines, separated by newlines. Currently only one line is present, the for- mat version number, 2.0 at the time this manual page was written. Programs which read new-format archives should be prepared for the minor number to be increased and new lines to be present, and should ignore these if this is the case. If the major number has changed, an incompatible change has been made and the program should stop. If it has not, then the program should be able to safely continue, unless it encounters an unexpected member in the archive (except at the end), as described below. The second required member is named control.tar.gz. It is a gzipped tar archive containing the package control information, as a series of plain files, of which the file control is mandatory and contains the core control information. The control tarball may optionally contain an entry for `.', the current directory. The third, last required member is named data.tar. It contains the filesystem as a tar archive, either not compressed (supported since dpkg 1.10.24), or compressed with gzip (with .gz extension), xz (with .xz extension, supported since dpkg 1.15.6), bzip2 (with .bz2 exten- sion, supported since dpkg 1.10.24) or lzma (with .lzma extension, supported since dpkg 1.13.25). These members must occur in this exact order. Current implementations should ignore any additional members after data.tar. Further members may be defined in the future, and (if possible) will be placed after these three. Any additional members that may need to be inserted before data.tar and which should be safely ignored by older programs, will have names starting with an underscore, `_'. Those new members which won't be able to be safely ignored will be inserted before data.tar with names starting with something other than underscores, or will (more likely) cause the major version number to be increased. SEE ALSO
deb-old(5), dpkg-deb(1), deb-control(5). Debian Project 2009-02-27 deb(5)
All times are GMT -4. The time now is 05:45 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy