SEO

Recently we added IBM Shark ESS storage to pSeries AIX 4.3.3 server.
There is one vpath and one VG build on that with 10 filesystem in
that.
Problem was today when users tried to access one of ten filesystems
and console hanged no response but all other filesystem in volumegroup
worked perfectly.
Errpt and /var/log/messages with full report level showed nothing.
After no success of unmounting I did shutdown even that wont work
becouse couldnt unmount that filesystem. After reboot everythink is
ok.
Is there any reasonible thing why that happened.

#lspv
hdisk0 0047549aaf6e4dbd rootvg
hdisk1 0047549acdb4037a rootvg
hdisk2 0047549adc32dfaf None < - not shark disks just SSA
hdisk3 0047548aa522c597 None < - not shark disks just SSA
hdisk4 none None <- shark links
hdisk5 none None
hdisk6 none None
hdisk7 none None
hdisk8 none None
hdisk9 none None
vpath0 0047549ad90bfe2b oraclevg


#datapath query device
Total Devices : 1


DEV#: 0 DEVICE NAME: vpath0 TYPE: 2105800 POLICY:
Optimized
SERIAL: ##########
================================================== ========================
Path# Adapter/Hard Disk State Mode Select
Errors
0 fscsi1/hdisk4 OPEN NORMAL 1073958
0
1 fscsi1/hdisk5 OPEN NORMAL 1074955
0
2 fscsi1/hdisk6 OPEN NORMAL 1072486
0
3 fscsi0/hdisk7 OPEN NORMAL 1080389
0
4 fscsi0/hdisk8 OPEN NORMAL 1081832
0
5 fscsi0/hdisk9 OPEN NORMAL 1081868
0

lslv medusalv
LOGICAL VOLUME: medusalv VOLUME GROUP: oraclevg
LV IDENTIFIER: 0047549adc32e8f2.10 PERMISSION: read/write
VG STATE: active/complete LV STATE:
opened/syncd
TYPE: jfs WRITE VERIFY: off
MAX LPs: 512 PP SIZE: 1024
megabyte(s)
COPIES: 1 SCHED POLICY: parallel
LPs: 87 PPs: 87
STALE PPs: 0 BB POLICY: relocatable
INTER-POLICY: minimum RELOCATABLE: yes
INTRA-POLICY: middle UPPER BOUND: 32
MOUNT POINT: /usr/medusa LABEL: /usr/medusa
MIRROR WRITE CONSISTENCY: on
EACH LP COPY ON A SEPARATE PV ?: yes

lsvg oraclevg
VOLUME GROUP: oraclevg VG IDENTIFIER:
0047549adc32e8f2
VG STATE: active PP SIZE: 1024
megabyte(s)
VG PERMISSION: read/write TOTAL PPs: 279 (285696
megabytes)
MAX LVs: 256 FREE PPs: 43 (44032
megabytes)
LVs: 11 USED PPs: 236 (241664
megabytes)
OPEN LVs: 11 QUORUM: 1
TOTAL PVs: 1 VG DESCRIPTORS: 2
STALE PVs: 0 STALE PPs: 0
ACTIVE PVs: 1 AUTO ON: yes
MAX PPs per PV: 1016 MAX PVs: 32

"Ervins" <ervins.tumulkans@verdi.lv> schrieb im Newsbeitrag
news:6d7d78bb.0401160245.417ea04c@posting.google.c om...
> Recently we added IBM Shark ESS storage to pSeries AIX 4.3.3 server.
> There is one vpath and one VG build on that with 10 filesystem in
> that.
> Problem was today when users tried to access one of ten filesystems
> and console hanged no response but all other filesystem in volumegroup
> worked perfectly.
> Errpt and /var/log/messages with full report level showed nothing.
> After no success of unmounting I did shutdown even that wont work
> becouse couldnt unmount that filesystem. After reboot everythink is
> ok.
> Is there any reasonible thing why that happened.
>
> #lspv
> hdisk0 0047549aaf6e4dbd rootvg
> hdisk1 0047549acdb4037a rootvg
> hdisk2 0047549adc32dfaf None < - not shark disks just SSA
> hdisk3 0047548aa522c597 None < - not shark disks just SSA
> hdisk4 none None <- shark links
> hdisk5 none None
> hdisk6 none None
> hdisk7 none None
> hdisk8 none None
> hdisk9 none None
> vpath0 0047549ad90bfe2b oraclevg
>
>
> #datapath query device
> Total Devices : 1
>
>
> DEV#: 0 DEVICE NAME: vpath0 TYPE: 2105800 POLICY:
> Optimized
> SERIAL: ##########
> ================================================== ========================
> Path# Adapter/Hard Disk State Mode Select
> Errors
> 0 fscsi1/hdisk4 OPEN NORMAL 1073958
> 0
> 1 fscsi1/hdisk5 OPEN NORMAL 1074955
> 0
> 2 fscsi1/hdisk6 OPEN NORMAL 1072486
> 0
> 3 fscsi0/hdisk7 OPEN NORMAL 1080389
> 0
> 4 fscsi0/hdisk8 OPEN NORMAL 1081832
> 0
> 5 fscsi0/hdisk9 OPEN NORMAL 1081868
> 0
>
> lslv medusalv
> LOGICAL VOLUME: medusalv VOLUME GROUP: oraclevg
> LV IDENTIFIER: 0047549adc32e8f2.10 PERMISSION: read/write
> VG STATE: active/complete LV STATE:
> opened/syncd
> TYPE: jfs WRITE VERIFY: off
> MAX LPs: 512 PP SIZE: 1024
> megabyte(s)
> COPIES: 1 SCHED POLICY: parallel
> LPs: 87 PPs: 87
> STALE PPs: 0 BB POLICY: relocatable
> INTER-POLICY: minimum RELOCATABLE: yes
> INTRA-POLICY: middle UPPER BOUND: 32
> MOUNT POINT: /usr/medusa LABEL: /usr/medusa
> MIRROR WRITE CONSISTENCY: on
> EACH LP COPY ON A SEPARATE PV ?: yes
>
> lsvg oraclevg
> VOLUME GROUP: oraclevg VG IDENTIFIER:
> 0047549adc32e8f2
> VG STATE: active PP SIZE: 1024
> megabyte(s)
> VG PERMISSION: read/write TOTAL PPs: 279 (285696
> megabytes)
> MAX LVs: 256 FREE PPs: 43 (44032
> megabytes)
> LVs: 11 USED PPs: 236 (241664
> megabytes)
> OPEN LVs: 11 QUORUM: 1
> TOTAL PVs: 1 VG DESCRIPTORS: 2
> STALE PVs: 0 STALE PPs: 0
> ACTIVE PVs: 1 AUTO ON: yes
> MAX PPs per PV: 1016 MAX PVs: 32

