Single filesystem wont mount after AIX upgrade

[jstauff4]

Hello,

I have a single filesystem that will not mount after a 44p 170 upgrade from AIX 5.1 to 5.3 (migration). This filesystem is on an external hard drive. When I try to mount, this is the error I receive:

mount: 0506-324 Cannot mount /dev/TMPTMP on /tmp/tmp: There is an input or output error.

This is the stanza in /etc/filesystems:

/tmp/tmp:
dev = /dev/TMPTMP
vfs = jfs
log = /dev/loglv00
mount = true
check = false
options = rw
account = false

This is the output from lslv:

thermal3-root:/etc # lslv TMPTMP
LOGICAL VOLUME: TMPTMP VOLUME GROUP: datavg1
LV IDENTIFIER: 0005842862a913d9.12 PERMISSION: read/write
VG STATE: active/complete LV STATE: closed/syncd
TYPE: jfs WRITE VERIFY: off
MAX LPs: 512 PP SIZE: 64 megabyte(s)
COPIES: 1 SCHED POLICY: parallel
LPs: 13 PPs: 13
STALE PPs: 0 BB POLICY: relocatable
INTER-POLICY: minimum RELOCATABLE: yes
INTRA-POLICY: middle UPPER BOUND: 32
MOUNT POINT: /tmp/tmp LABEL: /tmp/tmp
MIRROR WRITE CONSISTENCY: on/ACTIVE
EACH LP COPY ON A SEPARATE PV ?: yes
Serialize IO ?: NO

I noticed LV STATE is closed?

Any help would be greatly appreciated...thanks.

Jim

 

[KenCunningham]

Jim - probably asking the obvious, but you have checked the cables/connections? Are there any status lights on the drive?

I want to be good, is that not enough?

 

[jstauff4]

Ken,

I have a green light on the front of the drive and I have checked all of the cables.

Thanks,

Jim

 

[MoreFeo]

Any other filesystems in the same external drive?
What's the output of lspv -l on this drive?

 

[ogniemi]

does the /tmp/tmp mount point still exists after the migration?

 

[jstauff4]

ogniemi,

I had to re-create the tmp mount point directory under /tmp after the migration.


MoreFeo,

This is the only filesystem on this drive.

 

[khalidaaa]

Have you checked zoning in the storage switch (if it is SAN for example?)

Do you see the datavg1 from the lsvg output?

If not then you might have to varyonvg datavg1 and then mount the filesystem!

Regards,
Khalid

 

[jstauff4]

Khalid,

This is a direct attached SCSI drive on the workstation.
If I need to varyon this vg, would this cause problems for other LV's in the VG?

The LV STATE shows closed...what would that point to? Hardware failure, etc?

Thanks to all for your input.

Jim

 

[MoreFeo]

This filesystem is in datavg1, show us the output of:

# lsvg
# lsvg -o
# lspv
# lsvg datavg1
# lsvg -p datavg1
# lsvg -l datavg1

The state of closed is normal, since it's not mounted.

 

[p5wizard]

No it is closed as in not open ;-)

As you haven't yet been able to mount the filesystem that is on the LV, the LV stays closed.

show the output of these commands please:

lsvg datavg1
lsvg -l datavg1
lsvg -p datavg1

I'd hazard a guess that the LOG LV for this filesystem is not present; If you show the requested info I can look into it further.


HTH,

p5wizard

 

[Chapter11]

p5wizard is probably on the spot with the loglv for it missing.

 

[jstauff4]

All,

I was able to get the /tmp/tmp filesystem to mount after I ran an fsck -y on the device.

Thanks to all of you for your help and for all of the sugestions...

Jim