Fedora 23 (4.4.9-300.fc23) ZFS problem after reboot

[Maikel van Leeuwen]

Yesterday I upgraded a Fedora server to 4.4.9-300.fc23.x86_64, after the
reboot all my ZFS pools where
gone. After some fiddling and testing I created these set of steps to
solve the problem:

dnf remove zfs
dnf install  zfs
modprobe zfs
zpool import
zpool import -D
zpool import raid1
zfs mount -a

Can somebody acknowledge the same problem and is this to be more expected in the future? 

ZFS version: zfs-0.6.5.7-1.fc23.x86_64

[James Hogarth]

On 31 May 2016 at 11:42, Maikel van Leeuwen <maikel.van.leeuwen(a)sentia.com&gt;
wrote:

>  Yesterday I upgraded a Fedora server to 4.4.9-300.fc23.x86_64, after
> the
>  reboot all my ZFS pools where
>  gone. After some fiddling and testing I created these set of steps to
>  solve the problem:
>
>  dnf remove zfs
>  dnf install  zfs
>  modprobe zfs
>  zpool import
>  zpool import -D
>  zpool import raid1
>  zfs mount -a
>
>  Can somebody acknowledge the same problem and is this to be more expected
>  in the future?
>
>  ZFS version: zfs-0.6.5.7-1.fc23.x86_64
>
>
>
>  
Enjoy the fun of a DKMS based filesystem ... you really need to ask the
zfsonlinux guys about this as Fedora does not ship or support ZFS

[Tom H]

On Tue, May 31, 2016 at 12:42 PM, Maikel van Leeuwen
<maikel.van.leeuwen(a)sentia.com&gt; wrote:
>  Yesterday I upgraded a Fedora server to 4.4.9-300.fc23.x86_64, after
>  the reboot all my ZFS pools where gone. After some fiddling and
>  testing I created these set of steps to solve the problem:
>
>  dnf remove zfs
>  dnf install zfs
>  modprobe zfs
>  zpool import
>  zpool import -D
>  zpool import raid1
>  zfs mount -a
>
>  Can somebody acknowledge the same problem and is this to be more expected in the future?
It looks like dkms didn't build the zfs modules when the kernel was
upgraded but it did when you re-installed zfs.

You can check which modules are built with "dkms status" after a new
kernel's installed.

If a module hasn't been rebuilt for it, you might be able to trigger
the build via the "/etc/kernel/postinst.d/dkms" script.

[Corey Sheldon]

On 05/31/2016 07:07 AM, Tom H wrote:
>  On Tue, May 31, 2016 at 12:42 PM, Maikel van Leeuwen
>  <maikel.van.leeuwen(a)sentia.com&gt; wrote:
> > Yesterday I upgraded a Fedora server to 4.4.9-300.fc23.x86_64, after
> > the reboot all my ZFS pools where gone. After some fiddling and
> > testing I created these set of steps to solve the problem:
> >
> > dnf remove zfs
> > dnf install zfs
> > modprobe zfs
> > zpool import
> > zpool import -D
> > zpool import raid1
> > zfs mount -a
> >
> > Can somebody acknowledge the same problem and is this to be more expected in the
> future?
>  It looks like dkms didn't build the zfs modules when the kernel was
>  upgraded but it did when you re-installed zfs.
>
>  You can check which modules are built with "dkms status" after a new
>  kernel's installed.
>
>  If a module hasn't been rebuilt for it, you might be able to trigger
>  the build via the "/etc/kernel/postinst.d/dkms" script.
>  --
>  users mailing list
>  users(a)lists.fedoraproject.org
>  To unsubscribe or change subscription options:
>  https://lists.fedoraproject.org/admin/lists/[e-mail]
>  Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
>  Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
>  Have a question? Ask away: http://ask.fedoraproject.org 
What repo are you using for zfs?

Also,  what was the last kernel or was this a  fresh netinstall ?

