gmirror w/ softupdates fsck problem
Hello, I have one box with several gmirror filesystems. When the box panics I always have to reconnect lost inodes and also inconsistent filesystems. I never had this problem with non gmirrored mountpoints. Also, the mirrored mountpoints are almost completely idel regarding writes. Here's an error I don't know how to solve: ** /dev/mirror/dns (NO WRITE) ** Last Mounted on /§DNS ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames MISSING '.' I=149 OWNER=root MODE=40700 SIZE=9216 MTIME=Feb 22 08:21 2005 DIR=? UNEXPECTED SOFT UPDATE INCONSISTENCY CANNOT FIX, FIRST ENTRY IN DIRECTORY CONTAINS #058295 UNEXPECTED SOFT UPDATE INCONSISTENCY MISSING '..' I=149 OWNER=root MODE=40700 SIZE=9216 MTIME=Feb 22 08:21 2005 DIR=/lost+found UNEXPECTED SOFT UPDATE INCONSISTENCY CANNOT FIX, SECOND ENTRY IN DIRECTORY CONTAINS #058296 UNEXPECTED SOFT UPDATE INCONSISTENCY ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 10092 files, 123147 used, 366123 free (5491 frags, 45079 blocks, 1.1% fragmentation) Does anybody know why this error can happen? And how do I solve the missing"."? I thought softupdates guarantees that this cannot happen. Maybe it doesn't work in combination with gmirror? Thanks, -Harry pgp3iH3gB1GbN.pgp Description: PGP signature
Re: fsck problem
Jaime wrote: New info for this problem: S array.p0.s0 crashed S array.p0.s1 up S array.p0.s2 up S array.p0.s3 stale Should I just "vinum start" at the shell? Well, at this point you've got vinum started now. I would fix the raid problem before bothering with an fsck, if it were me. -- Bill Moran Potential Technologies http://www.potentialtech.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: fsck problem
New info for this problem: S array.p0.s0 crashed S array.p0.s1 up S array.p0.s2 up S array.p0.s3 stale Should I just "vinum start" at the shell? TIA, Jaime To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: fsck problem
On Mon, 24 Feb 2003, Jaime wrote:
> As I type, the server is in single user mode. The fsck commands
> result in:
> CAN NOT READ: BLK 16
>
vinum is not started.
--
:{ [EMAIL PROTECTED]
Andy Farkas
System Administrator
Speednet Communications
http://www.speednet.com.au/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
fsck problem
I have a RAID-5 array on /home via vinum. This morning, the server (running 4.8-PRERELEASE, compiled last week) wouldn't allow anyone to login via ssh, imap, or console. So I had someone reboot the server via control-alt-delete. Then it said that not all processes would dia, use ps axl. Of course, since we couldn't login, this was pointless advise. :) We then used the reset button on the chassis. As I type, the server is in single user mode. The fsck commands result in: CAN NOT READ: BLK 16 I've looked at http://docs.freebsd.org/44doc/smm/03.fsck/paper.html and found its information less than encouraging. Since its said to "seek a guru", I was hoping that someone here could help my poor little school district. If this wasn't on vinum, I would assume that my next step would be to assume a dead drive and remove it and move on. However, this is a vinum array. I'm not sure how it could be a bad drive if the array is composed of 4 drives. Any help, pointers, etc. would be GREATLY appreciated. My entire school district is effectively dead in the water until this server is running again. TIA, Jaime To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
