[gentoo-user] problems with installing zfs-kmod under new kernel

[gentoo-user] problems with installing zfs-kmod under new kernel

[John Covici]

Hi.  I am having problems installing zfs-kmod on my new kernel
5.4.69.  Originally I got this:

!!! Multiple package instances within a single package slot have been
    pulled
    !!! into the dependency graph, resulting in a slot conflict:

sys-fs/zfs-kmod:0

  (sys-fs/zfs-kmod-2.0.0_rc3:0/0::gentoo, ebuild scheduled for merge)
  USE="rootfs -custom-cflags -debug" ABI_X86="(64)" pulled in by
      (no parents that aren't satisfied by other packages in this
  slot)

  (sys-fs/zfs-kmod-2.0.0_rc1:0/0::gentoo, installed) USE="rootfs
  -custom-cflags -debug" ABI_X86="(64)" pulled in by
      ~sys-fs/zfs-kmod-2.0.0_rc1 required by
  (sys-fs/zfs-2.0.0_rc1-r1:0/0::gentoo, installed) USE="nls pam rootfs
  (split-usr) -custom-cflags -debug (-kernel-builtin) -libressl
  -minimal -python (-static-libs) -test-suite" ABI_X86="(64)"
  PYTHON_TARGETS="python3_7 -python3_6 -python3_8"
      ^                ^^^^^^^^^



It may be possible to solve this problem by using package.mask to
prevent one of those packages from being selected. However, it is also
possible that conflicting dependencies exist such that they are
impossible to satisfy simultaneously.  If such a conflict exists in
the dependencies of two different packages, then those packages can
not be installed simultaneously.

For more information, see MASKED PACKAGES section in the emerge man
page or refer to the Gentoo Handbook.

Then I masked off the -rc3 version thinking that would help and I got
this:


 
!!! Multiple package instances within a single package slot have been
pulled
!!! into the dependency graph, resulting in a slot conflict:

sys-fs/zfs-kmod:0

  (sys-fs/zfs-kmod-0.8.5:0/0::gentoo, ebuild scheduled for merge)
  USE="rootfs -custom-cflags -debug" ABI_X86="(64)" pulled in by
      (no parents that aren't satisfied by other packages in this
  slot)

  (sys-fs/zfs-kmod-2.0.0_rc1:0/0::gentoo, installed) USE="rootfs
  -custom-cflags -debug" ABI_X86="(64)" pulled in by
      ~sys-fs/zfs-kmod-2.0.0_rc1 required by
  (sys-fs/zfs-2.0.0_rc1-r1:0/0::gentoo, installed) USE="nls pam rootfs
  (split-usr) -custom-cflags -debug (-kernel-builtin) -libressl
  -minimal -python (-static-libs) -test-suite" ABI_X86="(64)"
  PYTHON_TARGETS="python3_7 -python3_6 -python3_8"
      ^                ^^^^^^^^^



It may be possible to solve this problem by using package.mask to
prevent one of those packages from being selected. However, it is also
possible that conflicting dependencies exist such that they are
impossible to satisfy simultaneously.  If such a conflict exists in
the dependencies of two different packages, then those packages can
not be installed simultaneously.

For more information, see MASKED PACKAGES section in the emerge man
page or refer to the Gentoo Handbook.

So, how do I fix -- I was thinking of uninstalling zfs-kmod, but was
afraid it would delete from my running kernel (4.19.144) or some other
fcatastrophe, so I thought I'd ask here first.

I am on the zfs-discuss list and a few months ago they were talking
about a necessary patch to install in 5.4 kernels because of not
exporting some symhbols as well.

Thanks in advance for any suggestions.

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici wb2una
         covici@ccs.covici.com

Re: [gentoo-user] problems with installing zfs-kmod under new kernel

[Rich Freeman]

On Wed, Oct 7, 2020 at 9:28 AM John Covici <covici@ccs.covici.com> wrote:
>
> Hi.  I am having problems installing zfs-kmod on my new kernel
> 5.4.69.  Originally I got this:
>
> !!! Multiple package instances within a single package slot have been
>     pulled
>     !!! into the dependency graph, resulting in a slot conflict:
>
> sys-fs/zfs-kmod:0
>
>   (sys-fs/zfs-kmod-2.0.0_rc3:0/0::gentoo, ebuild scheduled for merge)
>   USE="rootfs -custom-cflags -debug" ABI_X86="(64)" pulled in by
>       (no parents that aren't satisfied by other packages in this
>   slot)
>
>   (sys-fs/zfs-kmod-2.0.0_rc1:0/0::gentoo, installed) USE="rootfs
>   -custom-cflags -debug" ABI_X86="(64)" pulled in by
>       ~sys-fs/zfs-kmod-2.0.0_rc1 required by
>   (sys-fs/zfs-2.0.0_rc1-r1:0/0::gentoo, installed) USE="nls pam rootfs
>   (split-usr) -custom-cflags -debug (-kernel-builtin) -libressl
>   -minimal -python (-static-libs) -test-suite" ABI_X86="(64)"
>   PYTHON_TARGETS="python3_7 -python3_6 -python3_8"
>       ^                ^^^^^^^^^
>

