SUMMARY: Final Thoughts, moving root+usr

From: Tru64 User <tru64user_at_yahoo.com>
Date: Thu, 06 Sep 2001 08:35:01 -0700 (PDT)

Thanks very much to John Francini, once again.
He aprroached it one-to-one, this will give me comfort
as I go about moving the system disk.
His relpy follows below.

_Thanks
Richard

--- John Francini <francini_at_zk3.dec.com> wrote:
> You don't need to use tape, assuming both source and
> destination
> disks are on-line at the same time. Use a
> vdump/vrestore pipe to
> dump/restore the root AND /usr partitions. See the
> vdump(8) manpage
> for an example. vdump will not cross mount point
> boundaries. Trust
> me: it's MUCH easier (and less error-prone) than
> going to and from
> tape.
>
> As for telling the system to always boot re0a --
> just issue the command
>
> >>> set bootdef_dev re0
>
> at the console prompt. No partition name is given
> since the console
> doesn't know anything about UNIX partitions.
>
> Change the /etc/fstab entries as you described.
> Since the old disk
> is ufs, you don't have to do any renaming/relinking
> in /etc/fdmns.
> Otherwise you should be OK. Given that you have the
> swap space
> elsewhere, you don't need to make any other changes
> in /etc/fstab.
>
> Also look at /etc/rc.config to check/change any
> definitions there
> that reflect the old system disk.
>
> I'm sorry if the description in the archives seems
> complicated.
> However, when you move an AdvFS-based system disk to
> a new physical
> drive, there's more things to make sure are
> correctly changed than
> there are when it's UFS. That's why those
> instructions are a bit
> complex. There's also the fact that, if I recall
> correctly, what I
> wrote was intended to be valid for both V4.0x and
> V5.x systems, and
> there's enough difference between them that many
> steps require both
> V4 and V5 descriptions.
>
> Since you contemplate keeping the old system disk as
> a "hot spare",
> you'll need to configure _it_ as if you were going
> to move the system
> disk from one AdvFS disk to another -- in other
> words, most of my
> previous posting.
>
> Hope this helps,
>
> John Francini
>
>
>
>
>
> >Greetings,
> >Need some final thoughts here...running 4.0g on
> 4100
> >I have larger logical drive, configured as raid0 (2
> >disks, 9.1x2gb) Currently have it partioned for
> root,
> >2g and usr 15gb.
> >Plan:
> >1. Use "cd fromdir; tar cf - .|(cd todir; tar xpf
> -)"
> >to move data from current usr to new_User
> >2. use backup/restore(tar full bkup tapes) to move
> the
> >/ part to new_root. (tried tar on it, it was moving
> >data residing in mount points, eg, it was moving
> /usr
> >onto / partition)
> >
> >3.Change the /etc/fstab entries to reflect new
> devices
> >to old mount points ie, instead of rz16a mount
> point
> >being /, now re0a (root_dmn#root_fs will mount to
> >root. Same for /usr, usr_dmn#usr_fs /usr.
> >4. Reboot...........then??
> >
> >I saw a good summary on cloning root_fs in the
> >archives....from John Francini...a little bit
> >involved, i will try to see how it fits my
> environment
> >
> >
> >QUESTIONs:
> >1. How do i tell system to always boot from re0a,
> >instead of rz16a? at >>>>boot <cons_dev_name>?
> >
> >2. Have I overlooked any details, taking into
> account
> >old root was on disklabel 4.2BSD, and now it is
> going
> >to advfs?
> >3. I would like to retain rz16 disk, to be used as
> a
> >hot spare, incase re0 goes down. Any special
> attention
> >to this?
> >
> >
> >
> >
> >SUPPORTING INFO:
> >test_at_/$ df
> >Filesystem 1024-blocks Used
> >Available Capacity Mounted on
> >/dev/rz16a 257967 98773
> >133397 43% /
> >/proc 0 0
>
> >0 100% /proc
> >/dev/rz16g 8491059 4154639
> >3487314 55% /usr
> >
> >
> >
> >Move to:
> >root_dmn#root_fs 2097152 16
> >2092640 1% /new_root
> >usr_dmn#usr_fs 15675384 2977705
> >12644456 20% /new_usr
> >
> >disklabels:
> >/dev/rz16a
> >
> >8 partitions:
> ># size offset fstype [fsize bsize
>
> >cpg] # NOTE: values not exact
> > a: 524289 0 4.2BSD 1024
> 8192
> >16 # (Cyl. 0 - 156*)
> > b: 262144 131072 unused 0
> 0
> > # (Cyl. 39*- 117*)
> > c: 17773524 0 unused 0
> 0
> > # (Cyl. 0 - 5289*)
> > d: 0 0 unused 0
> 0
> > # (Cyl. 0 - -1)
> > e: 0 0 unused 0
> 0
> > # (Cyl. 0 - -1)
> > f: 0 0 unused 0
> 0
> > # (Cyl. 0 - -1)
> > g: 17249235 524289 4.2BSD 1024
> 8192
> >16 # (Cyl. 156*- 5289*)
> > h: 8690154 9083370 unused 0
> 0
> > # (Cyl. 2703*- 5289*)
> >
> >/dev/re0a
> >8 partitions:
> ># size offset fstype [fsize bsize
>
> >cpg] # NOTE: values not exact
> > a: 4194305 0 AdvFS
>
> > # (Cyl. 0 - 1024*)
> > b: 262144 131072 unused 0
> 0
> > # (Cyl. 32 - 95)
> > c: 35545088 0 unused 0
> 0
> > # (Cyl. 0 - 8677)
> > d: 0 0 unused 0
> 0
> > # (Cyl. 0 - -1)
> > e: 0 0 unused 0
> 0
> > # (Cyl. 0 - -1)
> > f: 0 0 unused 0
> 0
> > # (Cyl. 0 - -1)
> > g: 31350783 4194305 AdvFS
>
> > # (Cyl. 1024*- 8677)
> > h: 0 0 unused 0
> 0
> > # (Cyl. 0 - -1)
> >
> >
> >=====
> >
>
=== message truncated ===


=====


__________________________________________________
Do You Yahoo!?
Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger
http://im.yahoo.com
Received on Thu Sep 06 2001 - 15:36:13 NZST

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:42 NZDT