Date: Fri, 29 Jul 2005 16:08:41 +0100 (BST) From: "Angus MacGyver" <macgyver@calibre-solutions.co.uk> To: ticso@cicely.de Cc: Pawel Jakub Dawidek <pjd@freebsd.org>, freebsd-alpha@freebsd.org Subject: Re: Gmirror + AXP + 5.4.. (was Vinum + AXP + 5.4) Message-ID: <40417.193.131.192.94.1122649721.squirrel@webmail.calibre-solutions.co.uk> In-Reply-To: <20050729144257.GO26656@cicely12.cicely.de> References: <1121681574.5897.7.camel@falcon.calibre-solutions.co.uk> <1122398630.5860.7.camel@yavin4.calibre-solutions.co.uk> <20050726201815.GI46538@darkness.comp.waw.pl> <1122411849.5860.12.camel@yavin4.calibre-solutions.co.uk> <20050726212616.GL46538@darkness.comp.waw.pl> <1122446849.5860.25.camel@yavin4.calibre-solutions.co.uk> <20050727070537.GM46538@darkness.comp.waw.pl> <20050727084648.GC10772@calibre-solutions.co.uk> <20050727205850.GS46538@darkness.comp.waw.pl> <40377.193.131.192.94.1122647311.squirrel@webmail.calibre-solutions.co.uk> <20050729144257.GO26656@cicely12.cicely.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Bernd Walter said: >> >> 'Cept i have now has UFS panics... >> >> Upon creating a jail using Ths Lab's webmin insert, and creating a disk >> based install, of which there are already 3 created and installed.. >> >> /data/test: bad dir ino 60 at offset 0: mangled entry >> panic: ufs_dirbad: bad dir >> Uptime: 3h21m13s >> >> ... and so starts a reboot.. >> >> NOW.. >> >> Question i have to ask is this, as I cannot find a clear statement, and >> "man gmirror" only appears to hint at the metadata... >> >> I installed using sysinstall, and split the disk thus.. >> >> corse# bsdlabel /dev/da0 >> # /dev/da0: >> 8 partitions: >> # size offset fstype [fsize bsize bps/cpg] >> a: 524288 0 4.2BSD 2048 16384 32776 >> b: 2099200 524288 4.2BSD 2048 16384 28528 >> c: 35843670 0 unused 0 0 # "raw" part, >> don't edit >> d: 1048576 2623488 4.2BSD 2048 16384 8 >> e: 1048576 3672064 4.2BSD 2048 16384 8 >> f: 7340032 4720640 4.2BSD 2048 16384 28528 >> g: 23782998 12060672 4.2BSD 2048 16384 28528 >> >> >> I then copied this label to the second drive and setup the mirrors as >> described earlier. >> (for those that didnt see it....) >> corsec# gmirror status >> Name Status Components >> mirror/md0 COMPLETE da0a >> da1a >> mirror/md1 COMPLETE da0b >> da1b >> mirror/md2 COMPLETE da0d >> da1d >> mirror/md3 COMPLETE da0e >> da1e >> mirror/md4 COMPLETE da0f >> da1f >> mirror/md5 COMPLETE da0g >> da1g >> >> i.e. for each side of the mirror, I am using an identically sized slice >> (partition/lump) of each disk.. >> >> Now, question is, where does it store the metadata ? >> Manual says last sector. >> Ok, so in my case, is that last sector of c? (the whole disk), for ALL >> mirror devices, or the last sector of each slice on each disk ??? > > The last sector of the provider, e.g. da0a/da1a for md0 in your case. > Normally one would use the entire disks and then bsdlabel the mirror. OK, Right.. Makes sense. So when the disk gets sliced in sysinstall, and you install onto it, then create the individual slices on the disk that will be the mirror i guess you need to create the new slices one sector smaller than were on the install disk... (oops here) >> So what happens when disks ineveitably get full, is the metadata "safe" >> ? > > Normaly the resulting disk should be a sector smaller than the > provider, but if that really happened that wouldn't explain this error. > Typically this kind of problems arise if a mirror is our of sync. > I would suggest a resync of the mirror and then a forced fsck. Very odd, just done one ok, done a second ok, and a third dies... I will however keep investigating.. >> Or would I be best off starting again, and creating a mirror device that >> has the ENTIRE disk as the device, and then slice that mirror device up >> for /, /var /usr etc... > > That's what most people do. ... in the meantime, i will go to single disk mirro device... yeah, rapidly come to that conclusion. Thankfully it is not too painful to do.. It does make more sense. >> I am used to Solaris Disk Suite's mirroring, and we setup a slice on >> each >> disk JUST to keep the metadata in, so this causing me some brain >> troubles >> at the moment.. > > Special partitions for metadata is nice, but Disk Suite fails > miserably if you shuffle disks or have to move a raid to another > machine, because it identifies disks by devicenames, while GEOM > identifies eachs provider by it's metadata. SDS has + points, and I use it extensively at work. (well you would to save on Veritas licences) >> Most of the "howto" doc are x86 and only for IDE devices, neither of >> which >> I am using. > > Beside that RAID on IDE scares me there is not much difference, just > that we don't use fdisk-style slices on alpha. IDE scares me period.. ;-) And thankfully fdisk-style ain't on any sensbile platform (Sun/AXP) Thanks for your input. AM > -- > B.Walter BWCT http://www.bwct.de > bernd@bwct.de info@bwct.de > > -- I ain't perfect ... ...Yet
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?40417.193.131.192.94.1122649721.squirrel>