weird problem with the filesystem...

[Asya]

Hi,

I have a really weird problem.

ls on the directory shows the file as if it exists.
ls -la doesn't show it.
ls on the file shows that it doesn't exist.

bash-2.05b# rm nfs.server
rm: cannot stat nfs.server: I/O error

/var/adm/sys/syslog.log has the following;
Jun 16 10:11:05 giant automount[511]: WARNING: /etc/mnttab: line 23163635: bad entry removed

it started form line 1...and just goes on and on....i can't access /etc/mnttab

bash-2.05b# ls -la /etc/mnttab
-rw-r--r-- 1 root sys 1134 Jun 8 00:52 /etc/mnttab
bash-2.05b# cat /etc/mnttab
cat: read error: No such file or directory

What could be the problem..? Do i need to rebuild the server? This just seems too weird..

Thank you!
Asya

[James R. Ferguson]

Hi:

Try:

# rm /etc/mnttab
# mount all

Regards!

...JRF...

[Asya]

I did, thank you. This fixed /etc/mnttab

I'm still having problem with other files.

bash-2.05b# more nfs.server
nfs.server: I/O error

Thanks..

[Darrel Louis]

Hi,

As James already suggested recreate your mnttab, with the mount -a command.
Is this a NFS server or is it making use of NFS shares?

Darrel

[Asya]

Darrel,

it's NFS client..i was just using nfs.server file as an example..

bash-2.05b# more nfs.client
nfs.client: I/O error

thank you

[Darrel Louis]

Hi Asya,

Are you having problems with the NFS-share or the OS filesystem?

Darrel

[Asya]

Darrel,

OS Filesystem i think.
Some files i can access, some i can't.

like nfs.server and nfs.client are giving me this I/O error. Other files in the same directory work just fine. Seems like all nfs.* files are giving me a problem....nfsconf file is okay.

What would be the reason..?
Thank you

[Asya]

Darrel,

So is..

bash-2.05b# more /etc/rc.config.d/syslogd
/etc/rc.config.d/syslogd: I/O error

[Darrel Louis]

Hi,

It could be a faulty disk?
Can you check the following:
# dmesg
Does it report any errors.
# vgdisplay -v vg00
Do you see any stale extends.

Is your root disk mirrored?

Darrel

[Asya]

Darrel,

Yes..
vxfs: mesg 016: vx_ilisterr - / file system error reading inode 184
vxfs: mesg 016: vx_ilisterr - / file system error reading inode 188
vxfs: mesg 016: vx_ilisterr - / file system error reading inode 160
vxfs: mesg 016: vx_ilisterr - / file system error reading inode 163
vxfs: mesg 016: vx_ilisterr - / file system error reading inode 164
vxfs: mesg 016: vx_ilisterr - / file system error reading inode 169
vxfs: mesg 016: vx_ilisterr - / file system error reading inode 172
vxfs: mesg 016: vx_ilisterr - / file system error reading inode 175
vxfs: mesg 016: vx_ilisterr - / file system error reading inode 179
vxfs: mesg 016: vx_ilisterr - / file system error reading inode 182
vxfs: mesg 016: vx_ilisterr - / file system error reading inode 184
vxfs: mesg 016: vx_ilisterr - / file system error reading inode 188
vxfs: mesg 016: vx_ilisterr - / file system error reading inode 175
vxfs: mesg 016: vx_ilisterr - / file system error reading inode 175
vxfs: mesg 016: vx_ilisterr - / file system error reading inode 160
vxfs: mesg 016: vx_ilisterr - / file system error reading inode 160
vxfs: mesg 016: vx_ilisterr - / file system error reading inode 669
vxfs: mesg 016: vx_ilisterr - / file system error reading inode 669
vxfs: mesg 016: vx_ilisterr - / file system error reading inode 669

Does this mean the disk is faulty?

Thank you!

[Miguel Hernández]

Write the output of:

#vgdisplay -v vg00

As Darrel says, if there's is any stale extend your disk is damage.

[Darrel Louis]

Hi,

Do you see stale extends when executing vgdisplay -v vg00.

This looks like a hardware problem.

Darrel

[Asya]

Here it is..

# vgdisplay -v vg00
--- Volume groups ---
VG Name /dev/vg00
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 7
Open LV 7
Max PV 16
Cur PV 1
Act PV 1
Max PE per PV 4384
VGDA 2
PE Size (Mbytes) 8
Total PE 4374
Alloc PE 3151
Free PE 1223
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

--- Logical volumes ---
LV Name /dev/vg00/lvol1
LV Status available/syncd
LV Size (Mbytes) 2000
Current LE 250
Allocated PE 250
Used PV 1

LV Name /dev/vg00/lvol2
LV Status available/syncd
LV Size (Mbytes) 8192
Current LE 1024
Allocated PE 1024
Used PV 1

LV Name /dev/vg00/lvol3
LV Status available/syncd
LV Size (Mbytes) 360
Current LE 45
Allocated PE 45
Used PV 1

LV Name /dev/vg00/lvol4
LV Status available/syncd
LV Size (Mbytes) 200
Current LE 25
Allocated PE 25
Used PV 1

LV Name /dev/vg00/lvol5
LV Status available/syncd
LV Size (Mbytes) 1664
Current LE 208
Allocated PE 208
Used PV 1

LV Name /dev/vg00/lvol6
LV Status available/syncd
LV Size (Mbytes) 4600
Current LE 575
Allocated PE 575
Used PV 1

LV Name /dev/vg00/lvol7
LV Status available/syncd
LV Size (Mbytes) 8192
Current LE 1024
Allocated PE 1024
Used PV 1


--- Physical volumes ---
PV Name /dev/dsk/c2t6d0
PV Status available
Total PE 4374
Free PE 1223
Autoswitch On

[Darrel Louis]

Hi,

I thought you said in one of the previous post that vg00 is mirrored. According to your vgdisplay output there is only one disk attached to vg00.
I don't see any stale extends on the disk.

Have you performed a fsck?
man fsck

Darrel

[Asya]

Uhm..no, i didn't say it was mirrored. I actually forgot to respond to your question regarding it.

I will run fsck...will let you know how it went.

thanks!

[Asya]

Hello,

The server crashed when i tried to reboot it into single user mode. Every time it starts dumping memory..gets to 100% and reboots.
This is the second time a similar thing is happening with our HP-UX servers...last time i had to reinstall the server to get it to work.

Why would this happen? Both of the servers were gotten at around the same time, have the same hardware and from the same company that sells refurbished hardware. It still should be under warranty...

Thank you!