fsck of a mirrored root filesystem

[7280]

Hi,
I have the following error in /var/adm/messages:
Mar 23 12:17:06 aicprod0 ufs: [ID 879645 kern.notice] NOTICE: /: unexpected free inode 135961, run fsck(1M) -o f

The / fs is mirrored:
d10: Mirror
Submirror 0: d11
State: Okay
Submirror 1: d12
State: Okay
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 54122526 blocks (25 GB)

d11: Submirror of d10
State: Okay
Size: 54122526 blocks (25 GB)
Stripe 0:
Device Start Block Dbase State Reloc Hot Spare
c1t0d0s0 0 No Okay Yes


d12: Submirror of d10
State: Okay
Size: 54122526 blocks (25 GB)
Stripe 0:
Device Start Block Dbase State Reloc Hot Spare
c1t1d0s0 0 No Okay Yes

Filesystem kbytes used avail capacity Mounted on
/dev/md/dsk/d10 26639317 6429533 19943391 25% /

How can I fix this filesystem?
Is this the right approach?
1) boot cdrom -s
2) metadetach d10 d12 --> is this right? do I have to detach
primary or secondary disk?
3) fsck /dev/rdsk/c1t0d0s0
4) metaattach d10 d12
5) reboot

Thanks
Tarek

 

[harris79]

You don't need to split the mirror, the inode problem is in the file system not on the physical disk.

I would -
boot -s
fsck /dev/md/rdsk/d10
reboot



Steve

 

[7280]

Hi,
is it safe to boot in single user and not with cdrom?
If I want to boot with cdrom, what cd do I need?
Software 1 right?

Tarek

 

[bfitzmai]

Yes 7280 use Software Disk 1 of 2. Keep in mind that your metadevices will not be configured when booting off of CD. You will have to run fsck on the raw disks device. Example: fsck -y /dev/rdsk/c0t0d0s0

 

[7280]

Hi,
but why if I run
fsck -m /dev/rdsk/c1t0d0s0
** /dev/rdsk/c1t0d0s0
ufs fsck: sanity check: /dev/rdsk/c1t0d0s0 okay
fsck -m /dev/rdsk/c1t1d0s0
** /dev/rdsk/c1t1d0s0
ufs fsck: sanity check: /dev/rdsk/c1t1d0s0 okay
$ fsck -m /dev/md/rdsk/d11
** /dev/md/rdsk/d11 (NO WRITE)
ufs fsck: sanity check: /dev/md/rdsk/d11 okay
$ fsck -m /dev/md/rdsk/d12
** /dev/md/rdsk/d12 (NO WRITE)
ufs fsck: sanity check: /dev/md/rdsk/d12 okay

Why this says that my filesystems are ok?
Thanks
Tarek

 

[alray]

It's because the "-m" option only checks that the file system is "suitable for mounting", it doesn't do any of the other checks. Fell into this "trap" myself, you can always use the "-n" option to see what the problems are [or some of them at least].

Ray

 

[7280]

Ok, thanks!

I'm really not understanding how fsck works.
On my server I issued fsck -n and I recieved errors.
So I booted my system in single-user mode from cd and run:
fsck -o p /dev/rdsk/c1t0d0s0
fsck -o p /dev/rdsk/c1t1d0s0
The fsck does not give any error. It goes fine.
But then if I reboot the system and try again
fsck -n I recieve the same errors!
So I run the fsck in init 3 and this time the fsck fixed
the errors.
What I'm missing?
From where should fsck be run?
Thanks again all for your precious help!

Tarek