| 1 |
On 12/14/18 7:57 AM, Rich Freeman wrote: |
| 2 |
> Yes. At least by default LVM is going to scan all your drives looking |
| 3 |
> for LVM PVs and will identify them regardless of what device they are on, |
| 4 |
> as long as the device gets scanned. |
| 5 |
|
| 6 |
I wouldn't be surprised if LVM didn't scan all block devices. |
| 7 |
|
| 8 |
I think LVM always looks for /dev/sd* and /dev/hd* by default. (At |
| 9 |
least all the times I've used it.) |
| 10 |
|
| 11 |
I can't say the same for things like /dev/mpath* or other more |
| 12 |
intriguing block devices. |
| 13 |
|
| 14 |
> Yes, in general. The only time you might have an issue is if you use |
| 15 |
> something more exotic that creates a block device that might not get |
| 16 |
> scanned by default, but I believe that is just a configuration fix. |
| 17 |
> So, if you're using iSCSI or something maybe you might need to do a |
| 18 |
> little work. |
| 19 |
|
| 20 |
Yes, there should be an entry of devices to scan and an entry of black |
| 21 |
listed devices. I think this is in /etc/lvm.conf or something like |
| 22 |
that. (It's been a number of years since I've changed it.) |
| 23 |
|
| 24 |
Bog standard PCs shouldn't need to worry about this. Servers or things |
| 25 |
with more exotic storage may have a problem in that the default might |
| 26 |
not work for them. |
| 27 |
|
| 28 |
ProTip: Be careful if you are using LVM on multipath devices. You want |
| 29 |
to make sure that LVM is scanning the multipath device and not the |
| 30 |
member path devices. LVM will happily use the first one that it finds. |
| 31 |
So scan order and / or black listing is important. |
Archives