ProLiant Servers (ML,DL,SL)
cancel
Showing results for 
Search instead for 
Did you mean: 

Problems with RedHat 4, DL385 G2, EVA4000

 
Davide Depaoli_3
Valued Contributor

Problems with RedHat 4, DL385 G2, EVA4000

Hello,
I have a customer with follow configuration:

Server: DL385 G2 (AMD Opteron)
Storage: EVA4000
O.S. Red Had ES 4 (last update)
DB: Oracle 10g

He has the problem that the filesystems mounted from the SAN seems to be corrupted.

He told me that others users with AMD servers are the same problem, but I never heard something similar.

Does anyone has any idea ?

Attached the syslog


NOTE: I have cross-posted this message to Server and Storage forums because I'm not sure of the source of the problem.
4 REPLIES
Rob Leadbeater
Honored Contributor

Re: Problems with RedHat 4, DL385 G2, EVA4000

Hi,

Is is possible that another host on the SAN has mounted the same filesystems...?

That could cause filesystem corruption.

Hope this helps,

Regards,

Rob
Davide Depaoli_3
Valued Contributor

Re: Problems with RedHat 4, DL385 G2, EVA4000

Hi,
there aren't other servers on the SAN. This is a demo environment with only one server connected.

Regards,
Davide
Mike Stroyan
Honored Contributor

Re: Problems with RedHat 4, DL385 G2, EVA4000

Your customer says Red Hat ES 4 but the syslog kernel matches Red Hat ES 3 U8. I wonder if it is possible to get file system corruption by creating an ext2/3 file system on a newer release with new features, then mounting it on a system with an older kernel. I would expect the older kernel to refuse to mount a file system that enabled new features that the kernel didn't know. And yet...
Davide Depaoli_3
Valued Contributor

Re: Problems with RedHat 4, DL385 G2, EVA4000

Hi,
the problem is the server CPU, that is defective.