[daip] aips data, linux, ext2 => ext3

[joe cammisa]

greetings (eric, wes, et al).

we have an urgent need to upgrade our linux system from redhat 7.0 to
redhat 8.0; the only thing that is holding me back at this point is that
i am unsure of the safest/easiest way to migrate the aips data from an
ext2 filesystem to an ext3 one.  (unfortunately, i need to reconfigure
the raid array and thus can't keep around any disk partitions after the
fact; also unfortunately, i have been thus far unsuccessful in reading
an ext2 file system dump onto an ext3 filesystem).

ages ago, eric was kind enough to show me a means of moving data between
solaris and linux; this process involved creating a procedure within
aips, (run under each user number) that used the FITTP task to write the
user's data to disk (using the OUTFILE option).  in that instance, the
outfile was an nfs-mounted partition on the new system, from which a
parrallel procedure could be invoked that called FITLD on the files so
generated.  [see attached if my explanation is too garbled...]

my question is this:  could i not use a smiliar strategy to migrate my
existing data?  the only difference would be that rather than doing this
over nfs, i would write it to a local disk, archive it to tape, restore
from tape once the system is rebuilt, and *then* run the FITLD
procedure.  does this make sense?  does it sound feasible?  can you
think of a better way?

any insight you can offer would be hugely appreciated.  thanks in
advance for your time...

-joe


> joe cammisa writes:
>  > eric-
>  >     thanks for your prompt attention.  the old system is solaris, and the new
>  > is linux.  so, i guess fits is my only answer, although i'm encouraged to read
>  > that disk rather than tape can be used (i was having frightening visions of
>  > spending months changing tapes...)  can you please explain further?  thanks
>  > again...
>
> Task FITTP and FITAB offer the option of OUTFILE which would be a disk
> file, usually in the $FITS area.  This disk could be cross mounted on
> the 2 systems.  You need to make a unique name for each file.  A proc
> such as
>
>    proc tapeout(x,y)
> $ do a range of catalog numbers
>    dowait true
>    j = x-1;
>    for i=x:y
>       egetname(i)
>       if (^error) then
>          j = j + 1
>          outfile = char(indisk) !! '-' !! char(j)
>          go fittp
>          end
>       end
>    finish
>
> At the other end even easier
>
>    proc tapeout(x,y,j)
> $ do a range of old catalog numbers x-y, old disk j
>    dowait true
>    for i=x:y
>       infile = char(j) !! '-' !! char(i)
>       go fitld
>       end
>    finish
>
>
> If the disk area is not $FITS, then
>
>        outfile = '<area>' !! what I typed above
>
> where <area> is the environment variable pointing at  the disk area.
>
> Eric Greisen
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listmgr.nrao.edu/pipermail/daip/attachments/20030624/27f639ae/attachment.html>