On Wednesday, 23 June 1999 at 1:50:19 -0400, David E. Cross wrote:
> Neither is correct, you want to leave the parition identifier ("h") off of
> it. When vinum starts it scans all the partitions by attempting to add
> one of [abdefgh] to the end of whatever you give it. If you give it
> "wd0s1
Neither is correct, you want to leave the parition identifier ("h") off of
it. When vinum starts it scans all the partitions by attempting to add
one of [abdefgh] to the end of whatever you give it. If you give it
"wd0s1h" it will look for "wd0s1ha ... wd0s1hh" and never find it.
--
David Cros
On Wednesday, 23 June 1999 at 7:33:35 +0200, Thierry Herbelot wrote:
> Greg Lehey wrote:
>>
>
> [SNIP]
>
>> I've also changed the names of the drives. With the old ones, you
>> won't be able to start the volume after a reboot. To quote vinum(8):
>>
>> drive name option
>>
>>Def
Hello Greg,
If I may intrude in this discussion, I was wondering what is the correct
syntax for naming vinum drives in rc.conf.
I've got two drives merged and striped with vinum, but I'm not sure what
to put in rc.conf
vinum_conf :
drive drive1 device /dev/wd1s1h
drive drive2 device /dev/wd2s1h
On Tuesday, 22 June 1999 at 22:14:55 -0400, David E. Cross wrote:
> Ok, now that you have fixed the strerr() bug, I have another -current
> vinum dilema...
>
> I have 3 disks... da0, da1, and da2. da0 has a 100M /, 200M /var,
> 2048M /usr, 512M swap. each of da1 and da2 have 512M swap.
> I have
Ok, now that you have fixed the strerr() bug, I have another -current
vinum dilema...
I have 3 disks... da0, da1, and da2. da0 has a 100M /, 200M /var,
2048M /usr, 512M swap. each of da1 and da2 have 512M swap.
I have a vinum config similiar to:
disk drive1 /dev/da0s1h
disk drive2 /dev/da1s1h
On Tuesday, 22 June 1999 at 17:14:29 -0400, David E. Cross wrote:
> The recent patches include a reference to "strerr()" in kernel mode... there
> is no such beast.
Ugh. Fixed. That's what you get for compiling before I've enabled it.
Greg
--
See complete headers for address, home page and pho
The recent patches include a reference to "strerr()" in kernel mode... there
is no such beast.
--
David Cross | email: [EMAIL PROTECTED]
Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd
Rensselaer Polytechnic Institute, | Ph: 5
As I said on -hackers..
>
> There is a backported version of MAtt's NFS fixes at:
>
> ftp://ftp.whistle.com/pub/julian/nfs-3.diffs
>
> These include Andrew's fix to the fix
>
> results apreciated.
> If you've been having NFS server side problems on 3.x check these out..
>
> julian
>
>
On
I'll be happy to test a 3.2-STABLE version of the patches as soon as they
become available.
Tom
On Tue, 22 Jun 1999, Julian Elischer wrote:
> Ok I 've incorporated that into the patch set I have ready to commit..
> I've also been playing in 3.x
>
> The patches apply almost cleanly there, exc
Ok I 've incorporated that into the patch set I have ready to commit..
I've also been playing in 3.x
The patches apply almost cleanly there, except for 3 small problems that
I'm fixing by hand..
I'll then make a 3.x version of the patches available.
Hopefully people can start testing that..
jul
Julian Elischer writes:
> Matthew Dillon wrote:
> >
> > Here's the location:
> >
> > http://www.backplane.com/FreeBSD4/
> >
> > It's in the 'NFS bugs first found by David E. Cross' section.
> >
>
>
> I've looked it over a bit and can't see any major problems..
>
Doug White schrieb:
>
> Some PC BIOSes won't boot a disk without a MS partition table. Try
> booting a dangerously dedicated disk on a Phoenix machine and you'll see
> what I mean.
Hmm, I remember having exact this problem with a machine (Phoenix BIOS).
After some hacks to the secondary boot I
Julian Elischer writes:
> Matthew Dillon wrote:
> >
> > Here's the location:
> >
> > http://www.backplane.com/FreeBSD4/
> >
> > It's in the 'NFS bugs first found by David E. Cross' section.
> >
>
>
> I've looked it over a bit and can't see any major problems..
>
In the next few hours I will commit a bunch of changes to syscons
console driver. This is the second phase of syscons reorganization.
Here are some warnings :)
1) Because a few new files will be added to the source tree, you will
need to run config(8) on your kernel configuration file before
co
Oliver Fromme <[EMAIL PROTECTED]> wrote:
> This sounds like a bug in the device driver.
If it is, then the driver succeeds into getting the card into a state it
can't recover from. I rebooted and the problem persisted. It actually
took a powercycle to make the card operational again.
I'll see w
16 matches
Mail list logo
