Steve,
I was wrong to freak out so badly at your suggestion. I can give you an
explanation for why but it was wrong for me to do so.
I thought that the doc was better than it was and so I couldn't understand
and flashed to anger rather than listening.
So even so, my tone is well below the
John-Mark Gurney wrote:
>Rick Macklem wrote this message on Fri, Sep 04, 2020 at 01:20 +:
>> The server side NFS over TLS daemon (rpc.tlsservd) can reload an updated
>> CRL (Certificate Revocation List) when a SIGHUP is posted to it.
>> However, it does not SSL_shutdown()/close() extant TCP
On 30/08/2020 20:37, marco wrote:
…
However the boot fails dropping me to the mountroot prompt.
Luckily activating r364030-OpenZFS again is not a problem and the system will
happily boot from that again after attempting to boot from r364030-OpenZFS2.
So now I have only 1 working BE and it
Rick Macklem wrote this message on Fri, Sep 04, 2020 at 01:20 +:
> The server side NFS over TLS daemon (rpc.tlsservd) can reload an updated
> CRL (Certificate Revocation List) when a SIGHUP is posted to it.
> However, it does not SSL_shutdown()/close() extant TCP connections using TLS.
>
On Fri, Sep 04, 2020 at 09:41:56PM +0300, Ruslan Makhmatkhanov wrote:
> Mark Johnston wrote on 9/4/20 9:34 PM:
> > On Fri, Sep 04, 2020 at 09:27:54PM +0300, Ruslan Makhmatkhanov wrote:
> >> Hello,
> >>
> >> tried to make world and kernel from r365296. Kernel fails at install
> >> stage in zfs
On 9/4/20, O. Hartmann wrote:
> On Tue, 1 Sep 2020 19:21:36 +0200
> Mateusz Guzik wrote:
>
>> It's not my bug but i'll make sure it is taken care of.
>
> Oh, I'm sorry. But I grasp for every help I can get ...
>
> The problem is that I do not know whether the process "make installkernel"
> does
Mark Johnston wrote on 9/4/20 9:34 PM:
On Fri, Sep 04, 2020 at 09:27:54PM +0300, Ruslan Makhmatkhanov wrote:
Hello,
tried to make world and kernel from r365296. Kernel fails at install
stage in zfs module:
===> zfs (install)
install -T release -o root -g wheel -m 555 zfs.ko /boot/kernel/
On Fri, Sep 04, 2020 at 09:27:54PM +0300, Ruslan Makhmatkhanov wrote:
> Hello,
>
> tried to make world and kernel from r365296. Kernel fails at install
> stage in zfs module:
>
> ===> zfs (install)
> install -T release -o root -g wheel -m 555 zfs.ko /boot/kernel/
> install -T dbg -o root -g
Hello,
tried to make world and kernel from r365296. Kernel fails at install
stage in zfs module:
===> zfs (install)
install -T release -o root -g wheel -m 555 zfs.ko /boot/kernel/
install -T dbg -o root -g wheel -m 555 zfs.ko.debug
/usr/lib/debug/boot/kernel/
install:
On 9/4/20 6:30 AM, O. Hartmann wrote:
Running a most recent CURRENT (FreeBSD 13.0-CURRENT #1 r365325: Fri Sep 4
11:28:14 CEST 2020 amd64) with JAILS also running CURRENT of the very same
version, one specific jail which is designated to be a poudriere jail
with ZFS
filesystems doesn't start
Hi.
Encountering boot failure with fatal trap 18 on boot,
happening at (maybe) just before init() starts. Possibly on
root remount by kernel or zpool import by rc.d script.
The last revision tried is r365316 (r364788 is the last tried
clean rebuild).
The last health revision is r364744, just
Begin forwarded message:
Date: Fri, 4 Sep 2020 14:06:12 +0200
From: "O. Hartmann"
To: Matthew Macy
Cc: freebsd-current , freebsd-fs
, freebsd-hack...@freebsd.org Subject: Re: OpenZFS
support merged: problem mounting ZFS within JAILs
On Mon, 24 Aug 2020 19:38:53 -0700
Matthew Macy wrote:
On Mon, 24 Aug 2020 19:38:53 -0700
Matthew Macy wrote:
> r364746 merged OpenZFS support in to HEAD.
>
> The change should be transparent unless you want to use new features.
> I caution against 'zpool upgrade' for the next few weeks.
>
> https://svnweb.freebsd.org/base?view=revision=364746
>
>
On Tue, 1 Sep 2020 19:21:36 +0200
Mateusz Guzik wrote:
> It's not my bug but i'll make sure it is taken care of.
Oh, I'm sorry. But I grasp for every help I can get ...
The problem is that I do not know whether the process "make installkernel" does
silently proceed and drop the error message
Running a most recent CURRENT (FreeBSD 13.0-CURRENT #1 r365325: Fri Sep 4
11:28:14 CEST 2020 amd64) with JAILS also running CURRENT of the very same
version, one specific jail which is designated to be a poudriere jail with ZFS
filesystems doesn't start after an update today.
The message is:
Ryan Moeller wrote:
>
> On 9/1/20 7:42 PM, Julian H. Stacey wrote:
> > Hi curr...@freebsd.org,
> >
> > With .ctm_status src-cur 14656 .svn_revision 364986 /usr/src/cddl/sbin/zfs
> > # bmake[4]: don't know how to make zfs-change-key.8. Stop
>
>
> Thanks, fixed it:
On Thu, Sep 3, 2020 at 8:57 PM Alan Somers wrote:
>
> On Thu, Sep 3, 2020 at 4:06 AM Li-Wen Hsu wrote:
>
> >
> > FreeBSD CI Weekly Report 2020-08-30
> > ===
> > * https://ci.freebsd.org/job/FreeBSD-head-amd64-test_zfs/
> > * Total 681 tests, 525 success, 46
On 2020-09-04 01:42, Graham Perrin wrote:
This week for the first time I toyed with OpenZFS on a USB device: a
mobile hard disk drive connected to the dock of an HP EliteBook 8570p.
A light test, with the pool imported but not writing to the dataset at
suspend time.
At resume time (22:31),
18 matches
Mail list logo
