On Thu, 22 Oct 2020 16:42:16 +0300 Andriy Gapon <avg_at_FreeBSD.org> wrote: > On 22/10/2020 16:39, Cassiano Peixoto wrote: > > Hi Andriy, > > > > I've just tried copying my zfsloader from 11.2-STABLE (R350026) to FreeBSD > > 12.1 and 12.2 (STABLE) and fixed the issue. > > > > I also tried to use zfsloader of 11.3 but didn't work and the same issue > > happened. > > > > So it seems that something has changed on zfsloader after 11.2 that brings > > this issue. > > > > My question is: Should it be expected or is it a bug to be fixed? > > > > In my opinion it's a bug. > zfsloader should not require that disks must be partitioned. > +1 That's why I have terribly outdated 13-CURRENT on bunch of servers and can't update them. Most of them look like this: [tiger_at_st25]:~>zpool status pool: st25 state: ONLINE scan: none requested config: NAME STATE READ WRITE CKSUM st25 ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 ada0 ONLINE 0 0 0 ada1 ONLINE 0 0 0 mirror-1 ONLINE 0 0 0 ada2 ONLINE 0 0 0 ada3 ONLINE 0 0 0 mirror-2 ONLINE 0 0 0 ada4 ONLINE 0 0 0 ada5 ONLINE 0 0 0 mirror-3 ONLINE 0 0 0 ada6 ONLINE 0 0 0 ada7 ONLINE 0 0 0 errors: No known data errors They haven't separate boot device and have from 7 to 30+ Tb of data that I can't backup anywhere for re-install server with disk partitioning. Some time ago I managed to get aroud this reverting 2 commits ( r342151 + don't remember revision) but then there where some other improvements after which I lost the opportunity to revert this commits -- wbr, SergeyReceived on Thu Oct 22 2020 - 15:37:51 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:25 UTC