One other thing: I read that btrfs has some options that are turned off for SSDs as they might be harmful or so. In my case btrfs, however, would not know about the SSD and probably use its HDD optimized settings. The result, however, would be forwared also to the SSD via lvmcache. Do I see that right? Would that give any serious problems? Am 23.12.2015 um 11:45 schrieb Neuer User: > Hello > > I want to setup a small homeserver, based on a HP Microserver Gen8 (4GB > RAM, 2x3TB HDD + 1x120GB SSD) and Proxmox as distro. > > The server will be used to host a (small) number of virtual machines, > most of them being LXC containers, few being KVM machines. One of the > LXC containers will host a fileserver with app 1 TB of data and another > one a backup system for the desktops / laptops in my household, thus > probably holding quite a lot of files. The lxc containers will use the > filesystem of the proxmox host, the KVM machines probably raw disk files > (or qcow2). > > I would like to combine high data integrity with some speed, so I > thought of the following layout: > > - both hdd and ssd in one LVM VG > - one LV on each hdd, containing a btrfs filesystem > - both btrfs LV configured as RAID1 > - the single SDD used as a LVM cache device for both HDD LVs to speed up > random access, where possible > > Now, I wonder if that is a good architecture to go for. Any input on > that? Is btrfs the right way to go for, or should I better go for ZFS > (and purchase some more gigs of RAM)? > > Will there be any problems arising from the lvmcache? btrfs only sees > the HDDs, LVM does the SDD handling. > > Thanks for any input. I like btrfs very much, but data integrity is > important for this. > > Michael > > > -- > To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
