1833788 Members
2254 Online
110063 Solutions
New Discussion

Re: BAD FS

 
SOLVED
Go to solution
Nobody's Hero
Valued Contributor

BAD FS

Hello All,
I have a test Kclass with a corrupted vxfs filesystem. I had to abort a restore and it must have corrupted the FS. It wont mount. I get "vxfs mount: /dev/vg02/lvol1 is corrupted,needs checking". So I run a "fsck -F vxfs -n /dev/vg02/lvol1". Here is the output from my fsck.

[mailtest:/]# fsck -F vxfs -n /dev/vg02/lvol1
vxfs fsck: file system had I/O error(s) on user data.
pass0 - checking structural files
pass1 - checking inode sanity and blocks
pass2 - checking directory linkage
pass3 - checking reference counts
pass4 - checking resource maps
OK to clear log? (ynq)n
sanity checks/updates have not been completed - restart? (ynq)n

The system looks like it prompts for a y or n, but it enters a 'n' automatically. It does not give me a chance to answer the question. Any ideas? The file system is 3 4gb drives, striped for 1 12gb filesystem, called oracle_test.




UNIX IS GOOD
10 REPLIES 10
Helen French
Honored Contributor
Solution

Re: BAD FS

Hi Robert:

1) It will not prompt you because you have already given '-n' with fsck. This will answer all questions with 'n'. See man fsck_vxfs

2) Run this command:

# fsck -F vxfs -o full /dev/vg02/rlvol1

HTH,
Shiju
Life is a promise, fulfill it!
ashish nanjiani
Frequent Advisor

Re: BAD FS

Is it because you have said no to clear logs?I guess you should try to say yes on to clear logs and see what the systems does.

ashish
Jeff Schussele
Honored Contributor

Re: BAD FS

Hi Robert,

The -n is forcing the "No" responses.
Drop it from the command line OR if you do want "Yes" responses forced substitute -y for it.

Rgds,
Jeff
PERSEVERANCE -- Remember, whatever does not kill you only makes you stronger!
John Carr_2
Honored Contributor

Re: BAD FS

Hi

try

umount /dev/vg02/lvol1
fsck -y /dev/vg02/lvol1

John.
Victor_5
Trusted Contributor

Re: BAD FS

Don't use switch -n.
ashish nanjiani
Frequent Advisor

Re: BAD FS

Continue to my above answer remove -n from your command.That's where the problem lies.
Sandip Ghosh
Honored Contributor

Re: BAD FS

Since you have given -n as a option it has taken no as a reply. Run the same with -y option. It may come back okay.

Sandip
Good Luck!!!
John Carr_2
Honored Contributor

Re: BAD FS

Hi

of course Shiju answer is probably the best for you as you can answer interactively.

cheers
John.
MANOJ SRIVASTAVA
Honored Contributor

Re: BAD FS

Hi Robert

The problem is that you are using a -n option

fsck -F vxfs -n /dev/vg02/lvol1"

please use -y option so that it will ansewer y to the questions if you want that way .

Thaat should solve it.

fsck -F vxfs -y /dev/vg02/rlvol1


Manoj Srivastava
Nobody's Hero
Valued Contributor

Re: BAD FS

Thank You...........
UNIX IS GOOD