Date: Sun, 27 Jun 2004 01:57:00 -0700 From: "Richard Holmes" <rholmes@digitalpath.net> To: <freebsd-questions@freebsd.org> Subject: terabyte limit problem with vinum Message-ID: <000301c45c24$b5a3de90$0a00a8c0@guppy>
next in thread | raw e-mail | index | archive | help
Shawn, Did you ever find a solution to the terabyte limit problem you reported last year on FreeBSD.Questions (09/06/2003 and 01/12/2004). I'm having exactly the same problem. I've got eight Maxtor 250GB SATA drives ganged together into one big RAID5 volume with a net size of 1636GB. Everything is fine until "newfs -U -O2 /dev/vinum/..." gives the "can't read old UFS1 superblock" error. I'm using FreeBSD 5.2.1 csvup'd to REL_ENG_5_2 in mid June 2004. Thanks, Richard Holmes Lambda Software Development Rocklin, CA (916) 390-2057 (cell) rholmes@midtown.net rholmes@digitalpath.net (soon to be discontinued) P.S. I've also been having some other problems with vinum. "vinum resetconfig" doesn't always wipe out all of the vinum drives and seems to not reliably erase the vinum database from all of the drives. After resetconfig, "vinum list" may show one or two drives remaining. To get rid of them all, I need to do multiple cycles of "vinum rm -f -r", "vinum stop" and "vinum start". Have also had problems with empty vinum volumes being corrupted after reboot (remember "newfs" failed, so nothing was ever written to the volume). After successfully creating and initializing the vinum RAID5 volume, I "stop" it, then reboot. After reboot, vinum insists on reinitializing the entire volume (an 8 hour process).
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?000301c45c24$b5a3de90$0a00a8c0>