From: Christoph Hellwig <hch@infradead.org>
To: Rik van Riel <riel@redhat.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Xiaoming Li <forrubm2@gmail.com>,
linux-kernel@vger.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?
Date: Fri, 30 May 2008 03:31:49 -0400 [thread overview]
Message-ID: <20080530073149.GA7758@infradead.org> (raw)
In-Reply-To: <20080529230441.GB5134@disturbed>
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.
next prev parent reply other threads:[~2008-05-30 7:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-29 9:12 [help]How to block new write in a "Thin Provisioning" logical volume manager as a virtual device driver when physical spaces run out? Xiaoming Li
2008-05-29 10:31 ` Alan Cox
2008-05-29 16:08 ` Rik van Riel
2008-05-29 23:04 ` Dave Chinner
2008-05-30 7:31 ` Christoph Hellwig [this message]
2008-06-02 17:22 ` Xiaoming Li
2008-06-02 19:41 ` Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080530073149.GA7758@infradead.org \
--to=hch@infradead.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=forrubm2@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.