-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
spl-dkms ubuntu package, configure error #42
Comments
How did you install this system?
Please post this information:
You might need to run |
On Tue, Aug 21, 2012 at 01:45:47PM -0700, Darik Horn wrote:
I installed it over the net via PXE and kickseed (debian-installer). The
dkms statusspl, 0.6.0.71: added dpkg --get-selections | grep linuxliblinux-inotify2-perl install
dkms build -m spl -v 0.6.0.71 spl: I do not know how to handle spl. Kernel preparation unnecessary for this kernel. Skipping... Running the pre_build script: Building module: DKMS: build completed. Ummm...?
Attached. Its the config.log from the above run rather than from the For jollies I ran "apt-get --reinstall install spl-dkms" and it failed as apt-get --reinstall install spl-dkmsReading package lists... Done -------- Uninstall Beginning -------- Kernel: 3.2.0-29-generic (x86_64)Status: This module version was INACTIVE for this kernel. DKMS: uninstall completed. Deleting module version: 0.6.0.71 completely from the DKMS tree.Done. I've also attached the config.log from the above run (as config-bad.log). ls /usr/src/linux-headers-3.2.0-29-generic/arch/alpha cris ia64 microblaze parisc sh unicore32
I ran the remove/add commands and reran the build with similar success. I So apt-get's invocation of dkms is somehow different than the shell's? Ryan |
Github stripped your attachments, so please send those things to me directly. Apart from the missing module, it looks like the build succeeded, which is weird. Does your kickstart configuration install the ubuntu-minimal package by default? Ubuntu resolves a different dependency graph for base systems that get ubuntu-desktop, ubuntu-minimal, or neither. DKMS can fail to build ZoL on systems that didn't get ubuntu-minimal at install time because the kernel headers or a compiler component is missing. This is by design. However, your error message doesn't fit that problem. |
It shouldn't be, but there is a way to override it. Leave the ticket open if you want me to pursue this issue. I will have time to look at it next week. Otherwise, please click the "close issue" button. |
On Tue, Aug 21, 2012 at 03:33:32PM -0700, Darik Horn wrote:
I think it was operator error actually. I'll try again. :)
Yes, or rather a reverse dependency pulled it in. Ryan It was created by configure, which was $ /var/lib/dkms/spl/0.6.0.71/build/configure --prefix=/usr --with-config=kernel --with-linux=/lib/modules/3.2.0-29-generic/build --with-linux-obj=/lib/modules/3.2.0-29-generic/build ---------Platform.---------hostname = logit /usr/bin/uname -p = unknown /bin/arch = unknown PATH: /bin -----------Core tests.-----------configure:2176: checking metadata configure:3361: $? = 0 |
On Tue, Aug 21, 2012 at 04:00:04PM -0700, Darik Horn wrote:
Its not an emergency or anything, but it'd be great if you have time to Thanks, |
I du have a similar problem here is what I did: run VirtualBox 4.1.20 r80170 on Windows 7 64Bit host system I am not sure, why the kernel packages are held back, that is something I have not found out why ubuntu does that. Thanks, |
You will get the desired result by using |
Right now, the problem seems:
Ways to mitigate the problem are:
|
Right now using the 12.04.1 would solve the problem temporarily, as there is not yet a kernel update available for 12.04.1, but as soon as a kernal update will be available for 12.04.1, there is again a high propability for the same error. I did not use the alternate installer. I installed with the desktop.iso. I thought dist-upgrade just used for upgrading from like 11.10 to 12.04, but from googleing it seems that dist-upgrade should include the kernel. I just tried, and used dist-upgrade to install the new kernel, but ends with the same problem. I could send you an appliance to reproduce the problem. (I have dropbox, so I could send you a link. Will just take some time to upload. |
Just to summarize: My intention is to set up a new system to use ZFS for a 8 disk array and ubuntu 12.04 LTS. and run the system for a loooong time. Now I just want to make sure, the system will survive updates. So I set up the VirtualBox environment to simulate such situations. The experience within update/upgrade worries me a bit, that the system might be rendered not functional after such an upgrade. This is why I would just feel better, when the upgrade would flawlessly include the zfs part. Otherwise It might be to risky to run native zfs for the root filesystem too. I could still use it for some data pools but not for the root. Maybe it is still too risky to use the native zfs at all and use a fuse version instead for just data pools, or completely stay with software-raid5. But on the other side I like a lot of the exclusive features, that ZFS offers, especially the checksum to check data integrity. |
Please post a link here. I'm busy, but somebody else might look at it before me.
There are ZoL users tracking daily kernel builds, so this is unlikely.
But you previously said: The alternate installer does not produce the same result as the desktop installer. I get a non-trivial number of dud bug reports involving custom installations, especially on virtual hosts, so please confirm that you are doing a default installation using the ubuntu-12.04.1-desktop-amd64.iso image. Users that do custom installations are responsible for installing
Running a native ZFS root is experimental. |
Am 01.09.2012 13:45, schrieb Darik Horn:
I also guess that kernel updates will always require manual interaction |
I created a VirtualBox appliance file, that has 12.04 LTS desktop 64Bit installed and zfs from stable repository. |
(Thanks for posting the OVA.) I downloaded the virtual machine and did this:
The upgrade succeeded and I got this:
I tried both of Virtual Box 4.2.0.80231 (the Oracle build) and VMware Player 5.0.0.812388, but could not reproduce the error in either host. Perhaps your local Canadian mirror is inconsistent. Try again later, or try a different mirror. Also note that this VM has 1GB of memory, which is less than the minimum system requirements for ZoL. All installations should have 2GB, but preferably 4GB or more. |
On 02/09/2012 18:41, Darik Horn wrote:
I will try to import the appliance and try again. It is weird! |
I tried the Canadian mirror today and it worked. A video of the given https://github.com/downloads/dajhorn/pkg-zfs/ZFS%20Movie%20for%20@JoGruni.avi The avi file requires the vmnc codec because I used VMware Workstation for the capture. It would be a drudgery, but you could compare my result to your result. This issue is not-a-bug in ZoL if it is caused by an inconsistent mirror or apt cache. I will leave this ticket open for a few more weeks; maybe somebody else will notice the glitch and suggest a better explanation. |
I tried a few variants too. I think the dist-upgrade makes the difference. I am still trying and let you know, when i drilled down the source of the problem. JoachimSent from my Android phone with K-9 Mail. Please excuse my brevity. Darik Horn notifications@github.com wrote: I tried the Canadian mirror today and it worked. A video of the given ZFS.ova machine upgrading itself is here: https://github.com/downloads/dajhorn/pkg-zfs/ZFS%20Movie%20for%20@JoGruni.avi The avi file requires the vmnc codec because I used VMware Workstation for the capture. It would be a drudgery, but you could compare my result to your result. This issue is not-a-bug in ZoL if it is caused by an inconsistent mirror or apt cache. I will leave this ticket open for a few more weeks; maybe somebody else will notice the glitch and suggest a better explanation. — |
I appreciate your help. This problem sounds like it should be a FAQ item. |
But there is also another coincident. The zfs version meanwhile did a version jump from 73 to 74. So the zfs packages are deleted, reinstalled and recompiled anyway. |
I did a few more tests and here are my findings: When I initially ran into the error I was using the stable repository. So there was no newer version of the zfs modules during dist-upgrade while testing. This makes a difference! Now I did the following test and the error can be reproduced: This error will be more likely to encounter being on the stable repository, than when being on the daily repo. Hope that helps a bit. |
I got this error first hand yesterday. It was caused by an archive inconsistency; the mirror state does not necessarily reflect the Launchpad state. The error message is, unfortunately, misleading and there is no obvious way to improve it. The problem could be mitigated by implementing dajhorn/pkg-zfs#12 or resolved by bundling SPL into the ZFS package. |
The DKMS package with the experimental BUILD_DEPENDS directive only resolves dependencies for automatic installations, like those invoked through the run-parts for kernel packages. Set "Pre-Depends: spl-dkms" in the `debian/control` file so that the first non-automatic build by `/usr/lib/dkms/common.postinst` happens for SPL before ZFS is added to dkms. NB: Commit b08e6b3. This change plus the enhanced DKMS package... Closes: dajhorn/pkg-zfs#42 Closes: dajhorn/pkg-zfs#44
The fix for this family of problems will take effect when an updated DKMS package appears in the daily PPA sometime in the next two weeks. The solution is somewhat invasive, so it will likely be a while longer before it appears in the stable PPA. |
While installing the packages for the first time onto a 12.04 box:
Setting up spl-dkms (0.6.0.71-0ubuntu1~precise1) ...
Loading new spl-0.6.0.71 DKMS files...
First Installation: checking all kernels...
Building only for 3.2.0-29-generic
Building initial module for 3.2.0-29-generic
configure: error: *** Unable to build an empty module.
Error! Bad return status for module build on kernel: 3.2.0-29-generic (x86_64)
Consult /var/lib/dkms/spl/0.6.0.71/build/make.log for more information.
where the make.log contains:
DKMS make.log for spl-0.6.0.71 for kernel 3.2.0-29-generic (x86_64)
Tue Aug 21 10:43:24 PDT 2012
make: *** No targets specified and no makefile found. Stop.
The initial apt-get also failed to install the zfs-dkms package because of the dependency:
Setting up zfs-dkms (0.6.0.71-0ubuntu1~precise1) ...
Loading new zfs-0.6.0.71 DKMS files...
First Installation: checking all kernels...
Building only for 3.2.0-29-generic
Building initial module for 3.2.0-29-generic
configure: error:
*** Cannot determine the version of the spl source.
*** ZFS depends on the SPL kernel module, which is not yet ready.
*** DKMS should retry zfs-dkms momentarily after building spl-dkms.
*** If this error message persists, or if you are running DKMS manually,
*** then run 'apt-get install --reinstall spl-dkms' and try again.
Error! Bad return status for module build on kernel: 3.2.0-29-generic (x86_64)
Consult /var/lib/dkms/zfs/0.6.0.71/build/make.log for more information.
which resembles issue #30. I am able to manually build and install spl by going to /var/lib/dkms/spl/0.6.0.71/build/, but when I tried the same with the zfs module it advised against it:
Reattempting via 'apt-get install --reinstall spl-dkms' produces the same error.
The text was updated successfully, but these errors were encountered: