| 1 |
________________________________________ |
| 2 |
From: Rich Freeman <rich0@g.o> |
| 3 |
Sent: Tuesday, May 28, 2019 9:54 AM |
| 4 |
To: gentoo-user@l.g.o |
| 5 |
Subject: Re: [gentoo-user] block for zfs-0.8.0 how to fix safely |
| 6 |
|
| 7 |
On Tue, May 28, 2019 at 4:35 AM Neil Bothwick <neil@××××××××××.uk> wrote: |
| 8 |
> |
| 9 |
> On Tue, 28 May 2019 04:04:23 -0400, John Covici wrote: |
| 10 |
> |
| 11 |
> > In my latest update, there is a hard block sys-kernel/spl-0.7.13 is |
| 12 |
> > blocking 0.8.0. Can I unmerge the old one and still have access to my |
| 13 |
> > pools while the new one is compiled. My whole system except /boot is |
| 14 |
> > on zfs, this is wny I am asking, or should I do this one emerge from a |
| 15 |
> > rescue disk? |
| 16 |
> |
| 17 |
> spl is now part of the zfs package, so you will still have it after |
| 18 |
> updating. During the update, the module will still be in memory. If you |
| 19 |
> reboot during the update, you will have a problem, I kept a backup copy |
| 20 |
> of the spl modules just in case, or you could quickpkg spl. |
| 21 |
|
| 22 |
The one file you really need is: |
| 23 |
/lib/modules/4.19.46/extra/spl/spl.ko.gz |
| 24 |
(or whatever version you're using). |
| 25 |
|
| 26 |
I would personally do the switch during a kernel update, so that you |
| 27 |
can leave your old modules around and boot the old kernel. |
| 28 |
|
| 29 |
I'm honestly not sure if portage will leave the old kernel module in |
| 30 |
place when doing the switch. Looking at my kernel directory I see old |
| 31 |
spl modules so when re-emerging spl it isn't removing the old modules. |
| 32 |
However, I also can't see any documented mechanism that would protect |
| 33 |
kernel modules from unmerging. It could be an undocumented portage |
| 34 |
feature (it does make sense to leave the old kernel modules around). |
| 35 |
|
| 36 |
If you update an existing kernel in-place none of this will help as |
| 37 |
the zfs bundled spl would overwrite the spl-bundled version. And of |
| 38 |
course it wouldn't make sense to mix the two in a kernel anyway. |
| 39 |
|
| 40 |
I'll see how it goes in a few months when I try out 0.8. As much as |
| 41 |
I'm looking forward to a few of its features I'm really in no rush to |
| 42 |
go trying new versions of filesystems... |
| 43 |
|
| 44 |
-- |
| 45 |
Rich |
| 46 |
|
| 47 |
|
| 48 |
|
| 49 |
I have upgraded to zfs-0.8.0 while downgrading the kernel on my server to 4.19.45 to avoid the performance hit involved with encryption. |
| 50 |
|
| 51 |
Steps I took that seemed to work well. |
| 52 |
1. add >=sys-kernel/gentoo-sources-5.0 to package.mask |
| 53 |
2. emerge gentoo-sources-4.19.45 (auto picked just doing a normal emerge -av gentoo-sources) |
| 54 |
3. eselect kernel list/set to set the symlink for /usr/src/linux |
| 55 |
4. emerge -C sys-kernel/spl (it doesn't remove old installs in kernel modules for previous kernels that I've seen) |
| 56 |
5. enter /usr/src/linux and do your standard make -j(x) && make modules_install && make install && update bootloader etc |
| 57 |
6. manually emerge -auv zfs to get 0.8.0 pulled in and built (if you have other modules you can consider doing emerge -av @module-rebuild afterwards) |
| 58 |
7. reboot and test it out :) |
| 59 |
8. if everything is fine and running well, and you are positive you are not going to be going back to <0.8.0 you can do zpool upgrade -a, to take advantage of the new features of 0.8.0 |
| 60 |
|
| 61 |
Hope that helps |
Archives