From owner-freebsd-fs@freebsd.org  Mon Oct 23 13:08:39 2017
Return-Path: <owner-freebsd-fs@freebsd.org>
Delivered-To: freebsd-fs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id AB455E4B52E
 for <freebsd-fs@mailman.ysv.freebsd.org>; Mon, 23 Oct 2017 13:08:39 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 99EC56FE75
 for <freebsd-fs@FreeBSD.org>; Mon, 23 Oct 2017 13:08:39 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v9ND8cXt060426
 for <freebsd-fs@FreeBSD.org>; Mon, 23 Oct 2017 13:08:39 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-fs@FreeBSD.org
Subject: [Bug 223015] [tmpfs] [patch] tmpfs does not support sparse files
Date: Mon, 23 Oct 2017 13:08:38 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: kwhite@site.uottawa.ca
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-223015-3630-0RtbD8ro02@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-223015-3630@https.bugs.freebsd.org/bugzilla/>
References: <bug-223015-3630@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Oct 2017 13:08:39 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223015

--- Comment #8 from Keith White <kwhite@site.uottawa.ca> ---
I read but probably misunderstood! If I create a file with holes I don't wa=
nt
to be "charged" for it until the holes are filled in.  I may want to create=
 a
disk image file, say, that is 4g but I know that I will only be storing 20m=
 in
total.  ffs-like filesystems allow this.  tmpfs has a more straight-forward
idea of a file (allocate up-front, no hole management?).  A "BUGS" section =
in
tmpfs(5) would have guided me away from attempting to use tmpfs for sparse
files. Othersize tmpfs is an excellent fit for me since I'm running
diskless+swapless.

I'll re-read your comments. I see a drawing-board over there that I should =
get
back to...

...keith

--=20
You are receiving this mail because:
You are the assignee for the bug.=