Summary: VXFS errors...

From: Vipin Gupta (vgupta@legato.com)
Date: Fri Sep 08 2000 - 13:40:31 CDT


Hello,

Well I got 5 replies to my post and most of them suggested rebuilding the file
system and do a backup restore. That is what I finally did. Thanks to Danny
Cox, Don Grant, Vaibhav Gawde, Mike Salehi and Gary Jarrel.

Though I also posted my problem to Veritas list
mailto:veritas-vx@mailman.eng.auburn.edu (thanks to Don Grant), but as I am
not a member of list , it is still waiting for the moderator approval.

Thanks Guys.

Vipin

My Original Post:

> Hello,
>
> I have vxfs (I think latest version) installed on one of the 8 GB disk
> on a Solaris 2.6 system.
> The disk has 2 partitions of 4 GB each.
> While one partition is doing good and is clean, the other file systems
> is having problems:
>
> I get following errors while doing full file-system check:
>
> # fsck -o full -y /dev/rdsk/c0t1d0s5
> vxfs fsck: file system had I/O error(s) on meta-data.
> vxfs fsck: file system had I/O error(s) on user data.
> intent log marked bad in super-block
> cannot perform log replay
> fileset 1 primary-ilist inode 65 has invalid number of blocks (13152)
> fileset 1 primary-ilist inode 97 has invalid number of blocks (13152)
> no valid ILISTs for fileset 999
> file system check failure, aborting ...
>
> I can "dd" the this file system and pipe it to /dev/null without any
> errors.
>
> Any idea on how to fix this problem. I will aprreciate any help.
>
> Vipin
>


attached mail follows:


Hello,

I have vxfs (I think latest version) installed on one of the 8 GB disk
on a Solaris 2.6 system.
The disk has 2 partitions of 4 GB each.
While one partition is doing good and is clean, the other file systems
is having problems:

I get following errors while doing full file-system check:

# fsck -o full -y /dev/rdsk/c0t1d0s5
vxfs fsck: file system had I/O error(s) on meta-data.
vxfs fsck: file system had I/O error(s) on user data.
intent log marked bad in super-block
cannot perform log replay
fileset 1 primary-ilist inode 65 has invalid number of blocks (13152)
fileset 1 primary-ilist inode 97 has invalid number of blocks (13152)
no valid ILISTs for fileset 999
file system check failure, aborting ...

I can "dd" the this file system and pipe it to /dev/null without any
errors.

Any idea on how to fix this problem. I will aprreciate any help.

Vipin

S
U BEFORE POSTING please READ the FAQ located at
N ftp://ftp.cs.toronto.edu/pub/jdd/sun-managers/faq
. and the list POLICY statement located at
M ftp://ftp.cs.toronto.edu/pub/jdd/sun-managers/policy
A To submit questions/summaries to this list send your email message to:
N sun-managers@ececs.uc.edu
A To unsubscribe from this list please send an email message to:
G majordomo@sunmanagers.ececs.uc.edu
E and in the BODY type:
R unsubscribe sun-managers
S Or
. unsubscribe sun-managers original@subscription.address
L To view an archive of this list please visit:
I http://www.latech.edu/sunman.html
S
T

S
U BEFORE POSTING please READ the FAQ located at
N ftp://ftp.cs.toronto.edu/pub/jdd/sun-managers/faq
. and the list POLICY statement located at
M ftp://ftp.cs.toronto.edu/pub/jdd/sun-managers/policy
A To submit questions/summaries to this list send your email message to:
N sun-managers@sunmanagers.ececs.uc.edu
A To unsubscribe from this list please send an email message to:
G majordomo@sunmanagers.ececs.uc.edu
E and in the BODY type:
R unsubscribe sun-managers
S Or
. unsubscribe sun-managers original@subscription.address
L To view an archive of this list please visit:
I http://www.latech.edu/sunman.html
S
T



This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:14:16 CDT