Hi,
last year we had the same problem.
We solved it by updating the FC driver and devices.fcp.disk.rte.
The IBM APAR number is IY45311.

"Andreas Goldammer" <agoldammer@viega.de> wrote in message news:<4007c638$0$270$4d4ebb8e@read.news.de.uu.net> ...
> "Ervins" <ervins.tumulkans@verdi.lv> schrieb im Newsbeitrag
> news:6d7d78bb.0401160245.417ea04c@posting.google.c om...
> > Recently we added IBM Shark ESS storage to pSeries AIX 4.3.3 server.
> > There is one vpath and one VG build on that with 10 filesystem in
> > that.
> > Problem was today when users tried to access one of ten filesystems
> > and console hanged no response but all other filesystem in volumegroup
> > worked perfectly.
> > Errpt and /var/log/messages with full report level showed nothing.
> > After no success of unmounting I did shutdown even that wont work
> > becouse couldnt unmount that filesystem. After reboot everythink is
> > ok.
> > Is there any reasonible thing why that happened.
> >
> > #lspv
> > hdisk0 0047549aaf6e4dbd rootvg
> > hdisk1 0047549acdb4037a rootvg
> > hdisk2 0047549adc32dfaf None < - not shark disks just SSA
> > hdisk3 0047548aa522c597 None < - not shark disks just SSA
> > hdisk4 none None <- shark links
> > hdisk5 none None
> > hdisk6 none None
> > hdisk7 none None
> > hdisk8 none None
> > hdisk9 none None
> > vpath0 0047549ad90bfe2b oraclevg
> >
> >
> > #datapath query device
> > Total Devices : 1
> >
> >
> > DEV#: 0 DEVICE NAME: vpath0 TYPE: 2105800 POLICY:
> > Optimized
> > SERIAL: ##########
> > ================================================== ========================
> > Path# Adapter/Hard Disk State Mode Select
> > Errors
> > 0 fscsi1/hdisk4 OPEN NORMAL 1073958
> > 0
> > 1 fscsi1/hdisk5 OPEN NORMAL 1074955
> > 0
> > 2 fscsi1/hdisk6 OPEN NORMAL 1072486
> > 0
> > 3 fscsi0/hdisk7 OPEN NORMAL 1080389
> > 0
> > 4 fscsi0/hdisk8 OPEN NORMAL 1081832
> > 0
> > 5 fscsi0/hdisk9 OPEN NORMAL 1081868
> > 0
> >
> > lslv medusalv
> > LOGICAL VOLUME: medusalv VOLUME GROUP: oraclevg
> > LV IDENTIFIER: 0047549adc32e8f2.10 PERMISSION: read/write
> > VG STATE: active/complete LV STATE:
> > opened/syncd
> > TYPE: jfs WRITE VERIFY: off
> > MAX LPs: 512 PP SIZE: 1024
> > megabyte(s)
> > COPIES: 1 SCHED POLICY: parallel
> > LPs: 87 PPs: 87
> > STALE PPs: 0 BB POLICY: relocatable
> > INTER-POLICY: minimum RELOCATABLE: yes
> > INTRA-POLICY: middle UPPER BOUND: 32
> > MOUNT POINT: /usr/medusa LABEL: /usr/medusa
> > MIRROR WRITE CONSISTENCY: on
> > EACH LP COPY ON A SEPARATE PV ?: yes
> >
> > lsvg oraclevg
> > VOLUME GROUP: oraclevg VG IDENTIFIER:
> > 0047549adc32e8f2
> > VG STATE: active PP SIZE: 1024
> > megabyte(s)
> > VG PERMISSION: read/write TOTAL PPs: 279 (285696
> > megabytes)
> > MAX LVs: 256 FREE PPs: 43 (44032
> > megabytes)
> > LVs: 11 USED PPs: 236 (241664
> > megabytes)
> > OPEN LVs: 11 QUORUM: 1
> > TOTAL PVs: 1 VG DESCRIPTORS: 2
> > STALE PVs: 0 STALE PPs: 0
> > ACTIVE PVs: 1 AUTO ON: yes
> > MAX PPs per PV: 1016 MAX PVs: 32
>
> Hi,
> last year we had the same problem.
> We solved it by updating the FC driver and devices.fcp.disk.rte.
> The IBM APAR number is IY45311.

patch was already installed. ;(