[bvijaycom]

Dear All,

I am having AIX 5.3 server and HACMP cluster enabled.

At present we are not able to handle any file operation from one files system (basically this file system is configured through HACMP cluster).

When I try to do fsck I am getting following error. I think super block is corrupt.

Also since this file system is under cluster control,i am not able to unmount (If i try to unmount it is saying resource is busy) .

Can anyone help me resolve this issue?


bash-3.00# fsck -p /iims-home-local

The current volume is: /dev/iims-home
File system is currently mounted.
Invalid file system size in the primary superblock.
Primary superblock is corrupt.
Invalid file system size in the secondary superblock.
Secondary superblock is corrupt.
fsck: 0507-018 Superblock is corrupt and cannot be repaired.
Both primary and secondary copies are corrupt. Cannot continue.

Thanks & Regards,
BVIJAY

[john.samons]

Hi BVIJAY,

It's not quite clear. What is the problem you're experiencing?

AIX TL level and HACMP level please...

If you are staying that you can't do any file system operations? What do you mean...? Can you still write to the FS? Is production currently affected?

Or do you mean you cannot do operations such as dynamically increase the FS size...?

The FS isn't really under HACMP control, it's just managed by HACMP for failover.

It's also expected to get those fsck errors as your file system is currently mounted, which can cause ambigious output. For a proper fsck you have to unmount the file system first - and obviously before unmounting you would need to stop all processes accessing it, i.e. the application probabaly managed by HACMP.

Book some downtime on the system before you continue...

You could vi the /etc/filesystems file and set the check = true for this filesystem and failover to that system, however if you want a more direct approach....I would do the following...

---Assuming you have a failover cluster---
-bring the RG down
-this should stop your application, unmount the fs and varyoff the vg... if it's managed by HACMP
-varyonvg -c yourvg
then do fsck -y yourfs

Give us a bit more info and I've sure we'll be able to help more...