linux-kernel - Re: [help]How to block new write in a "Thin Provisioning" logical volume manager as a virtual device driver when physical spaces run out?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 30 May 2008 03:31:49 -0400
From:	Christoph Hellwig <hch@...radead.org>
To:	Rik van Riel <riel@...hat.com>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Xiaoming Li <forrubm2@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: [help]How to block new write in a "Thin Provisioning" logical
	volume manager as a virtual device driver when physical spaces run
	out?

On Fri, May 30, 2008 at 09:04:41AM +1000, Dave Chinner wrote:
> > In a block based thin provisioning system, like you proposed, there
> > is no way to free up space.  Once a user's filesystem has written a
> > block, it is allocated - when the user deletes a file inside the
> > filesystem, the space will not be freed again...
> 
> That's where we've been discussing bio hints to help communicate
> space being allocated and freed by the filesystem to the lower layers.

Or use the XFS multiple subvolume support based on that:

http://verein.lst.de/~hch/xfs/xfs-multiple-containers.txt

and yeah, I really need to finish the lose bits up and actually post it.
Hopefully next month.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/