From owner-freebsd-questions@FreeBSD.ORG Sat Oct 4 10:36:41 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 660DF16A4B3; Sat, 4 Oct 2003 10:36:41 -0700 (PDT) Received: from front1.mail.megapathdsl.net (front1.mail.megapathdsl.net [66.80.60.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id C01AC4400E; Sat, 4 Oct 2003 10:36:40 -0700 (PDT) (envelope-from aarong@megapathdsl.net) Received: from [64.32.182.44] (HELO megapathdsl.net) by front1.mail.megapathdsl.net (CommuniGate Pro SMTP 4.1.3) with ESMTP id 120737243; Sat, 04 Oct 2003 10:36:40 -0700 Date: Sat, 4 Oct 2003 10:36:15 -0700 Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v552) To: Greg 'groggy' Lehey From: aarong In-Reply-To: <20031004083007.GF45668@wantadilla.lemis.com> Message-Id: <41617EBD-F691-11D7-A2AE-000393A364C4@megapathdsl.net> Content-Transfer-Encoding: 7bit X-Mailer: Apple Mail (2.552) cc: freebsd-questions@freebsd.org Subject: Re: Issues mirroring drives with Vinum in FreeBSD 4.8-RELEASE X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Oct 2003 17:36:41 -0000 On Saturday, October 4, 2003, at 01:30 AM, Greg 'groggy' Lehey wrote: > [Format recovered--see http://www.lemis.com/email/email-format.html] > > Computer output unwrapped. Having seen that message in many of your replies on the lists, I went out of my way to make sure Mail.app (the OS X mailer) would send messages text/plain and nothing else. Upon further examination of my headers it seems it's adding some 'format=flowed' business to the Content-Type. I can't find a work around; perhaps a look at Entourage is in order. > I'd like to see the complaints. This is why I ask for the information > in the man page or at http://www.vinumvm.org/vinum/how-to-debug.html. I completely overlooked that; my apologies, Greg. This is when booting regularly: ...dmesg... vinum: reading configuration from /dev/da0s1h vinum: reading configuration from /dev/da1s1h vinum: using volume root for root device Mounting root from ufs:/dev/vinum/root swapon: adding /dev/vinum/swap as swap device fstab: /etc/fstab:9: Inappropriate file type or format Automatic boot in progress... /dev/vinum/root: FILESYSTEM CLEAN; SKIPPING CHECKS /dev/vinum/root: clean, 45939 free (633 frags, 5595 blocks, 1.0% fragmentation) fstab: /etc/fstab:9: Inappropriate file type or format fstab: /etc/fstab:9: Inappropriate file type or format /dev/vinum/var: UNALLOCATED I=44035 OWNER=root MODE=0 /dev/vinum/var: SIZE=0 MTIME=Oct 3 22:54 2003 /dev/vinum/var: NAME=/run/dmesg.boot /dev/vinum/var: UNEXPECTED SOFT UPDATE INCONSISTENCY; RUN fsck MANUALLY. Then I'm dropped into single user mode. Line 9 of /etc/fstab is proc, I have no idea why its complaining since its valid, and I never changed it. # fsck -n /dev/vinum/var ** /dev/vinum/var (NO WRITE) ** Last Mounted on /var ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups FREE BLK COUNT(S) WRONG IN SUPERBLK SALVAGE? no SUMMARY INFORMATION BAD SALVAGE? no ALLOCATED FRAG 1277319 MARKED FREE BLK(S) MISSING IN BIT MAPS SALVAGE? no ALLOCATED FRAG 1368488 MARKED FREE ...same message until 1368493... 74 files, 146 used, 2015829 free (141 frags, 251961 blocks, 0.0% fragmentation) fsck'ing the rest of the volumes produces more of the same; one notable difference is root has a reference count error in addition to missing bit maps, bad summary information, and incorrect number of block counts in the superblock. The usr volume seems to be fine according to fsck, however. vinum list correctly notes both drives are up, four volumes have two plexes, the 8 plexes are up and sized, and the subdisks are up. fsck -n /dev/vinum/var before mirroring produced no complaints, otherwise I'd conclude that I just mirrored a corrupt plex but that doesn't seem to be the case. The last lines in /var/log/vinum_messages are *** vinum started *** and list shortly there after. /var/log/messages reads exactly like dmesg, only with time stamps. Nothing useful pertaining to Vinum in either file. Regards, -aarong > Send the information I ask for and I might find it. > > Greg > -- > When replying to this message, please copy the original recipients. > If you don't, I may ignore the reply or reply to the original > recipients. > For more information, see http://www.lemis.com/questions.html > See complete headers for address and phone numbers. > NOTE: Due to the currently active Microsoft-based worms, I am limiting > all incoming mail to 131,072 bytes. This is enough for normal mail, > but not for large attachments. Please send these as URLs. >