| 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
| ||
|
Date: Thu, 29 May 2008 12:08:15 -0400 From: Rik van Riel <riel@...hat.com> To: Alan Cox <alan@...rguk.ukuu.org.uk> Cc: "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, 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... This means that once the disk is full it will stay full, no matter how many files are deleted in the guest filesystems. Overcommitting an unfreeable resource is a bad idea. -- All rights reversed. -- 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