Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

9090

January 6th, 2011 12:00

corrupted filesystem. Unable to umount and run fsck

Hi there

I have 1 fs which was corrupted in datamover panic (or dm panicked due to corruption???). Ran nas_fsck and I could mount it. Now in full backup I found 6 corrupted files (they're ok in pre-panic checkpoints). Can't delete them. Invalid file handle. Can't umount the fs and run fsck again.

Failure in umout is:

Error 3104 filesystem has backups in use.

Any ideas anybody or should I make SR?

--

Jussi

8.6K Posts

January 6th, 2011 15:00

open a SR

1 Rookie

 • 

20.4K Posts

January 6th, 2011 15:00

try unmounting checkpoints first and then the file system.

51 Posts

January 6th, 2011 15:00

yeah

typically there's no panics, corrupted filesystems, checkpoints that are active but unmounted.

Actually first time I have filesystem corruption. I think second time dm panicked.

But anyway sr is made, let's see what support has to say.

--

Jussi

51 Posts

January 6th, 2011 15:00

Thought about that. I'm just not sure I can remount the checkpoints. That's not really a problem. Have archive, redup and make it smaller anyway so checkpoints are gone anyway.

Anyway I'll open SR and see what support has to say abot that. Had 3 panics a day just before christmas (primary, just after failover the secondary, and later primary again). So now it's time to sort things out.

--

Jussi

1 Rookie

 • 

20.4K Posts

January 6th, 2011 15:00

typically you can re-mount checkpoints without issues ..but yeah with panic better have EMC folks check it out.

6 Posts

October 4th, 2018 12:00

Hi Everyone,

I have same issue, Please share the resolution

8.6K Posts

October 5th, 2018 02:00

same advice - open a service request and have support troubleshoot and fix

No Events found!

Top