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 09:04:41 +1000
From:	Dave Chinner <david@...morbit.com>
To:	Rik van Riel <riel@...hat.com>
Cc:	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 Thu, May 29, 2008 at 12:08:15PM -0400, Rik van Riel wrote:
> On Thu, 29 May 2008 11:31:59 +0100
> Alan Cox <alan@...rguk.ukuu.org.uk> wrote:
> 
> > > Does anyone have some ideas for a better solution?
> > 
> > Take one file system such as ext3, or even a cluster file system like
> > GFS2 or OCFS. Create top level subdirectories in it for each machine.
> > Either export the subdirectory via NFS.
> 
> Xiaoming, let me point out another advantage of Alan's approach.
> 
> 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.

See here:

http://marc.info/?l=linux-fsdevel&m=119370585902974&w=2

Alternatively, forget about block based thin provisioning and
just use XFS directory quotas....

Cheers,

Dave.
-- 
Dave Chinner
david@...morbit.com
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