Prev: Volume encryption software
Next: Sun Ray SRSS cluster using GNOME: esd issues
From: Ste on 8 Apr 2008 10:56
Hello all,

I've inherited a problem... two Sun v440 clustered for Oraclewith a
storedge 3510. Storedge has a single volume with 6 partitions:

sccli> show partitions
LD/LV ID-Partition Size
ld0-00 35F82660-00 50.78GB
ld0-01 35F82660-01 50.78GB
ld0-02 35F82660-02 32.23GB
ld0-03 35F82660-03 31.25GB
ld0-04 35F82660-04 19.53GB
ld0-05 35F82660-05 19.78GB

Looking the active node I see:

root(a)windn2 # vxdisk -e list
DEVICE TYPE DISK GROUP STATUS c#t#d#_NAME
SUN35100_0 sliced - - error c5t600C0FF0000000000825E535F8266005d0s2
SUN35100_1 sliced - - error c5t600C0FF0000000000825E535F8266004d0s2
SUN35100_2 sliced - - error c5t600C0FF0000000000825E535F8266003d0s2
SUN35100_3 sliced - - error c5t600C0FF0000000000825E535F8266002d0s2
SUN35100_4 sliced - - error c5t600C0FF0000000000825E535F8266001d0s2
SUN35100_5 sliced winddg00 winddg online
c5t600C0FF0000000000825E535F8266000d0s2
c1t0d0s2 sliced rootdisk_2 rootdg online c1t0d0s2
c1t1d0s2 sliced rootmirror rootdg online c1t1d0s2
c1t2d0s2 sliced - - error c1t2d0s2
c1t3d0s2 sliced - - error c1t3d0s2

root(a)windn2 # df -k | grep winddg
/dev/vx/dsk/winddg/winddb 47949507 40283573 2870984 94% /winddb
/dev/vx/dsk/winddg/windredo 1966056 107780 1661671 7% /windredo

root(a)windn2 # vxdisk list winddg00
Device: SUN35100_5
devicetag: SUN35100_5
type: sliced
hostid: windn2
disk: name=winddg00 id=1100274668.1149.windn1
group: name=winddg id=1100274669.1152.windn1
flags: online ready private autoconfig noautoimport imported
pubpaths: block=/dev/vx/dmp/SUN35100_5s4 char=/dev/vx/rdmp/SUN35100_5s4
privpaths: block=/dev/vx/dmp/SUN35100_5s3 char=/dev/vx/rdmp/SUN35100_5s3
version: 2.2
iosize: min=512 (bytes) max=2048 (blocks)
public: slice=4 offset=0 len=106487808
private: slice=3 offset=1 len=1791
update: time=1200548980 seqno=0.169
headers: 0 248
configs: count=1 len=1303
logs: count=1 len=197
Defined regions:
config priv 000017-000247[000231]: copy=01 offset=000000 enabled
config priv 000249-001320[001072]: copy=01 offset=000231 enabled
log priv 001321-001517[000197]: copy=01 offset=000000 enabled
Multipathing information:
numpaths: 1
c5t600C0FF0000000000825E535F8266000d0s2 state=enabled

Problem is that 've to expand the /dev/vx/dsk/winddg/winddb till at
least 100gb.
Then mount another partition of 25 gb ... but looking at the whole
system seems that only one partition is used and total amonut does not
correspond to sum of two volumes

Any hint?

Thanks!

Stefano
From: Darren Dunham on 8 Apr 2008 15:33
Ste <s.c(a)i.net.it> wrote:
> root(a)windn2 # df -k | grep winddg
> /dev/vx/dsk/winddg/winddb 47949507 40283573 2870984 94% /winddb
> /dev/vx/dsk/winddg/windredo 1966056 107780 1661671 7% /windredo

>
> Problem is that 've to expand the /dev/vx/dsk/winddg/winddb till at
> least 100gb.
> Then mount another partition of 25 gb ... but looking at the whole
> system seems that only one partition is used and total amonut does not
> correspond to sum of two volumes

I'm not sure I understand your question.

But you don't show any details of the two VxVM volumes.

The output of 'vxprint -g winddg -ht' should show their configuration.

--
Darren Dunham ddunham(a)taos.com
Senior Technical Consultant TAOS http://www.taos.com/
Got some Dr Pepper? San Francisco, CA bay area
< This line left intentionally blank to confuse you. >
From: Ste on 9 Apr 2008 02:28
Darren Dunham ha scritto:
> The output of 'vxprint -g winddg -ht' should show their configuration.

