Re: zfs mount -a spins the system after upgrading from 12.2 to 13-BETA

[Andriy Gapon]

On 06/03/2021 20:09, Yoshihiro Ota wrote:
> Hi all,
> 
> I'm upgrading fron 12.2-RELEASE to 13-BETA/RC one by one.
> 
> After upgrading one in VMWare, 'zfs mount -a' hangs the system.
> I don't have boottime zfs mount on nor don't have zfsroot.
> I just simply ran install world/kernel and mergemaster.

Please use procstat -kk to capture a kernel stack trace of the hung process.


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

Re: geli broken in 13.0-BETA4 and later on armv8

[Peter Jeremy via freebsd-stable]

On 2021-Mar-06 10:39:02 -0800, Oleksandr Tymoshenko  wrote:
>Peter Jeremy via freebsd-current (freebsd-curr...@freebsd.org) wrote:
>> [Adding arm@ and making it clearer that this is armv8-only]
>> 
>> On 2021-Mar-06 20:26:19 +1100, Peter Jeremy  
>> wrote:
>> >On 2021-Mar-06 19:18:37 +1100, Peter Jeremy via freebsd-stable 
>> > wrote:
>> >>Somewhere between 13.0-ALPHA2 (c256201-g02611ef8ee9) and 13.0-BETA4
>> >>(releng/13.0-n244592-e32bc253629), geli (at least on my RockPro64 -
>> >>RK3399, arm64) has changed so that a geli-encrypted partition (using
>> >>AES-XTS 128) that was readable on 13.0-ALPHA2 becomes garbage on
>> >>13.0-BETA4.
>> >
>> >I've confirmed that the problem is f76393a6305b - reverting that
>> >commit fixes the problem in releng/13.0.
>> >
>> >I've further verified that the bug is still present in main (14.x)
>> >at 028616d0dd69.
>
>Could you test this patch and let me know if it fixes the issue?
>
>https://people.freebsd.org/~gonzo/patches/armv8crypto-xts-fix.diff

Yes, it does.  Thank you very much.

--- 
Peter Jeremy


signature.asc
Description: PGP signature

FreeBSD 13.0-RC1 Now Available

[Glen Barber]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

The first RC build of the 13.0-RELEASE release cycle is now available.

Installation images are available for:

o 13.0-RC1 amd64 GENERIC
o 13.0-RC1 i386 GENERIC
o 13.0-RC1 powerpc GENERIC
o 13.0-RC1 powerpc64 GENERIC64
o 13.0-RC1 powerpc64le GENERIC64LE
o 13.0-RC1 powerpcspe MPC85XXSPE
o 13.0-RC1 armv6 RPI-B
o 13.0-RC1 armv7 GENERICSD
o 13.0-RC1 aarch64 GENERIC
o 13.0-RC1 aarch64 RPI
o 13.0-RC1 aarch64 PINE64
o 13.0-RC1 aarch64 PINE64-LTS
o 13.0-RC1 aarch64 PINEBOOK
o 13.0-RC1 aarch64 ROCK64
o 13.0-RC1 aarch64 ROCKPRO64
o 13.0-RC1 riscv64 GENERIC
o 13.0-RC1 riscv64 GENERICSD

Note regarding arm SD card images: For convenience for those without
console access to the system, a freebsd user with a password of
freebsd is available by default for ssh(1) access.  Additionally,
the root user password is set to root.  It is strongly recommended
to change the password for both users after gaining access to the
system.

Installer images and memory stick images are available here:

https://download.freebsd.org/ftp/releases/ISO-IMAGES/13.0/

The image checksums follow at the end of this e-mail.

If you notice problems you can report them through the Bugzilla PR
system or on the -stable mailing list.

If you would like to use SVN to do a source based update of an existing
system, use the "releng/13.0" branch.

A summary of changes since 13.0-BETA4 includes:

o An update to handle partial data resending on ktls/sendfile has been
  added.

o A bug fix in iflib.

o A fix to pf(4) for incorrect fragment handling.

o A TCP performance improvement when using TCP_NOOPT has been added.

o Several SCTP fixes and improvements.

o Several other miscellaneous fixes and improvements.

A list of changes since 12.2-RELEASE is available in the releng/13.0
release notes:

https://www.freebsd.org/releases/13.0R/relnotes.html

Please note, the release notes page is not yet complete, and will be
updated on an ongoing basis as the 13.0-RELEASE cycle progresses.

=== Virtual Machine Disk Images ===

VM disk images are available for the amd64, i386, and aarch64
architectures.  Disk images may be downloaded from the following URL
(or any of the FreeBSD download mirrors):

https://download.freebsd.org/ftp/releases/VM-IMAGES/13.0-RC1/

The partition layout is:

~ 16 kB - freebsd-boot GPT partition type (bootfs GPT label)
~ 1 GB  - freebsd-swap GPT partition type (swapfs GPT label)
~ 20 GB - freebsd-ufs GPT partition type (rootfs GPT label)

The disk images are available in QCOW2, VHD, VMDK, and raw disk image
formats.  The image download size is approximately 135 MB and 165 MB
respectively (amd64/i386), decompressing to a 21 GB sparse image.

Note regarding arm64/aarch64 virtual machine images: a modified QEMU EFI
loader file is needed for qemu-system-aarch64 to be able to boot the
virtual machine images.  See this page for more information:

https://wiki.freebsd.org/arm64/QEMU

To boot the VM image, run:

% qemu-system-aarch64 -m 4096M -cpu cortex-a57 -M virt  \
-bios QEMU_EFI.fd -serial telnet::,server -nographic \
-drive if=none,file=VMDISK,id=hd0 \
-device virtio-blk-device,drive=hd0 \
-device virtio-net-device,netdev=net0 \
-netdev user,id=net0

