From owner-freebsd-fs@FreeBSD.ORG Wed Jan 25 07:51:08 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 04F881065673 for ; Wed, 25 Jan 2012 07:51:08 +0000 (UTC) (envelope-from ndenev@gmail.com) Received: from mail-ee0-f54.google.com (mail-ee0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id 88C818FC12 for ; Wed, 25 Jan 2012 07:51:07 +0000 (UTC) Received: by eekb47 with SMTP id b47so2041584eek.13 for ; Tue, 24 Jan 2012 23:51:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:content-type:content-transfer-encoding:date:subject:to :message-id:mime-version:x-mailer; bh=IdtJ2z2hJxLavgaaEEEoR7SAMaUtCMpjIzLpJGTzDT4=; b=cRzkXKoCgXu8KdFA4xatv84HLwG/0Y3YNTtu/btTCfEQc81XE4QNXBFe2y948y+zM3 Lk7+9iSNTQ2ROah82tvRqXgowuQ1xIxqQEmMz5fs6CcqZpXJIO3l0ZzewcdP9L+yVri7 SDaiFAlhrY+xmhj6s8z7bOzb/Y1jjkIAf2BSM= Received: by 10.14.16.100 with SMTP id g76mr3456960eeg.102.1327477866106; Tue, 24 Jan 2012 23:51:06 -0800 (PST) Received: from ndenevsa.sf.moneybookers.net (g1.moneybookers.com. [217.18.249.148]) by mx.google.com with ESMTPS id x4sm78235078eeb.4.2012.01.24.23.51.04 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 24 Jan 2012 23:51:05 -0800 (PST) From: Nikolay Denev Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Wed, 25 Jan 2012 09:51:04 +0200 To: freebsd-fs@FreeBSD.ORG Message-Id: Mime-Version: 1.0 (Apple Message framework v1251.1) X-Mailer: Apple Mail (2.1251.1) Cc: Subject: BIO_DELETE support for ZVOLs? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jan 2012 07:51:08 -0000 I'm don't know if anyone thought about this but it seems like a nice feature to support TRIM like functionality for ZVOLs. For example : if there is a sparse ZFS volume, formatted with UFS, and you fill it up once, then the disk space used will be with the size = of the ZVOL. Then even if there is freed space on the UFS filesystem, the ZVOL disk space allocated from the ZVOL will remain the same. This also will be very nice if can be supported for FC exported ZVOLs = via the new CAM Target Layer.