root(a)windn2 # vxprint -g winddg -ht
DG NAME NCONFIG NLOG MINORS GROUP-ID
DM NAME DEVICE TYPE PRIVLEN PUBLEN STATE
RV NAME RLINK_CNT KSTATE STATE PRIMARY DATAVOLS SRL
RL NAME RVG KSTATE STATE REM_HOST REM_DG REM_RLNK
V NAME RVG KSTATE STATE LENGTH READPOL
PREFPLEX UTYPE
PL NAME VOLUME KSTATE STATE LENGTH LAYOUT
NCOL/WID MODE
SD NAME PLEX DISK DISKOFFS LENGTH [COL/]OFF DEVICE
MODE
SV NAME PLEX VOLNAME NVOLLAYR LENGTH [COL/]OFF AM/NM
MODE
DC NAME PARENTVOL LOGVOL
SP NAME SNAPVOL DCO

dg winddg default default 7000 1100274669.1152.windn1

dm winddg00 SUN35100_5 sliced 1791 106487808 -

v winddb - ENABLED ACTIVE 102292783 SELECT -
fsgen
pl winddb-01 winddb ENABLED ACTIVE 102293504 CONCAT -
RW
sd winddg00-01 winddb-01 winddg00 0 102293504 0
SUN35100_5 ENA

v windredo - ENABLED ACTIVE 4194304 SELECT -
fsgen
pl windredo-01 windredo ENABLED ACTIVE 4194304 CONCAT -
RW
sd winddg00-02 windredo-01 winddg00 102293504 4194304 0
SUN35100_5 ENA


And is this. So, as I'm able to understand, both winddb and windredo are
on SUN35100_5 Lun.

To grow the winddb lun I'have to initialize more LUNS and then grow
using vxresize... right?

A volume can be across two or more LUNs?


Thanks
Ste
From: Darren Dunham on 9 Apr 2008 11:42
Ste <s.c(a)i.net.it> wrote:
> And is this. So, as I'm able to understand, both winddb and windredo are
> on SUN35100_5 Lun.

Correct.

> To grow the winddb lun I'have to initialize more LUNS and then grow
> using vxresize... right?

You'll have to bring more "disks"(luns) into the group. Verify that
they are not used by any other external processes before doing so.

Vxresize is one valid method for extending the volume and the filesystem
onto new disks. My assumption is that it will do a concatenation. That
may or may not be what you're looking for.

> A volume can be across two or more LUNs?

Yes.

--
Darren Dunham ddunham(a)taos.com
Senior Technical Consultant TAOS http://www.taos.com/
Got some Dr Pepper? San Francisco, CA bay area
< This line left intentionally blank to confuse you. >
From: Ste on 11 Apr 2008 11:22
Darren Dunham ha scritto:
> Ste <s.c(a)i.net.it> wrote:
>> And is this. So, as I'm able to understand, both winddb and windredo are
>> on SUN35100_5 Lun.
>
> Correct.

K, some progress. Now winddg has 3 LUN:

root(a)windn2 # vxdg list
NAME STATE ID
rootdg enabled 1100268602.1025.windn2
winddg enabled 1100274669.1152.windn1
root(a)windn2 # vxdg list winddg
Group: winddg
dgid: 1100274669.1152.windn1
import-id: 0.1285
flags:
version: 90
detach-policy: global
copies: nconfig=default nlog=default
config: seqno=0.1130 permlen=1303 free=1297 templen=4 loglen=197
config disk SUN35100_3 copy 1 len=1303 state=clean online
config disk SUN35100_4 copy 1 len=1303 state=clean online
config disk SUN35100_5 copy 1 len=1303 state=clean online
log disk SUN35100_3 copy 1 len=197
log disk SUN35100_4 copy 1 len=197
log disk SUN35100_5 copy 1 len=197

Now using the command

vxassist -g winddg growto 103302783

volume should grow, but in fact running a df -k doesn't show more space...

/dev/vx/dsk/winddg/winddb
47949507 40299241 2855316 94% /winddb
/dev/vx/dsk/winddg/windredo
1966056 107780 1661671 7% /windredo

was and is the same size!

I'm loosing something??!

Ste

 |  Next  |  Last
Pages: 1 2
Prev: Volume encryption software
Next: Sun Ray SRSS cluster using GNOME: esd issues