On Tue, Apr 04, 2000 at 08:59:59AM +0930, Greg Lehey <[EMAIL PROTECTED]> wrote:
> Do you have dumps?
No, for obvious reasons explained earlier.
I'll spend some time today afternoon and set up suitable environment for
getting dumps and debugging.
--
Vallo Kallaste
[EMAIL PROTECTED]
To Unsubsc
On Monday, 3 April 2000 at 19:23:34 +0200, Søren Schmidt wrote:
> It seems Matthew Dillon wrote:
>>> Same story here, but using softupdates or async mounts I can reproduce
>>> the hang or panic in less than 60 secs..
>>>
>>> Vinum with raid5 is plain broken, include INVARIANTS in the kernel
>>>
On Monday, 3 April 2000 at 10:23:08 +0200, Vallo Kallaste wrote:
> On Sun, Apr 02, 2000 at 09:07:33PM +0200, Bernd Walter <[EMAIL PROTECTED]> wrote:
>
>> Just to clearify the things...
>> Are these problems with 4.0-RELEASE with 4.0-STABLE or with 5.0-CURRENT?
>
> Here's the sequence of what I di
It seems Matthew Dillon wrote:
> :Same story here, but using softupdates or async mounts I can reproduce
> :the hang or panic in less than 60 secs..
> :
> :Vinum with raid5 is plain broken, include INVARIANTS in the kernel
> :and see why...
> :
> :-Søren
>
> Hang on to that thought. As soon
:> 1. I had i386 system with two 20GB IBM ATA disks and 5.0-current system
:> built from March 31 sources. First I used striping over two disks and
:> put /usr filesystem onto it, did overnight testing and all was well.
:> 2. Same system, same sources plus two same disks. Now I tried raid5 over
:>
It seems Vallo Kallaste wrote:
>
> Here's the sequence of what I did:
>
> 1. I had i386 system with two 20GB IBM ATA disks and 5.0-current system
> built from March 31 sources. First I used striping over two disks and
> put /usr filesystem onto it, did overnight testing and all was well.
> 2. Sa
It seems Greg Lehey wrote:
> > This wont fix it on the i386 where the problem is, and btw I havn't seen
> > any commits yet...
>
> No, I was just about to do something when phk changed the interfaces.
> I don't have the time to keep chasing him, so I'll wait until we have
> a relatively stable si
On Sun, Apr 02, 2000 at 09:07:33PM +0200, Bernd Walter <[EMAIL PROTECTED]> wrote:
> Just to clearify the things...
> Are these problems with 4.0-RELEASE with 4.0-STABLE or with 5.0-CURRENT?
Here's the sequence of what I did:
1. I had i386 system with two 20GB IBM ATA disks and 5.0-current syste
On Monday, 3 April 2000 at 7:59:48 +0200, Søren Schmidt wrote:
> It seems Greg Lehey wrote:
>>> Unfortunately I don't have a toy i386 system ready and testet on alpha.
>>> There may be some differences how data corruptions efects on this platform.
>>
>> I found a potentially serious bug in the R
It seems Greg Lehey wrote:
> > Unfortunately I don't have a toy i386 system ready and testet on alpha.
> > There may be some differences how data corruptions efects on this platform.
>
> I found a potentially serious bug in the RAID calculations yesterday:
> it assumed that sizeof (int) == 4. I
On Mon, Apr 03, 2000 at 07:43:00AM +0930, Greg Lehey wrote:
> I found a potentially serious bug in the RAID calculations yesterday:
> it assumed that sizeof (int) == 4. I suspect that it would just slow
> down the calculations, but in any case I've fixed it.
That's generaly not good but allways
On Mon, Apr 03, 2000 at 07:41:54AM +0930, Greg Lehey wrote:
> On Sunday, 2 April 2000 at 22:22:39 +0200, Søren Schmidt wrote:
> > It seems Bernd Walter wrote:
> >> On Sun, Apr 02, 2000 at 09:39:36PM +0200, Soren Schmidt wrote:
> >>> I dont think vinum is/was usable under -current at least not the
:>> to vinum?
:>
:> The changes done by phk to seperate out the io stuff from struct
:> buf.
:
:Alfred and Bernd came up with fixes that seem to work. I still need
:to review them, but I'm in the process of installing an up-to-date
:-CURRENT on my test box. Watch this space.
:
:Greg
I won'
On Sunday, 2 April 2000 at 17:42:16 +0200, Bernd Walter wrote:
> On Sun, Apr 02, 2000 at 01:50:16AM +0200, Bernd Walter wrote:
>> On Sun, Apr 02, 2000 at 01:15:39AM +0200, Bernd Walter wrote:
>>>
>>> Greg - I'm using vinums raid5 code since months now for FreeBSDs CVS-Tree on
>>> 7x 200M disks -
On Sunday, 2 April 2000 at 22:22:39 +0200, Søren Schmidt wrote:
> It seems Bernd Walter wrote:
>> On Sun, Apr 02, 2000 at 09:39:36PM +0200, Soren Schmidt wrote:
>>> I dont think vinum is/was usable under -current at least not the
>>> RAID5 stuff, its broken, and some of it is because greg is not
* Soren Schmidt <[EMAIL PROTECTED]> [000402 13:05] wrote:
> It seems Alfred Perlstein wrote:
> > > > Just to clearify the things...
> > > > Are these problems with 4.0-RELEASE with 4.0-STABLE or with 5.0-CURRENT?
> > >
> > > I have the problem with 4.0-RELEASE, STABLE and 5.0-current but it
> >
It seems Bernd Walter wrote:
> On Sun, Apr 02, 2000 at 09:39:36PM +0200, Soren Schmidt wrote:
> > I dont think vinum is/was usable under -current at least not the
> > RAID5 stuff, its broken, and some of it is because greg is not
> > up to date with what -current looks like these days.
>
> Can y
On Sun, Apr 02, 2000 at 09:39:36PM +0200, Soren Schmidt wrote:
> I dont think vinum is/was usable under -current at least not the
> RAID5 stuff, its broken, and some of it is because greg is not
> up to date with what -current looks like these days.
Can you please explain what have massivly chan
It seems Alfred Perlstein wrote:
> > > Just to clearify the things...
> > > Are these problems with 4.0-RELEASE with 4.0-STABLE or with 5.0-CURRENT?
> >
> > I have the problem with 4.0-RELEASE, STABLE and 5.0-current but it
> > might only occur with RAID5...
>
> I've never seen it with just a s
* Soren Schmidt <[EMAIL PROTECTED]> [000402 12:42] wrote:
> It seems Bernd Walter wrote:
> > On Sun, Apr 02, 2000 at 08:02:54PM +0200, Vallo Kallaste wrote:
> > > Yes, but I don't have space for crashdump and I can't build new kernel
> > > with limited memory usage because I don't have /usr filesy
It seems Bernd Walter wrote:
> On Sun, Apr 02, 2000 at 08:02:54PM +0200, Vallo Kallaste wrote:
> > Yes, but I don't have space for crashdump and I can't build new kernel
> > with limited memory usage because I don't have /usr filesystem up and
> > running. Is there a way to limit memory usage with
On Sun, Apr 02, 2000 at 08:02:54PM +0200, Vallo Kallaste wrote:
> Yes, but I don't have space for crashdump and I can't build new kernel
> with limited memory usage because I don't have /usr filesystem up and
> running. Is there a way to limit memory usage without recompiling
> kernel? I can store
On Sun, Apr 02, 2000 at 06:16:43PM +0200, Bernd Walter <[EMAIL PROTECTED]> wrote:
> Do you see it only with R5 or also with other organisations?
I don't have any problems with my own -current system which has striped
volume over three UW SCSI disks. SCSI-only system, SMP.
Sources from March 14.
On Sun, Apr 02, 2000 at 05:37:30PM +0200, Bernd Walter <[EMAIL PROTECTED]> wrote:
> > I hook up serial console to get full traceback next time, but I don't
> > have any knowledge for further analysis.
>
> You don't need a serial console to get further informations.
> You should compile the kerne
It seems Bernd Walter wrote:
> On Sun, Apr 02, 2000 at 05:38:01PM +0200, Soren Schmidt wrote:
> > It seems Vallo Kallaste wrote:
> > > On Sun, Apr 02, 2000 at 03:39:35PM +0200, Vallo Kallaste
><[EMAIL PROTECTED]> wrote:
> > >
> > > > I hook up serial console to get full traceback next time, but
On Sun, Apr 02, 2000 at 05:38:01PM +0200, Soren Schmidt wrote:
> It seems Vallo Kallaste wrote:
> > On Sun, Apr 02, 2000 at 03:39:35PM +0200, Vallo Kallaste <[EMAIL PROTECTED]>
>wrote:
> >
> > > I hook up serial console to get full traceback next time, but I don't
> > > have any knowledge for fu
On Sun, Apr 02, 2000 at 05:37:30PM +0200, Bernd Walter wrote:
> Are you for any chance running the NFS Server without nfsd?
> I expect them to be needed if you are serving vinum volumes.
Sometimes I'm to stupid - the NFS case was a different thread.
--
B.Walter COSMO-Project
On Sun, Apr 02, 2000 at 01:50:16AM +0200, Bernd Walter wrote:
> On Sun, Apr 02, 2000 at 01:15:39AM +0200, Bernd Walter wrote:
> >
> > Greg - I'm using vinums raid5 code since months now for FreeBSDs CVS-Tree on
> > 7x 200M disks - it does not hang for me since a long time.
> > The latest current
It seems Vallo Kallaste wrote:
> On Sun, Apr 02, 2000 at 03:39:35PM +0200, Vallo Kallaste <[EMAIL PROTECTED]>
>wrote:
>
> > I hook up serial console to get full traceback next time, but I don't
> > have any knowledge for further analysis.
>
> Here's full traceback, environment is all same, exce
On Sun, Apr 02, 2000 at 03:39:35PM +0200, Vallo Kallaste wrote:
> I got now crash under 4.0-RELEASE, with syncer and bufdaemon in the same
> vrlock state, pax in flswait. I was in single-user mode using pax to
> extract usr archive to newly created raid5 volume. I'm using NFS mount
> with flags -3
On Sun, Apr 02, 2000 at 03:39:35PM +0200, Vallo Kallaste <[EMAIL PROTECTED]>
wrote:
> I hook up serial console to get full traceback next time, but I don't
> have any knowledge for further analysis.
Here's full traceback, environment is all same, except the filesystem is
mounted with async (bef
On Sun, Apr 02, 2000 at 01:50:16AM +0200, Bernd Walter <[EMAIL PROTECTED]> wrote:
> > Greg - I'm using vinums raid5 code since months now for FreeBSDs CVS-Tree on
> > 7x 200M disks - it does not hang for me since a long time.
> > The latest current I tested R5 well is from 19th March on alpha. Th
On Sun, Apr 02, 2000 at 01:15:39AM +0200, Bernd Walter wrote:
>
> Greg - I'm using vinums raid5 code since months now for FreeBSDs CVS-Tree on
> 7x 200M disks - it does not hang for me since a long time.
> The latest current I tested R5 well is from 19th March on alpha. That's shortly
> before PH
On Sat, Apr 01, 2000 at 09:11:40AM +0930, Greg Lehey wrote:
> On Friday, 31 March 2000 at 21:32:22 +0200, Søren Schmidt wrote:
> > Yup, Greg and I know of this problem, it also happens with the wd
> > driver and with CAM, so the problem is probably not the driver.
> > I'm investigating this right
On Fri, Mar 31, 2000 at 09:25:44PM +0200, Vallo Kallaste wrote:
> Hi
>
> I have four (4) ATA disks, all same new 20GB IBM 7200rpm models. Intel
> Seattle BX2 mobo, PIIX4 controller. I'm not expecting any performance
> increase or such, simply want to get my hands on. Ata driver, as the
> -current
It seems Greg Lehey wrote:
>
> The problem that Søren and I are looking at is usually a panic. We
> don't really know where it's happening, but we're each sure it's not
> in *our* code :-) From a Vinum standpoint, it happens between the time
> that Vinum sends a request to the driver and when th
On Friday, 31 March 2000 at 16:37:44 -0800, Matthew Dillon wrote:
>
>> I'm not sure that this is the same problem. Please supply the
>> information I ask for in http://www.lemis.com/vinum/how-to-debug.html.
>>
>> The problem that Søren and I are looking at is usually a panic. We
>> don't really
:I'm not sure that this is the same problem. Please supply the
:information I ask for in http://www.lemis.com/vinum/how-to-debug.html.
:
:The problem that Søren and I are looking at is usually a panic. We
:don't really know where it's happening, but we're each sure it's not
:in *our* code :-) F
On Friday, 31 March 2000 at 21:32:22 +0200, Søren Schmidt wrote:
> It seems Vallo Kallaste wrote:
>> Hi
>>
>> I have four (4) ATA disks, all same new 20GB IBM 7200rpm models. Intel
>> Seattle BX2 mobo, PIIX4 controller. I'm not expecting any performance
>> increase or such, simply want to get my h
It seems Vallo Kallaste wrote:
> Hi
>
> I have four (4) ATA disks, all same new 20GB IBM 7200rpm models. Intel
> Seattle BX2 mobo, PIIX4 controller. I'm not expecting any performance
> increase or such, simply want to get my hands on. Ata driver, as the
> -current doesn't have wd anymore.
> I hav
40 matches
Mail list logo
