On Sun, 14 Jul 2013, Craig Sanders wrote:
On Sun, Jul 14, 2013 at 12:15:59PM +1000, Jeremy Visser wrote:
On 14/07/13 01:53, Craig Sanders wrote:
and, unlike lvm, with both btrfs and zfs, once you've created the pool you don't need to remember or specify the device names of the disks in the pool unless you're replacing one of them
Can you clarify what you mean by this?
My volume group is /dev/vg_glimfeather. I haven?t interacted with the raw PV, /dev/sda6, in over a year.
here's an example from the lvextend man page:
Extends the size of the logical volume "vg01/lvol10" by 54MiB on physi- cal volume /dev/sdk3. This is only possible if /dev/sdk3 is a member of volume group vg01 and there are enough free physical extents in it:
lvextend -L +54 /dev/vg01/lvol10 /dev/sdk3
Yes, but why would you do that instead of just letting lvm pick where to put its extents? If I add a disk in lvm or zfs, I have to either zfs add tank <dev-id> (or is it zpool?) or vgextend <vg> <dev-node>. Same difference. In both cases, I have to read the manpage to remember quite how to use it.
and another from lvresize:
Extend a logical volume vg1/lv1 by 16MB using physical extents /dev/sda:0-1 and /dev/sdb:0-1 for allocation of extents:
lvresize -L+16M vg1/lv1 /dev/sda:0-1 /dev/sdb:0-1
Wow, damn. Maybe the manpage is deficient, or maybe you're reading the wrong section. It's *definitely* not that complicated. Just cargo cult off the net like everyone else! -- Tim Connors