Date: Mon, 14 Mar 2011 02:44:16 -0400 From: "J. Hellenthal" <jhell@DataIX.net> To: Urankar Mikael <mikael.urankar@ujf-grenoble.fr> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: ZFSv28, zfs list behaviour and sysutils/freebsd-snapshot Message-ID: <alpine.BSF.2.00.1103140225100.90115@qvfongpu.qngnvk.ybpny> In-Reply-To: <20110310131710.GG96225@iut-mir-o.ujf-grenoble.fr> References: <20110310131710.GG96225@iut-mir-o.ujf-grenoble.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 10 Mar 2011 08:17, mikael.urankar@ wrote: > Hi, > > I'm using sysutils/freebsd-snapshot to make periodic ZFS backup snapshot > and this soft is broken since the upgrade of my pool to ZFSv28. > After some debugging it appears that "zfs list" behaviour has changed > with ZFSv28, and since freebsd-snapshot relies on "zfs list" to retrieve > the "ZFS file system name" from the "mountpoint name" the soft doesn't > work anymore. > > output of "zfs list" on a 8.2R amd64 (ZFSv15) : > zfs list /home/murankar > NAME USED AVAIL REFER MOUNTPOINT > tank/home/murankar 1.47M 1.59T 1.47M /home/murankar > > zfs list tank/home/murankar > NAME USED AVAIL REFER MOUNTPOINT > tank/home/murankar 1.47M 1.59T 1.47M /home/murankar > > on a 9-Current amd64 I've got no output for "zfs list /home/murankar" > and a exit code of 1 > the output of "zfs list tank/home/murankar" is correct : > NAME USED AVAIL REFER MOUNTPOINT > tank/home/murankar 6,56G 286G 6,55G /home/murankar Looking at the output here I am hoping that this is not hand typed! the character ',' appears in this output which might fool a script into doing other things if it has not been avoided in the first place. If you have upgraded that machine to 9-CURRENT and have sysutils/zfsnap installed I would recommend deleting any snapshots that you have before it runs the snapshot scripts. This assumes that the snapshot script might have changed since you upgraded it and that the snapshot names are different. Better to be on the sane side. See UPDATING/20100929 for reference. # Correct syntax: zfs list pool/dataset1/dataset2 # Incorrect syntax: ( I hope you were hand typing that and missed... ) zfs list /dataset1/dataset2 > > Is it the normal behaviour for ZFSv28 or some kind of regression ? > No its not normal, and some sort of regression possible. Though I usually take regression as performance issues as in speed. Also, pkg-descr freebsd-snapshot is a set of convenience front-end tools to mount(8) and mdconfig(8) for the management of UFS2 snapshots. It is also the under-lying tool used in the periodic snapshot scheduler periodic-snapshot(8) and the mounting/unmouning command in the amd(8) map /usr/local/etc/amd.map.snap. It provides the making, expiring, visiting, mounting and unmounting of filesystem snapshots. pkg-descr zfSnap is simple sh script to make rolling zfs snapshots with cron. Main advantage of zfSnap is that it's written in %100 pure /bin/sh, doesn't require any additional software to run, and is simple to use. zfSnap keeps all information about snapshot in snapshot name. zfs snapshot names are in form: Time-stamp--TTL where time-stamp is date and time of snapshot creation and TTL is Time To Live in human readable form. Did you happen to mix the above two up ? If so then rinse and repeat. Good luck, - -- Regards, J. Hellenthal (0x89D8547E) JJH48-ARIN -----BEGIN PGP SIGNATURE----- Comment: THIS SOFTWARE AND/OR CONTENTS IS PROVIDED BY THE AUTHOR ``AS IS'' AND Comment: ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE Comment: IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR Comment: PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY Comment: DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL Comment: DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS Comment: OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) Comment: HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, Comment: STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING Comment: IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE Comment: POSSIBILITY OF SUCH DAMAGE. iQEcBAEBAgAGBQJNfblYAAoJEJBXh4mJ2FR+5cIH/0csXIcjgGofUFOxVtCjOnnQ NlBo9MCwbq5E7VdGxsLQ1tS56/svUH5b6n/iUjT1Yca/gxGl39jxdwnvLFV8IqxD ahJNcf7vmnwZYILh34jfCCCP8UUl4JEk/huj3fVtV0smjp7obqpx2CuF9EtyRtnh 0tYoiHJberXjzQOO3jrDQhciSqAGjhOL8n8K8bPP28SRWC4l7ujVZX/Av8pXf8TA NnsLOfIOT18tkdr6j69YFCDHazE/Y/qTxfRV6ECgmah2OSlYzaeyF6DjsE2EuHtk bHQ/qTOQ+SJL6wrt13kXdbVX1tPnVuN2Ru7aYBswWPeocEemmqmKEuotmnLXOlQ= =yK0/ -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1103140225100.90115>