On Jan 24, 2008 1:26 AM, A Darren Dunham <[EMAIL PROTECTED]> wrote:
> On Wed, Jan 23, 2008 at 05:56:15PM -0500, Romeo Theriault wrote:
>
> > Thank you for pointing this out. Though when I run it I get this error.
> >
> > # vxdiskunsetup c4t2d0
> > VxVM vxdiskunsetup NOTICE V-5-2-3522 c4t2d0: Disk
vxedit -fr rm might help
--
_/ sengork.blogspot.com /
___
Veritas-vx maillist - Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
On Wed, Jan 23, 2008 at 05:56:15PM -0500, Romeo Theriault wrote:
> Thank you for pointing this out. Though when I run it I get this error.
>
> # vxdiskunsetup c4t2d0
> VxVM vxdiskunsetup NOTICE V-5-2-3522 c4t2d0: Disk is not a volume manager
> disk
>
> So I guess veritas doesn't seem to think it
On Jan 23, 2008 4:24 PM, A Darren Dunham <[EMAIL PROTECTED]> wrote:
> On Wed, Jan 23, 2008 at 03:45:17PM -0500, Romeo Theriault wrote:
> > I am using Veritas Volume Manager 4.1 on Solaris 9. Disk c4t2d0s2 shows
> this
> > status:
> >
> > # vxdisk list | grep c4t2d0s2
> > c4t2d0s2 auto:sliced
On Wed, Jan 23, 2008 at 03:45:17PM -0500, Romeo Theriault wrote:
> I am using Veritas Volume Manager 4.1 on Solaris 9. Disk c4t2d0s2 shows this
> status:
>
> # vxdisk list | grep c4t2d0s2
> c4t2d0s2 auto:sliced --error
Is that a problem?
> Not a big deal but I wou
I am using Veritas Volume Manager 4.1 on Solaris 9. Disk c4t2d0s2 shows this
status:
# vxdisk list | grep c4t2d0s2
c4t2d0s2 auto:sliced --error
# vxdisk list c4t2d0s2
Device:c4t2d0s2
devicetag: c4t2d0
type: auto
info: format=sliced,privoffset=1,pubsli
