| 1 |
Joost Roeleveld wrote: |
| 2 |
> On Thursday, November 17, 2011 10:43:28 AM Florian Philipp wrote: |
| 3 |
>> Am 17.11.2011 07:50, schrieb Dale: |
| 4 |
>> [...] |
| 5 |
>> |
| 6 |
>>> One more question. I have two drives. A 250Gb and a 750Gb. Originally |
| 7 |
>>> the data was on the 750Gb drive. I set the 250Gb up on LVM then moved |
| 8 |
>>> things over from the 750Gb. I then added the 750Gb to the VG and |
| 9 |
>>> resized the file system. So, in theory the data is on the 250Gb drive. |
| 10 |
>>> Let's say I want to remove the 250Gb drive. I would use pvmove to do |
| 11 |
>>> that right? When I ran pvmove /dev/sdb, which is the 250Gb drive, then |
| 12 |
>>> it would remove all the data from that drive so that it could be |
| 13 |
>>> removed. Am I close? |
| 14 |
>>> |
| 15 |
>>> I'm not planning to do that but just wanting to get a better |
| 16 |
>>> understanding of this LVM thing. |
| 17 |
>>> |
| 18 |
>>> Dale |
| 19 |
>> Yes, that is correct. It moves the data by mirroring it temporarily on |
| 20 |
>> the new location before updating the metadata so that only the new |
| 21 |
>> location is used. Therefore you can safely reboot or abort operations. |
| 22 |
> Also, this will only work if the VG has sufficient unused space (eg. not used |
| 23 |
> by LVs) on the other disk(s) to accomodate the data moved. |
| 24 |
> |
| 25 |
> -- |
| 26 |
> Joost |
| 27 |
> |
| 28 |
> |
| 29 |
|
| 30 |
|
| 31 |
Thanks. Clear as mud now. lol I'm getting there. Is there a tool to |
| 32 |
see if there is enough room to do this before trying it? |
| 33 |
|
| 34 |
Curious about gkrellm and how it will see the new drives now. May be |
| 35 |
interesting. |
| 36 |
|
| 37 |
Dale |
| 38 |
|
| 39 |
:-) :-) |
| 40 |
|
| 41 |
-- |
| 42 |
I am only responsible for what I said ... Not for what you understood or how you interpreted my words! |
Archives