On Tuesday, 21 December 2004 at 13:42:40 -0500, Paul Mather wrote:
> On Tue, 2004-12-21 at 19:00 +0100, Nikolaj Hansen wrote:
>
>> I also do not think it belongs in the stable branch just yet :-D Any hope
>> of you fixing the old vinum in the 5.3 branch or is it a wait for the 5.4?
>
> AFAIK, the o
On Tue, 2004-12-21 at 19:00 +0100, Nikolaj Hansen wrote:
> I also do not think it belongs in the stable branch just yet :-D Any hope
> of you fixing the old vinum in the 5.3 branch or is it a wait for the 5.4?
AFAIK, the old vinum will *never* be "fixed" in the 5.3 branch or any
subsequent branch
On Mon, 20 Dec 2004, Matthias Schuendehuette wrote:
Am Montag, 20. Dezember 2004 00:04 schrieb Nikolaj Hansen:
[...] The whole problem is, I cannot
mount any thing without doing it this way. The reason for this is, as
you pointed out , that my disk setup is different than the norm:
$ sudo bsdlabel
On Mon, Dec 20, 2004 at 06:35:23PM +0100, Matthias Schuendehuette wrote:
> Am Montag, 20. Dezember 2004 00:04 schrieb Nikolaj Hansen:
> This disk setup seems to me perfectly legal. Your vinum-partition has an
> offset of 1740535 which is != 0, that's all that I meant.
>
OK, Thats a relief. I also
Am Montag, 20. Dezember 2004 00:04 schrieb Nikolaj Hansen:
> [...] The whole problem is, I cannot
> mount any thing without doing it this way. The reason for this is, as
> you pointed out , that my disk setup is different than the norm:
>
> $ sudo bsdlabel da1s1
> Password:
> # /dev/da1s1:
> 8 part
On Sun, Dec 19, 2004 at 10:50:52AM +0100, Matthias Schuendehuette wrote:
> Am Sonntag, 19. Dezember 2004 07:12 schrieb Nikolaj Hansen:
> > I gave the 5.3 upgrade another swing. Now the situation is:
> >
> > $ uname -a
> > FreeBSD sauron.barnabas.dk 5.3-RELEASE FreeBSD 5.3-RELEASE #0: Sat
> > Dec 18
Am Sonntag, 19. Dezember 2004 07:12 schrieb Nikolaj Hansen:
> I gave the 5.3 upgrade another swing. Now the situation is:
>
> $ uname -a
> FreeBSD sauron.barnabas.dk 5.3-RELEASE FreeBSD 5.3-RELEASE #0: Sat
> Dec 18 18:39:09 CET 2004
> [EMAIL PROTECTED]:/usr/obj/usr/src/sys/KERNEL_5_3 i386
Per
On Sat, Dec 18, 2004 at 07:27:58PM -0500, Paul Mather wrote:
> On Sun, 2004-12-19 at 00:15 +0100, Matthias Schuendehuette wrote:
> > Am Samstag, 18. Dezember 2004 23:35 schrieb Paul Mather:
> > >
> > > The biggest problem you'll have is if your system suffers the ATA
> > > "TIMEOUT - WRITE_DMA" woe
On Sun, 2004-12-19 at 00:15 +0100, Matthias Schuendehuette wrote:
> Am Samstag, 18. Dezember 2004 23:35 schrieb Paul Mather:
> >
> > The biggest problem you'll have is if your system suffers the ATA
> > "TIMEOUT - WRITE_DMA" woe that bedevils some of us under 5.3. When
> > that happens, your mirro
Am Samstag, 18. Dezember 2004 23:35 schrieb Paul Mather:
>
> The biggest problem you'll have is if your system suffers the ATA
> "TIMEOUT - WRITE_DMA" woe that bedevils some of us under 5.3. When
> that happens, your mirror will be knocked into a degraded state (half
> of your mirrored plexes will
On Sat, 2004-12-18 at 20:52 +0100, Nikolaj Hansen wrote:
> While some uncommon configurations, such as multiple vinum drives on a
> disk, are not supported, it is generally backward compatible. Note that
> for the geom(4)-aware vinum, its new userland control program, gvinum,
> should be used,
Am Samstag, 18. Dezember 2004 20:52 schrieb Nikolaj Hansen:
> [...]
> I think I have to disagree calling muliple drives on a disk
> "uncommon". In fact, I think I remember that being the way it was
> demonstrated in an old version of the handbook. Here is my current
> setup after rolling back to Fr
Hi all,
Forget the first post. My server is still somewhat unstable after the
upgrade attempts, and I appologize. Here goes the real deal:
I tried to upgrade my existing 5.2.1 to a 5.3. I ran into severe
problems with my vinum setup in trying to do so. I think i can answer
why, the reason is st
13 matches
Mail list logo