This is because you're attempting to upgrade zfs-kmod and not zfs.
You didn't paste your command line but chances are you didn't have
both packages on it.

> Then I masked off the -rc3 version thinking that would help and I got
> this:
>
>
>
> !!! Multiple package instances within a single package slot have been
> pulled
> !!! into the dependency graph, resulting in a slot conflict:
>
> sys-fs/zfs-kmod:0
>
>   (sys-fs/zfs-kmod-0.8.5:0/0::gentoo, ebuild scheduled for merge)
>   USE="rootfs -custom-cflags -debug" ABI_X86="(64)" pulled in by
>       (no parents that aren't satisfied by other packages in this
>   slot)
>
>   (sys-fs/zfs-kmod-2.0.0_rc1:0/0::gentoo, installed) USE="rootfs
>   -custom-cflags -debug" ABI_X86="(64)" pulled in by
>       ~sys-fs/zfs-kmod-2.0.0_rc1 required by
>   (sys-fs/zfs-2.0.0_rc1-r1:0/0::gentoo, installed) USE="nls pam rootfs
>   (split-usr) -custom-cflags -debug (-kernel-builtin) -libressl
>   -minimal -python (-static-libs) -test-suite" ABI_X86="(64)"
>   PYTHON_TARGETS="python3_7 -python3_6 -python3_8"
>       ^                ^^^^^^^^^
>

That is because masking rc3 forces it to downgrade to an older version
of zfs (which may or may not be compatible with what you have on-disk
so you might be in for a surprise when you reboot).  But, since you're
only updating one package but not the other you still get the same
error.

What version of zfs do you WANT to use?  Are you already running on
the v2 release candidate?  (Probably not what most people should be
doing...)  If so you need to figure out if your pools are even
compatible with v0.8.5 (I'm not sure offhand if new features were
added, and if they were it would probably depend on whether you
upgraded your pools).

If you are on the v2rc and want to stick with it, then undo whatever
masking you did and just update both packages together:
emerge -1au zfs-kmod zfs

Really though that should already happen if you did an emerge -u
@world assuming both are in your world.

If you want to run v0.8.5 then I would mask both zfs-kmod and zfs
>=0.9 and then run the same command.

If you're on 0.8.4 though you might seriously consider just accepting
only stable keywords on zfs though - it is a filesystem and maybe not
something you want to be cutting edge.

And you definitely don't want to go uninstalling zfs-kmod as now the
module will be gone and once again you'll get a surprise when you
reboot.

In the future though I'd probably avoid installing release candidates
if you are running one.  That is, unless it is your goal to beta-test
filesystems.

-- 
Rich

Re: [gentoo-user] problems with installing zfs-kmod under new kernel

[John Covici]

