[mailto:[EMAIL PROTECTED]
> Sent: Friday, June 29, 2007 9:43 AM
> To: Myers, Mike; Khurram Tariq; veritas-vx@mailman.eng.auburn.edu
> Subject: RE: [Veritas-vx] Resize problem
>
> Hi Mike,
>
> This is what I was trying to allude to in my mail earlier. In the
older
> versio
.eng.auburn.edu
> Subject: Re: [Veritas-vx] Resize problem
>
> It's been out experience that fsadm will not reorganize extents of
files
> that are open by an application. Thus, if you have even one extent of
a
> file in the area you wish to reclaim and that file is open, you mu
; Khurram Tariq; veritas-vx@mailman.eng.auburn.edu
Subject: RE: [Veritas-vx] Resize problem
Hi Mike,
This is what I was trying to allude to in my mail earlier. In the older
versions of SF it was sometimes not possible to move certain application
files due to them being memory mapped (Oracle in
rite...
Cheers,
- Mike.Myers nwdc.net
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Khurram
Tariq
Sent: Friday, June 29, 2007 5:01 AM
To: veritas-vx@mailman.eng.auburn.edu
Subject: Re: [Veritas-vx] Resize problem
Upgraded the dg version, ran defrag ag
3:01
To: veritas-vx@mailman.eng.auburn.edu
Subject: Re: [Veritas-vx] Resize problem
Upgraded the dg version, ran defrag again (used fsadm --F vxfs -d -e
/filesystem) and still the result of fsadm -D /filesystem is the same as
before (see below) & vxresize does not work:
Directory Fragm
lst the volume is quiesced..
> > --------------
> > *From:* [EMAIL PROTECTED] on behalf of Khurram
> > Tariq
> > *Sent:* Thu 6/28/2007 2:44 PM
> > *To:* veritas-vx@mailman.eng.auburn.edu
> > *Subject:* Re: [Veritas-vx] Resize problem
@mailman.eng.auburn.edu
Subject: Re: [Veritas-vx] Resize problem
After the evacuation I'm left with 2 x 200GB disks in the volume.
Disk_160 is 79% used & Disk_161 is 20% used and the volume still refuses
to shrink giving me the same error as before. I've started defrag again
in the hopes that it
size
> > attach mirror consisting of disk_160
> > remove disk_161 from mirror
> > all this should be possible whilst the volume is started
> >
> > Klaus
> >
> > --------------
> > *Von:* [EMAIL PROTECTED] [mailto:
>
e volume is quiesced..
--
*From:* [EMAIL PROTECTED] on behalf of Khurram
Tariq
*Sent:* Thu 6/28/2007 2:44 PM
*To:* veritas-vx@mailman.eng.auburn.edu
*Subject:* Re: [Veritas-vx] Resize problem
I had thought of it but the size of the volume is slightly larger than the
cap
PROTECTED] on behalf of Khurram Tariq
Sent: Thu 6/28/2007 2:44 PM
To: veritas-vx@mailman.eng.auburn.edu
Subject: Re: [Veritas-vx] Resize problem
I had thought of it but the size of the volume is slightly larger than the
capacity of Disk_161 so mirroring wont be possible. Size of the volume visible
in
n:* [EMAIL PROTECTED] [mailto:
[EMAIL PROTECTED] *Im Auftrag von *Khurram Tariq
*Gesendet:* Donnerstag, 28. Juni 2007 15:23
*An:*
*Betreff:* Re: [Veritas-vx] Resize problem
Agreed but I can also evacuate Disk_1 if I had enough free space on
Disk_160. This is why I'm decreasing the volume by 2G
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Im Auftrag von
Khurram Tariq
Gesendet: Donnerstag, 28. Juni 2007 15:23
An:
Betreff: Re: [Veritas-vx] Resize problem
Agreed but I can also evacuate Disk_1 if I had enough free space on
Disk_160. This is why I'm decreasin
[EMAIL PROTECTED]>
To: veritas-vx@mailman.eng.auburn.edu
Sent: Thursday, 28 June, 2007 5:17:33 PM
Subject: Re: [Veritas-vx] Resize problem
$ vxprint -ht ccbappl
Disk group: oraappdg
V NAME RVG/VSET/CO KSTATE STATELENGTH READPOL PREFPLEX
UTYPE
PL NAME VOLUME KSTAT
2007 5:17:33 PM
Subject: Re: [Veritas-vx] Resize problem
$ vxprint -ht ccbappl
Disk group: oraappdg
V NAME RVG/VSET/CO KSTATE STATELENGTH READPOL PREFPLEX UTYPE
PL NAME VOLUME KSTATE STATELENGTH LAYOUTNCOL/WID MODE
SD NAME PLEX D
tas-vx@mailman.eng.auburn.edu
*Subject:* Re: [Veritas-vx] Resize problem
Hi all,
could you perhaps evacuate the data from the 40GB LUN to some temporary
space, then remove the 40GB LUN, then shrink the volume and then remove the
temporary space?
Another option maybe is to mirror to other LUNS and then try and shri
: veritas-vx@mailman.eng.auburn.edu
Subject: Re: [Veritas-vx] Resize problem
Nopes. It has always been VxFS. Defrag didnt help either and
decreasing the size in chunks as small as 1GB isnt working either.
Initially this FS was 440GB & had 2 x 200GB LUNs & 1 x 40GB
up in messages?
Greg.
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Khurram
Tariq
Sent: Thursday, 28 June 2007 2:13 PM
To: veritas-vx@mailman.eng.auburn.edu
Subject: Re: [Veritas-vx] Resize problem
Nopes. It has always been VxFS. Defrag didnt
Nopes. It has always been VxFS. Defrag didnt help either and decreasing the
size in chunks as small as 1GB isnt working either. Initially this FS was
440GB & had 2 x 200GB LUNs & 1 x 40GB. Resize worked day before yesterday &
I was able to free up one 200GB LUN out of the volume but its not workin
> I have a 201GB volume which is composed of two LUNs (40GB & 200GB). Now I
> want to free up the 40GB LUN from that volume by shrinking the volume to
> 198GB but vxresize is giving me the following error:
>
> UX:vxfs fsadm: ERROR: V-3-20343: cannot shrink /dev/vx/rdsk/some-dg/volumea
> - blocks a
Khurram Tariq wrote:
> Hi All,
>
> I have a 201GB volume which is composed of two LUNs (40GB & 200GB). Now I
> want to free up the 40GB LUN from that volume by shrinking the volume to
> 198GB but vxresize is giving me the following error:
>
> UX:vxfs fsadm: ERROR: V-3-20343: cannot shrink
> /dev/v
Hi All,
I have a 201GB volume which is composed of two LUNs (40GB & 200GB). Now I
want to free up the 40GB LUN from that volume by shrinking the volume to
198GB but vxresize is giving me the following error:
UX:vxfs fsadm: ERROR: V-3-20343: cannot shrink /dev/vx/rdsk/some-dg/volumea
- blocks are
21 matches
Mail list logo
