Date: Wed, 2 May 2001 15:13:26 -0400 (EDT) From: Brian Skrab <bgs@pinky.us.net> To: <freebsd-questions@freebsd.org> Subject: Vinum & FreeBDS 4.3-stable??? Message-ID: <Pine.BSF.4.32.0105021459520.326-100000@pinky.us.net>
next in thread | raw e-mail | index | archive | help
Hello, I recently moved into a nice new Athlon 800Mhz motherboard and decided to start with a fresh install of FreeBSD 4.2->4.3-stable. With all the spring cleaning going on, I decided to re-create my Vinum RAID5 volume for completeness. I have 3 20GB IDE drives plugged into the two IDE controllers on the motherboard and have been attempting to use the following configuration to build a stable RAID5 volume: ----- vinum.config drive d1 device /dev/ad0s1e drive d3 device /dev/ad2s1e drive d2 device /dev/ad3s1e volume raid plex name raid.p0 org raid5 512s vol raid sd name raid.p0.s0 drive d1 plex raid.p0 len 39880704s driveoffset 265s plexoffset 0s sd name raid.p0.s1 drive d2 plex raid.p0 len 39880704s driveoffset 265s plexoffset 512s sd name raid.p0.s2 drive d3 plex raid.p0 len 39880704s driveoffset 265s plexoffset 1024s ----- I run 'vinum create -f vinum.config', then 'vinum init raid.p0'. After the subdisks have completed initialization, I run 'newfs -v /dev/vinum/raid' which succeeds. Immediately afterwards, running 'fsck -y' results in hundreds of errors reading: ** /dev/vinum/raid ** Last Mounted on ** Phase 1 - Check Blocks and Sizes PARTIALLY ALLOCATED INODE I=5734934 CLEAR? yes ... ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups BLK(S) MISSING IN BIT MAPS SALVAGE? yes Running fsck again gives the following output: ** /dev/vinum/raid ** Last Mounted on ** Phase 1 - Check Blocks and Sizes UNKNOWN FILE TYPE I=5099104 CLEAR? [yn] y UNKNOWN FILE TYPE I=6596000 CLEAR? [yn] y UNKNOWN FILE TYPE I=7599456 CLEAR? [yn] y ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts UNREF FILE I=4019616 OWNER=1070333466 MODE=27125 SIZE=0 MTIME=Dec 31 19:00 1969 RECONNECT? [yn] y NO lost+found DIRECTORY CREATE? [yn] y LINK COUNT FILE I=4019616 OWNER=1070333466 MODE=27125 SIZE=0 MTIME=Dec 31 19:00 1969 COUNT 16439 SHOULD BE 1 ADJUST? [yn] y ** Phase 5 - Check Cyl groups FREE BLK COUNT(S) WRONG IN SUPERBLK SALVAGE? [yn] y SUMMARY INFORMATION BAD SALVAGE? [yn] y BLK(S) MISSING IN BIT MAPS SALVAGE? [yn] y Finally, I stop and start vinum, then mount the volume. Everything appears to work. I can put files on the volume, and navigate thru any directory structures I create, but when I read files from the volume, I receive corrupted data. This is especially evident in .tar.gz archives which spit archive errors when reading the archive contents. Is there a problem with my configuration? Any optimization recommendations are welcome. This configuration did work with a 4.2-stable system before I moved to the new motherboard. Is there some difference between vinum on 4.2 and 4.3 that might cause a situation like this? Any advice will be greatly appreciated. Thanks, ~brian skrab bgs@pinky.us.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.32.0105021459520.326-100000>