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