See the release page (http://zfs-fuse.net/releases/0.7.0) for all the details and credits this time!
This article was culled from Announcing: ZFS-fuse 0.7.0.
]]>This should only interest users that exercise 'destructive inplace snapshot operations' (like e.g. zfs rollback) on live filesystems.
This article was culled from Security Notification.
]]>We have made a start by calling to life a wholesome documentation section. This was long overdue because, well, we had quite a number of frequently asked questions.
At the moment the documentation provides a number of FAQ sections and a How-To list.
As an example, consider the frequently asked question "Why is my pool not imported" in relation to changing device names. This is now addressed in the seminal FAQ entry Pool discovery.
Of course there is a long way to go before this documentation covers some ground. I'll make it my personal goal to add any generic Q/A that I see answered on the google group in it's rightful section.
Don't forget to publish your newly-writ FAQ entries, or no-one else but you will see them
wget -c 'http://gitweb.zfs-fuse.net/?p=official;a=snapshot;h=testing;sf=tgz'
http://gitweb.zfs-fuse.net/?p=official;a=shortlog;h=testing;hp=master
Alternatively, download the corresponding patch as
http://gitweb.zfs-fuse.net/?p=official;a=commitdiff_plain;h=testing;hp=master
Git web makes it far easier to cross-reference the history (e.g. the log comment for 2faf5475 will jump to the relevant commits in 2007). Lastly, blame has been enabled to make it easy to gauge how 'stable' a section of code has been over time.
This article was culled from Documentation and Gitweb Available; The Way Forward.
]]>The gentoo ebuilds have already been published, and we expect the other packagers to follow soon.
Refer to the release page for specifics and "What's New". This is also where you can conveniently grab the source tarball.
If you need help getting the new version to work, be sure to check
This article was culled from Announcing: ZFS-fuse 0.6.9.
]]>Emmanuel's fine last work (enabling NFS sharing using the convenient ZFS properties and zfs share -a) has since been stabilized and embedded in a lot of new work that gives rise to a grand new release of zfs-fuse.
Based on testing thus far, we are anticipating a stable version that will be in fact a bit more dependable than 0.6.0, which has seen it's share of issues since it's initial offering.
We are proud to let you know that we have already had many more testers giving 0.6.9_beta[123] a shot. Now's the time for any early adopters: ZFS for Linux 0.6.9 (Beta 3)
Keep in mind that this is still in beta so we appreciate your feedback and expect you know what risk you might be taking by installing a beta version
This article was culled from Upcoming release.
]]>After some initial testing, it seems to coming along nicely. Very nicely in fact. You can now
zfs set sharenfs=on pool/fs
This should automatically export the fs (readonly mode). Sometimes (depending on your setup) you might need to explicitely 'zfs unshare -a' or 'zfs share -a' (man ZFS(1)).
On debian/Ubuntu you will need the kernel nfs driver installed:
apt-get install nfs-kernel-server
(A reboot might be in order)
There are still noticeable differences between the syntax for the property between OpenSolaris and linux though. I'd use sharenfs='root=myusername' on Solaris. That won't fly on linux (message: exportfs failed).
On linux, I also had to explicitely allow writable exports (sharenfs='*:rw') whereas the behaviour on Solaris seemed to be that sharenfs=on already allows writable access. This may be dependent on some global nfs config that I don't currently know about.
Read over here for more information on the way to specify nfs options via zfs properties: http://groups.google.com/group/zfs-fuse/browse_thread/thread/2cdde8b804fa1f07
This article was culled from NFS auto-share (sharenfs) support landed in unstable.
]]>Applying these fixes will not require you to upgrade to later versions/of the code, the fixes have been backported against the official 0.6.0 tagged release. This should address:And since issue #22 this is a threading fix (instability) possibly quite a plethora of historically issues. More specifically, the following issues may be re-tested with this branch:
# description reference 1 disappearing datasets [regression] 2 tools hang on zfs ioctl due to bug in put_nvlist issue #13 3 zfs-fuse unstable under load issue #22
| description | reference |
|---|---|
| resilvering continues after offlining device to be resilvered | issue #20 |
| Resilvering interrupted when a vdev from another pool... | issue #12 |
| Hang while importing a pool with cache devices | issue #3 |
| parallel bandwidth | issue #2 |
Getting it should normally be a matter of# git clone http://git.zfs-fuse.net/official # cd official/ # git checkout origin/critical
and build/install
# cd src # scons -j2 # sudo scons install
See also: group list thread
Seth
This article was culled from Fixes released.
]]>This release brings a lots of news to the table:
-a and -e. -a doubles directory operations performances, and -e increases it up to 10000%. However, it is a known bug that -e breaks POSIX conformance and introduces a security bug. We are closely investigating the matter.-o that lets you specify additional FUSE mount options for your datasets at startup time.-m lets you cap the size of the built-in ARC to less memory than before, or increase it (though prefetch means you will still see memory usage higher than the cap). You can also disable page caching for files within ZFS datasets (--disable-page-cache option) and block cache as well (--disable-block-cache) but the later option will break mmap() in your ZFS datasets and, consequently, some applications like Skype./etc/default or /etc/sysconfig, so you don't have to worry about reconfiguring ZFS the next time you upgrade.Naturally, this release could not have been possible with the tireless efforts of the good people at the ZFS-FUSE list, who contributed selflessly to get this release out of the door. In no particular order, these are our heroes:
We invite you to install and test this release, and to file any issues that you might find in our bug tracker.
This article was culled from Announcing: ZFS-FUSE 0.6.0.
]]>Therefore, we are now using Git.
This article was culled from We have now moved to Git.
]]>