Be sure to replace "VMDISK" with the path to the virtual machine image.

BASIC-CI images can be found at:

https://download.freebsd.org/ftp/releases/CI-IMAGES/13.0-RC1/

=== Amazon EC2 AMI Images ===

FreeBSD/amd64 EC2 AMIs are available in the following regions:

  af-south-1 region: ami-024a37d8ee55504a9
  eu-north-1 region: ami-0f7e6ef964131a5c5
  ap-south-1 region: ami-0da383cf93cddac9d
  eu-west-3 region: ami-0c2e5eecf725c8480
  eu-west-2 region: ami-07e739abd39787f83
  eu-south-1 region: ami-042c036041ab5c683
  eu-west-1 region: ami-02b72374c39f164f4
  ap-northeast-3 region: ami-06b158bab2dc009b8
  ap-northeast-2 region: ami-0fbcb7db014004a7f
  me-south-1 region: ami-0a5040da848631036
  ap-northeast-1 region: ami-0ea2e5573427aa49c
  sa-east-1 region: ami-0e8ca0e56ecd00395
  ca-central-1 region: ami-08503cd732e74743f
  ap-east-1 region: ami-0fa7c7d12cd5c992f
  ap-southeast-1 region: ami-0adc820ff9c36b582
  ap-southeast-2 region: ami-0f031e3027fe5ed45
  eu-central-1 region: ami-0685d9bbc37652517
  us-east-1 region: ami-0dc102bfa2a63a6c0
  us-east-2 region: ami-0d65407784cf103ac
  us-west-1 region: ami-0d676e4b02aeac56e
  us-west-2 region: ami-0f2f2e90ae8956750

FreeBSD/aarch64 EC2 AMIs are available in the following regions:

  af-south-1 region: ami-00bc7809c32164ef7
  eu-north-1 region: ami-079c3b3939e1422f5
  ap-south-1 region: ami-09f83dd115907186c
  eu-west-3 region: ami-0b466ac2ccb1d9a17
  eu-west-2 region: ami-03127626a3b795617
  eu-south-1 region: ami-04b543c7eca712cb2
  eu-west-1 region: ami-04bec8381d23b2d33
  ap-northeast-3 region: ami-08ec822521c26b950
  ap-northeast-2 region: ami-08b8dd381dcc36d65
  me-south-1 region: ami-07253323150004fb7
  

zfs mount -a spins the system after upgrading from 12.2 to 13-BETA

[Yoshihiro Ota]

Hi all,

I'm upgrading fron 12.2-RELEASE to 13-BETA/RC one by one.

After upgrading one in VMWare, 'zfs mount -a' hangs the system.
I don't have boottime zfs mount on nor don't have zfsroot.
I just simply ran install world/kernel and mergemaster.

Are there any special steps we need to take before upgrading?

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

Re: geli broken in 13.0-BETA4 and later on armv8

[Peter Jeremy via freebsd-stable]

[Adding arm@ and making it clearer that this is armv8-only]

On 2021-Mar-06 20:26:19 +1100, Peter Jeremy  wrote:
>On 2021-Mar-06 19:18:37 +1100, Peter Jeremy via freebsd-stable 
> wrote:
>>Somewhere between 13.0-ALPHA2 (c256201-g02611ef8ee9) and 13.0-BETA4
>>(releng/13.0-n244592-e32bc253629), geli (at least on my RockPro64 -
>>RK3399, arm64) has changed so that a geli-encrypted partition (using
>>AES-XTS 128) that was readable on 13.0-ALPHA2 becomes garbage on
>>13.0-BETA4.
>
>I've confirmed that the problem is f76393a6305b - reverting that
>commit fixes the problem in releng/13.0.
>
>I've further verified that the bug is still present in main (14.x)
>at 028616d0dd69.

-- 
Peter Jeremy


signature.asc
Description: PGP signature

Re: geli broken in 13.0-BETA4 and later

[Peter Jeremy via freebsd-stable]

On 2021-Mar-06 19:18:37 +1100, Peter Jeremy via freebsd-stable 
 wrote:
>Somewhere between 13.0-ALPHA2 (c256201-g02611ef8ee9) and 13.0-BETA4
>(releng/13.0-n244592-e32bc253629), geli (at least on my RockPro64 -
>RK3399, arm64) has changed so that a geli-encrypted partition (using
>AES-XTS 128) that was readable on 13.0-ALPHA2 becomes garbage on
>13.0-BETA4.

I've confirmed that the problem is f76393a6305b - reverting that
commit fixes the problem in releng/13.0.

I've further verified that the bug is still present in main (14.x)
at 028616d0dd69.

-- 
Peter Jeremy


signature.asc
Description: PGP signature

geli broken in 13.0-BETA4 and later

[Peter Jeremy via freebsd-stable]

Somewhere between 13.0-ALPHA2 (c256201-g02611ef8ee9) and 13.0-BETA4
(releng/13.0-n244592-e32bc253629), geli (at least on my RockPro64 -
RK3399, arm64) has changed so that a geli-encrypted partition (using
AES-XTS 128) that was readable on 13.0-ALPHA2 becomes garbage on
13.0-BETA4.

I've verified that the garbage seems consistent between reboots and
isn't impacted by enabling the big cores in 7ba4d0f82955.  There's
nothing useful reported via geli debugging.

I've tried updating to releng/13.0 60e8939aa85b and it's still broken.

My suspicion is f76393a6305b - whilst that just talks about AES-GCM,
it does a reasonable job of roto-tilling the entire armv8crypto stack.
I notice that there are a fixes to f76393a6305b that don't seem to
have made it into releng/13.0 and I will continue to investigate.

-- 
Peter Jeremy


signature.asc
Description: PGP signature