| 1 |
On Wed, 29 Feb 2012 01:10:05 -0600 |
| 2 |
Dale <rdalek1967@×××××.com> wrote: |
| 3 |
|
| 4 |
> Neil Bothwick wrote: |
| 5 |
> > On Tue, 28 Feb 2012 20:38:13 -0600, Dale wrote: |
| 6 |
> > |
| 7 |
> >> tune2fs -m 1 /dev/data/data1 |
| 8 |
> >> |
| 9 |
> >> Which is where the ext4 file system is on the LVM. After I run |
| 10 |
> >> that then I can expand LVM from there, I hope it works that easy. |
| 11 |
> > |
| 12 |
> > It does. |
| 13 |
> > |
| 14 |
> > |
| 15 |
> |
| 16 |
> |
| 17 |
> Apparently I am missing something then. I looked at cfdisk for the |
| 18 |
> drive. It reported right at 750Gb as it should with the change. |
| 19 |
> Thing is, I can't get anything else to add it or to even show it is |
| 20 |
> available. Some results somewhat shortened: |
| 21 |
> |
| 22 |
> From cfdisk |
| 23 |
> |
| 24 |
> 750156.38Mb |
| 25 |
> |
| 26 |
> root@fireball / # pvs |
| 27 |
> PV VG Fmt Attr PSize PFree |
| 28 |
> /dev/sdc1 data lvm2 a-- 698.63g 0 |
| 29 |
> root@fireball / # vgs |
| 30 |
> VG #PV #LV #SN Attr VSize VFree |
| 31 |
> data 1 1 0 wz--n- 698.63g 0 |
| 32 |
> root@fireball / # lvs |
| 33 |
> LV VG Attr LSize Origin Snap% Move Log Copy% Convert |
| 34 |
> data1 data -wi-ao 698.63g |
| 35 |
> root@fireball / # |
| 36 |
> |
| 37 |
> |
| 38 |
> So, cfdisk is happy with the change but nothing else seems to see it. |
| 39 |
> What am I missing here? Where did the 50Gbs go to? |
| 40 |
> |
| 41 |
> Dale |
| 42 |
> |
| 43 |
> :-) :-) |
| 44 |
> |
| 45 |
|
| 46 |
Nowhere. |
| 47 |
|
| 48 |
Disk manufacturers measure kilos of data as 1000 |
| 49 |
Everyone else measures it in 1024 |
| 50 |
|
| 51 |
They do this because it fudges disk sizes to appear 2.4% bigger than |
| 52 |
they really are. |
| 53 |
|
| 54 |
When you get into TB drives, it gets worse as 1024*1024*1024*1024 |
| 55 |
differs from 1000*1000*1000*1000 bu a lot more than 2.4% |
| 56 |
|
| 57 |
-- |
| 58 |
Alan McKinnnon |
| 59 |
alan.mckinnon@×××××.com |
Archives