Corrupted FileSystems on Linux/390 causing failure of WebSphere installation
 Technote (troubleshooting)
 
Problem(Abstract)
Corrupted filesystems can cause a failure of the installation of the WebSphere 5.0 CD or Fix Packs (PTFs), or in the operation of WebSphere itself.

Recognizing corrupted files:
If WebSphere is found in the filesystem /data1, the following command can identify corrupted files. If the output is similar to those below their filesystem may be corrupted.

ll -R /data1 | grep "?"

?rwxr-Sr-x 58853 3857049061 3857049061 3857049061 Feb 15 1956 createIncTable.err
?rwxr-Sr-x 58853 3857049061 3857049061 3857049061 Feb 15 1956 wsadmin.valout
 
Cause
This can be caused by incorrectly formatting of the device (/dev/dasdb in this case). The "dasdfmt" command formats filesystems in one of two layout schemes as shown here:
 
Resolving the problem
When formatting a filesystem the customer should include the "-d ldl" option.

To correct this problem, reformat the filesystem as follows:

  1. Unmount the filesystem:
    umount /data1
  2. Format the device:
    dasdfmt -b 4096 -f /dev/dasdb -d ldl
  3. Make the filesystem:
    mke2fs -b 4096 /dev/dasdb1
  4. Mount the filesystem:
    mount -t ext2 /dev/dasdb1 /data1

NOTES:
  • In the example, above, assume device to be '/dev/dasdb' and the filesystem to be '/data1'.
  • All data on the /dev/dasdb device (filesystem /data1 in this case) will be
    lost by reformatting. Any data needed should be copied from the corrupted filesystem
    before beginning this process.
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Install
Operating system(s): Linux
Software version: 5.0
Software edition:
Reference #: 1110024
IBM Group: Software Group
Modified date: May 14, 2003