Hello,
The way I "guess" it, a zpool consisting of multiple vdevs acts like a raid-0 of these vdevs. In raid-0, data is segmented into blocks of some size, which are then distributed over the disks (i.e. vdevs) in a sequential way. So, the questions that arise to me are:
Alonso
The way I "guess" it, a zpool consisting of multiple vdevs acts like a raid-0 of these vdevs. In raid-0, data is segmented into blocks of some size, which are then distributed over the disks (i.e. vdevs) in a sequential way. So, the questions that arise to me are:
- Does this apply to zpools, too, or will an entire file (independent of size) get onto one vdev, and then the next file go to the next vdev and so on?
- If spreading happens by files and not blocks, how are Inodes spread?
- When another vdev is added to a zpool that already contains data, will only future allocations be distributed, or will a redistribution take place when the new devices are added?
- If a redistribution does not take place, is there a way to force it (other then backup+replay)?
Alonso