Re: OpenZFS support merged

[Toomas Soome]

> On 25. Aug 2020, at 22:49, driesm.michi...@gmail.com wrote:
> 
>> -Original Message-
>> From: owner-freebsd...@freebsd.org  On
>> Behalf Of Matthew Macy
>> Sent: Tuesday, 25 August 2020 04:39
>> To: freebsd-current ; freebsd-fs > f...@freebsd.org>; freebsd-hack...@freebsd.org
>> Subject: OpenZFS support merged
>> 
>> r364746 merged OpenZFS support in to HEAD.
> 
> First of all a big thank you to the whole team that made this possible!
> 
> Secondly, I would like to check in if the following statement is still in
> effect (taken from https://zfsonfreebsd.github.io/ZoF):
> "Beware that the FreeBSD boot loader does not allow booting from root pools
> with encryption active (even if it is not in use), so do not try encryption
> on a pool you boot from"
> 
> When we are talking about encryption active, does that mean the feature flag
> active or from the moment one sets encryption=on on any dataset of the root
> pool?
> As a follow-up, if it is not currently not possible, are there any
> long/short term plans to add the missing bits to our boot loader?µ


Yes. The current boot loader can handle features before switch to OpenZFS. New 
features will be added, it just will take some time.

rgds,
toomas

> 
>> 
>> 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&revision=364746
>> 
>> If you encounter problems please report them to me, Ryan Moeller, and -
>> current.
>> ___
>> freebsd...@freebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-fs
>> To unsubscribe, send any mail to "freebsd-fs-unsubscr...@freebsd.org"
> 
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: OpenZFS support merged

[Ben Woods]

On Tue, 25 Aug 2020 at 10:39 am, 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&revision=364746



Congratulations and thank you to all involved. This is a great step forward
for FreeBSD.

Looking forward to trying ZFS native encryption, and send/recv of encrypted
datasets!

I’ll second that boot loader support for ZFS native encryption and zstd
compression would greatly complement this change once they are ready.

Regards,
Ben

> 

-- 

--
From: Benjamin Woods
woods...@gmail.com
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: OpenZFS support merged

[Toomas Soome]

> On 25. Aug 2020, at 19:35, Danilo Egêa Gondolfo  wrote:
> 
> On Tue, Aug 25, 2020 at 3:39 AM 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&revision=364746
>> 
>> If you encounter problems please report them to me, Ryan Moeller, and
>> -current.
>> ___
>> freebsd-hack...@freebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers
>> To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
>> 
> 
> Hi, that is good news.
> 
> It seems that our boot loader will fail to boot after zpool upgrade. Is
> that a known issue?
> 

The loader is not updated to support zstd.

rgds,
toomas

> I've replicated my setup, root zfs over GELI, in a VM to avoid any surprise
> (phew!), and it booted fine after upgrading the system. Although it fails
> after zpool upgrade (yes, I know you've asked us to be cautious with zpool
> upgrade):
> 
> ZFS: unsupported feature: org.freebsd:zstd_compress
> ZFS: pool zroot is not supported
> ZFS: can't find pool by guid
> 
> Thank you!
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: OpenZFS support merged

[Ryan Moeller]

On 8/25/20 3:49 PM, driesm.michi...@gmail.com wrote:

-Original Message-
From: owner-freebsd...@freebsd.org  On
Behalf Of Matthew Macy
Sent: Tuesday, 25 August 2020 04:39
To: freebsd-current ; freebsd-fs ; freebsd-hack...@freebsd.org
Subject: OpenZFS support merged

r364746 merged OpenZFS support in to HEAD.

First of all a big thank you to the whole team that made this possible!

Secondly, I would like to check in if the following statement is still in
effect (taken from https://zfsonfreebsd.github.io/ZoF):
"Beware that the FreeBSD boot loader does not allow booting from root pools
with encryption active (even if it is not in use), so do not try encryption
on a pool you boot from"

When we are talking about encryption active, does that mean the feature flag
active or from the moment one sets encryption=on on any dataset of the root
pool?


The feature can be enabled on the pool, but as soon as you use it on any 
dataset
the feature goes from "enabled" to "active" and the boot loader will not 
be able
to read the pool, even if you switch encryption back off. At least 
that's how it
was when the ZoF page was written, if it's different now someone may 
correct me.




As a follow-up, if it is not currently not possible, are there any
long/short term plans to add the missing bits to our boot loader?µ


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&revision=364746

If you encounter problems please report them to me, Ryan Moeller, and -
current.
___
freebsd...@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-fs
To unsubscribe, send any mail to "freebsd-fs-unsubscr...@freebsd.org"

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: OpenZFS support merged

[Jakob Alvermark]

On 2020-08-25 20:23, Ryan Moeller wrote:


On 8/25/20 2:09 PM, Jakob Alvermark wrote:


On 2020-08-25 20:06, Ryan Moeller wrote:



On 8/25/20 2:00 PM, Jakob Alvermark wrote:


On 2020-08-25 17:42, Ryan Moeller wrote:


On 8/25/20 9:58 AM, Jakob Alvermark wrote:

Hi,


I updated from r364605 to r364768

'make buildkernel' fails like this:

Building 
/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG/modules/usr/src/sys/modules/zfs/zstd.o 

/usr/src/sys/contrib/openzfs/module/zstd/lib/zstd.c:1336:12: 
fatal error: 'immintrin.h' file not found

#  include    /* support for bextr (experimental) */
   ^
1 error generated.
*** Error code 1

Stop.



I'm trying to figure out how to reproduce this. Are you perhaps 
building with GCC?


-Ryan


Nope.


I do use WITH_META_MODE though, but it shouldn't affect this I think.

I tried clearing out /usr/obj and started a new build, but I still 
get the same error.



Jakob

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to 
"freebsd-current-unsubscr...@freebsd.org"

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to 
"freebsd-current-unsubscr...@freebsd.org" 


Okay I'm guessing your build env has something like `CPUTYPE?= 
native` in src.conf.  This was also an issue with the original zstd 
import. I've reproduced this error and will commit the fix shortly.




https://svnweb.freebsd.org/changeset/base/364777



It compiles now. And it boots.

Thanks for fixing it so quickly!


Jakob

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

RE: OpenZFS support merged

[driesm.michiels]

> -Original Message-
> From: owner-freebsd...@freebsd.org  On
> Behalf Of Matthew Macy
> Sent: Tuesday, 25 August 2020 04:39
> To: freebsd-current ; freebsd-fs  f...@freebsd.org>; freebsd-hack...@freebsd.org
> Subject: OpenZFS support merged
> 
> r364746 merged OpenZFS support in to HEAD.

First of all a big thank you to the whole team that made this possible!

Secondly, I would like to check in if the following statement is still in
effect (taken from https://zfsonfreebsd.github.io/ZoF):
"Beware that the FreeBSD boot loader does not allow booting from root pools
with encryption active (even if it is not in use), so do not try encryption
on a pool you boot from"

When we are talking about encryption active, does that mean the feature flag
active or from the moment one sets encryption=on on any dataset of the root
pool?
As a follow-up, if it is not currently not possible, are there any
long/short term plans to add the missing bits to our boot loader?µ

> 
> 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&revision=364746
> 
> If you encounter problems please report them to me, Ryan Moeller, and -
> current.
> ___
> freebsd...@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-fs
> To unsubscribe, send any mail to "freebsd-fs-unsubscr...@freebsd.org"

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Strange USB loop

[bob prohaska]

On Tue, Aug 25, 2020 at 09:41:41AM +0200, Hans Petter Selasky wrote:
> 
> Can you try r364346 ?
> 

The kernel compiled and installed without trouble. After running
run bootcmd_usb0 the machine loaded the kernel, but stopped at the 
loader prompt. The keyboard was connected direct to the Pi, the
mouse was disconnected.
 
It isn't obvious why it stopped at the loader prompt. 

lsdev reports
disk devices:
disk0:250085377 X 512 blocks (removable)
  disk0s1: DOS/Windows
  disk0s2: FreeBSD
disk0s2a: FreeBSD UFS
disk0s2b: FreeBSD swap
disk1:1953525169 X 512 blocks
  disk1s1: DOS/Windows
  disk1s2: FreeBSD
disk1s2a: FreeBSD UFS
disk1s2b: FreeBSD swap
http: (unknown)
net devices:
net0:
OK 

Disk0 is the (bootable) microSD, disk1 is the hard drive.

Boot -s came up single-user, with / mounted from /dev/da0s2a as desired.

Fsck reported the filesystem clean. Exit to multi-user worked.
The USB system keyboard (plugged into the Pi) worked. The mouse
(plugged into the hub after boot) also worked.

A second reboot with the mouse connected via the hub worked without
pausing at the loader prompt.

Plugging the FTDI FT232 adapter into the hub triggered a round of
uhub_reattach_port: giving up port reset - device vanished
messages, but this time they stopped when I pulled the FT232.
Plugging the FT232 directly into the Pi caused normal recognition.

It looks as if the FT232 somehow interferes with disk discovery.
A reboot with USB disk & mouse in the hub but keyboard and FT232
in the Pi again resulted in a mountroot failure, along with a few
other error messages:

uhub2: MTT enabled
Root mount waiting for: usbus1 CAM
uhub2: 4 ports with 4 removable, self powered
Root mount waiting for: usbus1 CAM
usb_alloc_device: set address 7 failed (USB_ERR_IOERROR, ignored)
Root mount waiting for: usbus1 CAM
Root mount waiting for: usbus1 CAM
usbd_setup_device_desc: getting device descriptor at addr 7 failed, 
USB_ERR_IOERROR
usbd_req_re_enumerate: addr=7, set address failed! (USB_ERR_IOERROR, ignored)
Root mount waiting for: usbus1 CAM
Root mount waiting for: usbus1 CAM
usbd_setup_device_desc: getting device descriptor at addr 7 failed, 
USB_ERR_IOERROR
Root mount waiting for: usbus1 CAM
usbd_req_re_enumerate: addr=7, port reset failed, USB_ERR_IOERROR
usbd_req_re_enumerate: addr=7, port reset failed, USB_ERR_IOERROR
Root mount waiting for: usbus1 CAM
usbd_req_re_enumerate: addr=7, port reset failed, USB_ERR_IOERROR
ugen1.7:  at usbus1 (disconnected)
uhub_reattach_port: could not allocate new device
Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM
Mounting from ufs:/dev/da0s2a failed with error 2; retrying for 3 more seconds
Mounting from ufs:/dev/da0s2a failed with error 2.

Loader variables:
  vfs.root.mountfrom=ufs:/dev/da0s2a
  vfs.root.mountfrom.options=rw

With the FT232 unplugged the machine came up normally.

With a _different_ FT232 plugged in it also came up normally.

Both are thought to be genuine, but they are of different age
and produce different recognition messages:

The FT232 that causes trouble reports
ugen1.4:  at usbus1
uftdi0 on uhub1
uftdi0:  on usbus1

The one that seems to work is newer and reports
ugen1.4:  at usbus1
uftdi0 on uhub1
uftdi0:  on usbus1

On balance I think the new kernel is better-behaved. Beyond that
I'm at a loss. If you can suggest other things to try please do.

Thanks for all your help,

bob prohaska
 
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: OpenZFS support merged

[Ryan Moeller]

On 8/25/20 2:09 PM, Jakob Alvermark wrote:


On 2020-08-25 20:06, Ryan Moeller wrote:



On 8/25/20 2:00 PM, Jakob Alvermark wrote:


On 2020-08-25 17:42, Ryan Moeller wrote:


On 8/25/20 9:58 AM, Jakob Alvermark wrote:

Hi,


I updated from r364605 to r364768

'make buildkernel' fails like this:

Building 
/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG/modules/usr/src/sys/modules/zfs/zstd.o 

/usr/src/sys/contrib/openzfs/module/zstd/lib/zstd.c:1336:12: fatal 
error: 'immintrin.h' file not found

#  include    /* support for bextr (experimental) */
   ^
1 error generated.
*** Error code 1

Stop.



I'm trying to figure out how to reproduce this. Are you perhaps 
building with GCC?


-Ryan


Nope.


I do use WITH_META_MODE though, but it shouldn't affect this I think.

I tried clearing out /usr/obj and started a new build, but I still 
get the same error.



Jakob

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to 
"freebsd-current-unsubscr...@freebsd.org"

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to 
"freebsd-current-unsubscr...@freebsd.org" 


Okay I'm guessing your build env has something like `CPUTYPE?= 
native` in src.conf.  This was also an issue with the original zstd 
import. I've reproduced this error and will commit the fix shortly.




https://svnweb.freebsd.org/changeset/base/364777




Oh! I do have that.

Thanks.


Jakob

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to 
"freebsd-current-unsubscr...@freebsd.org"

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: OpenZFS support merged

[Jakob Alvermark]

On 2020-08-25 20:06, Ryan Moeller wrote:



On 8/25/20 2:00 PM, Jakob Alvermark wrote:


On 2020-08-25 17:42, Ryan Moeller wrote:


On 8/25/20 9:58 AM, Jakob Alvermark wrote:

Hi,


I updated from r364605 to r364768

'make buildkernel' fails like this:

Building 
/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG/modules/usr/src/sys/modules/zfs/zstd.o 

/usr/src/sys/contrib/openzfs/module/zstd/lib/zstd.c:1336:12: fatal 
error: 'immintrin.h' file not found

#  include    /* support for bextr (experimental) */
   ^
1 error generated.
*** Error code 1

Stop.



I'm trying to figure out how to reproduce this. Are you perhaps 
building with GCC?


-Ryan


Nope.


I do use WITH_META_MODE though, but it shouldn't affect this I think.

I tried clearing out /usr/obj and started a new build, but I still 
get the same error.



Jakob

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to 
"freebsd-current-unsubscr...@freebsd.org"

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to 
"freebsd-current-unsubscr...@freebsd.org" 


Okay I'm guessing your build env has something like `CPUTYPE?= native` 
in src.conf.  This was also an issue with the original zstd import. 
I've reproduced this error and will commit the fix shortly.



Oh! I do have that.

Thanks.


Jakob

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: OpenZFS support merged

[Ryan Moeller]

On 8/25/20 2:00 PM, Jakob Alvermark wrote:


On 2020-08-25 17:42, Ryan Moeller wrote:


On 8/25/20 9:58 AM, Jakob Alvermark wrote:

Hi,


I updated from r364605 to r364768

'make buildkernel' fails like this:

Building 
/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG/modules/usr/src/sys/modules/zfs/zstd.o 

/usr/src/sys/contrib/openzfs/module/zstd/lib/zstd.c:1336:12: fatal 
error: 'immintrin.h' file not found

#  include    /* support for bextr (experimental) */
   ^
1 error generated.
*** Error code 1

Stop.



I'm trying to figure out how to reproduce this. Are you perhaps 
building with GCC?


-Ryan


Nope.


Okay I'm guessing your build env has something like `CPUTYPE?= native` 
in src.conf.  This was also an issue with the original zstd import. 
I've reproduced this error and will commit the fix shortly.




I do use WITH_META_MODE though, but it shouldn't affect this I think.

I tried clearing out /usr/obj and started a new build, but I still get 
the same error.



Jakob

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: OpenZFS support merged

[Jakob Alvermark]

On 2020-08-25 17:42, Ryan Moeller wrote:


On 8/25/20 9:58 AM, Jakob Alvermark wrote:

Hi,


I updated from r364605 to r364768

'make buildkernel' fails like this:

Building 
/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG/modules/usr/src/sys/modules/zfs/zstd.o
/usr/src/sys/contrib/openzfs/module/zstd/lib/zstd.c:1336:12: fatal 
error: 'immintrin.h' file not found

#  include    /* support for bextr (experimental) */
   ^
1 error generated.
*** Error code 1

Stop.



I'm trying to figure out how to reproduce this. Are you perhaps 
building with GCC?


-Ryan


Nope.

I do use WITH_META_MODE though, but it shouldn't affect this I think.

I tried clearing out /usr/obj and started a new build, but I still get 
the same error.



Jakob

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: OpenZFS support merged

[Danilo Egêa Gondolfo]

On Tue, Aug 25, 2020 at 5:43 PM Matthew Macy  wrote:

> On Tue, Aug 25, 2020 at 9:36 AM Danilo Egêa Gondolfo 
> wrote:
> >
> > On Tue, Aug 25, 2020 at 3:39 AM 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&revision=364746
> >>
> >> If you encounter problems please report them to me, Ryan Moeller, and
> -current.
> >> ___
> >> freebsd-hack...@freebsd.org mailing list
> >> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> >> To unsubscribe, send any mail to "
> freebsd-hackers-unsubscr...@freebsd.org"
> >
> >
> > Hi, that is good news.
> >
> > It seems that our boot loader will fail to boot after zpool upgrade. Is
> that a known issue?
>
> No. Unfortunately zstd support was merged in to openzfs very late in
> the CFT. Features needed for read like zstd need to be white listed in
> the loader and added to the support.
>
> -M
>
>
> > I've replicated my setup, root zfs over GELI, in a VM to avoid any
> surprise (phew!), and it booted fine after upgrading the system. Although
> it fails after zpool upgrade (yes, I know you've asked us to be cautious
> with zpool upgrade):
> >
> > ZFS: unsupported feature: org.freebsd:zstd_compress
> > ZFS: pool zroot is not supported
> > ZFS: can't find pool by guid
> >
> > Thank you!
>

Fair enough.

I believe it should be mentioned in the UPDATING file then. It's not clear
that it will happen if one zpool upgrades his/her pools.

Thank you.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: OpenZFS support merged

[Matthew Macy]

On Tue, Aug 25, 2020 at 9:36 AM Danilo Egêa Gondolfo  wrote:
>
> On Tue, Aug 25, 2020 at 3:39 AM 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&revision=364746
>>
>> If you encounter problems please report them to me, Ryan Moeller, and 
>> -current.
>> ___
>> freebsd-hack...@freebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers
>> To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
>
>
> Hi, that is good news.
>
> It seems that our boot loader will fail to boot after zpool upgrade. Is that 
> a known issue?

No. Unfortunately zstd support was merged in to openzfs very late in
the CFT. Features needed for read like zstd need to be white listed in
the loader and added to the support.

-M


> I've replicated my setup, root zfs over GELI, in a VM to avoid any surprise 
> (phew!), and it booted fine after upgrading the system. Although it fails 
> after zpool upgrade (yes, I know you've asked us to be cautious with zpool 
> upgrade):
>
> ZFS: unsupported feature: org.freebsd:zstd_compress
> ZFS: pool zroot is not supported
> ZFS: can't find pool by guid
>
> Thank you!
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: OpenZFS support merged

[Danilo Egêa Gondolfo]

On Tue, Aug 25, 2020 at 3:39 AM 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&revision=364746
>
> If you encounter problems please report them to me, Ryan Moeller, and
> -current.
> ___
> freebsd-hack...@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
>

Hi, that is good news.

It seems that our boot loader will fail to boot after zpool upgrade. Is
that a known issue?

I've replicated my setup, root zfs over GELI, in a VM to avoid any surprise
(phew!), and it booted fine after upgrading the system. Although it fails
after zpool upgrade (yes, I know you've asked us to be cautious with zpool
upgrade):

ZFS: unsupported feature: org.freebsd:zstd_compress
ZFS: pool zroot is not supported
ZFS: can't find pool by guid

Thank you!
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: OpenZFS support merged

[Ryan Moeller]

On 8/25/20 9:58 AM, Jakob Alvermark wrote:

Hi,


I updated from r364605 to r364768

'make buildkernel' fails like this:

Building 
/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG/modules/usr/src/sys/modules/zfs/zstd.o
/usr/src/sys/contrib/openzfs/module/zstd/lib/zstd.c:1336:12: fatal 
error: 'immintrin.h' file not found

#  include    /* support for bextr (experimental) */
   ^
1 error generated.
*** Error code 1

Stop.



I'm trying to figure out how to reproduce this. Are you perhaps building 
with GCC?


-Ryan




Best,

Jakob

On 2020-08-25 04:38, 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&revision=364746

If you encounter problems please report them to me, Ryan Moeller, and 
-current.

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to 
"freebsd-current-unsubscr...@freebsd.org"

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to 
"freebsd-current-unsubscr...@freebsd.org"

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: OpenZFS support merged

[Ryan Moeller]

On 8/25/20 10:43 AM, Bob Bishop wrote:

Hi,


On 25 Aug 2020, at 03:38, Matthew Macy  wrote:

r364746 merged OpenZFS support in to HEAD.

The change should be transparent unless you want to use new features.

For clarity, is autotrim enabled by default? If not, some people will be 
surprised.



It is on by default.

-Ryan




I caution against 'zpool upgrade' for the next few weeks.

https://svnweb.freebsd.org/base?view=revision&revision=364746

If you encounter problems please report them to me, Ryan Moeller, and -current.


--
Bob Bishop
r...@gid.co.uk




___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: OpenZFS support merged

[Bob Bishop]

Hi,

> On 25 Aug 2020, at 03:38, Matthew Macy  wrote:
> 
> r364746 merged OpenZFS support in to HEAD.
> 
> The change should be transparent unless you want to use new features.

For clarity, is autotrim enabled by default? If not, some people will be 
surprised.

> I caution against 'zpool upgrade' for the next few weeks.
> 
> https://svnweb.freebsd.org/base?view=revision&revision=364746
> 
> If you encounter problems please report them to me, Ryan Moeller, and 
> -current.


--
Bob Bishop
r...@gid.co.uk




___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: 'chflags: fts_read: Permission denied' on fresh -CURRENT

[Mateusz Guzik]

Should be fixed with r364769.

On 8/25/20, Roman Bogorodskiy  wrote:
> Yes, it allows to move further and build is currently running.
>
> Thanks
>
>   Mateusz Guzik wrote:
>
>> Does: sysctl vfs.cache_fast_lookup=0 clean it up for you?
>>
>> On 8/25/20, Roman Bogorodskiy  wrote:
>> > Hi,
>> >
>> > I've updated -CURRENT today to r364753, and poudriere started failing
>> > with:
>> >
>> > [00:00:00] Creating the reference jail...chflags: fts_read: Permission
>> > denied
>> > [00:00:00] Cleaning up
>> > [00:00:00] Unmounting file systems
>> > chflags: fts_read: Permission denied
>> >
>> > I've created a new jail and it fails with the same error.
>> >
>> > I'm not using zfs and also I use the same sources for poudriere jails
>> > as
>> > the host, i.e.:
>> >
>> > current 13.0-CURRENT 1300112 amd64   src=/usr/src 2020-08-25
>> > 13:17:30 /usr/local/poudriere/jails/current
>> > current13   13.0-CURRENT 1300113 amd64   src=/usr/src 2020-08-25
>> > 16:19:13 /usr/local/poudriere/jails/current13
>> >
>> > Any ideas what could be wrong with this?
>> >
>> > Roman Bogorodskiy
>> >
>>
>>
>> --
>> Mateusz Guzik 
>
> Roman Bogorodskiy
>


-- 
Mateusz Guzik 
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: OpenZFS support merged

[Jakob Alvermark]

Hi,


I updated from r364605 to r364768

'make buildkernel' fails like this:

Building 
/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG/modules/usr/src/sys/modules/zfs/zstd.o
/usr/src/sys/contrib/openzfs/module/zstd/lib/zstd.c:1336:12: fatal 
error: 'immintrin.h' file not found

#  include    /* support for bextr (experimental) */
   ^
1 error generated.
*** Error code 1

Stop.


Best,

Jakob

On 2020-08-25 04:38, 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&revision=364746

If you encounter problems please report them to me, Ryan Moeller, and -current.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: 'chflags: fts_read: Permission denied' on fresh -CURRENT

[Roman Bogorodskiy]

Yes, it allows to move further and build is currently running.

Thanks

  Mateusz Guzik wrote:

> Does: sysctl vfs.cache_fast_lookup=0 clean it up for you?
> 
> On 8/25/20, Roman Bogorodskiy  wrote:
> > Hi,
> >
> > I've updated -CURRENT today to r364753, and poudriere started failing
> > with:
> >
> > [00:00:00] Creating the reference jail...chflags: fts_read: Permission
> > denied
> > [00:00:00] Cleaning up
> > [00:00:00] Unmounting file systems
> > chflags: fts_read: Permission denied
> >
> > I've created a new jail and it fails with the same error.
> >
> > I'm not using zfs and also I use the same sources for poudriere jails as
> > the host, i.e.:
> >
> > current 13.0-CURRENT 1300112 amd64   src=/usr/src 2020-08-25
> > 13:17:30 /usr/local/poudriere/jails/current
> > current13   13.0-CURRENT 1300113 amd64   src=/usr/src 2020-08-25
> > 16:19:13 /usr/local/poudriere/jails/current13
> >
> > Any ideas what could be wrong with this?
> >
> > Roman Bogorodskiy
> >
> 
> 
> -- 
> Mateusz Guzik 

Roman Bogorodskiy


signature.asc
Description: PGP signature

Re: 'chflags: fts_read: Permission denied' on fresh -CURRENT

[Mateusz Guzik]

Does: sysctl vfs.cache_fast_lookup=0 clean it up for you?

On 8/25/20, Roman Bogorodskiy  wrote:
> Hi,
>
> I've updated -CURRENT today to r364753, and poudriere started failing
> with:
>
> [00:00:00] Creating the reference jail...chflags: fts_read: Permission
> denied
> [00:00:00] Cleaning up
> [00:00:00] Unmounting file systems
> chflags: fts_read: Permission denied
>
> I've created a new jail and it fails with the same error.
>
> I'm not using zfs and also I use the same sources for poudriere jails as
> the host, i.e.:
>
> current 13.0-CURRENT 1300112 amd64   src=/usr/src 2020-08-25
> 13:17:30 /usr/local/poudriere/jails/current
> current13   13.0-CURRENT 1300113 amd64   src=/usr/src 2020-08-25
> 16:19:13 /usr/local/poudriere/jails/current13
>
> Any ideas what could be wrong with this?
>
> Roman Bogorodskiy
>


-- 
Mateusz Guzik 
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

'chflags: fts_read: Permission denied' on fresh -CURRENT

[Roman Bogorodskiy]

Hi,

I've updated -CURRENT today to r364753, and poudriere started failing
with:

[00:00:00] Creating the reference jail...chflags: fts_read: Permission denied
[00:00:00] Cleaning up
[00:00:00] Unmounting file systems
chflags: fts_read: Permission denied

I've created a new jail and it fails with the same error.

I'm not using zfs and also I use the same sources for poudriere jails as
the host, i.e.:

current 13.0-CURRENT 1300112 amd64   src=/usr/src 2020-08-25 13:17:30 
/usr/local/poudriere/jails/current
current13   13.0-CURRENT 1300113 amd64   src=/usr/src 2020-08-25 16:19:13 
/usr/local/poudriere/jails/current13

Any ideas what could be wrong with this?

Roman Bogorodskiy


signature.asc
Description: PGP signature

Re: Strange USB loop

[Hans Petter Selasky]

On 2020-08-25 07:03, bob prohaska wrote:

On Tue, Aug 25, 2020 at 12:46:01AM +0200, Hans Petter Selasky wrote:

On 2020-08-24 18:37, bob prohaska wrote:

After updating to
FreeBSD 13.0-CURRENT (GENERIC) #5 r364475: Mon Aug 24 06:47:29 PDT 2020
on a Pi3 it was necessary to disconnect the mouse, keyboard and usb-serial


You are after:

https://svnweb.freebsd.org/changeset/base/364433

You may want to try a kernel before:

r364379


Can you try r364346 ?


A kernel for
FreeBSD 13.0-CURRENT (GENERIC) #6 r364378: Tue Aug 25 00:46:27 PDT 2020
compiled and installed without incident, but the problem persists. This
time I plugged the keyboard into the hub and got a stream of
uhub_reattach_port: giving up port reset - device vanished
which didn't stop when the keyboard was removed. If the keyboard is
moved to the Pi's internal USB connectors the keyboard is recognized
and works, but the once-per-second "...device vanished" messages continue.

Attempts to repeat this behavior were frustrating. After a few iterations
the error message was triggered by plugging in an FTDI usb-serial adapter,
but the messages stopped when it was unplugged.

The hub is
Bus /dev/usb Device /dev/ugen1.4: ID 05e3:0610 Genesys Logic, Inc. 4-port hub

The disk adapter is
Bus /dev/usb Device /dev/ugen1.5: ID 152d:1561 JMicron Technology Corp. / 
JMicron USA Technology Corp. JMS561U two ports SATA 6Gb/s bridge

Are either of these known troublmakers?


--HPS
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"