Re: r346025: ZFS filesystems do not mount anymore

2019-04-09 Thread Enji Cooper (yaneurabeya)
> On Apr 9, 2019, at 21:51, Enji Cooper wrote: … > CCing crees@, the author of r346017, for context. I will file a PR soon if > one hasn’t already been filed. I filed https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237172 to track the issue. Cheers! -Enji

Re: r346025: ZFS filesystems do not mount anymore

2019-04-09 Thread Enji Cooper
s this weekend, mounting ZFS filesystems on >>>>> CURRENT r346025 doesn't work anymore at boot time when ZFS is >>>>> built-in-kernel. zfs_enable="YES" is set in /etc/rc.conf. >>>>> >>>>> After the system has booted, mounting all ZFS f

Re: r346025: ZFS filesystems do not mount anymore

2019-04-09 Thread Michael Butler
-in-kernel. zfs_enable="YES" is set in /etc/rc.conf. >>>> >>>> After the system has booted, mounting all ZFS filesystems via "zfs mount >>>> -a" operates as expected and all filesystems are available as usual. >>> >>>

Re: lsof hangs with latest 13.0-CURRENT snapshot

2019-04-09 Thread Cy Schubert
On April 9, 2019 12:41:34 PM PDT, "Rodney W. Grimes" wrote: >> On Tue, 2019-04-09 at 12:20 -0700, Rodney W. Grimes wrote: >> > > After upgrading from FreeBSD-13.0-CURRENT-amd64-20190328-r345620 >to >> > > FreeBSD-13.0-CURRENT-amd64-20190404-r345863, lsof (4.92 from >> > > packages) >> > > hangs.

make buildkernel doesn't

2019-04-09 Thread tech-lists
/13-current/r346053/20190409-kernbuildfail.txt thanks, -- J. signature.asc Description: PGP signature

Re: lsof hangs with latest 13.0-CURRENT snapshot

2019-04-09 Thread Larry Rosenman
On 04/09/2019 2:41 pm, Rodney W. Grimes wrote: On Tue, 2019-04-09 at 12:20 -0700, Rodney W. Grimes wrote: > > After upgrading from FreeBSD-13.0-CURRENT-amd64-20190328-r345620 to > > FreeBSD-13.0-CURRENT-amd64-20190404-r345863, lsof (4.92 from > > packages) > > hangs. > > > > This is true for

Re: lsof hangs with latest 13.0-CURRENT snapshot

2019-04-09 Thread Rodney W. Grimes
> On Tue, 2019-04-09 at 12:20 -0700, Rodney W. Grimes wrote: > > > After upgrading from FreeBSD-13.0-CURRENT-amd64-20190328-r345620 to > > > FreeBSD-13.0-CURRENT-amd64-20190404-r345863, lsof (4.92 from > > > packages) > > > hangs. > > > > > > This is true for bare metal installs and virtual

Re: lsof hangs with latest 13.0-CURRENT snapshot

2019-04-09 Thread David Boyd
On Tue, 2019-04-09 at 12:20 -0700, Rodney W. Grimes wrote: > > After upgrading from FreeBSD-13.0-CURRENT-amd64-20190328-r345620 to > > FreeBSD-13.0-CURRENT-amd64-20190404-r345863, lsof (4.92 from > > packages) > > hangs. > > > > This is true for bare metal installs and virtual machine installs. >

Re: lsof hangs with latest 13.0-CURRENT snapshot

2019-04-09 Thread Rodney W. Grimes
> After upgrading from FreeBSD-13.0-CURRENT-amd64-20190328-r345620 to > FreeBSD-13.0-CURRENT-amd64-20190404-r345863, lsof (4.92 from packages) > hangs. > > This is true for bare metal installs and virtual machine installs. > > How to recreate: > > Install

Re: ZFS: can't read MOS of zpool...

2019-04-09 Thread Alexandre C. Guimarães
Hello, I don't get those messages when booting from the installation media, all disks are apparently showing up correctly from `gpart list` from there, and I updated the bootblocks: --- # gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada0 --- however the error messages still do persist

lsof hangs with latest 13.0-CURRENT snapshot

2019-04-09 Thread David Boyd
After upgrading from FreeBSD-13.0-CURRENT-amd64-20190328-r345620 to FreeBSD-13.0-CURRENT-amd64-20190404-r345863, lsof (4.92 from packages) hangs. This is true for bare metal installs and virtual machine installs. How to recreate: Install

Re: ZFS: can't read MOS of zpool...

2019-04-09 Thread Toomas Soome
When did you update the bootblocks last time? You can grab iso/usb image with current and check if loader there can see your pools - and if yes, update the boot blocks on disk… rgds, toomas > On 9 Apr 2019, at 20:37, Alexandre C. Guimarães wrote: > > Hello, > > I can't say the precise

ZFS: can't read MOS of zpool...

2019-04-09 Thread Alexandre C . Guimarães
Hello, I can't say the precise point this started but I am convinced that was right after running `zpool upgrade` after upgrading to 12-RELEASE: --- ZFS: i/o error - all block copies unavailable ZFS: can't read MOS of pool zdata --- So, I got another disk to substitute that one, and now I have

Re: r346025: ZFS filesystems do not mount anymore

2019-04-09 Thread O. Hartmann
> > > After the system has booted, mounting all ZFS filesystems via "zfs mount > > > -a" operates as expected and all filesystems are available as usual. > > > > I blame r346017: > > > > Trying to mount root from zfs:zroot/ROOT/20190409-

Re: r346025: ZFS filesystems do not mount anymore

2019-04-09 Thread Trond Endrestøl
gt; > expected and all filesystems are available as usual. > > I blame r346017: > > Trying to mount root from zfs:zroot/ROOT/20190409-r346017 [] > Setting hostuuid: 7b624d1c-4bc3-e2cb-4ac2-6487a4b4774c. > Setting hostid: 0xf9071336. > interface zfsctrl.1 already present in

Re: r346025: ZFS filesystems do not mount anymore

2019-04-09 Thread Trond Endrestøl
s_enable="YES" is > set in /etc/rc.conf. > > After the system has booted, mounting all ZFS filesystems via "zfs mount -a" > operates as > expected and all filesystems are available as usual. I blame r346017: Trying to mount root from zfs:zroot/ROOT/20