On Wed, 07 Oct 2020 09:53:42 -0400,
Rich Freeman wrote:
> 
> On Wed, Oct 7, 2020 at 9:28 AM John Covici <covici@ccs.covici.com> wrote:
> >
> > Hi.  I am having problems installing zfs-kmod on my new kernel
> > 5.4.69.  Originally I got this:
> >
> > !!! Multiple package instances within a single package slot have been
> >     pulled
> >     !!! into the dependency graph, resulting in a slot conflict:
> >
> > sys-fs/zfs-kmod:0
> >
> >   (sys-fs/zfs-kmod-2.0.0_rc3:0/0::gentoo, ebuild scheduled for merge)
> >   USE="rootfs -custom-cflags -debug" ABI_X86="(64)" pulled in by
> >       (no parents that aren't satisfied by other packages in this
> >   slot)
> >
> >   (sys-fs/zfs-kmod-2.0.0_rc1:0/0::gentoo, installed) USE="rootfs
> >   -custom-cflags -debug" ABI_X86="(64)" pulled in by
> >       ~sys-fs/zfs-kmod-2.0.0_rc1 required by
> >   (sys-fs/zfs-2.0.0_rc1-r1:0/0::gentoo, installed) USE="nls pam rootfs
> >   (split-usr) -custom-cflags -debug (-kernel-builtin) -libressl
> >   -minimal -python (-static-libs) -test-suite" ABI_X86="(64)"
> >   PYTHON_TARGETS="python3_7 -python3_6 -python3_8"
> >       ^                ^^^^^^^^^
> >
> 
> This is because you're attempting to upgrade zfs-kmod and not zfs.
> You didn't paste your command line but chances are you didn't have
> both packages on it.
> 
> > Then I masked off the -rc3 version thinking that would help and I got
> > this:
> >
> >
> >
> > !!! Multiple package instances within a single package slot have been
> > pulled
> > !!! into the dependency graph, resulting in a slot conflict:
> >
> > sys-fs/zfs-kmod:0
> >
> >   (sys-fs/zfs-kmod-0.8.5:0/0::gentoo, ebuild scheduled for merge)
> >   USE="rootfs -custom-cflags -debug" ABI_X86="(64)" pulled in by
> >       (no parents that aren't satisfied by other packages in this
> >   slot)
> >
> >   (sys-fs/zfs-kmod-2.0.0_rc1:0/0::gentoo, installed) USE="rootfs
> >   -custom-cflags -debug" ABI_X86="(64)" pulled in by
> >       ~sys-fs/zfs-kmod-2.0.0_rc1 required by
> >   (sys-fs/zfs-2.0.0_rc1-r1:0/0::gentoo, installed) USE="nls pam rootfs
> >   (split-usr) -custom-cflags -debug (-kernel-builtin) -libressl
> >   -minimal -python (-static-libs) -test-suite" ABI_X86="(64)"
> >   PYTHON_TARGETS="python3_7 -python3_6 -python3_8"
> >       ^                ^^^^^^^^^
> >
> 
> That is because masking rc3 forces it to downgrade to an older version
> of zfs (which may or may not be compatible with what you have on-disk
> so you might be in for a surprise when you reboot).  But, since you're
> only updating one package but not the other you still get the same
> error.
> 
> What version of zfs do you WANT to use?  Are you already running on
> the v2 release candidate?  (Probably not what most people should be
> doing...)  If so you need to figure out if your pools are even
> compatible with v0.8.5 (I'm not sure offhand if new features were
> added, and if they were it would probably depend on whether you
> upgraded your pools).
> 
> If you are on the v2rc and want to stick with it, then undo whatever
> masking you did and just update both packages together:
> emerge -1au zfs-kmod zfs
> 
> Really though that should already happen if you did an emerge -u
> @world assuming both are in your world.
> 
> If you want to run v0.8.5 then I would mask both zfs-kmod and zfs
> >=0.9 and then run the same command.
> 
> If you're on 0.8.4 though you might seriously consider just accepting
> only stable keywords on zfs though - it is a filesystem and maybe not
> something you want to be cutting edge.
> 
> And you definitely don't want to go uninstalling zfs-kmod as now the
> module will be gone and once again you'll get a surprise when you
> reboot.
> 
> In the future though I'd probably avoid installing release candidates
> if you are running one.  That is, unless it is your goal to beta-test
> filesystems.

I was on 0.8.4 and it upgraded me to 22.0.0_rc1.  I have not upgraded
my pools, so I think I can go back to 0.8.4 or 5.  The kernel I am
upgrading is not the running kernel, so would any of this effect my
 running kernel which is 4.19.144 -- unfortunately on 2.0.0_rc1, but I
 agree maybe I should mask it off and go to 0.8.5.
 

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici wb2una
         covici@ccs.covici.com

Re: [gentoo-user] problems with installing zfs-kmod under new kernel

[Rich Freeman]

On Wed, Oct 7, 2020 at 10:36 AM John Covici <covici@ccs.covici.com> wrote:
>
> I was on 0.8.4 and it upgraded me to 22.0.0_rc1.  I have not upgraded
> my pools, so I think I can go back to 0.8.4 or 5.  The kernel I am
> upgrading is not the running kernel, so would any of this effect my
>  running kernel which is 4.19.144 -- unfortunately on 2.0.0_rc1, but I
>  agree maybe I should mask it off and go to 0.8.5.

Yeah, or just stay on 0.8.4.  0.8.5 was only released upstream this
week.  With my root and multiple TB of data on zfs I really don't want
to face a restore situation.  I do have backups but it would take days
to restore everything.

As long as you never ran zpool upgrade you should be able to downgrade
the version you're running.  That said, anytime I change kernels I
keep some old ones lying around just in case, including their modules.

-- 
Rich

Re: [gentoo-user] problems with installing zfs-kmod under new kernel

[John Covici]

On Wed, 07 Oct 2020 20:48:29 -0400,
Rich Freeman wrote:
> 
> On Wed, Oct 7, 2020 at 10:36 AM John Covici <covici@ccs.covici.com> wrote:
> >
> > I was on 0.8.4 and it upgraded me to 22.0.0_rc1.  I have not upgraded
> > my pools, so I think I can go back to 0.8.4 or 5.  The kernel I am
> > upgrading is not the running kernel, so would any of this effect my
> >  running kernel which is 4.19.144 -- unfortunately on 2.0.0_rc1, but I
> >  agree maybe I should mask it off and go to 0.8.5.
> 
> Yeah, or just stay on 0.8.4.  0.8.5 was only released upstream this
> week.  With my root and multiple TB of data on zfs I really don't want
> to face a restore situation.  I do have backups but it would take days
> to restore everything.
> 
> As long as you never ran zpool upgrade you should be able to downgrade
> the version you're running.  That said, anytime I change kernels I
> keep some old ones lying around just in case, including their modules.
Yep, not a bid idea at all, I usually do that as well.

Thanks.

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici wb2una
         covici@ccs.covici.com