Summary: | sys-fs/zfs-kmod-0.6.0_rc13 fails to emerge on x86 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Moritz Schlarb <moschlar> |
Component: | New packages | Assignee: | Richard Yao (RETIRED) <ryao> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | creffett |
Priority: | Normal | Keywords: | Goal |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://github.com/zfsonlinux/zfs/issues/814 | ||
Whiteboard: | x86 support broke in Linux 3.4 and no one realized until now. | ||
Package list: | Runtime testing required: | --- | |
Attachments: |
Proposed patch for sys-kernel/spl to fix the issue
Config for sys-kernel/hardened-sources-3.5.4-r1 build.log Config for sys-kernel/openvz-sources-2.6.32.62.2 config.log |
Description
Moritz Schlarb
2013-01-06 19:18:43 UTC
Created attachment 334684 [details]
Proposed patch for sys-kernel/spl to fix the issue
This issue only occurs on a fraction of x86 systems. I currently do not understand the cause and I would like to change that. Would you attach your kernel .config and the build.log from sys-fs/zfs-kmod? By the way, I should warn you that x86 is currently not keyworded because x86 support has regressions in comparison to amd64. The main regression is that ZFS likely requires manual tuning of vmalloc and possibly also zfs_arc_max. My plan is to keyword x86 only after upstream does page cache unification, which should eliminate the tuning issue and open the door for more rigorous regression testing by upstream. Until then, it will remain unkeyworded. It should be safe (data integrity-wise) for you to use ZFS on x86, but you will likely encounter glitches such as this until the 32-bit issues have been fully resolved. Created attachment 334968 [details]
Config for sys-kernel/hardened-sources-3.5.4-r1
-
Created attachment 334984 [details]
build.log
I don't plan to use it productively on x86, I just did a presentation and wanted to show zfs in a virtual machine which only had x86 architecture.
Created attachment 335156 [details]
Config for sys-kernel/openvz-sources-2.6.32.62.2
#5 attachment is a kernel config where zfs compiles correctly. Moritz, would you attach the config.log from your system? You can get it by running: ebuild /usr/portage/sys-fs/zfs-kmod/zfs-kmod-0.6.0_rc13.ebuild clean configure Then the file would be /var/tmp/portage/sys-fs/zfs-kmod-0.6.0_rc13/work/zfs-zfs-0.6.0-rc13/config.log. Created attachment 335264 [details]
config.log
Here you go
The following upstream patch will fix this: https://github.com/zfsonlinux/spl/commit/dd3678fc29d75286b57e705454bbd7e60e1b44e0 The reason why some people were affected and others were not is that the affectd people were on Linux 3.4 and later. I will backport this patch to sys-kernel/spl later this week. This should be fixed in sys-fs/zfs-kmod-0.6.0_rc14-r1. |