Bug 904643

Summary: Unable to mount zfs-fuse filesystems
Product: [Fedora] Fedora Reporter: Ilpo Nyyssonen <iny>
Component: zfs-fuseAssignee: Gwyn Ciesla <gwync>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 18CC: gwync, jr_marcobal, rmj
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-10 04:41:22 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
test none

Description Ilpo Nyyssonen 2013-01-26 18:57:48 UTC 
In Fedora 17 I had no problems with zfs-fuse. Then I upgraded to Fedora 18 using fedup and the zfs-fuse partitions were not correctly mounted. Finally I got it working by downgrading from zfs-fuse-0.7.0-7.fc18.x86_64 to Fedora 17 zfs-fuse (zfs-fuse-0.7.0-2.fc17.x86_64).

After this I tried zfs-fuse in a kvm virtual machine with Fedora 18:

1. Installed zfs-fuse-0.7.0-7.fc18.x86_64.
2. Started it.
3. Created a simple pool (stuff) with one disk.
4. The root of the pool doesn't seem to be mounted.
5. zfs mount stuff => cannot mount 'stuff': mountpoint or dataset is busy
6. zfs set canmount=noauto stuff
7. systemctl restart zfs-fuse
8. zfs mount stuff => No output
9. zfs mount stuff => cannot mount 'stuff': mountpoint or dataset is busy
11. zfs umount stuff => cannot unmount 'stuff': not currently mounted
Comment 1 Gwyn Ciesla 2013-01-28 15:44:28 UTC 
Do any of the intermediate f18 builds in koji work?  There were a lot of changes from -2 to -7, and it might help if we can pinpoint which one broke for you.

http://koji.fedoraproject.org/koji/packageinfo?packageID=7116
Comment 2 Ilpo Nyyssonen 2013-01-28 16:36:57 UTC 
I was able to repeat this with zfs-fuse-0.7.0-4.fc18. The previous one has been deleted.
Comment 3 Gwyn Ciesla 2013-01-28 17:38:38 UTC 
Is this reproducible with an already-existing zfs filesystem?  Also, can I have the exact commands run for 1-11 so I can make sure I'm not making any assumptions?
Comment 4 Ilpo Nyyssonen 2013-01-28 17:59:48 UTC 
Created attachment 689184 [details]
test
Comment 5 Gwyn Ciesla 2013-01-29 15:29:05 UTC 
Ok, thanks.  I can reproduce this and I'll see what I can do.
Comment 6 Gwyn Ciesla 2013-01-29 16:40:25 UTC 
Does the f18 build work on an f17 system?
Comment 7 Gwyn Ciesla 2013-01-29 18:34:35 UTC 
I figured it out, it's systemd's PrivateTmp that's causing this.  You can disable it in your unit file, I'll get a fix out ASAP.
Comment 8 Fedora Update System 2013-01-29 19:11:07 UTC 
zfs-fuse-0.7.0-8.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/zfs-fuse-0.7.0-8.fc18
Comment 9 Fedora Update System 2013-02-01 17:10:19 UTC 
Package zfs-fuse-0.7.0-8.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing zfs-fuse-0.7.0-8.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-1790/zfs-fuse-0.7.0-8.fc18
then log in and leave karma (feedback).
Comment 10 Roderick Johnstone 2013-02-05 20:26:12 UTC 
The update in comment #9 fixed the same problem for me.

I added a comment to the link in comment #9, but don't have an account so cannot leave positive karma.
Comment 11 juanra 2013-02-09 12:38:27 UTC 
The update fixed the problem for me, too
Thanks
Comment 12 Fedora Update System 2013-02-10 04:41:24 UTC 
zfs-fuse-0.7.0-8.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.