Well I spoke too soon. I increased the load even more and it crashed again.
Same IP. So FYI, mpsafenet did not work, although it did allow me to stress
the system for longer than I've ever done before. Perhaps that just reduced
the concurrency enough. I will try kernel trace next.
Thanks,
Benjie
It has been impossible to change kern.ngroups - at least for several years
now. It was not fixed in either 5.x or 6.x :
http://lists.freebsd.org/pipermail/freebsd-bugs/2007-January/022140.html
It is seemingly a difficult problem:
http://www.atm.tut.fi/list-archive/freebsd-stable/msg09969.html
You are right, they may not be the same. From first look it seems like they
are similar based on the description of the problems -- system stable, then
under load related to network, get panic after different time intervals. I
just assumed that kernel is typically stable enough that this kind of pa
On Mon, 24 Sep 2007, John-Mark Gurney wrote:
> Ian Smith wrote this message on Sat, Sep 22, 2007 at 13:16 +1000:
> > This drew a blank in -questions. I don't know where else to post it, so
> > I'm hoping someone here might be able to spare me a clue.
>
> You should probably have posted this
On Tue, Sep 25, 2007 at 06:19:30PM -0400, Mark Saad wrote:
> Does anyone know off hand if this works in FreeBSD or NetBSD?
The last time (about 1.5 months ago) I tried the iSCSI target from
ports -- net/iscsi-target, it had some issues.
The first was that it didn't work with raw devices. The cau
On Monday 03 September 2007 08:03:53 am Yar Tikhiy wrote:
> On Sun, Sep 02, 2007 at 11:18:04AM -0700, Tim Kientzle wrote:
> > Yar Tikhiy wrote:
> > >Hi all,
> > >
> > >I've had to use /rescue recently and felt lack of a few basic tools
> > >in it, namely pgrep(1), head(1), tail(1), tee(1), and a te
On Wed, Sep 26, 2007 at 06:20:14PM +0200, Michael Reifenberger wrote:
> That issue is fixed.
Just looked at netbsd-iscsi-20070908 and it does look fixed in that
version.
Thanks,
Craig
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org
Hi,
...
> The other thing was that it was listening on a different port number
> than the FreeBSD initiator was trying to connect to. For some reason
> even though iscsi-target claims to have a "-p" option to specify the
> port number, after reading the code it was clear that it doesn't
> actually
rsync.net wrote:
It has been impossible to change kern.ngroups - at least for several years
now. It was not fixed in either 5.x or 6.x :
http://lists.freebsd.org/pipermail/freebsd-bugs/2007-January/022140.html
It is seemingly a difficult problem:
http://www.atm.tut.fi/list-archive/freebsd-sta
Are they any other target ports available ? Does Open-iSCSI work ?
Anyone working on it ?
Craig Boston wrote:
On Wed, Sep 26, 2007 at 06:20:14PM +0200, Michael Reifenberger wrote:
That issue is fixed.
Just looked at netbsd-iscsi-20070908 and it does look fixed in that
version.
Thanks,
Craig
rsync.net wrote:
On Wed, 26 Sep 2007, Julian Elischer wrote:
rsync.net wrote:
It has been impossible to change kern.ngroups - at least for several years
now. It was not fixed in either 5.x or 6.x :
http://lists.freebsd.org/pipermail/freebsd-bugs/2007-January/022140.html
It is seemingly a d
rsync.net wrote:
of more
than 16 groups, and that is currently impossible.
We are happy to lend financial support to a solution ... however it sounds
like $500 and free rsync.net storage space isn't going to be sufficient ?
Is it unexpected that someone has run into this limit ?
no. Others ha
12 matches
Mail list logo
