linux-kernel - Re: [RFC] LVM/RAID/FS integration

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] [day] [month] [year] [list]

Date:	Mon, 09 Jul 2007 14:09:46 -0400
From:	Phillip Susi <psusi@....rr.com>
To:	Kent Overstreet <kent.overstreet@...il.com>
CC:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [RFC] LVM/RAID/FS integration

Kent Overstreet wrote:
> The trouble is it's completely impractical with current tools; we need
> tighter integration between md and LVM. Basically, we need a new type
> of VG; you'd only be able to make it out of PVs that are the same size
> (or close). Then, when you create an LV you decide what kind of
> redundancy you want; the LVM internally creates multiple LVs and raids
> them together to make the LV the fs sees.

In theory LVM is meant to handle the raid bits as well, once the mirror 
target is improved to properly handle error correction, and the raid5 
target stabilizes.  Thus md won't be needed, you will just need an 
interface between the filesystem and lvm.

> This could, sort of, be done in userspace, but I think it'll work
> better if dm and md are better integrated in the kernel. I thought i'd
> throw out my ideas before I get too far in. Thoughts?

This is the kind of thing that should go in userspace.  The filesystem 
should just fire off events that tell a userspace daemon things like 
"the raid5 volume is now at x% use" and let it choose the policy, 
possibly by asking lvm to resize the underlying volume, then sending a 
message back to the fs that the volume has been resized, and it can 
start using the extra space.

-
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/