Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 29 Apr 2014 23:30:01 GMT
From:      Mark Martinec <Mark.Martinec@ijs.si>
To:        freebsd-ports-bugs@FreeBSD.org
Subject:   Re: ports/187922: sysutils/zfs-snapshot-mgmt =?UTF-8?Q?=32=30=30=39=30=32=30=31=5F=32=20stopped=20working=20with=20Fre?= =?UTF-8?Q?eBSD=31=30?=
Message-ID:  <201404292330.s3TNU1M7077495@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help
The following reply was made to PR ports/187922; it has been noted by GNATS.

From: Mark Martinec <Mark.Martinec@ijs.si>
To: bug-followup@FreeBSD.org, idefix@fechner.net
Cc:  
Subject: Re: ports/187922: sysutils/zfs-snapshot-mgmt
 =?UTF-8?Q?=32=30=30=39=30=32=30=31=5F=32=20stopped=20working=20with=20Fre?=
 =?UTF-8?Q?eBSD=31=30?=
Date: Wed, 30 Apr 2014 01:22:22 +0200

 > /usr/local/bin/zfs-snapshot-mgmt:130:in `join':
 >    can't convert nil into String (TypeError)
 
 This happens when a ZFS file system has no mountpoint.
 
 In case of a bsdinstall-ed FreeBSD-10 such filesystems are
 the top filesystem and a top/ROOT below it (both are empty).
 It is only the top/ROOT/default which has its mountpoint '/'.
 
 The zfs-snapshot-mgmt should not bail out on filesystems
 with no mountpoints, or at least it should issue a
 sensible error message.
 
 Currently a workaround is to either supply some dummy
 mountpoints for such filesystems, or avoid specifying
 in the zfs-snapshot-mgmt.conf the top file system
 (hoping the "recursive: true" would deal with the rest),
 but only list each mounted filesystem individually.
 



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201404292330.s3TNU1M7077495>