[zfs-fuse] beta version proposal

[sgheeren]

I propose to pull b79138c93d33261003512c33c0a849668d9a9169 into a new
branch called 0.6.9 (which is then the beta to 0.7.0)

If you all agree (at least Emmanuel) I will push to zfs-fuse.net and
post a notice containing major changes.

Perhaps it is nice for someone (Emmanuel?) to scan the STATUS (et al.)
doc for updates necessary

Seth

PS. i just checked and the pull is 'clean' except for a conflicting
changed comment

--
To post to this group, send email to zfs-...@googlegroups.com
To visit our Web site, click on http://zfs-fuse.net/

[Emmanuel Anne]

Is it because it's morning, but I can't find the
b79138c93d33261003512c33c0a849668d9a9169 in git log...
But git web seems to tell it's the latest commit, "fix for crash in
spa_history.c on powerpc arch".
Yes seems fine for me.

For the history, I am not sure I am the best placed to review it,
after all I have never used 0.6.x, so I'll leave that to others...
Are you pulling the zfsrc file this time ? It would be a good idea,
there are more and more parameters, and it's a good way to see what's
going on. The other way would be to write a man page for zfs-fuse,
maybe 1 day...
Anyway definitely an interesting version !

2010/5/4 sgheeren <sghe...@hotmail.com>:

--
zfs-fuse git repository :
http://rainemu.swishparty.co.uk/cgi-bin/gitweb.cgi?p=zfs;a=summary

[Xavier M.]

hello,
To summurize for the candides we are : is this new version a merge of the emmanuel branch and the Seth one?
Could you give us more information?
best regards
Xavier
ps : a zfs-fuse man would be great indead ;)

2010/5/4 Emmanuel Anne <emmanu...@gmail.com>

[sgheeren]

Ok,

i pushed a branch named 'testing', to get it either update your remotes or

    git clone http://git.zfs-fuse.net/official -b testing

for a fresh working copy.

I don't actively use my repo. It serves as a mirror only. So this branch is based on the 'official' master merged from Emmanuels master (b50a9e26f0367199667d).

I'll see if I can post a news item later but I'll give you guys a moment to check things for me :)

[sgheeren]

Oh PS:
I tagged it 0.6.9_beta

[Mike Gracy]

Dowloading it now and will compile at test it.
Platform: Ubuntu 9.10 on Dell Latitude D830 (dual core cpu), 4gb ram,
200gb 7200rpm drive

[Fajar A. Nugraha]

On Wed, May 5, 2010 at 3:27 AM, sgheeren <sghe...@hotmail.com> wrote:
> Oh PS:
> I tagged it 0.6.9_beta

This might be a good time to check the initscripts again. On testing branch:
contrib/zfs-fuse.initd.ubuntu: zpool import -a -f

and on Emmanuel's repo:
debian/zfs-fuse.init: zpool import -a -f

That may be dangerous considering these scenarios:
- cluster systems with zfs-fuse failover pool. Both nodes might import
the pool at the same time.
- Xen dom0, with domU using zfs, and dom0's partition/LVM directly
mapped as domU's partition. dom0 could potentially import domU's zfs
pools unconditionally.

--
Fajar

[Emmanuel Anne]

My init scripts are totally out of sync, I should resync them on
rudd-o's repository one day...

2010/5/5 Fajar A. Nugraha <fa...@fajar.net>:

--
zfs-fuse git repository :
http://rainemu.swishparty.co.uk/cgi-bin/gitweb.cgi?p=zfs;a=summary

[sgheeren]

It has come to my attention that not all versions of git support the mentioned '-b'. This has led to some confusion in testing (issue #38)

So here are the 'foolproof steps':

git clone http://git.zfs-fuse.net/official
cd official
git checkout -b testing origin/testing

This will create and checkout a new local branch named testing to track the upstream (official) testing branch.

If you already have a clone, update it (using git remote -v update, e.g.) and just issue the checkout command alone.

git log -1 should return the following information:

commit 12d41f24e1765ad541a90c5f0ecf176e63aed2da
Merge: b79138c b50a9e2
Author: Seth Heeren <sghe...@hotmail.com>
Date:   Tue May 4 22:00:38 2010 +0200

    0.6.9_beta