Package Details: zfs-linux 2.2.7_6.12.8.arch1.1-1

Git Clone URL: https://aur.archlinux.org/zfs-linux.git (read-only, click to copy)
Package Base: zfs-linux
Description: Kernel modules for the Zettabyte File System.
Upstream URL: https://openzfs.org/
Keywords: kernel linux openzfs zfs
Licenses: CDDL
Groups: archzfs-linux
Conflicts: spl-dkms, spl-dkms-git, spl-linux, zfs-dkms, zfs-dkms-git, zfs-dkms-rc, zfs-linux-git, zfs-linux-rc
Provides: spl, zfs
Replaces: spl-linux
Submitter: demizer
Maintainer: lightdot
Last Packager: lightdot
Votes: 273
Popularity: 1.91
First Submitted: 2016-04-21 08:45 (UTC)
Last Updated: 2025-01-04 04:03 (UTC)

Required by (19)

Sources (1)

Latest Comments

« First ‹ Previous 1 .. 26 27 28 29 30 31 32 33 34 35 36 .. 79 Next › Last »

cryptix commented on 2015-01-16 19:08 (UTC)

I did the update, too and my pool is still alive as well :) sorry for the noise ps: i also don't use ecc ram.

butler360 commented on 2015-01-15 21:35 (UTC)

No problems so far for me @cryptix.

kerberizer commented on 2015-01-15 21:32 (UTC)

Folks, some of you might have noticed that GRUB from the core packages doesn't recognize ZFS pools upgraded to support the most recent feature flags. This is because the upstream GRUB lacks the proper support for the hole_birth and embedded_data features. The problem doesn't affect booting, i.e. even systems with unpatched GRUB and fully upgraded pools boot normally, but especially on new installations grub-install fails, not recognizing the ZFS filesystem on the required devices. Tim Chase (@dweeezil on GitHub) has submitted patches upstream, but they have not yet been accepted. I've prepared a PKGBUILD, based on the standard package from the core repo and with Tim's patches [https://github.com/kerberizer/archzfs-git/tree/master/grub-zfs], and if you think it might be helpful, I can create an AUR here as well and/or perhaps @demizer could add the grub-zfs package to his repos. This should be a temporary problem only, but seeing that the activity in the GRUB repo is not too high, it might take some time before the patches that Tim has sent get incorporated upstream.

kerberizer commented on 2015-01-15 20:59 (UTC)

@cryptix, I always follow HEAD in my own PKGBUILDs and haven't faced any problems, but of course that's not an absolute guarantee.

cryptix commented on 2015-01-15 20:38 (UTC)

phew... that's a jump of 40 commits (on zfs, 10 on spl), did you test that zfs build? I see a lot of stuff I'm waiting for in there but it seems a bit risky to jump in there. thanks still! if this works out great i'd be really happy. compare of repos: https://github.com/zfsonlinux/zfs/compare/0ec07248...d958324f https://github.com/zfsonlinux/spl/compare/46c93675...03a78353

demizer commented on 2015-01-15 20:07 (UTC)

Hi everyone. I updated the packages for the 3.18.2-2 kernel. I have also moved the git commit target to HEAD for the spl and zfs packages.

demizer commented on 2015-01-14 18:16 (UTC)

I have 32gb non-ecc ram. I also use raidz-2 with six 3tb disks on http://amzn.com/B002RL8I7M with weekly scrubs. Smartd also sends me email if errors are detected on my disks. So far I have had three drives fail since 2012. ZFS has been a joy. This weekend I am going to setup http://www.mcelog.org/ for additional protection.

mpdavis73 commented on 2015-01-13 00:36 (UTC)

Check out episode 31 of BSDNow for a discussion - they had an interview with one of the OpenZFS devs in another episode. Also, read this blog: http://blog.brianmoses.net/2014/03/why-i-chose-non-ecc-ram-for-my-freenas.html . My current pool (a 2 disk mirrored VDEV with weekly scrubs) has been on Ubuntu, Arch, FreeBSD, and back to Arch, through 3 HDD replacements, all with the only issue being NFS syntax differences between Linux and FreeBSD. If you are worried about bad RAM, ZFS is the only FS I would trust.

cmtonkinson commented on 2015-01-12 21:13 (UTC)

For what it's worth, it's my understanding that ZFS is no more or less susceptible to damage from RAM bitflips than any other filesystem.