ecryptfs-setup-private fails with ZFS

Bug #1574174 reported by Richard Laager on 2016-04-24
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
eCryptfs
Undecided
Unassigned
ecryptfs-utils (Ubuntu)
Undecided
Unassigned

Bug Description

The obvious approach for using ZFS and ecryptfs together involves creating a dataset like this:
zfs create -o mountpoint=/home/.ecryptfs/USER rpool/home/USER

As a result, /proc/mounts looks like this:
rpool/home/USER /home/.ecryptfs/USER zfs rw,xattr 0 0

ecryptfs-setup-private checks for existing mount points:
grep -qs "$MOUNTPOINT " /proc/mounts && error "[$MOUNTPOINT]" "$(gettext 'is already mounted')"

This matches the list in /proc/mounts because of the device column ("rpool/home/USER").

Adding a space before $MOUNTPOINT in the grep (just like the space after it) solves this problem and shouldn't impact the intended purpose of the check.

Related branches

Richard Laager (rlaager) wrote :

I proposed the fix for upstream as a BZR branch:
https://code.launchpad.net/~rlaager/ecryptfs/fix-lp-1574174/+merge/292844

Tyler Hicks (tyhicks) wrote :

r881

Changed in ecryptfs:
status: New → Fix Committed
Richard Laager (rlaager) wrote :

Any chance of an ecryptfs update in time for Yakkety?

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ecryptfs-utils (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers