HP3000-L Archives

September 2005, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"James B. Byrne" <[log in to unmask]>
Reply To:
James B. Byrne
Date:
Tue, 13 Sep 2005 11:34:27 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (64 lines)
On 13 Sep 2005 at 15:36, Tony Summers wrote:

> We must avoid getting confused between the emulation of the MPE file
> system supported by various 3rd party vendors (MPUX and AMXW ) which
> implement MPE type files as byte-stream files with little bits
> attached.

This is the extract from the MPEiX tar man page to which I refer:


 MPE/iX NOTES
     The current MPE/iX implementation of tar has the following
     limitations:

     * By default, the -c and -x options store and restore,
     respectively, only the following MPE attributes:

           MPE.RECORDSIZE
           MPE.FILECODE
           MPE.FILELIMIT
           MPE.NUMEXTENTS
           MPE.NUMUSERLABELS
           MPE.BLOCKFACTOR
           MPE.RECORDFORMAT
           MPE.CCTL
           MPE.ASCII

     All other MPE attributes are ignored.  The -A option toggles this
     behaviour. For example, when you use -cA to create an archive, MPE
     attributes are not stored.

"tar -cf /BACKUPS/TRANSFER/STDXFTP.tar /BACKUPS/SYSTEM/STD*" seems
to me sufficient to create a tar file from the STORE STD multi-reel
set suitable for storing on a Linux repository and capable of
recovery of the native MPE file characteristics when returned to an
MPEiX system assuming binary transfers in both directions.  I
intend to do tests on these assumptions of course but does anyone
here already possess contra experience with doing this?

I seem nonetheless to have overlooked a major defect in my
assumptions.  The original problem is created by the STORE
limitation requiring creation multiple disc "reels" for store to
disc sets containing more than 4 Gb of data. The issue thus becomes
one of assembling these multiple files into a package for ease of
automated transmission and reliability of recovery. The question
is: How big can a tar disc archives get on MPEiX 7.0/7.5?  Can
anyone here answer this?  The man page is silent on the issue as
far as I can see.

Regards,
Jim


--
     *** e-mail is not a secure channel ***
mailto:byrnejb.<token>@harte-lyne.ca
James B. Byrne                Harte & Lyne Limited
vox: +1 905 561 1241          9 Brockley Drive
fax: +1 905 561 0757          Hamilton, Ontario
<token> = hal                 Canada L8E 3C3

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2