Package Details: openafs-modules-dkms 1.8.6-3

Git Clone URL: https://aur.archlinux.org/openafs-modules-dkms.git (read-only, click to copy)
Package Base: openafs-modules-dkms
Description: Kernel module for OpenAFS (dkms)
Upstream URL: http://www.openafs.org
Licenses: custom:"IBM Public License Version 1.0"
Conflicts: openafs<1.6.6-2, openafs-features-libafs, openafs-modules
Provides: openafs-modules=1.8.6
Submitter: Bevan
Maintainer: Bevan
Last Packager: Bevan
Votes: 17
Popularity: 0.026634
First Submitted: 2014-03-23 13:24
Last Updated: 2020-10-17 21:51

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 Next › Last »

cptiglo commented on 2016-03-15 17:24

Any news concerning Linux 4.4?

Bevan commented on 2016-02-29 16:42

There are first reports of data corruption when running OpenAFS on Linux 4.4. The proposed patches should therefore only be considered for testing and debugging and not for actual use in production.

warai_otoko commented on 2016-02-17 01:20

I've installed the patched version; it at least builds fine, I'll let you know if I run into any issues.

Bevan commented on 2016-02-14 18:22

Unfortunately I don't know more than what was mentioned in that mailing list post. So I'd say your data would be as safe as your latest backup…
It may also very well be that there are no issues. It's just that no developer had a closer look on this yet.

warai_otoko commented on 2016-02-14 17:34

I'd be interested in testing the patches, as long as the potential data loss isn't anything too nasty; can you give more details on what sorts of issues I might encounter?

Bevan commented on 2016-02-09 10:43

You can test the proposed patches for Linux 4.4.
Download the corresponding branch of my PKGBUILDs from https://github.com/michaellass/AUR/archive/openafs-linux-4.4.zip, enter the openafs-modules-dkms folder and run makepkg.

Testing these patches (and providing feedback) would be very helpful in the process of getting these patches included, you should be aware of possible unresolved data loss issues:
https://lists.openafs.org/pipermail/openafs-info/2016-January/041627.html
This is also the main reason why I did not include the patches here, yet.

RobvW commented on 2016-02-09 10:38

doesn't build anymore on 4.4 kernel. Any patch in the works?

alexpe87 commented on 2015-05-03 12:54

Stupid me, forgot to delete the old version of the package. Alright, works now again!

Thanks again!

Bevan commented on 2015-05-03 12:53

@alexpe87: No worries. That's what the comment system is for :)

It very much looks like you have installed an old version of the openafs-modules-dkms package (1.6.11):
Creating symlink /var/lib/dkms/openafs/1.6.11/source -> /usr/src/openafs-1.6.11

This should be 1.6.11.1.

1.6.11 doesn't know what kernel version 4 means, that's why it's saing "Couldn't guess your Linux version".

So just install the current version and dkms should be able to build the module.

alexpe87 commented on 2015-05-03 11:51



Sorry for spamming your packages, but I got this problem when building the current version of this package (see attached logfile). Kernel is 4.0.1-1 (current, mainline), usually had no issues building this here. In the mentioned logfile it says that it can't guess my linux version ;-)

"
...
checking whether byte order is known at compile time... yes
checking whether byte ordering is bigendian... no
checking whether printf understands the %z length modifier... yes
checking your OS... linux
configure: error: Couldn't guess your Linux version 2
...
"

Creating symlink /var/lib/dkms/openafs/1.6.11/source ->
/usr/src/openafs-1.6.11

DKMS: add completed.

Kernel preparation unnecessary for this kernel. Skipping...

Building module:
cleaning build area....
(./configure --prefix=/usr --sysconfdir=/etc --sbindir=/usr/bin --libexecdir=/usr/bin --with-linux-kernel-packaging --disable-fuse-client --with-linux-kernel-headers=/usr/lib/modules/4.0.1-1-ARCH/build && make )....(bad exit status: 1)
Error! Bad return status for module build on kernel: 4.0.1-1-ARCH (x86_64)
Consult /var/lib/dkms/openafs/1.6.11/build/make.log for more information.
error: command failed to execute correctly