Try truncating some files.
-Kip
On Tue, Jul 28, 2009 at 8:29 PM, grarpamp wrote:
> One week old build...
>
> # df -i .
> Filesystem 1K-blocks Used Avail Capacity iused ifree %iused Mounted on
> ram01/mnt1 239465344 239465344 0 100% 13163 0 100% /mnt1
> # ls -aliT zero
> 207
freebsd-stable is not an advocacy list. This is very off-topic.
On Mon, Jun 22, 2009 at 7:06 PM, Daniel Bolgheroni
wrote:
> On Fri, 19 Jun 2009, Holger Kipp wrote:
>
>> On Fri, Jun 19, 2009 at 09:47:35AM +0100, Michal wrote:
>>
>> For the masses:
>>
>> - NetBSD: Run on any hardware (including
> I agree, this shouldn't necessarily be treated as flamebait or trolling.
>
> But shouldn't the question be redirected to the advocacy mailing
> list/team?
Yes. This list is for targeted technical questions. It isn't realistic
to expect a discussion of this nature to stay on-topic.
-Kip
Individuals in each of the camps (Free, Open, Net) are frequently
deeply invested in their platforms of choice to the point where they
identify with them. In addition, many if not most of us are only
familiar with one of them. Thus, it isn't really fair to ask us to
compare the three. You will enjo
> I was wondering if there are plans to document and keep the ZFS user library
> as a reasonably stable API.
You really need to ask that on the ZFS lists. Usually Solaris man
pages indicate that an API is not stable (assuming) man pages exist.
With a few minor exceptions, ZFS in FreeBSD just trac
On Sat, Jun 13, 2009 at 1:53 PM, Dan Allen wrote:
> I have now proven that the recent post June 8th version of
>
> /usr/src/sys/boot/i386/loader/Makefile
>
> causes catastrophic data loss.
Then it should be disabled by default until the problem is fixed.
> Why on earth would this change no
show sleepchain
show thread 100263
On Fri, Jun 12, 2009 at 6:56 AM, Andriy Gapon wrote:
>
> This is on a recent stable/7 amd64, with zpool and filesystems upgraded to the
> latest version.
> I did zfs rollback x...@yyy
> And then did ls on a directory in the rolled-back fs.
>
> I have the core fil
fixed.
On Tue, May 26, 2009 at 5:05 AM, Wu, Yue wrote:
> Hi, list,
>
> I have a FreeBSD 7-stable box, which has been cvsed up yesterday, even with my
> src.conf which has the line of WITHOUT_ZFS=yes, FreeBSD always wants to
> install libzfs relative stuffs when installing kernel and world, so erro
On Mon, Jun 8, 2009 at 6:22 AM, Richard
Tector wrote:
> Kip Macy wrote:
>>>
>>> The second bug is the use of LOADER_ZFS_SUPPORT without any
>>> consideration of WITHOUT_CDDL and/or WITHOUT_ZFS (or MK_ZFS)
>
>> I'll try get it fixed by Wednesday.
>
Must be a weird geom interaction. I don't see this with raw disk. I'll
look at it eventually but UMA and performance are further up in the
queue.
-Kip
On Fri, Jun 5, 2009 at 1:44 AM, Ulrich Spörlein wrote:
> On Tue, 02.06.2009 at 11:24:08 +0200, Ulrich Spörlein wrote:
>> On Tue, 02.06.2009 at 11:
On Thu, Jun 4, 2009 at 2:13 PM, Kip Macy wrote:
> As I mentioned in the initial e-mail, auto-tuning is only safe to rely
> on on amd64.
>
Tying ZFS in to UMA to allow zone limits to reduce memory pressure on
write as well as reduce the ARC's ability to grow without bound is on
As I mentioned in the initial e-mail, auto-tuning is only safe to rely
on on amd64.
-Kip
On Thu, Jun 4, 2009 at 7:48 AM, Tim Chase wrote:
> Hello,
>
> I decided to give the new zfs code a try and upgraded my stable-7 system
> and discovered a panic that I can reproduce at will.
>
> This is an i3
> Same here..
>
> The first bug is the use of a LIBZFS variable in
> src/sys/boot/i386/loader/Makefile, as this variable is set in
> share/mk/bsd.libnames.mk
>
> I just replaced LIBZFS by LIBZFSBOOT and the buildworld succeeded.
>
> The second bug is the use of LOADER_ZFS_SUPPORT without any
> cons
On Mon, Jun 1, 2009 at 10:21 AM, Adam McDougall wrote:
> I'm thinking that too. I spent some time taking stabs at figuring it out
> yesterday but didn't get anywhere useful. I did try compiling the -current
> src/sys/boot tree on 7.2 after a couple header tweaks to make it compile but
> the load
Odds are that there are more changes that were made in HEAD to the
loader that need to be MFC'd.
-Kip
On Mon, Jun 1, 2009 at 3:55 AM, Alberto Villa wrote:
> On Mon, Jun 1, 2009 at 12:06 PM, Henri Hennebert wrote:
>> This is the file /boot/loader from 7.2-STABLE which is wrong.
>>
>> You can fin
Please try applying this change to your tree and let me know.
Thanks,
Kip
http://svn.freebsd.org/viewvc/base?view=revision&revision=193110
On Sat, May 30, 2009 at 2:11 AM, Henri Hennebert wrote:
> Kip Macy wrote:
>>
>> On Wed, May 20, 2009 at 2:59 PM, Kip Macy wrote
The flags checks are too strict. File a PR. I'll fix it when I get to
it. Sorrry.
-Kip
On Wed, May 27, 2009 at 7:24 PM, Mike Andrews wrote:
> On Tue, 26 May 2009, Mike Andrews wrote:
>
>> Takahashi Yoshihiro wrote:
>>>
>>> Today's stable has a problem creating a new file via NFS on ZFS.
>>>
>>>
7;d rather find out why owner isn't
NULL when the calling convention expects it. Getting a backtrace from
where the assert is hit would be helpful.
-Kip
>
>
> On Wed, May 27, 2009 at 3:00 AM, Henri Hennebert wrote:
>> Kip Macy wrote:
>>>
>>> On Wed, May 20, 2009
MFC'd in 192969
On Wed, May 27, 2009 at 3:31 PM, Artis Caune wrote:
> 2009/5/28 Lorenzo Perone :
>> Hi, I'm a bit confused:
>>
>> I can't find this change (rev 185095) in the stable log, yet stable has some
>> other
>> recent changes related to the current posts (in turn commited also to
>> head)
27; could not be loaded as it was last accessed by another
>> system (host: unset hostid: 0x8a08f344). See:
>> http://www.sun.com/msg/ZFS-8000-EY
>> zdb: can't open rpool: No such file or directory
>>
>> But rpool have been used for many boot now -
I haven't looked at the panic yet, but adding a USB quirk (no
SYNCHRONIZE_CACHE) would certainly reduce the noise in your logs.
-Kip
On Mon, May 25, 2009 at 4:16 AM, Henri Hennebert wrote:
> Kip Macy wrote:
>>
>> On Wed, May 20, 2009 at 2:59 PM, Kip Macy wrote:
>>&
Motin is your best bet in tracking down ATA problems.
Cheers,
Kip
On Fri, May 22, 2009 at 10:40 AM, Joe Karthauser wrote:
> Hi Kip,
>
> I seriously don't understand what has happened. If I boot kernel.old I still
> get the same problem. Very confusing. :(.
>
> Joe
>
> I did an update on one of my less critical boxes today. I upgraded the
> version as well to lucky 13 :) So far so good! I am rsyncing a few hundred
> GB to it now. One thing I noticed, and not sure if this is normal because
> of the compression, the capacity shows 31%, df shows 13%
Your sna
Looks like a (corrupted) space management bug. I'll take a closer look
this weekend to see if it can be recovered from.
-Kip
On Thu, May 21, 2009 at 12:50 PM, Dmitry Morozovsky wrote:
> On Wed, 20 May 2009, Kip Macy wrote:
>
> KM> I will be MFC'ing the newer ZFS support so
I have no idea what is happening. I think our best bet is having
someone with insight into ATA provide us with help in adding
diagnostics.
Sorry for the trouble. Perhaps you can just roll back to 7.2 for now.
Cheers,
Kip
On Thu, May 21, 2009 at 10:50 AM, Joe Karthauser wrote:
> Hmm, I've had a
>> Please, fix 4 times repetition of all its content in
>> stable/7/cddl/compat/opensolaris/include/libshare.h.
>>
>
> The same:
> stable/7/sys/cddl/compat/opensolaris/sys/pathname.h
> stable/7/sys/cddl/compat/opensolaris/sys/kidmap.h
> stable/7/sys/cddl/compat/opensolaris/sys/file.h
>
fixed by r1
>
> Unfortunately not a lot but we can do the following:
>
> - Donate some hardware (Fibre Channel HBAs) to the FreeBSD project (paid
> from my pocket, not my employer's one);
> - Donate some money (paid from my employer's pocket, if I can demonstrate
> that this can help us to save big bucks on hi
> Not really a problem but a question: Is the v13 on-disk format
> exactly the same as that used by Solaris/Opensolaris?
It is supposed to be. The sources are the same. However, I have not
tested interoperability.
> Does this make
> it possible to have a ZFS-only dual boot system running FreeBS
On Wed, May 20, 2009 at 2:59 PM, Kip Macy wrote:
> I will be MFC'ing the newer ZFS support some time this afternoon. Both
> world and kernel will need to be re-built. Existing pools will
> continue to work without upgrade.
>
>
> If you choose to upgrade a pool to take ad
On Wed, May 20, 2009 at 3:11 PM, Mike Tancsa wrote:
> At 05:59 PM 5/20/2009, Kip Macy wrote:
>>
>> If you choose to upgrade a pool to take advantage of new features you
>> will no longer be able to use it with sources prior to today. 'zfs
>> send/recv' is
I will be MFC'ing the newer ZFS support some time this afternoon. Both
world and kernel will need to be re-built. Existing pools will
continue to work without upgrade.
If you choose to upgrade a pool to take advantage of new features you
will no longer be able to use it with sources prior to toda
On Tue, May 19, 2009 at 4:00 PM, Dmitry Morozovsky wrote:
> On Tue, 19 May 2009, Kip Macy wrote:
>
> KM> I created a branch for a reason. With all the renames applying a patch
> KM> is a nightmare. Either use the branch or wait until I do the MFC.
>
> Ah well, Kip, t
I created a branch for a reason. With all the renames applying a patch
is a nightmare. Either use the branch or wait until I do the MFC.
Cheers,
Kip
On Tue, May 19, 2009 at 3:49 PM, Dimitry Andric wrote:
> On 2009-05-19 23:57, Dmitry Morozovsky wrote:
>> ... but then again, on `build all'' p
Many people are happily running an old pool with the new code. I have
done that in a VM and run load over it just to be certain. The tuning
still applies to i386. On amd64 vm backpressure works, but may
actually be too aggressive - shrinking the ARC in favor of the
inactive pages queue.
Cheers,
Ki
For those of you who prefer to stay on a release I've created a 7.2
branch with v13 ZFS.
http://svn.freebsd.org/base/user/kmacy/releng_7_2_zfs/
--
When bad men combine, the good must associate; else they will fall one
by one, an unpitied sacrifice in a contemptible struggle.
Edmund Burke
On Sun, May 17, 2009 at 3:19 PM, Dmitry Morozovsky wrote:
> On Sun, 17 May 2009, Kip Macy wrote:
>
> KM> I will if you can reproduce on this branch. A lot has changed between
> KM> ZFS v7 and ZFS v13.
>
> So, if I understand you correctrly, you wish me to upgrade to the la
I will if you can reproduce on this branch. A lot has changed between
ZFS v7 and ZFS v13.
-Kip
On Sun, May 17, 2009 at 3:48 AM, Dmitry Morozovsky wrote:
> Kip,
>
> On Fri, 15 May 2009, Kip Macy wrote:
>
> KM> I've MFC'd ZFS v13 to RELENG_7 in a work branch. Please
I've MFC'd ZFS v13 to RELENG_7 in a work branch. Please test if you can.
http://svn.freebsd.org/base/user/kmacy/ZFS_MFC/
The standard disclaimers apply. This has only been lightly tested in a
VM. Please do not use it with data you care about at this time.
Thanks,
Kip
--
When bad men combine,
I think most if not all of the gains are from increasing the maximum
tcp socket buffer sizes.
You might test it out with only those to confirm.
-Kip
On Thu, Apr 9, 2009 at 3:42 PM, Freddie Cash wrote:
> On Wed, Apr 8, 2009 at 3:55 PM, Antony Mawer wrote:
>> Freddie Cash wrote:
>> ...
>>> We'
see ixgbe(4)
On Wed, Feb 11, 2009 at 2:43 PM, Greg Rivers
wrote:
> I'm trying to light an Intel 10GbE adapter in an HP DL380 G5 using very
> recent 7.1-STABLE amd64 with GENERIC kernel. I expected the ixbg(4) driver
> to attach, but it does not.
>
> The labels on the card show:
>INTEL(R)
I don't know off hand how you could end up with that many pipes.
Nonetheless, sys_pipe.c has a good explanation of what that does and
how pipe sizing works.
-Kip
On Thu, Nov 13, 2008 at 9:37 PM, Bruce Simpson <[EMAIL PROTECTED]> wrote:
> I just got lots and lots of this:
> kern.ipc.maxpipekva e
>
> You sound as if you just got the machine and haven't given MacOS X a chance.
> Give MacOS X a chance. Download (if its not on your MacOS X install DVD) X
> Code, and Apple X11.
>
X11 is barely usable under Leopard. Apps crash regularly and
full-screen doesn't work.
He may simply want to be ab
On Sat, Aug 23, 2008 at 9:34 PM, Sevan / Venture37
<[EMAIL PROTECTED]> wrote:
>
>
>> I can't find anything that suggests NetBSD runs on sun4v. Their sparc64
>> port only covers the US-I/II families and there's no mention of sun4v.
>
> OpenBSD/sparc64 supports the sun4v architecture & has done for
Hi Peter,
There really isn't any magic to bringing up a port. You compile it,
install it, and then run it until it breaks. Once it breaks you spend
a lot of time instrumenting the code to track down what went wrong.
Then, depending on the amount of technical insight you have in to the
issue, you g
> Well, let's see what architecture the upcoming Rock CPUs are;
> judging their feature list they appear to be a continuation of
> the Fujitsu sun4u line rather than a successor of UST1/2 :)
That is not what I've heard.
-Kip
___
freebsd-stable@freebsd.o
I apologise for cross-posting.
I believe that there is a general expectation by freebsd users and
developers that unsupported code should not be in CVS. Although sun4v
is a very interesting platform for developers doing SMP work, I simply
do not have the time or energy to maintain it. If someone e
On Mon, Aug 18, 2008 at 3:42 PM, Mike Tancsa <[EMAIL PROTECTED]> wrote:
> At 06:32 PM 8/18/2008, Kip Macy wrote:
>>
>> Hi Mike,
>> Could you please check that this doesn't happen on HEAD as well? This
>> same code has been in 8 since shortly after the branch.
Hi Mike,
Could you please check that this doesn't happen on HEAD as well? This
same code has been in 8 since shortly after the branch.
Thanks,
Kip
On Mon, Aug 18, 2008 at 10:14 AM, Mike Tancsa <[EMAIL PROTECTED]> wrote:
> At 12:55 PM 8/18/2008, Kip Macy wrote:
>>
>&g
got it
On Mon, Aug 18, 2008 at 9:22 AM, Mike Tancsa <[EMAIL PROTECTED]> wrote:
> At 10:24 AM 8/18/2008, John Baldwin wrote:
>
>> > Edit src/sys/conf/files
>> >Add delta 1.1243.2.32 2008.07.30.20.35.41 kmacy
>> > Edit src/sys/netinet/tcp_subr.c
>> >Add delta 1.300.2.4 2008.07.30.20.35.4
I'd just like to observe that due to bugs in their real-mode emulation
(only required on intel) FreeBSD won't run on Xen 3.1 in HVM on Intel
processors. This longstanding issue was finally fixed very recently
in the 3.2 branch.
-Kip
On Fri, Feb 29, 2008 at 3:34 PM, Freddie Cash <[EMAIL PROTECTE
What workload, if any, was running at the time?
Have you run memtest on the machine to confirm that there are no memory issues?
-Kip
2008/2/12 Mikhail T. <[EMAIL PROTECTED]>:
> The kernel is from:
> FreeBSD 6.3-STABLE #0: Thu Feb 7 ... amd64
>
> The crash:
>
> Unread portion of the ker
On Jan 14, 2008 1:42 PM, Peter Wemm <[EMAIL PROTECTED]> wrote:
> Kip, do you think a CTASSERT might be in order?
Good idea. Your patch or mine? :-)
-Kip
>
> On Jan 14, 2008 1:27 PM, Kip Macy <[EMAIL PROTECTED]> wrote:
> > Read the comment in pmap.h:
> >
>
Read the comment in pmap.h:
/*
* Size of Kernel address space. This is the number of page table pages
* (4MB each) to use for the kernel. 256 pages == 1 Gigabyte.
* This **MUST** be a multiple of 4 (eg: 252, 256, 260, etc).
*/
#ifndef KVA_PAGES
#ifdef PAE
#define KVA_PAGES 512
#else
#d
Are you sure that the settitle call is disabled on FreeBSD?
On 12/20/07, Krassimir Slavchev <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hello,
>
> I have read all related threads about performance problems with multi
> core systems but still have no idea what
FreeBSD's HWPMC doesn't currently support post-P4 processors.
-Kip
On Dec 8, 2007 7:00 PM, Michael Butler <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> dmesg reads:
>
> Copyright (c) 1992-2007 The FreeBSD Project.
> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1
On Nov 19, 2007 9:53 AM, Anish Mistry <[EMAIL PROTECTED]> wrote:
> On Wednesday 07 November 2007, Anish Mistry wrote:
> > On Monday 05 November 2007, [LoN]Kamikaze wrote:
> > > Marc Fonvieille wrote:
> > > > On Thu, Oct 18, 2007 at 05:53:47PM +0200, [LoN]Kamikaze wrote:
> > > >> Anish Mistry wrote:
It was initially brought in by Alfred but I don't think anyone has
done much work on NFSv4 on FreeBSD. It would be nice to have.
-Kip
On Nov 16, 2007 5:31 PM, Adam McDougall <[EMAIL PROTECTED]> wrote:
> I am beginning to dabble with NFSv4 client functionality. I noticed
> idmapd is not built i
s Kennaway <[EMAIL PROTECTED]> wrote:
> Kip Macy wrote:
> > Unfortunately, ZERO_COPY_SOCKETs have long been a known source of
> > problems. I think also, when a page is copied as part of COW the new
> > page is unwired (see pmap_copy et al.), this could lead to
> > socow
Unfortunately, ZERO_COPY_SOCKETs have long been a known source of
problems. I think also, when a page is copied as part of COW the new
page is unwired (see pmap_copy et al.), this could lead to
socow_iodone unwiring after send a page that was not wired. An added
issue is that parts of the VM assume
Jack, you should know by now that we're not Linux. All we care about
is that you not break the code that we rely on. I'm still slightly
embarrassed when I explain to people that I build if_em as a module
because em0 doesn't come up sometimes due to a race condition on
initialization, so I need to b
The machine is down. Don't know why yet.
-Kip
On 10/3/07, Chris H. <[EMAIL PROTECTED]> wrote:
> Greetings,
> Lately I've been finding it difficult, to impossible to reach freebsd.org.
> (hope this message makes it)
> At any rate, no matter my location; all routes to freebsd.org appear to
> be dea
You're obviously going to have to modify the install scripts to
recognize FreeBSD in addition to RHEL3 & RHEL4. When I tried it on
-CURRENT there was some symbol versioning issue so I just installed it
in a CentOS VM instead (its not for me and its only being used for
development). You'll probably
tially loss of locality on cards that
support multiple queues (i.e. most 10GigE cards).
-Kip
>
> 2007/7/29, Kip Macy <[EMAIL PROTECTED]>:
> >
> > Expanding the net a bit.
> >
> > ------ Forwarded message --
> > From: Kip Macy <[EMAIL P
Expanding the net a bit.
-- Forwarded message --
From: Kip Macy <[EMAIL PROTECTED]>
Date: Jul 28, 2007 2:03 PM
Subject: call for ALTQ users
To: freebsd-net <[EMAIL PROTECTED]>
I'm looking at extending ifnet to support multiple tx queues. It
appears that thi
On 6/17/07, Mike Jakubik <[EMAIL PROTECTED]> wrote:
Kip Macy wrote:
> I don't know. I just deleted dev/cxgb and recreated it from cvs and
> LINT builds for me.
Re-cvsupped your version from RELENG_6 and all is well now.
Good to he
I don't know. I just deleted dev/cxgb and recreated it from cvs and
LINT builds for me.
-Kip
On 6/17/07, Mike Jakubik <[EMAIL PROTECTED]> wrote:
Kip Macy wrote:
> Oops - thanks.
I've included the file from cvs on my box, however i now get this error
while com
Oops - thanks.
On 6/17/07, Mike Jakubik <[EMAIL PROTECTED]> wrote:
mkdep -f .depend -a -nostdinc -DCONFIG_CHELSIO_T3_CORE -DDEFAULT_JUMBO
-DCONFIG_DEFINED -D_KERNEL -DKLD_MODULE -I-
-I/usr/src/sys/modules/cxgb/../../dev/cxgb -DHAVE_KERNEL_OPTION_HEADERS
-I. -I@ -I@/contrib/altq -I@/../include
On 6/6/07, David Christensen <[EMAIL PROTECTED]> wrote:
> I have a version of code ready to MFC, the big difference with CURRENT
> is that TSO is #ifdef'd off until Andre is able to get that back.
Is something broken with TSO? I just added TSO support to bce on
CURRENT
and was planning on MFC'i
On 5/29/07, steve <[EMAIL PROTECTED]> wrote:
Howdy!
I had this issue on 4.x, which is basically, I have
machines that do cgi stuff for customers, and there is a local
md device that is used as a tmp. When it fills the machine
logs errors
vnode_pager_putpages I/O error 28..
and
as i've mentioned in my original email, does mfs speed up I/O stuff ?
there's been a lot of threads in teh past that a buildworld on mfs
increases speed --- tho it might not be the appropriate test for
high-end machines (speaking of w/c I just gots a T2000).
buildworld on NFS or local disk on t
> Please be very careful. The only real alternative (Intel comes and
> goes) is Nvidia whose driver is binary-only for i386 (no amd64
> support) and has a history for being notoriously buggy. I only buy ATI
> because of the problems I keep seeing people have with the Nvidia
> driver. I have a frie
I know you were working on Xen support in FreeBSD, but web about it
(http://www.fsmware.com/xenofreebsd/7.0/STATUS) has one year old info
(support planned in FreeBSD 6.1). So is there any progress, or Xen will
not be in any near future release?
Basically Xen did not mature in the fashion that I
Please be very careful. The only real alternative (Intel comes and
goes) is Nvidia whose driver is binary-only for i386 (no amd64
support) and has a history for being notoriously buggy. I only buy ATI
because of the problems I keep seeing people have with the Nvidia
driver. I have a friend who has
On 3/12/07, Ivan Voras <[EMAIL PROTECTED]> wrote:
Nikolas Britton wrote:
> Free Solaris DVD software kits (Free shipping too):
>
> http://www.sun.com/solaris/freemedia
Or NetBSD: http://www.netbsd.org/Ports/xen/
Heh, you're still confused about what list your on.
__
If you create a patch against -CURRENT I can test on sun4v. The timeouts
with em on sun4v are so severe that I have to use the driver from June for
any kind of workload.
-Kip
On 11/3/06, Jack Vogel <[EMAIL PROTECTED]> wrote:
I have been hard at work trying to understand and fix the
remaining i
On Wed, 18 Oct 2006, Jack Vogel wrote:
> On 10/18/06, Kip Macy <[EMAIL PROTECTED]> wrote:
> > I have a Sun T2000 that I generally run with the em driver from as of
> > July in order to avoid watchdog timeouts. One trivial scenario that
> > reproduces the problem with
I have a Sun T2000 that I generally run with the em driver from as of
July in order to avoid watchdog timeouts. One trivial scenario that
reproduces the problem with 100% consistency is running the ghc
configure script (a 20kloc shell script) over NFS. As the T2000
doesn't exactly represent "typic
>
> Some work is now being done so that -j can be reliably used on
> 'make buildkernel', but I don't think that has been completed yet. For
> now, my own opinion is that you're not going to save enough time with
> -j on buildkernel to justify the amount of time you'll lose if it does
> not work.
Please do not feed the trolls.
-Kip
On Thu, 12 Oct 2006, Danial Thom wrote:
>
>
> --- Alexander Leidinger <[EMAIL PROTECTED]>
> wrote:
>
> > Quoting Dan Lukes <[EMAIL PROTECTED]> (from Thu, 12
> > Oct 2006 09:43:20 +0200):
> >
> > [moved from security@ to [EMAIL PROTECTED
There are a couple of people who have expressed interest in the work,
but no one is working on it currently.
-Kip
On 10/3/06, Marc G. Fournier <[EMAIL PROTECTED]> wrote:
I know there is work being done on this for -HEAD, but does anyone know if it
will run under -STABLE?
I don't see a port fo
eserk.
-Kip
On 9/1/06, Kip Macy <[EMAIL PROTECTED]> wrote:
I've seen this when running stress2 with a large number of
incarnations. Why don't we return an error to the user?
-Kip
On 9/1/06, Julian Elischer <[EMAIL PROTECTED]> wrote:
> Vyacheslav V
I've seen this when running stress2 with a large number of
incarnations. Why don't we return an error to the user?
-Kip
On 9/1/06, Julian Elischer <[EMAIL PROTECTED]> wrote:
Vyacheslav Vovk wrote:
can you see how many threads thre are in the system?
I think you will have to ext
I've seen with libthr. What libraries are you using?
-Kip
On Tue, 22 Aug 2006, Jiawei Ye wrote:
> On 8/16/06, Dan Nelson <[EMAIL PROTECTED]> wrote:
> > > How can mysql use 160%? Is this a reporting bug in top because mysql is
> > > threaded?
> >
> > You have multiple
I haven't been keeping the xen port up to date. There is an SoC student
who is making some progress with it but he is looking more at what is
required to make the installer work with it.
Making 6.2 work would not be that difficult, but no one is currently
working on it.
-Kip
On Sun,
Actually, in my tree, 19 files don't compile. In all of the files I've
looked at PCPU_SET is the offender. My guess is that the issue could be
fixed by passing the type as an argument.
On 2/4/06, Dag-Erling Smørgrav <[EMAIL PROTECTED]> wrote:
>
> Matthew Jacob <[EMAIL PROTECTED]> writes:
> > a) Th
IIRC, at NetApp -O2 was the default for all builds. I think it is safe to
say that the generated code is quite stable. If -O2 allows the compiler to
catch errors earlier it should be the default.
-Kip
On 2/4/06, M. Warner Losh <[EMAIL PROTECTED]> wrote:
>
> In message: <[EMAIL PROTECTED]>
--- Jeroen Ruigrok/asmodai <[EMAIL PROTECTED]> wrote:
> -On [20020411 15:45], Darren Reed
> ([EMAIL PROTECTED]) wrote:
> >By definition, /usr/include/sys _IS_ kernel include
> files.
>
> Err, APIs to kernel related interfaces.
>
> The kernel uses the files in the compile/
> directory, src/inclu
rneath you.
-Kip
On Sat, 6 Apr 2002, Aditya wrote:
> Kip,
>
> with v3 TCP mounts I'm getting:
>
> Stale NFS file handle.
>
> complaints after a few hours of inactivity. I've verified that the filer has
> not rebooted.
>
> Adi
>
>
On Tue, 28 Dec 1999, Vivek Khera wrote:
> > "MS" == Mike Smith <[EMAIL PROTECTED]> writes:
>
> >> FreeBSD has a tendency to panic in out of mbuf situations. That
> >> shouldn't happen.
>
> MS> The semantics of "should" and "shouldn't" are debatable. In this case,
> MS> the panic is a s
Thanks.
-Kip
On Wed, 10 Nov 1999, Scot W. Hetzel wrote:
> From: "Kip Macy" <[EMAIL PROTECTED]>
> > I just grabbed the source from
> > ftp://ftp3.freebsd.org/u/FreeBSD/releases/i386/3.3-RELEASE/src/
> > and ran install.sh.
Thanks to all. I will do that. I was seriously worried that I might have
to install Linux.
-Kip
On Sun, 7 Nov 1999, Jacques Vidrine wrote:
> On 7 November 1999 at 11:36, Mike Smith <[EMAIL PROTECTED]> wrote:
> > Turn off the 'memory stick' device in the
You are, as is so often the case, correct. The way you phrase your
responses sometimes blinds me, and evidently others, to the complete
circumstances.
-Kip
On 21 Sep 1999, Dag-Erling Smorgrav wrote:
> Kip Macy <[EMAIL PROTECTED]> writes:
> > Th
Obviously not from the default settings.
Typically limits are in place to protect something from something. This,
however, may be an exception.
-Kip
On Tue, 21 Sep 1999, David Schwartz wrote:
> > Thanks. Although having maxfiles == maxfilesperproc might
You are correct -- what one really needs is a per user limit on files --
there may already be something to that effect, although I do not know of
it.
On Tue, 21 Sep 1999, Bryan Talbot wrote:
> At 04:23 PM 9/21/99 , Kip Macy wrote:
> >Thanks. Although having maxfiles == maxfilesperp
With their ever-stricter licensing agreements and their ever-less
competitive position in the market, it is likely to be some time before
the source is released under a usable license.
-Kip
On Mon, 20 Sep 1999, Chad R. Larson wrote:
> As I recall, Mike Smith wrot
Is kern.maxfiles the total number of files that can be open on the system
at one time? If so it seems very silly that by default it is the same
number as kern.maxfilesperproc -- meaning that any process can use up the
total number of files available to the system.
Thanks.
I am debugging a mail sending program under 3.3-R. My program received a
SIGBUS: Too many files open on system - this is odd since I did not have
all that many files open and the program itself only had 128 sockets open.
When I type sysctl -a after machdep.msgbuf: I get a couple hundred lines
of:
Would raising the number of NMBCLUSTERS help? Or would it just postpone
the problem? Solaris/x86 also does not have any problems with the code.
-Kip
On Mon, 9 Aug 1999, Marc Olzheim wrote:
> > Isn't this a huge problem for ordinary users on a system?? I mean
> >
98 matches
Mail list logo
