Date: Thu, 29 Nov 2018 11:10:26 -0700 From: Warner Losh <imp@bsdimp.com> To: Eugene Grosbein <eugen@freebsd.org> Cc: lists@jnielsen.net, src-committers <src-committers@freebsd.org>, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: Re: svn commit: r341232 - in head/usr.bin: . trim Message-ID: <CANCZdfp26rZvU9f7mgbUvwNwGdkDhoeF_FPCXRiJ2vVJq4U4OA@mail.gmail.com> In-Reply-To: <505717d1-ffad-5241-2dae-deb2e9900335@freebsd.org> References: <201811291421.wATELQbx059318@repo.freebsd.org> <9812F670-DD3D-4A56-A826-28B4A055F488@jnielsen.net> <CANCZdfrpMHncR2cigSpJZtdxBuEfHyK8zbKgV7d=up-PWTtkNA@mail.gmail.com> <505717d1-ffad-5241-2dae-deb2e9900335@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Nov 29, 2018 at 11:08 AM Eugene Grosbein <eugen@freebsd.org> wrote: > 30.11.2018 0:52, Warner Losh wrote: > > > It could work on files within a filesystem, but not in its current > state. ftruncate, however, is a better match there. None of the filesystems > support the DIOCDELETE ioctl. > > However, both of UFS and ZFS issue BIO_DELETE while freeing their fs > blocks, do they? > Yes. They do. You can't just open a file that's backed by ufs/zfs and issue the DIOCGDELETE ioctl. ZFS devices, though, do honor it. Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfp26rZvU9f7mgbUvwNwGdkDhoeF_FPCXRiJ2vVJq4U4OA>