Re: vinum list anomaly
On Sat, Mar 27, 2004 at 10:53:42AM +1030, Greg 'groggy' Lehey wrote: > On Friday, 26 March 2004 at 16:10:13 -0800, Sean Ellis wrote: > > On Sat, Mar 27, 2004 at 10:00:18AM +1030, Greg 'groggy' Lehey wrote: > >> On Friday, 26 March 2004 at 11:12:45 -0800, Sean Ellis wrote: > > The line that I'm curious about though appears below; the line referring > > to spanned_log.p0.s0. The two disks are identical, and I thought that > > I'd prepared them in like fashion, yet one displays "0 B Size" and the > > other "4100 MB Size". > > You're misparsing. They are both "Size: 4100 MB". The first is > at plex offset 0 MB, the second at plex offset 4100 MB. Aha. PO .. plex offset. Ok, thanks. > > > > S spanned_log.p0.s0 State: up PO:0 B Size: 4100 MB > > S spanned_log.p0.s1 State: crashed PO: 4100 MB Size: 4100 MB > > Take a look at http://www.vinumvm.org/vinum/how-to-debug.html if you > haven't already done so. Ok, great. -- Sean ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: vinum list anomaly
On Friday, 26 March 2004 at 16:10:13 -0800, Sean Ellis wrote: > On Sat, Mar 27, 2004 at 10:00:18AM +1030, Greg 'groggy' Lehey wrote: >> On Friday, 26 March 2004 at 11:12:45 -0800, Sean Ellis wrote: > >>> after adding too drives as a concatenated vinum volume I see a line in >>> the `vinum list` output which doesn't look right to me. Specifically, the >>> line that refers to spanned_log.p0.s0. Is there a typical explanation for >>> something like this? >>> >>> 2 drives: >>> D a State: up Device /dev/ad2s1e Avail: >>> 10/4110 MB (0%) >>> D b State: up Device /dev/ad3s1e Avail: >>> 10/4110 MB (0%) >> >> This looks like your MUA folded it. It should look like this: >> >>> 2 drives: >>> D a State: up Device /dev/ad2s1e Avail: 10/4110 MB >>> (0%) >>> D b State: up Device /dev/ad3s1e Avail: 10/4110 MB >>> (0%) > > Sorry, the pasted in details did lose their formatting. > > The line that I'm curious about though appears below; the line referring > to spanned_log.p0.s0. The two disks are identical, and I thought that > I'd prepared them in like fashion, yet one displays "0 B Size" and the > other "4100 MB Size". You're misparsing. They are both "Size: 4100 MB". The first is at plex offset 0 MB, the second at plex offset 4100 MB. > I've just ran `vinum list` again, and I now have other problems (below), > so I will be dealing with them and seeing how things stand at that > point. > > new 'list' > > S spanned_log.p0.s0 State: up PO:0 B Size: 4100 MB > S spanned_log.p0.s1 State: crashed PO: 4100 MB Size: 4100 MB Take a look at http://www.vinumvm.org/vinum/how-to-debug.html if you haven't already done so. 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 Note: I discard all HTML mail unseen. Finger [EMAIL PROTECTED] for PGP public key. See complete headers for address and phone numbers. pgp0.pgp Description: PGP signature
Re: vinum list anomaly
On Sat, Mar 27, 2004 at 10:00:18AM +1030, Greg 'groggy' Lehey wrote: > On Friday, 26 March 2004 at 11:12:45 -0800, Sean Ellis wrote: > > after adding too drives as a concatenated vinum volume I see a line in > > the `vinum list` output which doesn't look right to me. Specifically, the > > line that refers to spanned_log.p0.s0. Is there a typical explanation for > > something like this? > > > > 2 drives: > > D a State: up Device /dev/ad2s1e Avail: > > 10/4110 MB (0%) > > D b State: up Device /dev/ad3s1e Avail: > > 10/4110 MB (0%) > > This looks like your MUA folded it. It should look like this: > > > 2 drives: > > D a State: up Device /dev/ad2s1e Avail: 10/4110 MB > > (0%) > > D b State: up Device /dev/ad3s1e Avail: 10/4110 MB > > (0%) Sorry, the pasted in details did lose their formatting. The line that I'm curious about though appears below; the line referring to spanned_log.p0.s0. The two disks are identical, and I thought that I'd prepared them in like fashion, yet one displays "0 B Size" and the other "4100 MB Size". > > S spanned_log.p0.s0 State: up PO:0 B Size: 4100 MB > > S spanned_log.p0.s1 State: up PO: 4100 MB Size: 4100 MB I've just ran `vinum list` again, and I now have other problems (below), so I will be dealing with them and seeing how things stand at that point. new 'list' S spanned_log.p0.s0 State: up PO:0 B Size: 4100 MB S spanned_log.p0.s1 State: crashed PO: 4100 MB Size: 4100 MB -- Sean ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: vinum list anomaly
On Friday, 26 March 2004 at 11:12:45 -0800, Sean Ellis wrote: > Hello, > > after adding too drives as a concatenated vinum volume I see a line in > the `vinum list` output which doesn't look right to me. Specifically, the > line that refers to spanned_log.p0.s0. Is there a typical explanation for > something like this? > > 2 drives: > D a State: up Device /dev/ad2s1e Avail: > 10/4110 MB (0%) > D b State: up Device /dev/ad3s1e Avail: > 10/4110 MB (0%) > > 1 volumes: > V spanned_log State: up Plexes: 1 Size: 8200 > MB > > 1 plexes: > P spanned_log.p0 C State: up Subdisks: 2 Size: 8200 > MB > > 2 subdisks: > S spanned_log.p0.s0 State: up PO:0 B Size: 4100 > MB > S spanned_log.p0.s1 State: up PO: 4100 MB Size: 4100 > MB This looks like your MUA folded it. It should look like this: > 2 drives: > D a State: up Device /dev/ad2s1e Avail: 10/4110 MB > (0%) > D b State: up Device /dev/ad3s1e Avail: 10/4110 MB > (0%) > > 1 volumes: > V spanned_log State: up Plexes: 1 Size: 8200 MB > > 1 plexes: > P spanned_log.p0 C State: up Subdisks: 2 Size: 8200 MB > > 2 subdisks: > S spanned_log.p0.s0 State: up PO:0 B Size: 4100 MB > S spanned_log.p0.s1 State: up PO: 4100 MB Size: 4100 MB 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 Note: I discard all HTML mail unseen. Finger [EMAIL PROTECTED] for PGP public key. See complete headers for address and phone numbers. pgp0.pgp Description: PGP signature
