Date: Sat, 23 Aug 2003 20:15:09 +0200 From: Bernd Walter <ticso@cicely12.cicely.de> To: Shawn Ostapuk <flagg@slumber.org> Cc: freebsd-questions@freebsd.org Subject: Re: problem adding subdisk to vinum Message-ID: <20030823181509.GM5426@cicely12.cicely.de> In-Reply-To: <20030812164049.GA5490@slumber.org> References: <20030812164049.GA5490@slumber.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Aug 12, 2003 at 09:40:49AM -0700, Shawn Ostapuk wrote: > V pr0n State: up Plexes: 1 Size: 1172 GB > P vinum0.p0 C State: corrupt Subdisks: 11 Size: 1172 GB > S vinum0.p0.s0 State: up PO: 0 B Size: 152 GB > S vinum0.p0.s1 State: up PO: 152 GB Size: 28 GB > S vinum0.p0.s2 State: up PO: 181 GB Size: 76 GB > S vinum0.p0.s3 State: up PO: 257 GB Size: 76 GB > S vinum0.p0.s4 State: up PO: 333 GB Size: 76 GB > S vinum0.p0.s5 State: up PO: 410 GB Size: 76 GB > S vinum0.p0.s6 State: up PO: 486 GB Size: 76 GB > S vinum0.p0.s7 State: up PO: 562 GB Size: 74 GB > S vinum0.p0.s8 State: up PO: 637 GB Size: 233 GB > S vinum0.p0.s9 State: up PO: 871 GB Size: 152 GB > S vinum0.p0.s10 State: empty PO: 1023 GB Size: 149 GB vinum0.p0.s10 is at PO 1023G - reaching over the 1TByte limit on FreeBSD 4.x. That is because block numbers are signed 32 bit values. You need 5.x for volumes of this size. I'm not shure how the limit could result in this kind of symptom, but it won't work anyway and debugging this case can only change symptoms. Either use 5.x or be happy with your nearly 1T volume and start a new one for the next disk. -- B.Walter BWCT http://www.bwct.de ticso@bwct.de info@bwct.de
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030823181509.GM5426>