From owner-freebsd-fs@FreeBSD.ORG Fri Feb 20 16:23:20 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7D1C243A for ; Fri, 20 Feb 2015 16:23:20 +0000 (UTC) Received: from lwfs1-cam.cam.lispworks.com (mail.lispworks.com [46.17.166.21]) by mx1.freebsd.org (Postfix) with ESMTP id D2F762A1 for ; Fri, 20 Feb 2015 16:23:18 +0000 (UTC) Received: from higson.cam.lispworks.com (higson.cam.lispworks.com [192.168.1.7]) by lwfs1-cam.cam.lispworks.com (8.14.5/8.14.5) with ESMTP id t1KGCbXT046012; Fri, 20 Feb 2015 16:12:37 GMT (envelope-from martin@lispworks.com) Received: from higson.cam.lispworks.com (localhost.localdomain [127.0.0.1]) by higson.cam.lispworks.com (8.14.4) id t1KGCbHv014659; Fri, 20 Feb 2015 16:12:37 GMT Received: (from martin@localhost) by higson.cam.lispworks.com (8.14.4/8.14.4/Submit) id t1KGCacu014655; Fri, 20 Feb 2015 16:12:36 GMT Date: Fri, 20 Feb 2015 16:12:36 GMT Message-Id: <201502201612.t1KGCacu014655@higson.cam.lispworks.com> From: Martin Simmons To: "Ivailo A. Tanusheff" In-reply-to: <1422065A4E115F409E22C1EC9EDAFBA42214513E@sofdc01exc02.postbank.bg> (ITanusheff@postbank.bg) Subject: Re: ZVOL and snapshots length problem References: <1422065A4E115F409E22C1EC9EDAFBA42214513E@sofdc01exc02.postbank.bg> Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Feb 2015 16:23:20 -0000 >>>>> On Fri, 20 Feb 2015 13:19:28 +0000, Ivailo A Tanusheff said: > > Dear all, > > I have some trouble creating and manipulating ZVOL on my server. I am using FreeBSD 10 and I am creating a little bit sophisticated structure, where I create several file systems and volumes inside them for easy manipulation and snapshot management. > An example structure is: > / / / / > > Whenever my ZVOL path exceeds 63 characters, both when creating volume or snapshot, I receive this error in my messages log: > Feb 20 13:05:04 FreeBSD kernel: g_dev_taste: make_dev_p() failed (gp->name=zvol/TANK/Bank system/Core/DB@Daily_operations_2015-02-20-13:05, error=22) > Feb 20 13:05:04 FreeBSD kernel: g_dev_taste: make_dev_p() failed (gp->name=zvol/TANK/Bank system/Core/FS@Daily_operations_2015-02-20-13:05, error=22) > Feb 20 13:05:05 FreeBSD kernel: g_dev_taste: make_dev_p() failed (gp->name=zvol/TANK/Bank system/Core/Report@Daily_operations_2015-02-20-13:05, error=63) > > Feb 20 13:10:05 FreeBSD kernel: g_dev_taste: make_dev_p() failed (gp->name=zvol/TANK/Bank system/Core/DB@Daily_operations_2015-02-20-13:10, error=22) > Feb 20 13:10:05 FreeBSD kernel: g_dev_taste: make_dev_p() failed (gp->name=zvol/TANK/Bank system/Core/FS@Daily_operations_2015-02-20-13:10, error=22) > Feb 20 13:10:05 FreeBSD kernel: g_dev_taste: make_dev_p() failed (gp->name=zvol/TANK/Bank system/Core/Report@Daily_operations_2015-02-20-13:10, error=63) > > As far as I digged into it this is due to impossibility of creation of /dev/zvol/... pointing to that volume or snapshot, while the volume/snapshot is still visible in the zfs list tree, although I am not quite sure I can use it. > > Is there any way to fix this behavior or this is an implementation bug, not described in the manual? > If I create shorter names the problem disappears, but this is contra version of what I needed, so it is a not acceptable solution. I think this is a limitation in FreeBSD device naming. error=22 is EINVAL, because you have a space in the name. error=63 is ENAMETOOLONG, because the name is longer than SPECNAMELEN (also 63 by coincidence). __Martin