----
Corey W. Sheldon
PGP: 
0x5A88E539 / C006 564F FA67 CDEA E29B F202 8B4E 8943 5A88 E539
0xD2264944 / 6292 9ABD 6374 6AA7 6D4B 730F 5927 6298 D226 4944
Find me elsewhere: https://gist.github.com/linux-modder/ac5dc6fa211315c633c9

Confidentiality Note:  This message is intended for use only by the individual or entity
to which it is addressed and may contain information that is privileged, confidential,
and
exempt from disclosure under applicable law.  If the reader of this message is not the
intended recipient or the employee or agent responsible for delivering the message to the

intended recipient, you are hereby notified that any dissemination, distribution or
copying of this communication is strictly prohibited.  If you have received this
communication 
in error, please contact the sender immediately and destroy the material in its entirety,
whether electronic or hard copy.

[Maikel van Leeuwen]

On 06/01/2016 03:42 AM, Corey 'linuxmodder' Sheldon wrote:
>  On 05/31/2016 07:07 AM, Tom H wrote:
> > On Tue, May 31, 2016 at 12:42 PM, Maikel van Leeuwen
> > <maikel.van.leeuwen(a)sentia.com&gt; wrote:
> >> Yesterday I upgraded a Fedora server to 4.4.9-300.fc23.x86_64, after
> >> the reboot all my ZFS pools where gone. After some fiddling and
> >> testing I created these set of steps to solve the problem:
> >>
> >> dnf remove zfs
> >> dnf install zfs
> >> modprobe zfs
> >> zpool import
> >> zpool import -D
> >> zpool import raid1
> >> zfs mount -a
> >>
> >> Can somebody acknowledge the same problem and is this to be more expected in the
> future?
> > It looks like dkms didn't build the zfs modules when the kernel was
> > upgraded but it did when you re-installed zfs.
> >
> > You can check which modules are built with "dkms status" after a new
> > kernel's installed.
> >
> > If a module hasn't been rebuilt for it, you might be able to trigger
> > the build via the "/etc/kernel/postinst.d/dkms" script.
> > --
> > users mailing list
> > users(a)lists.fedoraproject.org
> > To unsubscribe or change subscription options:
> > https://lists.fedoraproject.org/admin/lists/[e-mail]
> > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> > Have a question? Ask away: http://ask.fedoraproject.org
>  What repo are you using for zfs?
http://archive.zfsonlinux.org/fedora/$releasever/$basearch/



>  Also,  what was the last kernel or was this a  fresh netinstall ? 
Current
kernel's installed on the system:

kernel-4.4.9-300.fc23.x86_64
kernel-4.4.8-300.fc23.x86_64
kernel-4.4.6-301.fc23.x86_64

And now I recall, this happened also when I jumped from 4.4.6 to 4.4.8

So basically, I'll need to check every reboot if there's a new kernel
release and build a kernel module or is there a way to force the
/etc/kernel/postist.d/dkms script after every dnf update?

In regards,
Maikel van Leeuwen

>  ----
>  Corey W. Sheldon
>  PGP: 
>  0x5A88E539 / C006 564F FA67 CDEA E29B F202 8B4E 8943 5A88 E539
>  0xD2264944 / 6292 9ABD 6374 6AA7 6D4B 730F 5927 6298 D226 4944
>  Find me elsewhere: https://gist.github.com/linux-modder/ac5dc6fa211315c633c9
>
>  Confidentiality Note:  This message is intended for use only by the individual or entity
> to which it is addressed and may contain information that is privileged, confidential,
> and
>  exempt from disclosure under applicable law.  If the reader of this message is not the
> intended recipient or the employee or agent responsible for delivering the message to the
>
>  intended recipient, you are hereby notified that any dissemination, distribution or
> copying of this communication is strictly prohibited.  If you have received this
> communication 
>  in error, please contact the sender immediately and destroy the material in its entirety,
> whether electronic or hard copy.
>
>
>
>
>  --
>  users mailing list
>  users(a)lists.fedoraproject.org
>  To unsubscribe or change subscription options:
>  https://lists.fedoraproject.org/admin/lists/[e-mail]
>  Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
>  Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
>  Have a question? Ask away: http://ask.fedoraproject.org