Hi Paul,
Doing a google search for:
vxvm:vxconfigd: V-5-1-543 Differing version of vxconfigd installed
Reveals only 2 matches. Both from symantic and both saying reboot the
system is the appropriate action. Since rebooting for you does not
work, I would open a support case.
Possible further a
Hazel, Geoff wrote:
> I'm going to be using fsadm tonight to expand a filesystem on an
> existing volume. The volume itself does NOT need expanding, it's big
> enough, but the filesystem is smaller than the volume and I'm going to
> enlarge it to the full size of the volume.
>
> 2 questions:
Doug, that makes perfect sense. Thanks!
Geoff Hazel, UNIX System Engineer
AT&T Mobility Network Operations
Core Services Systems & Storage
425-877-5634 wireless
425-288-2034 desk
[EMAIL PROTECTED]
-Original Message-
From: Doug Hughes [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 2
I'm going to be using fsadm tonight to expand a filesystem on an
existing volume. The volume itself does NOT need expanding, it's big
enough, but the filesystem is smaller than the volume and I'm going to
enlarge it to the full size of the volume.
2 questions:
I'm assuming I can do this "hot"
may need -g option if tooldwnld-dg is not your default dg
also -o rm will delete the old sub-disk (most of the time it is what you
want), here d012-01 for example.
so you can use --
vxse -g tooldwnld-dg mv oldsd newsd
then if you don't need the oldsd indeed, you can use --
vxedit -g tooldwnld-dg
Hi All,
Really appreciate for those who have give me a reply, Anyhow, pls
find the following for the related console log
...
Oct 14 14:59:25 2008 VxVM sysboot INFO V-5-2-3409 starting in boot mode...
Oct 14 14:59:25 2008 Oct 14 15:03:54 arthur01 vxvm:vxconfigd: V-5-1-543 Differin
g version of v
