On 29-6-2023 14:01, Dimitry Andric wrote:
Actually I had that in my Ceph-ports as well, and chose to ignore it
Looked into the difference between FreeBSD and Linux.
Linux prevents that message by counting the number of loads, and only unloads
when the counter hits zero. FreeBSD just seems to
On 29-6-2023 12:37, Dimitry Andric wrote:
On 29 Jun 2023, at 12:25, Willem Jan Withagen wrote:
On 26-6-2023 17:38, Dimitry Andric wrote:
On 26 Jun 2023, at 17:29, Bjoern A. Zeeb wrote:
On Mon, 26 Jun 2023, Dimitry Andric wrote:
On 26 Jun 2023, at 17:00, Bjoern A. Zeeb wrote:
while
On 26-6-2023 17:38, Dimitry Andric wrote:
On 26 Jun 2023, at 17:29, Bjoern A. Zeeb wrote:
On Mon, 26 Jun 2023, Dimitry Andric wrote:
On 26 Jun 2023, at 17:00, Bjoern A. Zeeb wrote:
while building world and current I see a lot of:
__cxa_thread_call_dtors: dtr 0x.. from unloaded dso, ski
6:23 AM Willem Jan Withagen
wrote:
Hi,
I tried upgrading a 14.0-CURRENT system from somewhere Dec 2021,
to the
most recent state.
So I build everything and installed the things...
Reboot and I end up in BTX
Oke, so I perhaps should also update pmbr and gptzfsb
Hi,
I tried upgrading a 14.0-CURRENT system from somewhere Dec 2021, to the
most recent state.
So I build everything and installed the things...
Reboot and I end up in BTX
Oke, so I perhaps should also update pmbr and gptzfsboot.
Booted from stick, and update...
Still I end up in BTX.
So
On 10-10-2021 07:57, Rick Macklem wrote:
This leads me to a couple of questions:
- Is there a good reason for not using vop_stdallocate() for ZFS?
Yes. posix_fallocate is supposed to guarantee that subsequent writes
to the file will not fail with ENOSPC. But ZFS, being a copy-on-write
file s
On 16-7-2021 18:46, Ian Lepore wrote:
On Fri, 2021-07-16 at 09:01 -0600, Alan Somers wrote:
FreeBSD has always placed /usr/local/X after /usr/X in the default PATH.
AFAICT that convention began with SVN revision 37 "Initial import of 386BSD
0.1 othersrc/etc". Why is that? It would make sense t
On 2-7-2021 12:17, Tobias Kortkamp wrote:
On Fri, Jul 02, 2021 at 11:52:14AM +0200, Willem Jan Withagen via
freebsd-current wrote:
Hi,
Have there been changes in the backtrace() calls?
I recently upgraded my current server, and now the Ceph backtrace test
starts to fail
It looks like it
Hi,
Have there been changes in the backtrace() calls?
I recently upgraded my current server, and now the Ceph backtrace test
starts to fail
It looks like it is implemented in the llvm code.
So it could be that something is off in that code.
--WjW
Program terminated with signal SIGSEGV, Seg
On 15-4-2021 14:20, Emmanuel Vadot wrote:
On Thu, 15 Apr 2021 10:51:39 +0200
Willem Jan Withagen via freebsd-current
wrote:
Hi,
I actually went completely back to the basic setup with directories
/usr/src and /usr/obj
But even then I do not manage to buildworld.
The process keeps bumping
On 15-4-2021 14:20, Emmanuel Vadot wrote:
On Thu, 15 Apr 2021 10:51:39 +0200
Willem Jan Withagen via freebsd-current
wrote:
Hi,
I actually went completely back to the basic setup with directories
/usr/src and /usr/obj
But even then I do not manage to buildworld.
The process keeps bumping
On 15-4-2021 12:44, Yuri Pankov wrote:
Willem Jan Withagen via freebsd-current wrote:
On 15-4-2021 11:47, Gary Jennejohn wrote:
On Thu, 15 Apr 2021 10:51:39 +0200
Willem Jan Withagen via freebsd-current
wrote:
Hi,
I actually went completely back to the basic setup with directories
/usr/src
On 15-4-2021 11:47, Gary Jennejohn wrote:
On Thu, 15 Apr 2021 10:51:39 +0200
Willem Jan Withagen via freebsd-current wrote:
Hi,
I actually went completely back to the basic setup with directories
/usr/src and /usr/obj
But even then I do not manage to buildworld.
The process keeps bumping
Hi,
I actually went completely back to the basic setup with directories
/usr/src and /usr/obj
But even then I do not manage to buildworld.
The process keeps bumping into missing bsm/audit.
First case was when it tried to build the 64bit libc.
I copied the bsm directory into
/usr/obj/usr/sr
On 2-9-2020 21:24, Rainer Duffner wrote:
Am 02.09.2020 um 18:22 schrieb Warner Losh :
On Sep 2, 2020, at 10:14 AM, Ed Maste wrote:
On Wed, 2 Sep 2020 at 02:31, Steve Kargl
wrote:
A short intro on git for svn users:
https://hackmd.io/ML5TSl8mQ5-27B5eqDf7YA?view
ROTFL. From the "short
On 14-7-2020 22:59, mike tancsa wrote:
On 7/14/2020 5:14 AM, Willem Jan Withagen wrote:
On 14-7-2020 07:45, Andriy Gapon wrote:
On 14/07/2020 03:39, Willem Jan Withagen wrote:
And what I read from the manual page, mrsas plays even nicer with
CAM which is a
plus.
If by "nicer" you
On 14-7-2020 11:18, Hans Petter Selasky wrote:
On 2020-07-14 02:39, Willem Jan Withagen wrote:
I guess that there are reason not to do this by default.
I've seen the exact same panic.
+1 for fixing it :-)
I do not have the knowledge to fix this panic.
So the only thing I/we can do is:
On 14-7-2020 07:45, Andriy Gapon wrote:
On 14/07/2020 03:39, Willem Jan Withagen wrote:
And what I read from the manual page, mrsas plays even nicer with CAM which is a
plus.
If by "nicer" you mean that mfi does not integrate with CAM at all, then you are
right :-)
Also, last I look
On 14-7-2020 00:47, Yuri Pankov wrote:
Willem Jan Withagen wrote:
Hi,
I have this Supermicro SUPERSERVER®2028TP
Which hold four nodes each with a X10DRT-PT motherboard
and a LSI-3108 SAS controller connecting to 6 disks.
Trying to run the most recent current snapshot on it.
# uname -a
FreeBSD
Hi,
I have this Supermicro SUPERSERVER®2028TP
Which hold four nodes each with a X10DRT-PT motherboard
and a LSI-3108 SAS controller connecting to 6 disks.
Trying to run the most recent current snapshot on it.
# uname -a
FreeBSD quadbox-d.digiware.nl 13.0-CURRENT FreeBSD 13.0-CURRENT #0
r363032:
I keep getting errors in building my ports from portsbuilder.
But it is with Current/Clang10.
So I'm trying to get a server at that level, but building world
keeps giving me:
--- all_subdir_cddl ---
ld: error: /usr/obj/usr/srcs/head/amd64.amd64/tmp/usr/lib/libuutil.so:
undefined reference to __a
On 17-2-2020 08:02, Borja Marcos wrote:
On 14 Feb 2020, at 19:18, Ed Maste wrote:
Upstream OpenSSH-portable removed libwrap support in version 6.7,
released in October 2014. We've maintained a patch in our tree to
restore it, but it causes friction on each OpenSSH update and may
introduce sec
On 05/12/2018 00:48, Toomas Soome wrote:
Yes, that must be true but it does not hurt to get checked.
And of course, lsdev -v from 11.x loader would be good too.
Anyhow, I am afraid we have reached to point where more specific debug info is
needed (printed out), with lack of output about disks
2018, at 14:18, Willem Jan Withagen wrote:
Hi,
I've sent the question below to the Ceph-devel list, asking if any recent
changes would be able to cause this.
But then of course this could stem from FreeBSD libs, and of ports
So the question here is if anybody has gotten these "wa
tools.
--WjW
Forwarded Message
Subject: Warnings about dlclose before thread exit
Date: Sat, 18 Aug 2018 14:46:35 +0200
From: Willem Jan Withagen
To: Ceph Development
Hi,
I've have upgraded to FreeBSD ALPHA 12.0, but I don't think the errors
them from there. Although they could b
On 11/02/2018 00:10, Alan Somers wrote:
On Sat, Feb 10, 2018 at 3:50 PM, Willem Jan Withagen <mailto:w...@digiware.nl>> wrote:
On 10/02/2018 20:43, Ian Lepore wrote:
On Sat, 2018-02-10 at 11:24 -0700, Alan Somers wrote:
On Sat, Feb 10, 2018 at 10:28 AM, W
On 10/02/2018 20:43, Ian Lepore wrote:
On Sat, 2018-02-10 at 11:24 -0700, Alan Somers wrote:
On Sat, Feb 10, 2018 at 10:28 AM, Willem Jan Withagen
wrote:
Hi,
This has been disabled on ZFS since last November.
And I do understand the rationale on this.
BUT
I've now upgraded some of my
On 10/02/2018 19:24, Alan Somers wrote:
On Sat, Feb 10, 2018 at 10:28 AM, Willem Jan Withagen <mailto:w...@digiware.nl>> wrote:
Hi,
This has been disabled on ZFS since last November.
And I do understand the rationale on this.
BUT
I've now upgraded some o
Hi,
This has been disabled on ZFS since last November.
And I do understand the rationale on this.
BUT
I've now upgraded some of my HEAD Ceph test systems and they now fail,
since Ceph uses posix_fallocate() to allocate space for the
FileStore-journal.
Is there any expectation that this is g
On 23/12/2017 12:25, O. Hartmann wrote:
Am Thu, 14 Dec 2017 12:05:20 +0100
Willem Jan Withagen schrieb:
On 13/12/2017 17:47, Rodney W. Grimes wrote:
On Tue, 12 Dec 2017 14:58:28 -0800
Cy Schubert wrote:
I think people responding to my thread made it clear that the WD Green
isn't the
On 13/12/2017 17:47, Rodney W. Grimes wrote:
On Tue, 12 Dec 2017 14:58:28 -0800
Cy Schubert wrote:
I think people responding to my thread made it clear that the WD Green
isn't the first-choice-solution for a 20/6 (not 24/7) duty drive and
the fact, that they have serviced now more than 25000 hou
On 07/06/2017 09:40, blubee blubeeme wrote:
> Ahhh, that was it. Doing a find and ask to replace all instances of sed
> with gsed passed that part.
>
> By the way, is knowledge like this written down somewhere centralized or is
> it just floating in the ether?
>From my experience of porting Ceph.
On 31/05/2017 18:21, Masachika ISHIZUKA wrote:
Hi.
I was using 12-current r318249 and did 'pkg upgrade', and
could not start xorg with alphasort error.
After updating r319315, xorg works again.
Right I had more or less the same with r319216.
And I was going to reinstall from a snapsho
On 23-12-2016 22:07, Slawa Olhovchenkov wrote:
> On Fri, Dec 23, 2016 at 09:37:40PM +0100, Willem Jan Withagen wrote:
>
>> On 23-12-2016 20:30, Slawa Olhovchenkov wrote:
>>> On Fri, Dec 23, 2016 at 08:16:39PM +0100, Willem Jan Withagen wrote:
>>>
>>>> On
On 23-12-2016 20:30, Slawa Olhovchenkov wrote:
> On Fri, Dec 23, 2016 at 08:16:39PM +0100, Willem Jan Withagen wrote:
>
>> On 23-12-2016 14:26, Slawa Olhovchenkov wrote:
>>> On Thu, Dec 22, 2016 at 09:26:02PM +0100, Willem Jan Withagen wrote:
>>>
>>>&g
On 23-12-2016 14:26, Slawa Olhovchenkov wrote:
> On Thu, Dec 22, 2016 at 09:26:02PM +0100, Willem Jan Withagen wrote:
>
>> On 16-12-2016 00:57, Adrian Chadd wrote:
>>> heh, an updated BIOS that solves the problem will solve the problem. :)
>>>
>>> I think yo
On 16-12-2016 00:57, Adrian Chadd wrote:
> heh, an updated BIOS that solves the problem will solve the problem. :)
>
> I think you have enough information to provide to supermicro. Ie,
> "SMAP says X, when physical memory pages at addresses X are accessed,
> they don't behave like memory, maybe so
On 22-8-2016 17:02, Willem Jan Withagen wrote:
> Giving it a last retry building over NFS mounts.
>
> Which sort of worked after I exclude some boot code that nagged me about
> things growing to big. Which I attributed to "-g -O0".
> But then I was able to complete
On 22-8-2016 00:43, Ben Woods wrote:
> On Monday, 22 August 2016, Willem Jan Withagen <mailto:w...@digiware.nl>> wrote:
>
> Tried an old trick:
> Build on another system (10.3) and then mount
> /usr/src
> /usr/obj
> on the system
On 18-8-2016 14:30, O'Connor, Daniel wrote:
>
>> On 18 Aug 2016, at 20:59, Willem Jan Withagen wrote:
>>>
>>> Remove NO_CLEAN et al and delete /usr/obj/* then try again.
>>
>> It is running single thread, but compiling clang is a rather hefty build.
On 18-8-2016 14:30, O'Connor, Daniel wrote:
>
>> On 18 Aug 2016, at 20:59, Willem Jan Withagen wrote:
>>>
>>> Remove NO_CLEAN et al and delete /usr/obj/* then try again.
>>
>> It is running single thread, but compiling clang is a rather hefty build.
On 18-8-2016 00:56, O'Connor, Daniel wrote:
>
>> On 18 Aug 2016, at 06:12, Willem Jan Withagen wrote:
>>
>>> There's nothing immediately obvious. I suggest trying without the
>>> "-DNOCLEAN -DNO_CLEAN" - they are shortcuts that aren't gu
On 17-8-2016 21:39, Peter Jeremy wrote:
> On 2016-Aug-16 23:14:45 +0200, Willem Jan Withagen wrote:
>> And I'm running:
>> make -j8 buildworld
>> So getting a good target that give the error is hard.
>>
>> So I continued with make -DNOCLEAN -DNO_CLEAN buildw
On 17-8-2016 21:39, Peter Jeremy wrote:
> On 2016-Aug-16 23:14:45 +0200, Willem Jan Withagen wrote:
>> And I'm running:
>> make -j8 buildworld
>> So getting a good target that give the error is hard.
>>
>> So I continued with make -DNOCLEAN -DNO_CLEAN buildw
On 16-8-2016 22:33, Peter Jeremy wrote:
> On 2016-Aug-16 20:31:57 +0200, Willem Jan Withagen wrote:
>> I'm trying to compile world, but I keep getting:
>>
>> /usr/obj/usr/srcs/head/src/tmp/usr/lib/libgcc_s.so: undefined reference
>> to `__gxx_personality_v0'
I'm trying to compile world, but I keep getting:
/usr/obj/usr/srcs/head/src/tmp/usr/lib/libgcc_s.so: undefined reference
to `__gxx_personality_v0'
cc: error: linker command failed with exit code 1 (use -v to see invocation)
*** [h_raw.full] Error code 1
Even after refetching the complete tree.
On 14-12-2015 16:35, Brad Davis wrote:
> On Mon, Dec 14, 2015 at 06:03:25AM -0700, Warner Losh wrote:
>> On Mon, Dec 14, 2015 at 2:21 AM, Ronald Klop wrote:
>>
>>> On Mon, 14 Dec 2015 10:11:35 +0100, Ronald Klop
>>> wrote:
>>>
>>> On Mon, 14 Dec 2015 08:18:40 +0100, Matthias Apitz
wrote:
>>
On 27-11-2015 06:59, Matthew Grooms wrote:
On 10/16/2014 3:10 AM, Edward Tomasz Napierała wrote:
On 1010T1529, Matthew Grooms wrote:
All,
I am a long time user and advocate of FreeBSD and manage a several
deployments of FreeBSD in a few data centers. Now that these
environments are almost alwa
eeBSD. And what I tried to explain, was that the
bugtracker is used for more than just bugs. I've learnt that from
several responses on the lists.
I also saw that Justin picked up with a functional answers on your
patch, so I'll go back into lurking mode.
--WjW
>
>
>
>
even submitted a few myself.
An alternative for this might be submission to Phabricator if you'd like
a more reviewing type of evaluation.
--WjW
> But then again, it may be just me.
>
> Dan
>
>
>
>> On 19 Nov 2015, at 15:44, Willem Jan Withagen wrote:
>>
>
On 19-11-2015 10:57, Dan Partelly wrote:
> Hey Pedro,
>
> Thanks a lot , mate.
>
> I’m reluctant to put it up as a PR, since some PR are outstanding for
> years.
What a strange argument
Some PR's are fixed within hours/days
Letting it linger in your mailbox after mental evaluation is no
On 10-11-2015 12:11, Dag-Erling Smørgrav wrote:
Willem Jan Withagen writes:
Digging in my logfiles , and its things like:
sshd[84942]: Disconnecting: Too many authentication failures [preauth]
So errors/warnings without IP-nr.
And I think I fixed it on one server to also write:
error
On 10-11-2015 11:55, Dag-Erling Smørgrav wrote:
> Willem Jan Withagen writes:
>> I know I've installed the ports once to see if, and how I would be
>> able to add more IP-address infor to some of the warnings and
>> errors. And then to get thos errors recognised by
On 10-11-2015 10:42, Dag-Erling Smørgrav wrote:
Some of you may have noticed that OpenSSH in base is lagging far behind
the upstream code.
The main reason for this is the burden of maintaining the HPN patches.
They are extensive, very intrusive, and touch parts of the OpenSSH code
that change si
On 6-10-2015 06:28, Don Lewis wrote:
On 3 Oct, Willem Jan Withagen wrote:
On 2-10-2015 23:32, Don Lewis wrote:
On 2 Oct, Willem Jan Withagen wrote:
Hi
10.2-STABLE FreeBSD 10.2-STABLE #0 r287102: Mon Aug 24
Processor: Opteron 6812, in Supermicro H8SGL
dev.cpu.7.temperature: 11.1C
dev.cpu
On 4-10-2015 03:26, Shane Ambler wrote:
> On 03/10/2015 20:12, Willem Jan Withagen wrote:
>> On 2-10-2015 23:32, Don Lewis wrote:
>>> On 2 Oct, Willem Jan Withagen wrote:
>>>>
>>>> Hi
>>>>
>>>> 10.2-STABLE FreeBSD 10.2-STABLE #0 r2
On 2-10-2015 23:32, Don Lewis wrote:
> On 2 Oct, Willem Jan Withagen wrote:
>>
>> Hi
>>
>> 10.2-STABLE FreeBSD 10.2-STABLE #0 r287102: Mon Aug 24
>>
>> Processor: Opteron 6812, in Supermicro H8SGL
>>
>> dev.cpu.7.temperature: 11.1C
>> dev
Hi
10.2-STABLE FreeBSD 10.2-STABLE #0 r287102: Mon Aug 24
Processor: Opteron 6812, in Supermicro H8SGL
dev.cpu.7.temperature: 11.1C
dev.cpu.6.temperature: 11.1C
dev.cpu.5.temperature: 11.1C
dev.cpu.4.temperature: 11.1C
dev.cpu.3.temperature: 11.1C
dev.cpu.2.temperature: 11.1C
dev.cpu.1.temperat
Hi,
I was trying to restore some deleted files from a snapshot with rsync:
[/home/www/.zfs/snapshot/zfs-auto-snap_hourly-2015-08-31-12h00/www.tegenbosch28.nl]
r...@zfs.digiware.nl# rsync -rav * /tmp
rsync: getcwd(): No such file or directory (2)
rsync error: errors selecting input/output file
On 29-7-2015 18:01, Jordan Hubbard wrote:
On Jul 27, 2015, at 7:32 AM, Willem Jan Withagen
wrote:
You have any idea what is/was actual the hardware that was in the
box?
If I remember correctly we gave Jordan a check for like 5000
guilders. Which I guess would be 2500 us$ at that time. Which
On 27/07/2015 16:42, Glen Barber wrote:
> On Mon, Jul 27, 2015 at 04:32:34PM +0200, Willem Jan Withagen wrote:
>> On 27/07/2015 16:25, Glen Barber wrote:
>>> On Mon, Jul 27, 2015 at 04:14:54PM +0200, Willem Jan Withagen wrote:
>>>> On 27/07/2015 04:39, Benjamin Ka
On 27/07/2015 16:25, Glen Barber wrote:
> On Mon, Jul 27, 2015 at 04:14:54PM +0200, Willem Jan Withagen wrote:
>> On 27/07/2015 04:39, Benjamin Kaduk wrote:
>>> * Separated email services (and single-point-of-failure cases) from
>>> the machine that has been han
On 27/07/2015 04:39, Benjamin Kaduk wrote:
> * Separated email services (and single-point-of-failure cases) from
> the machine that has been handling this task for over 18 years, to
> new, single-purpose service installations
Hi,
This sort of sounds like the system that a former company
On 30/06/2015 17:32, Simon J. Gerraty wrote:
> Jeffrey Bouquet wrote:
>
>> If I've a spare /mnt/usr/src , it seems buildworld quite soon fails,
>> where it otherwise may succeed in /usr/src. Any CLI parameters or> the
>> build system is hardcoded enough so that there will always be
>> problems?
>
On 24/04/2015 12:05, Garrett Cooper wrote:
> On Apr 24, 2015, at 3:03, Garrett Cooper
> wrote:
>
>> On Apr 24, 2015, at 2:59, Garrett Cooper
>> wrote:
>>
>>> On Apr 23, 2015, at 2:05, Willem Jan Withagen
>>> wrote:
>>>
>>>>
On 24/04/2015 12:05, Garrett Cooper wrote:
> On Apr 24, 2015, at 3:03, Garrett Cooper wrote:
>
>> On Apr 24, 2015, at 2:59, Garrett Cooper wrote:
>>
>>> On Apr 23, 2015, at 2:05, Willem Jan Withagen wrote:
>>>
>>>> On 22/04/2015 23:37, Ed Mast
On 22/04/2015 23:37, Ed Maste wrote:
> On 22 April 2015 at 15:55, Willem Jan Withagen wrote:
>>
>>> Yes:
>>> https://lists.freebsd.org/pipermail/freebsd-current/2015-February/054740.html
>>>
>>
>> But this is not enough to make yacc part of the
On 22-4-2015 23:37, Ed Maste wrote:
On 22 April 2015 at 15:55, Willem Jan Withagen wrote:
Yes:
https://lists.freebsd.org/pipermail/freebsd-current/2015-February/054740.html
But this is not enough to make yacc part of the build tools??
yacc is unconditionally built during bootstrap-tools
On 22/04/2015 18:45, Warren Block wrote:
> On Wed, 22 Apr 2015, Willem Jan Withagen wrote:
>
>> Hi,
>>
>> [I thought that I've seen talk about this before.]
>>
>> On a customers system I'm trying to build a new world, with a fresh tree.
>&
Hi,
[I thought that I've seen talk about this before.]
On a customers system I'm trying to build a new world, with a fresh tree.
I've deleted lines from other tracks in parallel compilation.
--- aslcompilerparse.c ---
yacc -d -pAslCompiler -oaslcompilerparse.c aslcompiler.y
yacc: 89 shift/reduc
On 21-4-2015 12:18, Garrett Cooper wrote:
On Apr 21, 2015, at 3:00, Willem Jan Withagen wrote:
Hi,
With a freshly fetched HEAD, and 'make -j 8 buildworld' I get:
--- _bootstrap-tools-kerberos5/lib/libvers ---
--- roken.h ---
make-roken > roken.h
ma
Hi,
With a freshly fetched HEAD, and 'make -j 8 buildworld' I get:
--- _bootstrap-tools-kerberos5/lib/libvers ---
--- roken.h ---
make-roken > roken.h
make-roken: not found
--- _bootstrap-tools-kerberos5/tools/make-roken ---
--- make-roken.c ---
awk -f
/usr/srcs/he
Hoi,
Looked at:
http://sources.zabbadoz.net/freebsd/lor.html#howtoreportalor
But did not find any reference to ffs_vnops, so it might be a new one?
I got this from running 'make installworld' of todays HEAD IN a bhyveVM
which was already running thismornings kernel.
So it was not the Dom0 ser
On 2015-01-21 11:08, Garrett Cooper wrote:
On Jan 21, 2015, at 2:05, Willem Jan Withagen wrote:
On 2015-01-21 10:51, Benjamin Perrault wrote:
On Jan 21, 2015, at 1:34 AM, Willem Jan Withagen
wrote:
Found this lastnight build. Just fetched the most recent HEAD.
Error remains
--- zfs
On 2015-01-21 10:51, Benjamin Perrault wrote:
On Jan 21, 2015, at 1:34 AM, Willem Jan Withagen
wrote:
Found this lastnight build. Just fetched the most recent HEAD.
Error remains
--- zfs/zfs.o --- In file included from
/usr/srcs/src11/src/lib/libprocstat/zfs/../zfs.c:39:
/usr/srcs/src11
Found this lastnight build.
Just fetched the most recent HEAD.
Error remains
--- zfs/zfs.o ---
In file included from /usr/srcs/src11/src/lib/libprocstat/zfs/../zfs.c:39:
/usr/srcs/src11/src/lib/libprocstat/zfs/../../../cddl/contrib/opensolaris/lib/libzpool/common/sys/zfs_context.h:538:9:
error:
On 2015-01-20 2:05, Xin Li wrote:
Doing it in 11 makes sense since there is a compat layer for 10
now… if I knew all of the steps I would happily do them as annoys
me from time to time as well with the path length issue.
Compat layer may break applications in other funny ways and we
probably ha
On 19-1-2015 22:20, Garrett Cooper wrote:
> On Jan 19, 2015, at 8:46, Brandon Allbery
> wrote:
>
>> On Mon, Jan 19, 2015 at 10:44 AM, Anton Shterenlikht
>> wrote:
>>
>>> So perhaps changing MNAMELEN will break statfs(2) on -stable
>>> too?
>>>
>>
>> I believe the context there is not so much
On 6-12-2014 13:40, Baptiste Daroussin wrote:
> Hi,
>
> We have released a new 1.4.0 rc2 version of pkg (available in
> ports-mgmt/pkg-devel) since first beta it has received tons of bug fixes and
> should be now way more reliable and able to handle ootb without mistakes
> upgrades like the gettex
On 16-10-2014 5:00, Anish Gupta wrote:
> Hi all,
>
> The projects/bhyve_svm branch is ready to be merged to HEAD.
>
> This branch contains patches to bhyve to enable it to work on AMD
> processors with SVM/AMD-V hardware extensions[1]. Pretty much any AMD
> processor since 2010 will have the feat
On 2014-07-29 0:07, Kevin Oberman wrote:
And all IPv6 NAT is evil and should be cast into (demonic residence of your
choosing) on sight!
NAT on IPv6 serves no useful purpose at all. It only serves to complicate
things and make clueless security officers happy. It adds zero security. It
is a gre
On 2014-07-01 17:33, O. Hartmann wrote:
Am Tue, 01 Jul 2014 17:23:14 +0200
Willem Jan Withagen schrieb:
On 2014-07-01 16:48, Rang, Anton wrote:
DOT => DOD
444F54 => 444F44
That's a single-bit flip. Bad memory, perhaps?
Very likely, especially if the system does not have ECC.
On 2014-07-01 16:48, Rang, Anton wrote:
DOT => DOD
444F54 => 444F44
That's a single-bit flip. Bad memory, perhaps?
Very likely, especially if the system does not have ECC
It just happens on rare occasions that a alpha particle, power cycle, or
any things else disruptive damages a memory
On 2013-01-04 17:52, O. Hartmann wrote:
> Am 01/04/13 15:52, schrieb Garrett Cooper:
>> Answering just the trivial question...
>>
>> On Fri, Jan 4, 2013 at 2:13 AM, O. Hartmann
>> wrote:
>>
>> ...
>>
>>> server-1: FreeBSD 10.0-CURRENT #0 r244957: Wed Jan 2 12:06:13 CET 2013
>>>
>>> By the way, c
On 2012-07-06 2:29, YongHyeon PYUN wrote:
> On Wed, Jul 04, 2012 at 12:08:16PM +0200, Willem Jan Withagen wrote:
>> Hi,
>>
>> I've got tons of these since I stopped loading the port with traffic
>> It seems to have a pretty steady 27 min interval.
>>
&
Hi,
I've got tons of these since I stopped loading the port with traffic
It seems to have a pretty steady 27 min interval.
Jul 4 07:00:05 freetest kernel: sk0: link state changed to DOWN
Jul 4 07:00:05 freetest kernel: sk0: link state changed to UP
Jul 4 07:27:21 freetest kernel: sk0: link
On 2012-05-28 1:25, Garrett Cooper wrote:
> Here's a revised patch (based on something I brought up earlier)
> that converts periodic over to an rc.subr-like paradigm.
> This can be directly applied to HEAD; you will need to backport
> r231849 first if you want to apply the patch to 9-STABL
On 2012-05-24 19:05, Doug Barton wrote:
> On 05/24/2012 03:49 AM, Willem Jan Withagen wrote:
>> [I looked for a better list to drop this on, but other that freebsd-rc
>> nothing seems close.]
>
> freebsd-rc@ is not appropriate for discussing periodic, as the 2 are
> tot
On 2012-05-24 14:01, Sergey Kandaurov wrote:
> On 24 May 2012 11:49, Willem Jan Withagen wrote:
>> [I looked for a better list to drop this on, but other that freebsd-rc
>> nothing seems close.]
>>
>> Hi,
>>
>> I nagged about the verbosity of the periodic s
[I looked for a better list to drop this on, but other that freebsd-rc
nothing seems close.]
Hi,
I nagged about the verbosity of the periodic scripts.
But did not give any example.
Well I just ran into a perfect example:
--
Checking setuid files and devices:
Checking for uids of 0:
root 0
Chec
Op 8 sep. 2011 om 19:00 heeft "Andrey V. Elsukov" het
volgende geschreven:
> On 08.09.2011 20:13, Willem Jan Withagen wrote:
>> This however results in that I can not find any "normal" way in the
>> guided and expert config menus to actual tell it to us
Hi,
Tried to install the BETA2 from a mem-stick onto a 250Gb disk.
Which turned out to be used in a ZFS box.
Since it does contain GPT info telling me ada0p1 was a freebsd-zfs partion.
This however results in that I can not find any "normal" way in the
guided and expert config menus to actual t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10-5-2010 20:09, Bruce Cran wrote:
> On Friday 30 April 2010 09:11:49 Gary Jennejohn wrote:
>
>> A number of variables go into calculating vm.kmem_size (see kmeminit()
>> in kern_malloc.c).
>>
>> In the end, the kernel won't allocate more than twic
On 29-4-2010 6:17, Artem Belevich wrote:
Do you have vm.kmem_size set in /boot/loader.conf?
If not, do set it to about double of your physical RAM size. Defaults
are way too conservative for use with large amounts of memory and ZFS.
As per this suggestion I set this value to 2*8G:
vm.kmem_size
Hi,
When everything is life is just smoothly flowing by, and all is hunky-dory,
some things don't get the credits they deserve.
So here we go ;)
Standing at the coffee machine this morning I realized that FreeBSD has been
part of my professional life for already way, way too long. Before
Hi,
I have a sort of working Pascal compiler up and running.
It used to be an old research project of mine, which never really made it
out since I started to play ISP. The last build was done in the COFF area,
and I've found that things have somewhat changed...
Small programs are working, because
Instruction pointer: 0x8:0c021B8C0
And then the box was frozen solid
The trap occured while compiling world over NFS V3/UDP.
FreeBSD 5.1-RELEASE-p10 #0: Tue Oct 28 22:09:12 CET 2003
[EMAIL PROTECTED]:/mnt2/obj/usr/src51/src/sys/FILES
Preloaded elf kernel "/boot/kernel/kernel" at 0xc04b60
> I was donated a ML370 with 256Mb, single processor.
>
> It boots an 5.0-DP1 cd just fine, and it runs like a normal baby.
> So I tried upgrading it to 5.1-current. And it freezes.
> After some tinkering in /etc/loader.conf it now shows that it is probing
> devices:
>
> in short:
> isa_probe
Hi,
I was donated a ML370 with 256Mb, single processor.
It boots an 5.0-DP1 cd just fine, and it runs like a normal baby.
So I tried upgrading it to 5.1-current. And it freezes.
After some tinkering in /etc/loader.conf it now shows that it is probing
devices:
in short:
isa_probe_children: pr
Hi,
(Not quite for current@, but that's where leading edge is going on)
For the new house we are building I'm looking into EIB.
(European Installation Bus).
And I'm searching for EIB/IP gateways and applications on FreeBSD.
Has anybody used these kinds of tools with FBSD (or Linux)
Or even bette
1 - 100 of 118 matches
Mail list logo
