IC5Notice: We have upgraded developerWorks Community to the latest version of IBM Connections. For more information, read our upgrade FAQ.
Topic
  • 2 replies
  • Latest Post - ‏2012-08-30T13:50:57Z by Ramu Surneni
Ramu Surneni
Ramu Surneni
3 Posts

Pinned topic Shared SAN disk gets corrupted, using with TSA for RHEL

‏2012-08-20T05:58:04Z |
Hi,

I have some problem regarding the SAN shared disk using with TSA, I'm not sure where the procedure went wrong but disk get corrupted if install any thing into shared disk (i tried to create DB in the shared disk path with db2inst1). And if i try to mount manually i get below pasted error.

root@tivnode1 ~# mount /sharedisk
mount: wrong fs type, bad option, bad superblock on /dev/vg1/lv0,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

Prior installation/ creation of database, i have tested the mount and umount by moving resource group in TSA, and it works fine..
I also tested by creating txt file manually in the shared disk from node 1 and modified successfully from node2.
Because of this i couldn't go head anymore.

Is any aware of this problem, can plz help regarding. Thanks in advance
Updated on 2012-08-30T13:50:57Z at 2012-08-30T13:50:57Z by Ramu Surneni
  • sedgewick_de
    sedgewick_de
    36 Posts

    Re: Shared SAN disk gets corrupted, using with TSA for RHEL

    ‏2012-08-30T13:21:08Z  
    Hi Ramu,

    I suggest creating a mountable filesystem with mkfs with TSA in manual mode. Then make sure you have a suitable tiebreaker defined and run your bucket of high-availability tests.
    If you see filesystem corruption again, you could open up a PMR.

    Regards,
    Markus Müller
  • Ramu Surneni
    Ramu Surneni
    3 Posts

    Re: Shared SAN disk gets corrupted, using with TSA for RHEL

    ‏2012-08-30T13:50:57Z  
    Hi Ramu,

    I suggest creating a mountable filesystem with mkfs with TSA in manual mode. Then make sure you have a suitable tiebreaker defined and run your bucket of high-availability tests.
    If you see filesystem corruption again, you could open up a PMR.

    Regards,
    Markus Müller
    HI

    My issue was resolved!

    Procedure followed was wrong, as i was formatting the disk from two nodes, it just requires to format from NODE1 and move the volumes from 'NODE1' to 'NODE2' using the following steps.

    1. Unmounting the volumes from 'NODE1'.
    2. Exporting the VG from 'NODE1'.
    3. Importing the VG on 'NODE2'.
    4. Activating the VG on 'NODE2'.
    5. Mounting the volumes on 'NODE2'.

    thank you