On Saturday, 26 October 2002 at 21:35:13 -0400, Scott Dodson wrote:
Over the past few weeks I've had continuous problems booting
my 5-current system with an SMP kernel. Immediately after
the system has booted and the login screen displays the machine
panics. The motherboard is an Abit BP6.
On Sunday, 27 October 2002 at 1:06:11 -0700, Juli Mallett wrote:
* De: Greg 'groggy' Lehey [EMAIL PROTECTED] [ Data: 2002-10-27 ]
[ Subjecte: Re: 5-current crashing when booting SMP ]
On Saturday, 26 October 2002 at 21:35:13 -0400, Scott Dodson wrote:
Over the past few weeks I've had
Now that uucp is no longer in the base system, is there any reason to
keep user uucp in /usr/src/etc/master.passwd?
Greg
--
See complete headers for address and phone numbers
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
I've just tried to start pppd on two different -CURRENT machines, one
built on 26 October, the other on 5 November. In each case I get the
following message:
pppd: This system lacks kernel support for PPP. To include PPP support
in the kernel, please follow the steps detailed in the
On Friday, 15 November 2002 at 12:05:22 -0800, Archie Cobbs wrote:
Dag-Erling Smorgrav wrote:
=== vinum
Makefile, line 4441: warning: duplicate script for target geom_bsd.o ignored
cc1: warnings being treated as errors
/h/des/src/sys/dev/aic7xxx/aic79xx_osm.c: In function `ahd_ddb_in':
On Friday, 6 December 2002 at 15:27:29 -0600, Dan Nelson wrote:
I haven't seen this one reported yet.
FreeBSD dan.emsphone.com 5.0-RC FreeBSD 5.0-RC #228: Thu Dec 5 17:28:33 CST 2002
[EMAIL PROTECTED]:/usr/src/sys/i386/compile/DANSMP i386
lock order reversal
1st 0xc2d454b0 vnode
On Monday, 9 December 2002 at 20:23:44 -0500, David Rhodus wrote:
I have also been having a few problems with vinum on 5.0-RC1.
I've been having a hard time making a striped or raid5 vinum with more
than 4 disk's. On the 5th+ disk's vinum will see and says device is
not configured.
That's a
On Wednesday, 11 December 2002 at 12:45:05 -0700, Aaron D. Gifford wrote:
I wrote in my previous message:
# newfs -O 2 -U /dev/vinum/raid5vol
newfs: /dev/vinum/raid5vol: 'e' partition is unavailable
...
Here's my vinum setup:
...
volume raid5vol
Let me correct this to state that the
On Saturday, 14 December 2002 at 20:55:05 -0800, Terry Lambert wrote:
M. Warner Losh wrote:
One problem with most 386 boxes is that they have very little memory.
sysinstall is a big, bloated pig dog these days that takes more RAM
than most 386 boxes have. This is true also for many 486 boxes
On Saturday, 14 December 2002 at 20:53:05 -0800, Terry Lambert wrote:
Alex wrote:
It means that you can not install FreeBSD on a 386 unless you have a
486+ machine that can compile a new FreeBSD system and have a way to
get that version to the 386.
Yes, this is true. Several of us were
On Monday, 16 December 2002 at 12:02:10 -0700, M. Warner Losh wrote:
In message: [EMAIL PROTECTED]
Greg 'groggy' Lehey [EMAIL PROTECTED] writes:
I suppose it would be a good idea to include an alternatvie i386
kernel on the CD-ROM. There may be a space issue, of course. How
many
On Monday, 16 December 2002 at 10:09:48 -0800, Chris Doherty wrote:
2) I'm scared that 5.0 is going to be unpleasantly slow on my p2-366, let
alone a 386.
I'm running it diskless on a K6/233. I'm surprised how snappy it is.
Greg
--
See complete headers for address and phone numbers
To
I've been experiencing a lot of lockups (system completely dead, no
reaction at the keyboard, can't ping) on an Intel SMP machine running
CURRENT. Normally I do my kernel builds over NFS, but in the last few
months I haven't been able to complete a 'make world'. Along with
-DNOCLEAN I can get a
On Wednesday, 18 December 2002 at 22:36:08 -0600, Dan Nelson wrote:
In the last episode (Dec 19), Greg 'groggy' Lehey said:
I've been experiencing a lot of lockups (system completely dead, no
reaction at the keyboard, can't ping) on an Intel SMP machine running
CURRENT. Normally I do my
On Tuesday, 24 December 2002 at 13:37:02 -0800, TwinsPop wrote:
I'm getting a flurry of these message since upgrading from 4.7-stable to
5.0-current (cvsup'd @ 1200PST 12/23):
calcru: negative time of -676146 usec for pid blah blah...
It's an AMD K6-2 system.
On Monday, 6 January 2003 at 10:27:21 -0800, Nate Lawson wrote:
I'd like to have a mirrored root partition. I tried ccd(4) but the boot
blocks couldn't find the fs. Any idea how much work it would take to
enable booting a ccd root? Also, does vinum already support this?
I've had this
On Wednesday, 8 January 2003 at 10:00:59 -0800, Darryl Okahata wrote:
Hi,
Has anyone gotten vinum to work using the 5.0RC2 ISO distribution?
I've tried creating a raid5, a raid10, and (finally) a basic,
one-drive volume, and newfs fails for all cases, with:
# newfs -U
On Wednesday, 8 January 2003 at 13:29:06 -0800, Darryl Okahata wrote:
Willem Jan Withagen [EMAIL PROTECTED] write:
Vinum is running fine here on 5.0 for already quite some time.
the trick is most likely:
newfs -T ufs /dev/vinum/vinum0
Nope. No joy:
# newfs -T ufs
I haven't done much with PCCARD on -CURRENT lately. Last time I
tried, a couple of months ago, I got repeated freezes on the two 100
Mb/s NICs I have. I've just built a kernel as of about 30 hours ago,
and I find:
1. Xircom RealPort RE-100 (xe driver).
Comes up with unidentified media.
[adding current@ to the list; that's where my part of this thread started]
On Sunday, 12 January 2003 at 23:16:14 -0700, M. Warner Losh wrote:
In message: [EMAIL PROTECTED]
Greg 'groggy' Lehey [EMAIL PROTECTED] writes:
On Sunday, 12 January 2003 at 22:01:18 -0700, M. Warner Losh
Some changes in device driver locking recently broke Vinum for a short
period of time. The problem is now fixed. If you have any problems
with a recent version of Vinum, please let me know.
Greg
--
See complete headers for address and phone numbers
pgp0.pgp
Description: PGP signature
On Saturday, 23 August 2003 at 5:05:11 -0700, Rostislav Krasny wrote:
When FreeBSD 5.0-RELEASE had been released I tried to install it from
floppies. I got system panic and then reported this problem into
[EMAIL PROTECTED] mailing list. You can find this report in
On Thursday, 25 September 2003 at 3:04:52 +0200, Willem Jan Withagen wrote:
Hi,
I'm trying to upgrade my firewall/router to 5.x but I'm getting caught by
the fact that I cannot find a 'sl0' interface.
Are you really still using SLIP? What's wrong with PPP?
I've tried the both with if_sl
On Thursday, 25 September 2003 at 1:12:21 -0400, Lanny Baron wrote:
On Wed, 2003-09-24 at 22:42, Greg 'groggy' Lehey wrote:
On Thursday, 25 September 2003 at 3:04:52 +0200, Willem Jan Withagen wrote:
Hi,
I'm trying to upgrade my firewall/router to 5.x but I'm getting caught by
the fact
On Friday, 26 September 2003 at 18:38:48 -0400, Robert Watson wrote:
On Fri, 26 Sep 2003, David Gilbert wrote:
Recent changes to -CURRENT prohibit vinum swap:
[1:6:[EMAIL PROTECTED]:~ swapon /dev/vinum/swapmu swapon: /dev/vinum/swapmu:
Operation not supported by device
In order to support
On Friday, 26 September 2003 at 19:28:45 -0400, David Gilbert wrote:
Robert == Robert Watson [EMAIL PROTECTED] writes:
Robert On Fri, 26 Sep 2003, David Gilbert wrote:
Recent changes to -CURRENT prohibit vinum swap:
[1:6:[EMAIL PROTECTED]:~ swapon /dev/vinum/swapmu swapon:
On Friday, 26 September 2003 at 22:08:25 -0400, David Gilbert wrote:
Greg == Greg Lehey Greg writes:
Greg Don't hold your breath. This will probably happen in the course
Greg of migrating Vinum functionality to GEOM.
So... is vinum-as-we-know-it going to disappear into the GEOM
monster?
I
On Sunday, 28 September 2003 at 23:22:07 +0200, Poul-Henning Kamp wrote:
Basically:
3. If you do a normal device driver, cache the result
from when you call make_dev().
...
./dev/vinum
Failure to cache result of make_dev() ?
Where should this be cached?
On Sunday, 28 September 2003 at 19:46:20 -0400, Robert Watson wrote:
On Mon, 29 Sep 2003, Greg 'groggy' Lehey wrote:
On Sunday, 28 September 2003 at 23:22:07 +0200, Poul-Henning Kamp wrote:
Basically:
3. If you do a normal device driver, cache the result
from when you call
After building a new kernel, remote serial gdb no longer works. When
I issue a 'continue' command, I lose control of the system, but it
doesn't continue running. Has anybody else seen this?
Greg
--
See complete headers for address and phone numbers.
NOTE: Due to the currently active
On Tuesday, 30 September 2003 at 16:23:35 +1000, Bruce Evans wrote:
On Mon, 29 Sep 2003, Greg 'groggy' Lehey wrote:
After building a new kernel, remote serial gdb no longer works. When
I issue a 'continue' command, I lose control of the system, but it
doesn't continue running. Has anybody
On Tuesday, 30 September 2003 at 16:13:09 -0400, Andrew Gallatin wrote:
Sam Leffler writes:
It reliably locks up for me when you break into a running system; set a
breakpoint; and then continue. Machine is UP+HTT. Haven't tried other
machines.
Perhaps related, perhaps a red-herring:
On Tuesday, 14 October 2003 at 18:46:44 +0200, Balazs Nagy wrote:
Hi,
I had a -CURRENT setting with an Abit BE7-S and two SATA disks with
vinum configuration. It worked very well until a power failure, and
the mainboard died. Yesterday I got a replacement mainboard, the only
type met the
On Wednesday, 8 October 2003 at 2:08:55 +1000, Bruce Evans wrote:
On Tue, 30 Sep 2003, Sam Leffler wrote:
It reliably locks up for me when you break into a running system; set a
breakpoint; and then continue. Machine is UP+HTT. Haven't tried other
machines.
This seems to be because
I'm running a -CURRENT kernel built about a week ago, and on
'camcontrol devlist' I get the following repeatable panic:
#10 0xc063b1d5 in panic (fmt=0xc084458e vmapbuf)
at /src/FreeBSD/5-CURRENT-WANTADILLA/src/sys/kern/kern_shutdown.c:534
#11 0xc0684d4e in vmapbuf (bp=0xc4659400) at
Following on from the panic on a week-old -CURRENT, I note that
camcontrol rescan doesn't do the right thing either. On yesterday's
kernel, I did:
- remove a disk from a string
- run camcontrol rescan. No change Re-scan of bus 1 was successful,
but the device entry was still there.
- Ran
I've just cvsupped the latest -CURRENT, and it dies on me in
gnu/usr.bin/gperf/doc:
=== gnu/usr.bin/gperf/doc
c++ -O -pipe -std=iso9899:1999
-I/usr/obj/src/FreeBSD/5-CURRENT-ZAPHOD/src/i386/legacy/usr/include
-I/src/FreeBSD/5-CURRENT-ZAPHOD/src/gnu/usr.bin/gperf/../../../contrib/gperf/lib
On Monday, 2 June 2003 at 10:54:06 +0930, Greg 'groggy' Lehey wrote:
I've just cvsupped the latest -CURRENT, and it dies on me in
gnu/usr.bin/gperf/doc:
*sigh*
Yes, of course I saw the dialogue between DES and obrien, and the
subsequent commit, so I re-supped and cvs updated and it still
On Tuesday, 10 June 2003 at 14:05:11 +0200, Bernd Walter wrote:
fatal kernel trap:
Stopped at g_dev_strategy+0x44:stq t0,0x20(v0) 0x20
t0=0x1a61da400,v0=0x0
db trace
g_dev_strategy() at g_dev_strategy+0x44
launch_requests() at launch_requests+0x390
prologue botch:
I've just upgraded my laptop to a recent -CURRENT, and since then I've
been having a lot of network problems. Here's a rough chronology:
- Machine is a Dell Inspiron 7500, which I've been using with releases
4 and 5 of FreeBSD without problems for the last 3 years. It's
usually connected to
On Thursday, 3 July 2003 at 16:33:30 +0200, Harti Brandt wrote:
On Thu, 3 Jul 2003, M. Warner Losh wrote:
MWLIn message: [EMAIL PROTECTED]
MWLHarti Brandt [EMAIL PROTECTED] writes:
MWL: I think the same problem was reported by Rob Holmes two weeks ago and by
MWL: me (although
I've spent the last couple of days tracking down a problem starting X
on a Dell Inspiron 5100. I've got as far as discovering that the
video BIOS is not being completely mapped: it's 60 kB long, but only
48 kB are being mapped into memory. To make matters worse, the
machine doesn't have a serial
On Saturday, 26 July 2003 at 9:41:14 +0100, Bruce M Simpson wrote:
On Sat, Jul 26, 2003 at 05:32:17PM +0930, Greg 'groggy' Lehey wrote:
Can anybody point me in the right direction? Where should I be
looking for this? Is this memory mapped permanently, or is it only
during X startup
On Saturday, 26 July 2003 at 11:27:06 -0600, M. Warner Losh wrote:
In message: [EMAIL PROTECTED]
Greg 'groggy' Lehey [EMAIL PROTECTED] writes:
machine doesn't have a serial port, so I can't apply a kernel debugger
to find out what's going on.
Does it have a firewire port?
Yes
On Saturday, 26 July 2003 at 18:44:43 -0600, M. Warner Losh wrote:
In message: [EMAIL PROTECTED]
Greg 'groggy' Lehey [EMAIL PROTECTED] writes:
On Saturday, 26 July 2003 at 11:27:06 -0600, M. Warner Losh wrote:
In message: [EMAIL PROTECTED]
Greg 'groggy' Lehey [EMAIL
On Saturday, 26 July 2003 at 19:47:50 -0600, M. Warner Losh wrote:
In message: [EMAIL PROTECTED]
Greg 'groggy' Lehey [EMAIL PROTECTED] writes:
On Saturday, 26 July 2003 at 18:44:43 -0600, M. Warner Losh wrote:
In message: [EMAIL PROTECTED]
Greg 'groggy' Lehey [EMAIL
On Saturday, 26 July 2003 at 11:00:40 -0600, M. Warner Losh wrote:
In message: [EMAIL PROTECTED]
M. Warner Losh [EMAIL PROTECTED] writes:
The reason I keep saying that is that nobody knows for sure. Nobody
has reverse engineered anything, got sued and won (or lost). Just
On Saturday, 26 July 2003 at 22:18:59 -0600, M. Warner Losh wrote:
In message: [EMAIL PROTECTED]
Greg 'groggy' Lehey [EMAIL PROTECTED] writes:
Presuming that it's the ROM driver, I get this in the dmesg I posted:
pnpbios: Bad PnP BIOS data checksum
That's likely the problem
On Sunday, 27 July 2003 at 21:42:35 -0600, M. Warner Losh wrote:
In message: [EMAIL PROTECTED]
Greg 'groggy' Lehey [EMAIL PROTECTED] writes:
On Saturday, 26 July 2003 at 22:18:59 -0600, M. Warner Losh wrote:
In message: [EMAIL PROTECTED]
Greg 'groggy' Lehey [EMAIL
On Sunday, 27 July 2003 at 22:03:57 -0600, M. Warner Losh wrote:
In message: [EMAIL PROTECTED]
Greg 'groggy' Lehey [EMAIL PROTECTED] writes:
Sure. The data at offset 0xc are:
C000: 55 AA 78 E9 44 06 00 00-00 00 00 00 00 00 00 00 U.x.D...
The 0xaa55
On Sunday, 27 July 2003 at 22:11:29 -0600, M. Warner Losh wrote:
Where are you getting the data? A windows tool?
If you're talking about the BIOS contents I'm printing, yes, I'm using
a Microsoft tool called DEBUG (which has been around since before
Microsoft bought DOS :-).
Greg
--
See
On Sunday, 27 July 2003 at 22:17:32 -0600, M. Warner Losh wrote:
In message: [EMAIL PROTECTED]
Greg 'groggy' Lehey [EMAIL PROTECTED] writes:
On Sunday, 27 July 2003 at 22:11:29 -0600, M. Warner Losh wrote:
Where are you getting the data? A windows tool?
If you're talking about
On Sunday, 27 July 2003 at 22:32:42 -0600, M. Warner Losh wrote:
In message: [EMAIL PROTECTED]
Greg 'groggy' Lehey [EMAIL PROTECTED] writes:
On Sunday, 27 July 2003 at 22:17:32 -0600, M. Warner Losh wrote:
In message: [EMAIL PROTECTED]
Greg 'groggy' Lehey [EMAIL
Earlier this month I sent a message saying that my wireless card
(Orinoco) doesn't work at all any more. In the meantime, I've
narrowed the problem down to IBSS (ad-hoc) mode: it works fine in
BSS (base station) mode. I'd like to know if *anybody* is using IBSS
(maybe with Orinoco cards) on a
On Saturday, 2 August 2003 at 2:11:24 -0700, Terry Lambert wrote:
Eivind Olsen wrote:
Can anyone suggest what I do next to find out about this crash?
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x14
Dereference of NULL pointer; reference is for element at
On Saturday, 2 August 2003 at 17:00:59 +0200, Eivind Olsen wrote:
--On 2. august 2003 11:16 +0200 Bernd Walter [EMAIL PROTECTED]
wrote:
Looks like a problem in vinum. The other backtrace was the same, right?
Please take a look at an older thread named (IIRC) vinum or geom bug?
Greg asked
On Saturday, 2 August 2003 at 16:47:13 +0200, Eivind Olsen wrote:
--On 2. august 2003 02:11 -0700 Terry Lambert [EMAIL PROTECTED]
wrote:
db trace
g_dev_strategy(c2156024,c2153800,0,cfb528d0,c2099eca) at
g_dev_strategy+0x29 launch_requests(c299bf00,0,1,,47) at
On Saturday, 2 August 2003 at 17:54:03 -0700, Terry Lambert wrote:
Eivind Olsen wrote:
(kgdb) list *(launch_requests+448)
No symbol launch_requests in current context.
(kgdb) list *(vinumstart+2b2)
No symbol vinumstart in current context.
(kgdb)
If anyone wants to take a look at this
On Saturday, 2 August 2003 at 17:56:49 -0700, Terry Lambert wrote:
Greg 'groggy' Lehey wrote:
You don't actually need a crash dump to debug a stack traceback.
Great! So you know the answer? Please submit a patch.
Seriously, this is nonsense. Yes, it's a null pointer dereference.
What
On Saturday, 2 August 2003 at 18:06:36 -0700, Terry Lambert wrote:
Greg 'groggy' Lehey wrote:
Please take a look at an older thread named (IIRC) vinum or geom bug?
Greg asked for special debug output, but it never happened again for me.
A real murphy bug - it happend on three machines once
On Saturday, 2 August 2003 at 18:36:24 -0700, Terry Lambert wrote:
Greg 'groggy' Lehey wrote:
The information I gave him gets him to lines of source code, instead
of just function names with strange hexadecimal numbers that resolve
to instruction offsets that may be specific to his compile
On Sunday, 3 August 2003 at 0:31:45 -0400, John Baldwin wrote:
On 03-Aug-2003 Greg 'groggy' Lehey wrote:
On Saturday, 2 August 2003 at 16:47:13 +0200, Eivind Olsen wrote:
[EMAIL PROTECTED]:~/tmp/debug gdb -k kernel.debug
(kgdb) list *(g_dev_strategy+29)
This is almost certainly
On Sunday, 3 August 2003 at 11:17:49 +0200, Eivind Olsen wrote:
--On 3. august 2003 09:37 +0930 Greg 'groggy' Lehey [EMAIL PROTECTED]
wrote:
Read the links I just sent you. You haven't loaded the Vinum symbols.
I'm not sure exactly what to do here. I have absolutely no previous
experience
On Thursday, 31 July 2003 at 9:30:31 +0200, Eirik Oeverby wrote:
Hey,
I have a few Orinoco cards, and they 'work' in both ad-hoc and
infrastructure mode. However with dhclient it gets tricky, because it
will only work the first time dhclient assigns an address to the card.
Whenever it tries
On Sunday, 3 August 2003 at 23:51:55 -0600, M. Warner Losh wrote:
In message: [EMAIL PROTECTED]
Greg 'groggy' Lehey [EMAIL PROTECTED] writes:
On Thursday, 31 July 2003 at 9:30:31 +0200, Eirik Oeverby wrote:
Hey,
I have a few Orinoco cards, and they 'work' in both ad-hoc
On Monday, 4 August 2003 at 11:37:44 +0200, Brad Knowles wrote:
At 11:51 PM -0600 2003/08/03, M. Warner Losh wrote:
In message: [EMAIL PROTECTED]
Greg 'groggy' Lehey [EMAIL PROTECTED] writes:
On Thursday, 31 July 2003 at 9:30:31 +0200, Eirik Oeverby wrote:
Oh and btw.. Get
On Friday, 8 August 2003 at 10:27:31 +0200, Erwin Lansing wrote:
On Fri, Aug 08, 2003 at 10:22:06AM +0200, Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Aaron Wohl writes:
I just cvsuped -current this afternoon to get about 1 weeks updates.
After that the kernel panics booting
On Friday, 8 August 2003 at 16:04:05 +0200, Rob wrote:
Greg 'groggy' Lehey wrote:
On Tuesday, 5 August 2003 at 22:21:41 +0200, Rob wrote:
Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Rob writes:
Hi all,
After cvs'upping (about 12 hours ago) and building world/kernel vinum
On Friday, 8 August 2003 at 15:24:09 +0200, Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Aaron Wohl writes:
Panicstring: mutex Giant owned at /usr/src/sys/geom/geom_dev.c:198
Ok, then I think I know what it is.
Vinum appearantly does not go through SPECFS but rather calls into
On Thursday, 7 August 2003 at 18:23:10 -0600, Aaron Wohl wrote:
I just cvsuped -current this afternoon to get about 1 weeks updates.
After that the kernel panics booting starting vinum. I removed the one
vinum volume (reformated as UFS2) I had for testing. And it still panics.
I changed the
[Format recovered--see http://www.lemis.com/email/email-format.html]
Long/short syndrome.
On Tuesday, 12 August 2003 at 20:49:05 -0400, James Quick wrote:
I am seeking feedback on the status of vinum, and whether the
following plan makes sense as an upgrade plan for a host with a
light load
On Tuesday, 5 August 2003 at 22:21:41 +0200, Rob wrote:
Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Rob writes:
Hi all,
After cvs'upping (about 12 hours ago) and building world/kernel vinum
stopped working. It does show my two disks but nothing more. I also
get an error message
On Wednesday, 5 February 2003 at 1:07:47 +0100, Poul-Henning Kamp wrote:
In message a05200f08ba65f714a4e9@[146.106.12.76], Brad Knowles writes:
At 10:44 PM +0100 2003/02/04, Poul-Henning Kamp wrote:
In difference from the devstat framework which measures how big a
percentage of the time a
[redirected to -current]
On Tuesday, 4 February 2003 at 17:55:42 -0800, [EMAIL PROTECTED] wrote:
with last hour, cvsup current, rebuild everything,... immediately
after kernel mount msg for /
kernel cranks out msg
Be nice to each other, mmmkay?
system otherwise fine. Is this a known
On Saturday, 8 February 2003 at 0:00:45 +0100, Joerg Wunsch wrote:
As Michael Reifenberger wrote:
What does your sysctl kern.disks say?
(nihil)(root) # sysctl -a kern.disks
kern.disks: da1 da0 ad1 ad0
That's OK.
I guess it's time to dump the old vinum start code from
vinum(8)
On Saturday, 8 February 2003 at 21:42:27 +0100, Joerg Wunsch wrote:
As Greg 'groggy' Lehey wrote:
I guess it's time to dump the old vinum start code from
vinum(8) completely, and use the in-kernel scan now.
This sounds like a good idea.
Not after looking a bit closer. ;-) The only
On Saturday, 8 February 2003 at 18:34:04 +0100, Michael Reifenberger wrote:
On Fri, 7 Feb 2003, Michael Reifenberger wrote:
...
As a workaround, you can try setting
vinum_load=YES
vinum.autostart=YES
in your /boot/loader.conf, /and/ remove the start_vinum line from
rc.conf. Please tell
On Friday, 14 February 2003 at 12:23:48 +0100, Dag-Erling Smorgrav wrote:
Alfred Perlstein [EMAIL PROTECTED] writes:
What exactly is broken about dumps for you on ata?
Well, after you told me that call dumpsys is no longer kosher (when
did that happen, and where was it documented?), I tried
On Friday, 21 February 2003 at 10:00:46 +0200, Vallo Kallaste wrote:
On Thu, Feb 20, 2003 at 02:28:45PM -0800, Darryl Okahata
[EMAIL PROTECTED] wrote:
Vallo Kallaste [EMAIL PROTECTED] wrote:
I'll second Brad's statement about vinum and softupdates
interactions. My last experiments with
On Friday, 21 February 2003 at 1:56:56 -0800, Terry Lambert wrote:
Vallo Kallaste wrote:
The crashes and anomalies with filesystem residing on R5 volume were
related to vinum(R5)/softupdates combo. The vinum R5 and system as
a whole were stable without softupdates. Only one problem remained
On Saturday, 1 March 2003 at 20:43:10 +0200, Vallo Kallaste wrote:
On Thu, Feb 27, 2003 at 11:53:02AM +0200, Vallo Kallaste vallo wrote:
The vinum R5 and system as a whole were stable without
softupdates. Only one problem remained after disabling softupdates,
while being online and user I/O
On Friday, 14 March 2003 at 10:05:28 +0200, Vallo Kallaste wrote:
On Fri, Mar 14, 2003 at 01:16:02PM +1030, Greg 'groggy' Lehey
[EMAIL PROTECTED] wrote:
So I did. Loaned two SCSI disks and 50-pin cable. Things haven't
improved a bit, I'm very sorry to say it.
Sorry for the slow reply
On Saturday, 15 March 2003 at 10:34:54 +0200, Vallo Kallaste wrote:
On Sat, Mar 15, 2003 at 12:02:23PM +1030, Greg 'groggy' Lehey
[EMAIL PROTECTED] wrote:
-current, system did panic everytime at the end of
initialisation of parity (raidctl -iv raid?). So I used the
raidframe patch
On Saturday, 15 March 2003 at 23:56:24 +0100, Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Greg 'groggy' Lehey
writes:
Ok, I'll try to simulate the disk failure by switching off the
power, then.
I think you misunderstand. I simulated the disk failures by doing a
stop -f. I
On Monday, 17 March 2003 at 22:39:02 +0100, Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Bakul Shah writes:
UFS is the real problem here, not fsck. Its tradeoffs for
improving normal access latencies may have been right in the
past but not for modern big disks. The seek time RPM
On Monday, 17 March 2003 at 23:02:38 -0500, Jeff Roberson wrote:
On Mon, 17 Mar 2003, Terry Lambert wrote:
Jeff Roberson wrote:
On Mon, 17 Mar 2003, Brooks Davis wrote:
I am still intrested in improvements to fsck since I'm planning to buy
several systems with two 1.4TB IDE RAID5 arrays in
On Monday, 24 March 2003 at 19:07:56 -0500, Hiten Pandya wrote:
Hi Gang!
I was wondering, what's the point of making Vinum use a totally
different SYSINIT type? Isn't there a possibility it can just use
SI_SUB_RAID?
Probably. SI_SUB_VINUM was there first.
Greg
--
See complete headers for
On Tuesday, 25 March 2003 at 18:44:03 +0100, Hartmut Brandt wrote:
Hi,
when calling 'vinum start' it responds with
usage: read drive [drive ...]
from looking at the code, it appears that it cannot find the disk drives
to read the configuration from.
vinum read da0 da1
just works.
So
On Wednesday, 26 March 2003 at 13:35:28 +, Jason Morgan wrote:
I just got a panic. As I have never had one before, I don't know what to
do. It's on another system so I don't have to reboot immediately (that
would solve the problem temporarily, wouldn't it?) if someone would give
me some
On Saturday, 15 June 2002 at 11:30:08 -0700, Gordon Tetlow wrote:
On Fri, 14 Jun 2002, Terry Lambert wrote:
Mike Makonnen wrote:
Danny Braniss [EMAIL PROTECTED] wrote:
in amd,
# REQUIRE: rpcbind mountall ypbind nfsclient
**
since i don't use yp,
On Friday, 21 June 2002 at 22:24:14 -0400, Robert Watson wrote:
On Thu, 20 Jun 2002, Greg 'groggy' Lehey wrote:
On Wednesday, 19 June 2002 at 10:07:29 +0200, Poul-Henning Kamp wrote:
Kirk is loading and aiming is committatron with the UFS2 patch,
expect to see it hit -current any day soon
On Thursday, 4 July 2002 at 19:20:00 +1000, Bruce Evans wrote:
On Wed, 3 Jul 2002, Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Bruce Evans writes:
This is mostly because resources have been diverted away from updating
working code to write a second system.
Make that third
On Tuesday, 1 October 2002 at 9:48:59 +0200, Sheldon Hearn wrote:
On (2002/09/30 21:09), Poul-Henning Kamp wrote:
Provided nothing terminal pops up in the next 5 days, GEOM will
become default in -current on Saturday 5th of october.
Please test it now on _your_ configuration and tell me
On Friday, 4 October 2002 at 14:11:57 -0700, Peter Wemm wrote:
Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], n0go013 writ
es
:
On 04.10-15:40, fergus wrote:
On 04.10-14:20, Poul-Henning Kamp wrote:
[...]
I suspect vinum uses this sysctl to get an inventory of disks in
the
On Friday, 4 October 2002 at 16:03:24 -0700, Peter Wemm wrote:
Terry Lambert wrote:
Emiel Kollof wrote:
* Peter Wemm ([EMAIL PROTECTED]) wrote:
vinum is so much unbelievable stuff in it. Consider this stuff:
sys/dev/vinum/vinumio.c:
[ ... ]
This crud has *got* to be taken out and
On Friday, 4 October 2002 at 20:07:11 -0400, Robert Watson wrote:
On Fri, 4 Oct 2002, Terry Lambert wrote:
The assumption here is that the devfs will be available to the system
before the root is mounted transparently over it. This is also doable
with an unmounted instance of the backing
On Friday, 4 October 2002 at 20:21:29 -0400, Robert Watson wrote:
On Fri, 4 Oct 2002, Robert Watson wrote:
On Fri, 4 Oct 2002, Terry Lambert wrote:
The assumption here is that the devfs will be available to the system
before the root is mounted transparently over it. This is also doable
On Friday, 4 October 2002 at 20:29:51 -0400, Robert Watson wrote:
On Sat, 5 Oct 2002, Greg 'groggy' Lehey wrote:
FWIW, I've never seen this code. The dates on the patch suggest that
it was made in the last quarter of an hour:
I didn't claim that this was his code. This was code I just
On Saturday, 5 October 2002 at 4:08:19 +0100, Ian Dowse wrote:
[CCs trimmed]
The divide by zero problem seems to be caused by an interaction
between two bugs: GEOM refuses to return the sector size because
...
The next failure I get is:
Can't write config to /dev/da1s1d, error 45
On Saturday, 5 October 2002 at 4:08:19 +0100, Ian Dowse wrote:
[CCs trimmed]
The divide by zero problem seems to be caused by an interaction
between two bugs: GEOM refuses to return the sector size because
...
The next failure I get is:
Can't write config to /dev/da1s1d, error 45
1 - 100 of 158 matches
Mail list logo
