From: Daniel Clar (Daniel.Clar@supelec.fr)
Date: Tue Nov 19 2002 - 01:33:33 EST
The original posting was :
>
> Hello Managers,
>
> I'm still running an old AS 1000A 5/333 with a small system disk.
>
> The root partition is an advfs file system and it's very often full.
>
> Are there known problems to add a volume to this root domain ?
>
> Thanks
>
> Daniel Clar
Thank you for the answers (in short summary it's not possible) :
-------------------------------------------------------
David J. DeWolfe [sxdjd@ts.sois.alaska.edu]
AdvFS does not support a multi-volume root domain. See the "addvol"
manpage.
Schoepflin, Keith [Keith.Schoepflin@hp.com]
You can't add a volume to the root domain. The OS will not allow it.
Degerness, Mandell MSER:EX [Mandell.Degerness@gems2.gov.bc.ca]
I am certain about v5.*, but all prior versions of Tru64 have a
restriction
on the root file system which prevents it from being more than a single
volume. This is part of what is done when the AdvFS domain is created
using
the -r switch (required for a root partition).
Dr Thomas.Blinn@HP.com [tpb@doctor.zk3.dec.com]
It won't work. You need to move the root to a larger disk. If
you did manage to add a disk volume to the domain, then you'd
be extremely lucky if the system continued to be able to boot
since the bootstrap code can't deal with a multi-volume root
domain, and never will.
Lavelle, Bryan [Bryan.Lavelle@hp.com]
You can not add volumes to the root domain prior to 5.x Cluster root
domains.
Thomas L. Sjolshagen [Thomas.Sjolshagen@hp.com]
The addvol command will not allow you to add a LUN to a boot/root file
system (unless it's a V5.x cluster where you can add a LUN/Volume to the
cluster root, but not the member boot). One reson for this behavior
(restriction) is that the placement of the osf_boot and vmunix files
which a) needs to be on the same volume and b) needs to be on the volume
spelled out in the boot command. Since you technically speaking aren't
supposed to know this (due to the design of AdvFS w/its layers of
abstraction), it wasn't considered safe to allow the expansion of a root
domain. (no way to guarantee where the osf_boot and vmunix files landed)
Your only choice for expanding the root/boot file system is to use
either V5.1 (or later) w/ a UFS based root file system residing on a LSM
volume - or some other RAID controller capable of expanding a LUN - (you
can then expand the lsm volume and use "mount -o expand" to expand the
UFS file system), V5.1B (once it ships w/the same underlying storage
stack as the UFS based solution), or the always(?) trusted
"backup-create-new-root-on-bigger-partition/volume-restore" process.
Deacy, Michael [Michael.Deacy@TycoHealthcare.com]
I may be mistaken but I don't believe you can have a multivolume domain
for
root. The man pages or manual may shed some light on that. Good luck.
------------------------------
Regards
Daniel
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:48:59 EDT