Date: Thu, 22 Oct 2020 17:29:35 -0300 From: Cassiano Peixoto <peixotocassiano@gmail.com> To: "Sergey V. Dyatko" <sergey.dyatko@gmail.com>, tsoome@me.com Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: Zpool doesn't boot anymore after FreeBSD 12.1 Message-ID: <CAJajdNW5xGw7agyw8KAQrAPAcgbHm7V2HjebLUsks8NDORRyjg@mail.gmail.com> In-Reply-To: <CAJajdNUddV64%2Bd82xOjD-fNjtqruWhimpQxXHv0k1nVUV%2BLoFQ@mail.gmail.com> References: <CAJajdNWgiKyd1jmX4uPogWU4Ty=OiEgDnQGaoLZUWgj_pr9WKw@mail.gmail.com> <CAJajdNXPhGj-mKj6R_N94Bfnhvm=nHr3RwfBm4qoTB3g_=6kGw@mail.gmail.com> <CAJajdNV0nGdhAm6cgs2SKMBsY=Hi1Azb8fA_0PFrLUuejCT8ag@mail.gmail.com> <e109cba7-2716-7a83-3d39-66de48b93c8b@FreeBSD.org> <CAJajdNXo-rqBjR8FL4GTw6sy691NFH0B-CnHv_88i5P6XJECDA@mail.gmail.com> <33381216-498a-51ff-839c-da772c43b60e@FreeBSD.org> <20201022203752.36fb6f3f@laptop.domain> <CAJajdNUddV64%2Bd82xOjD-fNjtqruWhimpQxXHv0k1nVUV%2BLoFQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Toomas, Thank you for this patch. Can I know when it will be MFCed? I'd like to try. Hi! Please try 366951:) I think, it should get things better for you. rgds, toomas On Thu, Oct 22, 2020 at 3:04 PM Cassiano Peixoto <peixotocassiano@gmail.com> wrote: > Sergey, > > I agree with you. The best thing is to revert the commit on zfsloader. > Many people didn't realize this issue yet, but they will run into a big > problem soon. > > On Thu, Oct 22, 2020 at 2:41 PM Sergey V. Dyatko <sergey.dyatko@gmail.com> > wrote: > >> On Thu, 22 Oct 2020 16:42:16 +0300 >> Andriy Gapon <avg@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@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, Sergey >> >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >> >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJajdNW5xGw7agyw8KAQrAPAcgbHm7V2HjebLUsks8NDORRyjg>