| 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 11:31:59 +0100 From: Alan Cox <alan@...rguk.ukuu.org.uk> To: "Xiaoming Li" <forrubm2@...il.com> Cc: 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? > As a result, with LVM, you can never export a "logical volume" with > claimed storage space larger than of the underlying physical storage > devices (e.g. SATA disks, Hardware RAID array etc.); but with ASD, you > can export "logical volumes" which have much larger logical storage > space. Why do that ? > 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. Alternatively mount the clustered file system somewhere on each node and then remount the subdirectory into the right place in the file tree (And for a clustered/shared pool root you can use pivot_root() to start from initrd or local disk and then switch to running entirely within the clusterfs) Alan -- 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