Greg 'groggy' Lehey schrieb:
Provide a dump? Analyse the problem yourself? This *is* -CURRENT,
after all.
I can reproduce this here (same MB). I don't think it's a vinum problem,
but vinum seems to be a good way to reproduce the bug. I set up a stripe
over 2 SATA disks, newfs it, run iozone
On Monday, Oct 20, 2003, at 19:02 Europe/Budapest, Alexander Leidinger
wrote:
Greg 'groggy' Lehey schrieb:
Provide a dump? Analyse the problem yourself? This *is* -CURRENT,
after all.
I can reproduce this here (same MB). I don't think it's a vinum
problem,
but vinum seems to be a good way to
On Wednesday, Oct 15, 2003, at 01:24 Europe/Budapest, Greg 'groggy'
Lehey wrote:
On Tuesday, 14 October 2003 at 18:46:44 +0200, Balazs Nagy wrote:
What can I do?
Provide a dump? Analyse the problem yourself? This *is* -CURRENT,
after all.
Well... There is a tricky problem... I have two
It seems 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 requirements (eg. two SATA ports)
On Wednesday, Oct 15, 2003, at 10:34 Europe/Budapest, Soren Schmidt
wrote:
First loose vinum from the mix, if we should have a chance finding
the problem we need to lower the number of unknowns. Then tell us
if and how it fails, dmesg from verbose booted system, backtrace
etc, you know the drill
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 requirements (eg. two SATA ports) in the store: an Asus
P4P800.
My
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
