1 |
Manuel McLure wrote: |
2 |
> You should be able to use e2label (or "tune2fs -L" as I do) on the |
3 |
> /dev/data/data1 device to set the filesystem label. That's the logical |
4 |
> volume that the operating system needs to mount. # tune2fs -L mylabel |
5 |
> /dev/data/data1 should do what you need. I haven't done this with |
6 |
> ext4, but I have used LVM with ext2, ext3 and labels in this fashion. |
7 |
|
8 |
That is the problem. I was using e2label and got a error. tune2fs |
9 |
worked fine. I get this now: |
10 |
|
11 |
root@fireball / # blkid /dev/mapper/data-data1 |
12 |
/dev/mapper/data-data1: UUID="7500437d-700c-4836-a878-29507af67a8d" |
13 |
TYPE="ext4" LABEL="data" |
14 |
root@fireball / # |
15 |
|
16 |
Sort of hard to believe I got this far with LVM tho. I got some space now. |
17 |
|
18 |
/dev/mapper/data-data1 960906608 255981512 656122832 29% /data |
19 |
|
20 |
Now I can download some more of my TV shows. |
21 |
|
22 |
One more question. I have two drives. A 250Gb and a 750Gb. Originally |
23 |
the data was on the 750Gb drive. I set the 250Gb up on LVM then moved |
24 |
things over from the 750Gb. I then added the 750Gb to the VG and |
25 |
resized the file system. So, in theory the data is on the 250Gb drive. |
26 |
Let's say I want to remove the 250Gb drive. I would use pvmove to do |
27 |
that right? When I ran pvmove /dev/sdb, which is the 250Gb drive, then |
28 |
it would remove all the data from that drive so that it could be |
29 |
removed. Am I close? |
30 |
|
31 |
I'm not planning to do that but just wanting to get a better |
32 |
understanding of this LVM thing. |
33 |
|
34 |
Dale |
35 |
|
36 |
:-) :-) |
37 |
|
38 |
-- |
39 |
I am only responsible for what I said ... Not for what you understood or how you interpreted my words! |