Hello,
I've upgraded a working blacklistd with ipfw server from 12.1 to 12.2
and now it gives the following error:
blacklistd[51583]: getnum: /etc/blacklistd.conf, 22: Bad number for
service []
My config:
rc.conf:
blacklistd_enable="YES" #
activates
> -Original Message-
> From: Matthias Apitz
> Sent: Monday, April 29, 2019 10:50 AM
> To: Emmanuel Vadot
> Cc: Kris Moore ; FreeBSD Stable sta...@freebsd.org>; freebsd-...@freebsd.org; freebsd-
> hack...@freebsd.org; FreeBSD Current ;
> freebsd-pkgb...
> -Original Message-
> From: Rodney W. Grimes
> Sent: Monday, April 29, 2019 10:41 AM
> To: Kris Moore
> Cc: Rodney W. Grimes ; Goran Mekić
> ; Emmanuel Vadot ; FreeBSD
> Stable ; FreeBSD Current curr...@freebsd.org>; freebsd-pkgb...@freebsd.org; freebsd-
>
e packages haven't pushed to the
mirrors yet, Jenkins is still chewing on a build of them here. I was using
the 12-stable packages yesterday which has these changes. They should be
synced up to the mirrors in the next 24-48 hours. Sorry about the confusion.
--
Kris Moore
Vice President of E
>
> > For UFS, there will need to be additional care taken when doing updates.
> >
> > --
> > Kris Moore
> > Vice President of Engineering
> > iXsystems, Inc
> > Ph: (408) 943-4100
> > Ph: (408) 943-4101
> > The Groundbreaking TrueNAS M-Series -
> > E
On Mon, Apr 29, 2019 at 9:55 AM Emmanuel Vadot
wrote:
> On Mon, 29 Apr 2019 09:25:05 -0400
> Kris Moore wrote:
>
> > On Mon, Apr 29, 2019 at 8:12 AM Emmanuel Vadot
> > wrote:
> >
> > >
> > > Hi Kris,
> > >
> > > On Sun, 28 Apr 20
Correct, this is ZFS only. And it's something we're using specific to FreeNAS /
TrueOS, which is why I didn't originally mention it as apart of our CFT.
For UFS, there will need to be additional care taken when doing updates.
--
Kris Moore
Vice President of Engineering
iX
On Mon, Apr 29, 2019 at 8:12 AM Emmanuel Vadot
wrote:
>
> Hi Kris,
>
> On Sun, 28 Apr 2019 15:52:21 -0400
> wrote:
>
> > FreeBSD Community,
> >
> >
> >
> > I'm pleased to announce a CFT for builds of FreeBSD 12-stable and
> 13-current
&g
Its on the agenda for next months Working Group. That and tooling to help
migrating to pkg base and keeping /etc files intact.
--
Kris Moore
Vice President of Engineering
iXsystems, Inc
Ph: (408) 943-4100
Ph: (408) 943-4101
The Groundbreaking TrueNAS M-Series -
Enterprise Storage & Ser
sign we're
using here is compelling enough that it can be adopted in FreeBSD.
Some cool asides, being able to 'pkg install src' and have /usr/src be kept in
sync with the current packages is super handy. 😉
--
Kris Moore
Vice President of Engineering
iXsystems, Inc
P
se-docs/
Download Links
-
FreeBSD 12-STABLE:
https://pkg.trueos.org/iso/freebsd12-pkgbase/
FreeBSD 13-CURRENT:
https://pkg.trueos.org/iso/freebsd-pkgbase/
--
Kris Moore
Vice President of Engineering
iXsystems, Inc
Ph: (408) 943-4100
Ph: (408) 943-4101
The G
the base version when its ready. However the
port is super useful for testing new ZoL versions / fixes, so we'll probably
want to keep both around for the time being.
--
Kris Moore
Vice President of Engineering
iXsystems, Inc
Ph: (408) 943-4100
Ph: (408) 943-4101
The Groundbreaking TrueN
EAD
https://pkg.trueos.org/iso/freebsd13-zol/
Please report issues on our GitHub tracker at:
https://github.com/zfsonfreebsd/ZoF
Thanks and happy testing!
--
Kris Moore
Vice President of Engineering
iXsystems, Inc
Ph: (408) 943-4100
Ph: (408) 943-4101
The Groundbreaking
On 4/7/2019 6:49 AM, Matthew Macy wrote:
On Sat, Apr 6, 2019 at 1:23 PM Michael Butler
wrote:
I'd be interested to see if substituting the port net/intel-em-kmod
has any effect on the issue,
I would as well. igb, em, and lem are all the same driver in 12. This
makes maintenance a lot easier.
On 4/6/2019 2:56 AM, Pete French wrote:
Something odd going on there there - I am using 12-STABLE and I have
igb just fine, and it attaches to the same hardware that 11 did:
I ran apache bench, and I got a result of 100 requests/sec on 12-STABLE
vs 16,000 requests/sec on 11-STABLE. So somethin
On 4/6/2019 2:56 AM, Pete French wrote:
Something odd going on there there - I am using 12-STABLE and I have
igb just fine, and it attaches to the same hardware that 11 did:
It does work in 12, throughput is great, just that the latency is higher
than 11.
igb0: flags=8843 metric 0 mtu 1500
o
Hello,
I've upgraded from Stable 11 to Stable 12, and noticed that igb has been
removed and is now part of em driver. However, the performance seems a
lot worse. This is using HP 366FLR which is just HP's version of Intel
i350 I believe.
I've tried incorporating the sysctl settings I used in
/tcp_reass_plugzoneleak_10.x.r227986.patch
>>
>>
>> The patch is against head r227986 but will apply and work correctly for
>> 9.0 as well.
>>
>
> Cleanly applied against RELENG_9_0.
>
> As my case was not exactly the same as Kris or Stefan I'd wait thei
On Fri, Nov 25, 2011 at 11:23 PM, Lawrence Stewart wrote:
> On 11/25/11 13:01, Lawrence Stewart wrote:
>
>> On 11/24/11 18:02, Kris Bauer wrote:
>>
>>> Hello,
>>>
>>> I am currently experiencing an issue with FreeBSD 9.0-RC2 r227852
>>>
On Thu, Nov 24, 2011 at 10:20 PM, Lawrence Stewart wrote:
> On 11/25/11 14:19, Kris Bauer wrote:
>
>> On Thu, Nov 24, 2011 at 8:00 PM, Jeremy Chadwick
>> wrote:
>>
>> On Thu, Nov 24, 2011 at 07:13:39PM -0600, Kris Bauer wrote:
>>>
>>>> On Thu, N
On Thu, Nov 24, 2011 at 8:00 PM, Jeremy Chadwick
wrote:
> On Thu, Nov 24, 2011 at 07:13:39PM -0600, Kris Bauer wrote:
> > On Thu, Nov 24, 2011 at 5:35 PM, Adrian Chadd
> wrote:
> >
> > > Have you tried disabling the tcp offload features of your NIC?
> > >
>
o/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
>
To test this, I added net.inet.tcp.tso=0 to sysctl.conf and restarted the
box; it didn't work. net.inet.tcp.reass.cursegments immediately started
climbing u
On Thu, Nov 24, 2011 at 4:06 PM, Stefan Bethke wrote:
> Am 24.11.2011 um 21:30 schrieb Kris Bauer:
>
> > On Thu, Nov 24, 2011 at 1:20 PM, Raul wrote:
> >
> > I am seeing the same sorts of things in netstat & vmstat:
> >
> > # netstat -s -p tcp |gre
__
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
>
I am seeing the same sorts of things in netstat & vmstat:
# netstat -s
On Thu, Nov 24, 2011 at 10:33 AM, Ivan Voras wrote:
> On 24.11.2011. 8:02, Kris Bauer wrote:
>
>> Hello,
>>
>> I am currently experiencing an issue with FreeBSD 9.0-RC2 r227852 where
>> the
>> net.inet.tcp.reass.curesegments value is constantly increasing (
the reass.maxsegments value to 16384 to temporarily avoid
the problem, but the cursegments number keeps rising and it seems it will
occur again.
Is this an issue that anyone else has seen? I can provide more information
if need be.
Thanks,
Kris
, Oct 21, 2009 at 14:11, Kris Weston wrote:
> > been looking for months now, trawled google no help, i just dont
> understand.
> > do you need a GPT table with zfs ?
> > i have a pentium D 3ghz (running 64bit stable 7.2) and i cant seem to
> import
> > my zpool into
been looking for months now, trawled google no help, i just dont understand.
do you need a GPT table with zfs ?
i have a pentium D 3ghz (running 64bit stable 7.2) and i cant seem to import
my zpool into it
exported fine on solaris , its definitely the same version (v13)
but when i import into zfs i
hey upgraded to 4.0.
Kris
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
you
reproduce the problem with the provided instructions yourself?
Kris
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
hi guys n gals,
im getting a problem about corrupt GPT tables upon trying to import my
solaris mirror.
should i just overwrite the GPT ? and if anyone can tell me how that
would be awesome ?
im on 7.2 stable zfs v13
ive seen its a known issue on the forums but cant see a solution ?
thanks
--
particular problem is included in later releases.
Kris
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
needed. Thanks.
Unread portion of the kernel message buffer:
panic: lock (sleep mutex) Giant not locked @
/usr/src/sys/kern/kern_ntptime.c:965
This is strange because the corresponding mtx_lock is only a few lines
above. Can you provide your kernel config?
Kris
cpuid = 1
Uptime: 1d15h34m6s
the /home fs to disable softupdates. I also removed the
.snap directory.
I would appreciate any suggestions...
http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html
Kris
___
freebsd-stable@freebsd.org mailing list
http://lists.free
t in a changing codebase
this is never possible to guarantee or to always achieve.
Kris
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Pete Carah wrote:
Kris writes:
You and anyone else seeing performance problems should try to work
through the advice given here:
> http://people.freebsd.org/~kris/scaling/Help_my_system_is_slow.pdf
<http://people.freebsd.org/%7Ekris/scaling/Help_my_system_is_slow.pdf>
Well,
c/sys/i386/i386/exception.s:205
(kgdb)
Looks likely to be a hardware fault, to me.
Kris
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
You and anyone else seeing performance problems should try to work
through the advice given here:
http://people.freebsd.org/~kris/scaling/Help_my_system_is_slow.pdf
Kris
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/list
again, run savecore to save the
crashdump (assuming one was made).
Kris
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
e kernel. If the -o reserve option is not
set, creating and filling a large malloc-backed
memory
disk is a very easy way to panic a system.
You almost never want to use malloc backing for a md, in favour of swap
backing.
Kris
to the
deadlock.
Kris
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
clone becomes so large that my pool fills up :-)
I should have a few months before that happens though.
Is it possible you could boot a -current system and promote the clone
without upgrading your pools/filesystems, then reboot to -stable?
The promotion is not backwards co
but I trust that everyone will
appreciate the need to watch and wait before dumping an enormous and
potentially risky filesystem change into the laps of all 7-STABLE users.
Kris
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/ma
down the cause?
See the developers handbook chapter on kernel debugging for full
instructions on how to gather the necessary information to proceed.
Kris
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
is so confidently without even comparing
the process wait channels.
Peter, there was a bug causing dump to hang (completely unrelated to
UFS2 snapshot generation) merged to RELENG_7 a month or so ago. Can you
try updating?
Kris
___
freebsd-stable
Mario Sergio Fujikawa Ferreira wrote:
On Sun, Sep 21, 2008 at 11:48:19AM +0100, Kris Kennaway wrote:
Mario Sergio Fujikawa Ferreira wrote:
Hi,
I've been running FreeBSD 7.0-STABLE from August 1 without problems.
I tried updating to the latest -STABLE but I got a system panic.
rg/~lioux/panic/2008092100/pciconf.txt
- 'sysctl -a'
http://people.freebsd.org/~lioux/panic/2008092100/sysctl.txt
- /etc/sysctl.conf
http://people.freebsd.org/~lioux/panic/2008092100/sysctl.conf
- gdb backtrace?
Kris
___
freebsd-stable@free
O. Hartmann wrote:
Kris Kennaway wrote:
O. Hartmann wrote:
O. Hartmann wrote:
Kris Kennaway wrote:
O. Hartmann wrote:
Kris Kennaway wrote:
O. Hartmann wrote:
Steve Bertrand wrote:
Dan Allen wrote:
Well I got bit by this and am dead in the water. Nothing
builds. I tried the DEBUG_FLAGS
O. Hartmann wrote:
O. Hartmann wrote:
Kris Kennaway wrote:
O. Hartmann wrote:
Kris Kennaway wrote:
O. Hartmann wrote:
Steve Bertrand wrote:
Dan Allen wrote:
Well I got bit by this and am dead in the water. Nothing
builds. I tried the DEBUG_FLAGS=-g trick but to no avail.
My 7.0 box
O. Hartmann wrote:
Kris Kennaway wrote:
O. Hartmann wrote:
Steve Bertrand wrote:
Dan Allen wrote:
Well I got bit by this and am dead in the water. Nothing builds.
I tried the DEBUG_FLAGS=-g trick but to no avail.
My 7.0 box upgraded fine this morning:
FreeBSD ids.eagle.ca 7.1-PRERELEASE
- the module does not load automatically at initialization
time nor is it loadable via kldload (there is an error about missing
opensolaris module but I can't find anything about this module ...).
It's new, you need to build it.
Kris
___
free
interfaces with the "bare
metal", and who are willing to make a long term (multi-year) commitment
to supporting the platform.
Kris
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe
ngs he looked at, but
the most serious bugs might be in pmap or perhaps trap handling.
Operationally, things like buildworld -jN die quickly with random
signals, kernel traps, etc.
Kris
P.S. It looks like marius has made progress on US III but sun4u is still
cking this down!
Kris
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Borja Marcos wrote:
On Aug 13, 2008, at 3:18 PM, Kris Kennaway wrote:
Borja Marcos wrote:
((Sorry for the long dump))
(gdb) bt
#0 0x3827cfe7 in __error () from /lib/libthr.so.3
#1 0x3827cd4a in __error () from /lib/libthr.so.3
#2 0x08702120 in ?? ()
As you can see the debugging symbols
ot be relevant in
your situation.
Kris
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
.so.3
Previous frame identical to this frame (corrupt stack?)
(gdb)
and it seems all the threads in the process are stuck here. Any ideas?
This trace doesn't show anything really. You need to recompile the
binaries with debugging symbols as we
ot;
Well, that is a workaround for some users, but it's not a solution.
Kris
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
to fix it.
Kris
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
system, but
we found that if we run varnish using malloc mode with big swap, it
became stable.
Thank you all for the information, I'll try to look into the kernel code.
See
http://www.freebsd.org/cgi/getmsg.cgi?fetch=540837+0+/usr/local/www/db/text/2008/freebsd-questions/2
from 6.2-RELEASE to
6.3-RELEASE with freebsd-update.
We use the same hardware (board and chassis), and have no such problems
running both RELENG_6 and RELENG_7.
I don't think your issue is specific to the board or chassis. Kris's
explanation makes a lot more sense. :-)
Jeremy/Kris/C
Kostik Belousov wrote:
On Mon, Jul 28, 2008 at 09:52:45PM +0200, Kris Kennaway wrote:
Kostik Belousov wrote:
On Mon, Jul 28, 2008 at 01:16:39PM -0400, Michael toth wrote:
I had someone run a Dell Diags CD on the machine and it passed all tests.
Before that it core'd again; here i
, but can
never tell you when a machine is working perfectly.
Kris
You may use memtest86 (Google for it) for memory/chipset/cpu cache
test.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubs
(kgdb) q
Not much there, check for RAM/hardware problems.
Kris
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
nted
WARNING: /tmp was not properly dismounted
WARNING: /usr was not properly dismounted
WARNING: /var was not properly dismounted
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail
s more
capable then it is a performance optimization.
Someone needs to obtain the usual debugging information.
Kris
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
command would not complete. I did not see any messages in
/var/log/message. State in top showed 'ufs-'.
That means that it was UFS that hung, not ZFS. What was the process
backtrace, and what role does UFS play on this system?
Kris
A similar test on solaris express developer edition
;t confuse the issue :)
Kris
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
backtraces always the same, no, they are
not. But I am still confused as to what this means??
I would appreciate any further insight anyone can give.
That's another corrupted backtrace that doesn't point to an actual
software problem. Still sounds like bad RAM, or bad hardware.
Royce Williams wrote:
Kris Kennaway wrote, on 7/22/2008 12:12 PM:
Royce Williams wrote:
db> trace
Tracing pid 71182 tid 100325 td 0xcc08b180
kdb_enter(c095f294) at kdb_enter+0x2b
panic(c09768ad,1000,1400,c145bc88,1000,...) at panic+0x127
kmem_malloc(c14680c0,1000,102,eba6a8cc,c07e3
is probably the "kmem_map too
small" panic. It says that your kernel ran out of memory, and the
solution is to fix that situation by giving more memory to the kernel.
Increase the vm.kmem_size tunable until your system stops running out of
memory on your wor
Mikhail Teterin wrote:
Kris Kennaway написав(ла):
Well, I mean kernel backtrace.
Can I obtain that remotely and without restarting/panicking the box?
Thanks,
-mi
kgdb on /dev/mem or procstat
Kris
___
freebsd-stable@freebsd.org mailing list
Jeremy Chadwick wrote:
On Tue, Jul 22, 2008 at 12:13:25PM -0400, Mikhail Teterin wrote:
Kris Kennaway ???(??):
Mikhail Teterin wrote:
Hello!
My attempt to build openoffice.org-3 seems to be hanging. Pressing
Ctrl-T produces:
load: 0.11 cmd: tcsh 79759 [sleeping without queue
Thanks!
What is the process backtrace?
Kris
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
David Southwell wrote:
On Thursday 17 July 2008 06:39:26 Kris Kennaway wrote:
David Southwell wrote:
It looks as though I have missed something!!
FreeBSD dns1.vizion2000.net 7.0-STABLE FreeBSD 7.0-STABLE #0: Wed Jul 16
09:27:38 PDT 2008
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC amd64
ch port(s) you didnt recompile as part of the upgrade (e.g.
check mtime in /usr/local), and do that now. You may need to also
recompile the ports that depend on them to undo the damage.
Kris
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.
m running
6.3 patch 2.
Unless you have information you haven't yet shared, no it doesn't :)
"Fatal trap 12" is an effect, not a cause. We still need your backtrace
to make progress understanding the cause of your panic.
Kris
_
gger and obtain backtraces etc, which is useful when dumps are
not being saved.
Kris
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ould be (your data stream
could be corrupted in transit and you'd never know until you tried to
verify or restore the backup).
Kris
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
eg->uk_size,
Is this that you were looking for?
Are you sure that is the same source tree you are running? The
7.0-RELEASE source has the zone->uz_ctor on line 1835, which is
consistent with your backtrace.
Kris
___
freebsd-stable@freeb
d cause it
otherwise but I don't know this code in detail.
Do all of the panics have the same backtrace?
Kris
#10 0x80661ecf in ffs_vget (mp=0xff00047f4978, ino=47884512,
flags=2, vpp=0xb1d7f728) at uma.h:277
#11 0x8066d010 in ufs_lookup (ap=0xb1d7f
y own tiny script.
Kris
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ll very new and experimental
(however, ZFS is marked experimental, too), so you probably
don't want to use it on critical production machines.
Let's not get carried away here :)
Kris
___
freebsd-stable@freebsd.org mailing list
http://lists.fre
ntentional", yes. They were
written to support bg fsck, not as a lightweight filesystem feature for
general use.
Kris
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
b/ddb backtraces.
Kris
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
eems a bit dated also. 'if you last updated from
current before 20020224 or from -stable before 20020408.'
Or is upgrading from 5.x to 7 also supported?
I think so, yes.
Kris
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.
f GEOM, so it's all fine. e.g. you can build a
zpool on top of a gmirror if you wanted to (although that example would
probably be pointless)
Kris
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
about the metadata format changed in one of
the geom providers (mirror/stripe/something) so there might be a problem
there. Try to research whether that is the case.
In general you'll be better off if you just run it on 7.0 of course.
Kris
_
[EMAIL PROTECTED] wrote:
-- Original message --
From: Kris Kennaway <[EMAIL PROTECTED]>
[EMAIL PROTECTED] wrote:
I have a fresh install of FreeBSD 7.0 but it it seems several system related
modules are broken. One I would like to have a solution on urgen
me to get started?
You'll have to start by showing us exactly what you are doing, and what
is going wrong.
Kris
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
rectly, and either port their changes
directly or by taking patches from freebsd ports.
Kris
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Lev Serebryakov wrote:
Hello, Kris.
You wrote 23 июня 2008 г., 19:56:14:
Is there a PR filed with this bug? Having the specific information
recorded will be very useful.
Kostik (kib@) says, that I don't need to fill PR for this issue...
OK, that is good enough for me :)
n deadlock in buffer allocator when
buffer map is fragmented (thnx to [EMAIL PROTECTED]). Workaround is known:
don't
use FSes with 16Kb and 64Kb blocks on same system in one time. 16/32
mixture works well :)
Is there a PR filed with this bug? Having the spe
Martin Cracauer wrote:
Kris Kennaway wrote on Mon, Jun 16, 2008 at 11:27:53AM +0200:
Martin Cracauer wrote:
Kris Kennaway wrote on Sat, Mar 01, 2008 at 10:22:26PM +0100:
Jakub Siroky wrote:
I've just confirmed the same situation on 6.2-RELEASE amd64/GENERIC. I
did not noticed it b
Martin Cracauer wrote:
Kris Kennaway wrote on Sat, Mar 01, 2008 at 10:22:26PM +0100:
Jakub Siroky wrote:
I've just confirmed the same situation on 6.2-RELEASE amd64/GENERIC. I
did not noticed it before because I started using ext2fs extensively
some months ago.
Regards,
Jakub
On Sat, 1
e in 7.x). I don't know if it is possible to
downgrade a pool - you should check the ZFS documentation/support materials.
Kris
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
?? ()
#17 0xc0700746 in crypto_invoke (cap=0x8, crp=0xd61a0950,
hint=-1616994916) at cryptodev_if.h:53
Previous frame inner to this frame (corrupt stack?)
(kgdb)
Unfortunately the trace is bogus. Try to rebuild with -O instead of -O2
and reproduce the panic.
Kris
Jona Joachim wrote:
On Sun, Jun 08, 2008 at 03:57:55PM +0200, Kris Kennaway wrote:
Jona Joachim wrote:
Hi!
pkg_delete core dumps on me when it tries to remove linux-tiff.
I can reproduce this reliably.
FWIW you can find the core dump here:
http://www.hcl-club.lu/~jaj/stuff/pkg_delete.core
Jona Joachim wrote:
Hi!
pkg_delete core dumps on me when it tries to remove linux-tiff.
I can reproduce this reliably.
FWIW you can find the core dump here:
http://www.hcl-club.lu/~jaj/stuff/pkg_delete.core
You need to obtain the backtrace, see the developers handbook.
Kris
can go offline comfortably for several hours without anyone
but me noticing. But if the web box goes down for 30 seconds, queries
from the users start pouring in.
Come now, even some of the biggest websites on the planet have scheduled
downtime :)
Kris
___
1 - 100 of 1476 matches
Mail list logo
