[SunHELP] Veritas Weirdness
Naser Ali
sunhelp at sunhelp.org
Wed Jan 24 08:11:32 CST 2001
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01C0860F.8D8FD920
Content-Type: text/plain;
charset="iso-8859-1"
Increasing the size of a file system (actually the volume in the case of
veritas) is not as simple as they say it is. It took me a while to figure
the damn thing out.
Regards
Hope this helps. Just follow the steps.
===========================================================================
sun02:root:> df -k | more
Filesystem kbytes used avail capacity Mounted on
/dev/vx/dsk/EFDS_PY/db01 118639872 110119144 8454224 93% /EFDS/DB1
NOTE: volume db01 's size is needed to be increased.
Add the new disk to the disk group and create a subdisk,if there is no
additional disk space
left in the group, and then drag and drop that subdisk in the volume who's
size has to be
increased.
sun02:root:> vxassist growby db01 6144m
sun02:root:> vxprint -l db01
Disk group: EFDS_PY
Volume: db01
info: len=249862656
type: usetype=fsgen
state: state=ACTIVE kernel=ENABLED
assoc: plexes=db01-01
policies: read=SELECT (round-robin) exceptions=GEN_DET_SPARSE
flags: open writeback
logging: type=NONE
apprecov: seqno=0
device: minor=76000 bdev=140/76000 cdev=140/76000
path=/dev/vx/dsk/EFDS_PY/db01
perms: user=root group=other mode=0644
sun02:root:> /etc/vx/bin/vxresize -g EFDS_PY -F vxfs db01 249862656
vxresize: NOTE: Volume db01: Volume length is already 249862656
vxfs fsadm: /dev/vx/rdsk/EFDS_PY/db01 is currently 237279744 sectors - size
will be increased
sun02:root:> df -k | more
Filesystem kbytes used avail capacity Mounted on
/dev/vx/dsk/EFDS_PY/db01 124931328 110119336 14696336 89% /EFDS/DB1
Add some more space....
sun02:root:> /usr/sbin/vxassist growby db01 10240m
sun02:root:> vxprint -l db01
Disk group: EFDS_PY
Volume: db01
info: len=270834176
type: usetype=fsgen
state: state=ACTIVE kernel=ENABLED
assoc: plexes=db01-01
policies: read=SELECT (round-robin) exceptions=GEN_DET_SPARSE
flags: open writeback
logging: type=NONE
apprecov: seqno=0
device: minor=76000 bdev=140/76000 cdev=140/76000
path=/dev/vx/dsk/EFDS_PY/db01
perms: user=root group=other mode=0644
sun02:root:> /etc/vx/bin/vxresize -g EFDS_PY -F vxfs db01 270834176
vxresize: NOTE: Volume db01: Volume length is already 270834176
vxfs fsadm: /dev/vx/rdsk/EFDS_PY/db01 is currently 249862656 sectors - size
will be increased
sun02:root:>
sun02:root:> df -k | more
Filesystem kbytes used avail capacity Mounted on
/dev/vx/dsk/EFDS_PY/db01 135417088 110119664 25099856 82% /EFDS/DB1
============================================================================
Aali Naser
EFDS Development
Ali.Naser at irs.gov
(202)-927-4616
-----Original Message-----
From: Lund, Dennis [mailto:Dennis.Lund at sciatl.com]
Sent: Tuesday, January 23, 2001 8:18 AM
To: 'sunhelp at sunhelp.org'
Subject: RE: [SunHELP] Veritas Weirdness
I have not seen any responses to your problem, so I thought I would send
this
in case you were still looking for a solution.
This is an interesting command, about which almost nothing is written.
syntax: vxresize (file name) (size in gb=g or m=mb )
used to expand a file system under volume manager, it also resizes
the volume to fit the increased file system (if you should happen to
resize a volume when you should have resized the filesystem).
In the event a volume is expanded first, the filesystem will remain at
it's original size. If this is the case use vxresize to expand the file
system to slightly larger than the volume size( even 1mb). The resized
file system will utilize all of the increased volume size.
If the file system is type ufs then the syntax to expand is:
vxresize -F ufs (file name) ( size in g or m )
EXAMPLE: vxresize -F ufs u05 22g <<< expand ufs file u05 to 22g
For a vxfs file the syntax to expand is:
EXAMPLE: vxresize -F vxvs u05 22g <<< expand ufs file u05 to 22g
Hope this helps, or helps in the future should you need it.
Dennis L. Lund
-----Original Message-----
From: Marc Belanger [ mailto:mbelang1 at travelers.com
<mailto:mbelang1 at travelers.com> ]
Sent: Thursday, January 18, 2001 8:58 PM
To: sunhelp
Subject: [SunHELP] Veritas Weirdness
Hello sunhelpers-
I am looking for a reasonably safe solution to a SEVM 2.5 abnormality.
It seems a striped plex was created, and the volume was created at a
smaller size. The difference is ~6GB. I am looking for a way to correct
the situation without having to rebuild the volume, and restore. I
understand it may be the only way to correctly fix the problem.
I have researched a bit and found I may be able to "grow" the volume by
adding 3 more disks, but I do not know what that will do to the plex.
Further, I'm not so sure I want to *start* slicing up whole 9GB disks.
Here's some */slightly snipped/* output:
*/ NOTE: some of this might be line wrapped at 72 chars, sorry /*
# uname -a
SunOS */snip/* 5.6 Generic_105181-19 sun4u sparc SUNW,Ultra-4
# pkginfo -l SUNWvxvm
PKGINST: SUNWvxvm
NAME: Sun Enterprise Volume Manager
CATEGORY: system
ARCH: sparc
VERSION: 2.5
BASEDIR: /
# vxprint -ht */relavent group anyway/*
v xtra fsgen ENABLED ACTIVE 41886720 SELECT
xtra-04
pl xtra-04 xtra ENABLED ACTIVE 52704000 STRIPE
3/128 RW
sd midg16-01 xtra-04 midg16 0 17568000 0/0
c6t20d1 ENA
sd midg17-01 xtra-04 midg17 0 17568000 1/0
c6t20d2 ENA
sd midg18-01 xtra-04 midg18 0 17568000 2/0
c6t20d3 ENA
# df -k */relavent fs/*
Filesystem kbytes used avail capacity Mounted on
/dev/vx/dsk/midg/xtra 20615385 18064179 1520437 93% /xtra
# cat /etc/vfstab */again with the relavent stuff/*
#device device mount FS fsck mount
mount
#to mount to fsck point type pass at boot
options
#
/dev/vx/dsk/midg/xtra /dev/vx/rdsk/midg/xtra /xtra ufs 3 yes -
Any thoughts or comments are welcomed. I would be most interested in
knowing if there is an easier method of repairing the v/pl size
mismatch, especially if I will not cause an outage to do so. Any ideas
on how/why this happened would be helpful to prevent future occurances.
I am looking to know what will happen to v/pl if I was to try to grow
the volume.
I would not usually try to "fall forward", however, info on this
situation under Solaris 8 and VxVm 3.0.1 (or better) might be worth a
shot.
Thanks in advance,
-Marc
_______________________________________________
SunHELP maillist - SunHELP at sunhelp.org
http://www.sunhelp.org/mailman/listinfo/sunhelp
<http://www.sunhelp.org/mailman/listinfo/sunhelp>
- - - - - - - Appended by Scientific-Atlanta, Inc. - - - - - - -
This e-mail and any attachments may contain information which is
confidential, proprietary, privileged or otherwise protected by law. The
information is solely intended for the named addressee (or a person
responsible for delivering it to the addressee). If you are not the intended
recipient of this message, you are not authorized to read, print, retain,
copy or disseminate this message or any part of it. If you have received
this e-mail in error, please notify the sender immediately by return e-mail
and delete it from your computer.
------_=_NextPart_001_01C0860F.8D8FD920
Content-Type: text/html;
charset="iso-8859-1"
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>RE: [SunHELP] Veritas Weirdness</TITLE>
<META content="MSHTML 5.00.2314.1000" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=731110014-24012001>Increasing the size of a file system (actually the
volume in the case of veritas) is not as simple as they say it is. It took me a
while to figure the damn thing out.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=731110014-24012001>Regards</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=731110014-24012001>Hope
this helps. Just follow the steps.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=731110014-24012001></SPAN></FONT> </DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=731110014-24012001>===========================================================================</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=731110014-24012001>sun02:root:> df -k |
more<BR>Filesystem
kbytes used avail capacity Mounted
on</SPAN></FONT></DIV>
<DIV> </DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=731110014-24012001><BR>/dev/vx/dsk/EFDS_PY/db01 118639872 110119144
8454224 93% /EFDS/DB1</SPAN></FONT></DIV>
<DIV> </DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=731110014-24012001>NOTE:
volume db01 's size is needed to be increased.<BR>Add the new disk to the disk
group and create a subdisk,if there is no additional disk space
</SPAN></FONT></DIV>
<DIV> </DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=731110014-24012001>left
in the group, and then drag and drop that subdisk in the volume who's size has
to be </SPAN></FONT></DIV>
<DIV> </DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=731110014-24012001>increased.</SPAN></FONT></DIV>
<DIV> </DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=731110014-24012001>sun02:root:> vxassist growby db01
6144m</SPAN></FONT></DIV>
<DIV> </DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=731110014-24012001>sun02:root:> vxprint -l db01<BR>Disk group:
EFDS_PY</SPAN></FONT></DIV>
<DIV> </DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=731110014-24012001>Volume:
db01<BR>info:
len=249862656<BR>type:
usetype=fsgen<BR>state: state=ACTIVE
kernel=ENABLED<BR>assoc: plexes=db01-01<BR>policies:
read=SELECT (round-robin) exceptions=GEN_DET_SPARSE<BR>flags:
open writeback<BR>logging: type=NONE<BR>apprecov:
seqno=0<BR>device: minor=76000 bdev=140/76000 cdev=140/76000
<BR>path=/dev/vx/dsk/EFDS_PY/db01<BR>perms: user=root
group=other mode=0644</SPAN></FONT></DIV>
<DIV> </DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=731110014-24012001>sun02:root:> /etc/vx/bin/vxresize -g EFDS_PY -F vxfs
db01 249862656<BR>vxresize: NOTE: Volume db01: Volume length is already
249862656<BR>vxfs fsadm: /dev/vx/rdsk/EFDS_PY/db01 is currently 237279744
sectors - size <BR>will be increased<BR>sun02:root:> df -k |
more<BR>Filesystem
kbytes used avail capacity Mounted
on</SPAN></FONT></DIV>
<DIV> </DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=731110014-24012001><BR>/dev/vx/dsk/EFDS_PY/db01 124931328 110119336
14696336 89% /EFDS/DB1</SPAN></FONT></DIV>
<DIV> </DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=731110014-24012001><BR>Add some more space....<BR>sun02:root:>
/usr/sbin/vxassist growby db01 10240m</SPAN></FONT></DIV>
<DIV> </DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=731110014-24012001>sun02:root:> vxprint -l db01<BR>Disk group:
EFDS_PY</SPAN></FONT></DIV>
<DIV> </DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=731110014-24012001>Volume:
db01<BR>info:
len=270834176<BR>type:
usetype=fsgen<BR>state: state=ACTIVE
kernel=ENABLED<BR>assoc: plexes=db01-01<BR>policies:
read=SELECT (round-robin) exceptions=GEN_DET_SPARSE<BR>flags:
open writeback<BR>logging: type=NONE<BR>apprecov:
seqno=0<BR>device: minor=76000 bdev=140/76000 cdev=140/76000
<BR>path=/dev/vx/dsk/EFDS_PY/db01<BR>perms: user=root
group=other mode=0644</SPAN></FONT></DIV>
<DIV> </DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=731110014-24012001>sun02:root:> /etc/vx/bin/vxresize -g EFDS_PY -F vxfs
db01 270834176<BR>vxresize: NOTE: Volume db01: Volume length is already
270834176<BR>vxfs fsadm: /dev/vx/rdsk/EFDS_PY/db01 is currently 249862656
sectors - size <BR>will be increased<BR>sun02:root:></SPAN></FONT></DIV>
<DIV> </DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=731110014-24012001>sun02:root:> df -k |
more<BR>Filesystem
kbytes used avail capacity Mounted
on</SPAN></FONT></DIV>
<DIV> </DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=731110014-24012001>/dev/vx/dsk/EFDS_PY/db01 135417088 110119664
25099856 82% /EFDS/DB1</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=731110014-24012001>============================================================================</SPAN></FONT></DIV>
<DIV> </DIV>
<P><B><FONT color=#000080 face="Lucida Sans Unicode" size=1>Aali
Naser</FONT></B> <BR><B><FONT color=#000080 face="Lucida Sans Unicode"
size=1>EFDS Development</FONT></B> <BR><B><FONT color=#000080
face="Lucida Sans Unicode" size=1>Ali.Naser at irs.gov</FONT></B> <BR><B><FONT
color=#000080 face="Lucida Sans Unicode" size=1>(202)-927-4616</FONT></B> </P>
<BLOCKQUOTE>
<DIV align=left class=OutlookMessageHeader dir=ltr><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B> Lund, Dennis
[mailto:Dennis.Lund at sciatl.com]<BR><B>Sent:</B> Tuesday, January 23, 2001 8:18
AM<BR><B>To:</B> 'sunhelp at sunhelp.org'<BR><B>Subject:</B> RE: [SunHELP]
Veritas Weirdness<BR><BR></DIV></FONT>
<P><FONT size=2>I have not seen any responses to your problem, so I thought I
would send this</FONT> <BR><FONT size=2>in case you were still looking for a
solution.</FONT> </P>
<P><FONT size=2>This is an interesting command, about which almost nothing is
written.</FONT> </P>
<P><FONT size=2>syntax: vxresize (file name) (size in gb=g or m=mb
)</FONT> </P>
<P><FONT size=2>used to expand a file system under volume manager, it also
resizes</FONT> <BR><FONT size=2>the volume to fit the increased file system
(if you should happen to</FONT> <BR><FONT size=2>resize a volume when you
should have resized the filesystem).</FONT> </P>
<P><FONT size=2>In the event a volume is expanded first, the filesystem will
remain at</FONT> <BR><FONT size=2>it's original size. If this is the
case use vxresize to expand the file</FONT> <BR><FONT size=2>system to
slightly larger than the volume size( even 1mb). The resized</FONT> <BR><FONT
size=2>file system will utilize all of the increased volume size.</FONT> </P>
<P><FONT size=2>If the file system is type ufs then the syntax to expand
is:</FONT> </P>
<P><FONT size=2> vxresize -F ufs (file name) ( size in g or m
)</FONT> </P>
<P><FONT size=2>EXAMPLE: vxresize -F ufs u05 22g <<< expand
ufs file u05 to 22g</FONT> </P>
<P><FONT size=2>For a vxfs file the syntax to expand is:</FONT> </P>
<P><FONT size=2>EXAMPLE: vxresize -F vxvs u05 22g <<< expand
ufs file u05 to 22g</FONT> </P>
<P><FONT size=2>Hope this helps, or helps in the future should you need
it.</FONT> </P>
<P><FONT size=2>Dennis L. Lund</FONT> </P>
<P><FONT size=2>-----Original Message-----</FONT> <BR><FONT size=2>From: Marc
Belanger [<A
href="mailto:mbelang1 at travelers.com">mailto:mbelang1 at travelers.com</A>]</FONT>
<BR><FONT size=2>Sent: Thursday, January 18, 2001 8:58 PM</FONT> <BR><FONT
size=2>To: sunhelp</FONT> <BR><FONT size=2>Subject: [SunHELP] Veritas
Weirdness</FONT> </P><BR>
<P><FONT size=2>Hello sunhelpers-</FONT> </P>
<P><FONT size=2>I am looking for a reasonably safe solution to a SEVM 2.5
abnormality.</FONT> <BR><FONT size=2>It seems a striped plex was created, and
the volume was created at a</FONT> <BR><FONT size=2>smaller size. The
difference is ~6GB. I am looking for a way to correct</FONT> <BR><FONT
size=2>the situation without having to rebuild the volume, and restore.
I</FONT> <BR><FONT size=2>understand it may be the only way to correctly fix
the problem.</FONT> </P>
<P><FONT size=2>I have researched a bit and found I may be able to "grow" the
volume by</FONT> <BR><FONT size=2>adding 3 more disks, but I do not know what
that will do to the plex.</FONT> <BR><FONT size=2>Further, I'm not so sure I
want to *start* slicing up whole 9GB disks.</FONT> </P>
<P><FONT size=2>Here's some */slightly snipped/* output:</FONT> <BR><FONT
size=2>*/ NOTE: some of this might be line wrapped at 72 chars, sorry
/*</FONT> </P>
<P><FONT size=2># uname
-a
</FONT><BR><FONT size=2>SunOS */snip/* 5.6 Generic_105181-19 sun4u sparc
SUNW,Ultra-4</FONT> </P>
<P><FONT size=2># pkginfo -l
SUNWvxvm
</FONT><BR><FONT size=2> PKGINST:
SUNWvxvm
</FONT><BR><FONT size=2> NAME: Sun
Enterprise Volume
Manager
</FONT><BR><FONT size=2> CATEGORY:
system
</FONT><BR><FONT size=2> ARCH:
sparc
</FONT><BR><FONT size=2> VERSION:
2.5
</FONT><BR><FONT size=2> BASEDIR: /</FONT> </P>
<P><FONT size=2># vxprint -ht
*/relavent group anyway/*</FONT>
<BR><FONT size=2>v xtra
fsgen ENABLED
ACTIVE 41886720 SELECT </FONT><BR><FONT
size=2>xtra-04 </FONT><BR><FONT size=2>pl
xtra-04
xtra ENABLED
ACTIVE 52704000 STRIPE </FONT><BR><FONT
size=2>3/128 RW </FONT><BR><FONT size=2>sd
midg16-01 xtra-04
midg16 0 17568000
0/0 </FONT><BR><FONT size=2>c6t20d1
ENA</FONT> <BR><FONT size=2>sd midg17-01
xtra-04 midg17
0 17568000
1/0 </FONT><BR><FONT size=2>c6t20d2
ENA</FONT> <BR><FONT size=2>sd midg18-01
xtra-04 midg18
0 17568000
2/0 </FONT><BR><FONT size=2>c6t20d3
ENA</FONT> </P>
<P><FONT size=2># df -k
*/relavent fs/*</FONT> <BR><FONT
size=2>Filesystem
kbytes used avail capacity Mounted
on</FONT> <BR><FONT size=2>/dev/vx/dsk/midg/xtra 20615385 18064179
1520437 93% /xtra</FONT> </P>
<P><FONT size=2># cat /etc/vfstab */again
with the relavent stuff/*</FONT> <BR><FONT
size=2>#device
device
mount
FS fsck mount
</FONT><BR><FONT size=2>mount </FONT><BR><FONT size=2>#to
mount to
fsck
point
type pass at boot</FONT> <BR><FONT
size=2>options</FONT> <BR><FONT size=2>#</FONT> <BR><FONT
size=2>/dev/vx/dsk/midg/xtra /dev/vx/rdsk/midg/xtra /xtra
ufs 3 yes -</FONT> </P>
<P><FONT size=2>Any thoughts or comments are welcomed. I would be most
interested in</FONT> <BR><FONT size=2>knowing if there is an easier method of
repairing the v/pl size</FONT> <BR><FONT size=2>mismatch, especially if I will
not cause an outage to do so. Any ideas</FONT> <BR><FONT size=2>on how/why
this happened would be helpful to prevent future occurances.</FONT> <BR><FONT
size=2>I am looking to know what will happen to v/pl if I was to try to
grow</FONT> <BR><FONT size=2>the volume.</FONT> </P>
<P><FONT size=2>I would not usually try to "fall forward", however, info on
this</FONT> <BR><FONT size=2>situation under Solaris 8 and VxVm 3.0.1 (or
better) might be worth a</FONT> <BR><FONT size=2>shot.</FONT> </P>
<P><FONT size=2>Thanks in advance,</FONT> <BR><FONT size=2>-Marc</FONT> </P>
<P><FONT size=2>_______________________________________________</FONT>
<BR><FONT size=2>SunHELP maillist - SunHELP at sunhelp.org</FONT>
<BR><FONT size=2><A href="http://www.sunhelp.org/mailman/listinfo/sunhelp"
target=_blank>http://www.sunhelp.org/mailman/listinfo/sunhelp</A></FONT>
</P><BR>
<P> - - - - - - - Appended by
Scientific-Atlanta, Inc. - - - - - - - <BR>This e-mail and any
attachments may contain information which is confidential, proprietary,
privileged or otherwise protected by law. The information is solely intended
for the named addressee (or a person responsible for delivering it to the
addressee). If you are not the intended recipient of this message, you are not
authorized to read, print, retain, copy or disseminate this message or any
part of it. If you have received this e-mail in error, please notify the
sender immediately by return e-mail and delete it from your computer.
</P><BR></BLOCKQUOTE></BODY></HTML>
------_=_NextPart_001_01C0860F.8D8FD920--
More information about the SunHELP
mailing list