On Mon, Jun 26, 2017 at 8:14 PM, FERNANDO FREDIANI <fernando.frediani@xxxxxxx> wrote: > Well, just a bit more detail of my scenario. This 8TB is a Linux RAID 10 on > the top of 4 x 4TB disks, therefore the filesystem is currently mounted in a > /dev/md124 which is a ext4. The physical disks in turn have each a single > partition with type "Linux RAID" and they apparently start on sector 2048 > (see below on of these disks): > > Disk /dev/sdd: 4000.8 GB, 4000787030016 bytes, 7814037168 sectors > Units = sectors of 1 * 512 = 512 bytes > Sector size (logical/physical): 512 bytes / 512 bytes > I/O size (minimum/optimal): 512 bytes / 512 bytes > Disk label type: gpt > # Start End Size Type Name > 1 2048 7814037134 3.7T Linux RAID OK, setup is clear. I am only using this stack (w.r.t. backing device): harddisk(gpt partitioned) - bcache - luks - btrfs. That layering for 1 HDD + 1 SSD, but also for 1 SSD + 4 HDD using btrfs raid10. I wanted to use btrfs multi-device/raid feature, so that is one reason why I prefer bcache directly on top of partition. So for the btrfs raid10 situation, I have 4 bcache devices. But if you use MD, you could choose to put bcache on top of MD. There is someone on the list who uses bcache on top of MD RAID5 AFAIR. I think I would choose to add bcache to each of the four harddisks, primarily because I am not familiar enough now with Linux multiple devices tooling, only how it was 10 years back. I would definitely need to study, trial-run, etc it first. gdisk and dd are relatively simple and static w.r.t changes, so that is what I have been usiing to add and remove bcache. But maybe you feel comfortable enough with changing things just above or below the MD layer and is it the same accaptable risk. -- To unsubscribe from this list: send the line "unsubscribe linux-bcache" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
