[linux-lvm] PFree is 0 on a drive with nothing on it

[linux-lvm] PFree is 0 on a drive with nothing on it

[Adam Mooz]

[-- Attachment #1: Type: text/plain, Size: 886 bytes --]

Hello List,

I have a fileserver that is driving me nuts at the moment.  Setup:
4x 1TB HDD's
1x 320GB HDD
They all have the same partition layout:
512MB Swap, rest is LVM data.
The LVM only contains ~400GB of data, but 2 of the TB drives report  
having 0 free PFree's:
   PV                   VG        Fmt  Attr PSize   PFree
   /dev/mapper/cryptsda fileshare lvm2 a-   931.03G      0
   /dev/mapper/cryptsdb fileshare lvm2 a-   931.03G      0
   /dev/mapper/cryptsdc fileshare lvm2 a-   297.61G 297.61G
   /dev/mapper/cryptsdd fileshare lvm2 a-   931.03G 633.42G
   /dev/mapper/cryptsde           lvm2 --   931.04G 931.04G

I've successfully managed to remove SDE from the LVM, but I need to  
move the data off SDD onto either SDA or SDB.  When the whole system  
is mounted it properly reports having 2.1TB of free space (931 * 2 +  
297). Is there an easy way to fix this issue?


[-- Attachment #2: Type: text/html, Size: 1644 bytes --]

Re: [linux-lvm] PFree is 0 on a drive with nothing on it

[Ray Morris]

What is the output of?:

pvdisplay -m /dev/mapper/cryptsda


--
Ray Morris
support@bettercgi.com

Strongbox - The next generation in site security:
http://www.bettercgi.com/strongbox/

Throttlebox - Intelligent Bandwidth Control
http://www.bettercgi.com/throttlebox/

Strongbox / Throttlebox affiliate program:
http://www.bettercgi.com/affiliates/user/register.php


On 11/05/2009 01:57:53 AM, Adam Mooz wrote:
> Hello List,
> 
> I have a fileserver that is driving me nuts at the moment.  Setup:
> 4x 1TB HDD's
> 1x 320GB HDD
> They all have the same partition layout:
> 512MB Swap, rest is LVM data.
> The LVM only contains ~400GB of data, but 2 of the TB drives report  
> having 0 free PFree's:
>   PV                   VG        Fmt  Attr PSize   PFree
>   /dev/mapper/cryptsda fileshare lvm2 a-   931.03G      0
>   /dev/mapper/cryptsdb fileshare lvm2 a-   931.03G      0
>   /dev/mapper/cryptsdc fileshare lvm2 a-   297.61G 297.61G
>   /dev/mapper/cryptsdd fileshare lvm2 a-   931.03G 633.42G
>   /dev/mapper/cryptsde           lvm2 --   931.04G 931.04G
> 
> I've successfully managed to remove SDE from the LVM, but I need to  
> move the data off SDD onto either SDA or SDB.  When the whole system  
> is mounted it properly reports having 2.1TB of free space (931 * 2 +  
> 297). Is there an easy way to fix this issue?
> 

------quoted attachment------
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

Re: [linux-lvm] PFree is 0 on a drive with nothing on it

[Adam Mooz]

[-- Attachment #1: Type: text/plain, Size: 3108 bytes --]

Here it is for both SDA and SDB:

#pvdisplay -m /dev/mapper/cryptsda
File descriptor 4 left open
   --- Physical volume ---
   PV Name               /dev/mapper/cryptsda
   VG Name               fileshare
   PV Size               931.04 GB / not usable 3.87 MB
   Allocatable           yes (but full)
   PE Size (KByte)       4096
   Total PE              238344
   Free PE               0
   Allocated PE          238344
   PV UUID               6OfRxC-R59i-CVjX-igtB-pg4e-2qAw-OdiPSc

   --- Physical Segments ---
   Physical extent 0 to 238343:
     Logical volume	/dev/fileshare/lv_fileshare
     Logical extents	0 to 238343

#pvdisplay -m /dev/mapper/cryptsdb
File descriptor 4 left open
   --- Physical volume ---
   PV Name               /dev/mapper/cryptsdb
   VG Name               fileshare
   PV Size               931.04 GB / not usable 3.87 MB
   Allocatable           yes (but full)
   PE Size (KByte)       4096
   Total PE              238344
   Free PE               0
   Allocated PE          238344
   PV UUID               zCLder-PF5b-fQpy-RdMS-Ayc0-caWh-LA2Esm

   --- Physical Segments ---
   Physical extent 0 to 238343:
     Logical volume	/dev/fileshare/lv_fileshare
     Logical extents	238344 to 476687



On 2009-11-05, at 10:10 AM, Ray Morris wrote:

> What is the output of?:
>
> pvdisplay -m /dev/mapper/cryptsda
>
>
> --
> Ray Morris
> support@bettercgi.com
>
> Strongbox - The next generation in site security:
> http://www.bettercgi.com/strongbox/
>
> Throttlebox - Intelligent Bandwidth Control
> http://www.bettercgi.com/throttlebox/
>
> Strongbox / Throttlebox affiliate program:
> http://www.bettercgi.com/affiliates/user/register.php
>
>
> On 11/05/2009 01:57:53 AM, Adam Mooz wrote:
>> Hello List,
>> I have a fileserver that is driving me nuts at the moment.  Setup:
>> 4x 1TB HDD's
>> 1x 320GB HDD
>> They all have the same partition layout:
>> 512MB Swap, rest is LVM data.
>> The LVM only contains ~400GB of data, but 2 of the TB drives report  
>> having 0 free PFree's:
>>  PV                   VG        Fmt  Attr PSize   PFree
>>  /dev/mapper/cryptsda fileshare lvm2 a-   931.03G      0
>>  /dev/mapper/cryptsdb fileshare lvm2 a-   931.03G      0
>>  /dev/mapper/cryptsdc fileshare lvm2 a-   297.61G 297.61G
>>  /dev/mapper/cryptsdd fileshare lvm2 a-   931.03G 633.42G
>>  /dev/mapper/cryptsde           lvm2 --   931.04G 931.04G
>> I've successfully managed to remove SDE from the LVM, but I need to  
>> move the data off SDD onto either SDA or SDB.  When the whole  
>> system is mounted it properly reports having 2.1TB of free space  
>> (931 * 2 + 297). Is there an easy way to fix this issue?
>
> ------quoted attachment------
>> _______________________________________________
>> linux-lvm mailing list
>> linux-lvm@redhat.com
>> https://www.redhat.com/mailman/listinfo/linux-lvm
>> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/


[-- Attachment #2: Type: text/html, Size: 11277 bytes --]

Re: [linux-lvm] PFree is 0 on a drive with nothing on it

[Ray Morris]

>   --- Physical Segments ---
>   Physical extent 0 to 238343:
>     Logical volume	/dev/fileshare/lv_fileshare
>     Logical extents	0 to 238343


   OK according to that both are full of an LV
called "lv_fileshare".  Try mounting that and
see what, if anything, is on it.  Don't remember
creating that?  Try history | grep -10 lv_fileshare
for a reminder.
--
Ray Morris
support@bettercgi.com

Strongbox - The next generation in site security:
http://www.bettercgi.com/strongbox/

Throttlebox - Intelligent Bandwidth Control
http://www.bettercgi.com/throttlebox/

Strongbox / Throttlebox affiliate program:
http://www.bettercgi.com/affiliates/user/register.php


On 11/05/2009 09:36:35 AM, Adam Mooz wrote:
> Here it is for both SDA and SDB:
> 
> #pvdisplay -m /dev/mapper/cryptsda
> File descriptor 4 left open
>   --- Physical volume ---
>   PV Name               /dev/mapper/cryptsda
>   VG Name               fileshare
>   PV Size               931.04 GB / not usable 3.87 MB
>   Allocatable           yes (but full)
>   PE Size (KByte)       4096
>   Total PE              238344
>   Free PE               0
>   Allocated PE          238344
>   PV UUID               6OfRxC-R59i-CVjX-igtB-pg4e-2qAw-OdiPSc
> 
>   --- Physical Segments ---
>   Physical extent 0 to 238343:
>     Logical volume	/dev/fileshare/lv_fileshare
>     Logical extents	0 to 238343
> 
> #pvdisplay -m /dev/mapper/cryptsdb
> File descriptor 4 left open
>   --- Physical volume ---
>   PV Name               /dev/mapper/cryptsdb
>   VG Name               fileshare
>   PV Size               931.04 GB / not usable 3.87 MB
>   Allocatable           yes (but full)
>   PE Size (KByte)       4096
>   Total PE              238344
>   Free PE               0
>   Allocated PE          238344
>   PV UUID               zCLder-PF5b-fQpy-RdMS-Ayc0-caWh-LA2Esm
> 
>   --- Physical Segments ---
>   Physical extent 0 to 238343:
>     Logical volume	/dev/fileshare/lv_fileshare
>     Logical extents	238344 to 476687
> 
> 
> 
> On 2009-11-05, at 10:10 AM, Ray Morris wrote:
> 
>> What is the output of?:
>> 
>> pvdisplay -m /dev/mapper/cryptsda
>> 
>> 
>> --
>> Ray Morris
>> support@bettercgi.com
>> 
>> Strongbox - The next generation in site security:
>> http://www.bettercgi.com/strongbox/
>> 
>> Throttlebox - Intelligent Bandwidth Control
>> http://www.bettercgi.com/throttlebox/
>> 
>> Strongbox / Throttlebox affiliate program:
>> http://www.bettercgi.com/affiliates/user/register.php
>> 
>> 
>> On 11/05/2009 01:57:53 AM, Adam Mooz wrote:
>>> Hello List,
>>> I have a fileserver that is driving me nuts at the moment.  Setup:
>>> 4x 1TB HDD's
>>> 1x 320GB HDD
>>> They all have the same partition layout:
>>> 512MB Swap, rest is LVM data.
>>> The LVM only contains ~400GB of data, but 2 of the TB drives report  
>>> having 0 free PFree's:
>>>  PV                   VG        Fmt  Attr PSize   PFree
>>>  /dev/mapper/cryptsda fileshare lvm2 a-   931.03G      0
>>>  /dev/mapper/cryptsdb fileshare lvm2 a-   931.03G      0
>>>  /dev/mapper/cryptsdc fileshare lvm2 a-   297.61G 297.61G
>>>  /dev/mapper/cryptsdd fileshare lvm2 a-   931.03G 633.42G
>>>  /dev/mapper/cryptsde           lvm2 --   931.04G 931.04G
>>> I've successfully managed to remove SDE from the LVM, but I need to  
>>> move the data off SDD onto either SDA or SDB.  When the whole  
>>> system is mounted it properly reports having 2.1TB of free space  
>>> (931 * 2 + 297). Is there an easy way to fix this issue?
>> 
>> ------quoted attachment------
>>> _______________________________________________
>>> linux-lvm mailing list
>>> linux-lvm@redhat.com
>>> https://www.redhat.com/mailman/listinfo/linux-lvm
>>> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>> 
>> 
>> _______________________________________________
>> linux-lvm mailing list
>> linux-lvm@redhat.com
>> https://www.redhat.com/mailman/listinfo/linux-lvm
>> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
> 

------quoted attachment------
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

Re: [linux-lvm] PFree is 0 on a drive with nothing on it

[Adam Mooz]

That is correct.  All drives are part of 'fileshare/lv_fileshare',  
which only has 400GB of data on it at the moment; which I can see  
reflected in the PFREE columns of the PVS output.  Is there an easy  
way to force the LVM to rescan it's allocation unit or would I have to  
remove the drives and re-insert them into the LVM?


On 2009-11-05, at 10:55 AM, Ray Morris wrote:

>>  --- Physical Segments ---
>>  Physical extent 0 to 238343:
>>    Logical volume	/dev/fileshare/lv_fileshare
>>    Logical extents	0 to 238343
>
>
>  OK according to that both are full of an LV
> called "lv_fileshare".  Try mounting that and
> see what, if anything, is on it.  Don't remember
> creating that?  Try history | grep -10 lv_fileshare
> for a reminder.
> --
> Ray Morris
> support@bettercgi.com
>
> Strongbox - The next generation in site security:
> http://www.bettercgi.com/strongbox/
>
> Throttlebox - Intelligent Bandwidth Control
> http://www.bettercgi.com/throttlebox/
>
> Strongbox / Throttlebox affiliate program:
> http://www.bettercgi.com/affiliates/user/register.php
>
>
> On 11/05/2009 09:36:35 AM, Adam Mooz wrote:
>> Here it is for both SDA and SDB:
>> #pvdisplay -m /dev/mapper/cryptsda
>> File descriptor 4 left open
>>  --- Physical volume ---
>>  PV Name               /dev/mapper/cryptsda
>>  VG Name               fileshare
>>  PV Size               931.04 GB / not usable 3.87 MB
>>  Allocatable           yes (but full)
>>  PE Size (KByte)       4096
>>  Total PE              238344
>>  Free PE               0
>>  Allocated PE          238344
>>  PV UUID               6OfRxC-R59i-CVjX-igtB-pg4e-2qAw-OdiPSc
>>  --- Physical Segments ---
>>  Physical extent 0 to 238343:
>>    Logical volume	/dev/fileshare/lv_fileshare
>>    Logical extents	0 to 238343
>> #pvdisplay -m /dev/mapper/cryptsdb
>> File descriptor 4 left open
>>  --- Physical volume ---
>>  PV Name               /dev/mapper/cryptsdb
>>  VG Name               fileshare
>>  PV Size               931.04 GB / not usable 3.87 MB
>>  Allocatable           yes (but full)
>>  PE Size (KByte)       4096
>>  Total PE              238344
>>  Free PE               0
>>  Allocated PE          238344
>>  PV UUID               zCLder-PF5b-fQpy-RdMS-Ayc0-caWh-LA2Esm
>>  --- Physical Segments ---
>>  Physical extent 0 to 238343:
>>    Logical volume	/dev/fileshare/lv_fileshare
>>    Logical extents	238344 to 476687
>> On 2009-11-05, at 10:10 AM, Ray Morris wrote:
>>> What is the output of?:
>>> pvdisplay -m /dev/mapper/cryptsda
>>> --
>>> Ray Morris
>>> support@bettercgi.com
>>> Strongbox - The next generation in site security:
>>> http://www.bettercgi.com/strongbox/
>>> Throttlebox - Intelligent Bandwidth Control
>>> http://www.bettercgi.com/throttlebox/
>>> Strongbox / Throttlebox affiliate program:
>>> http://www.bettercgi.com/affiliates/user/register.php
>>> On 11/05/2009 01:57:53 AM, Adam Mooz wrote:
>>>> Hello List,
>>>> I have a fileserver that is driving me nuts at the moment.  Setup:
>>>> 4x 1TB HDD's
>>>> 1x 320GB HDD
>>>> They all have the same partition layout:
>>>> 512MB Swap, rest is LVM data.
>>>> The LVM only contains ~400GB of data, but 2 of the TB drives  
>>>> report having 0 free PFree's:
>>>> PV                   VG        Fmt  Attr PSize   PFree
>>>> /dev/mapper/cryptsda fileshare lvm2 a-   931.03G      0
>>>> /dev/mapper/cryptsdb fileshare lvm2 a-   931.03G      0
>>>> /dev/mapper/cryptsdc fileshare lvm2 a-   297.61G 297.61G
>>>> /dev/mapper/cryptsdd fileshare lvm2 a-   931.03G 633.42G
>>>> /dev/mapper/cryptsde           lvm2 --   931.04G 931.04G
>>>> I've successfully managed to remove SDE from the LVM, but I need  
>>>> to move the data off SDD onto either SDA or SDB.  When the whole  
>>>> system is mounted it properly reports having 2.1TB of free space  
>>>> (931 * 2 + 297). Is there an easy way to fix this issue?
>>> ------quoted attachment------
>>>> _______________________________________________
>>>> linux-lvm mailing list
>>>> linux-lvm@redhat.com
>>>> https://www.redhat.com/mailman/listinfo/linux-lvm
>>>> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>>> _______________________________________________
>>> linux-lvm mailing list
>>> linux-lvm@redhat.com
>>> https://www.redhat.com/mailman/listinfo/linux-lvm
>>> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>
> ------quoted attachment------
>> _______________________________________________
>> linux-lvm mailing list
>> linux-lvm@redhat.com
>> https://www.redhat.com/mailman/listinfo/linux-lvm
>> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

Re: [linux-lvm] PFree is 0 on a drive with nothing on it

[Ray Morris]

> All drives are part of 'fileshare/lv_fileshare',
> which only has 400GB of data on it at the moment;

    The FILESYSTEM which you built in lv_fileshare
has 400GB of data in a 2TB filesystem, probably.
The lv_fileshare LV itself is around 2TB, so it won't
fit on a 1TB drive.  You would need to first reduce
the size of the filesystem, using resize2fs or similar,
then reduce the size of the LV using lvreduce, then
move it using pvmove.

   A tip - reduce the filesystem 10%-20% smaller than
the LV will be on - making it about 800GB, to make sure
it will fit on a 1000GB volume.  A 1000GB filesystem
won'yt necesarily fit on a 1000GB volume because of
rounding, GB versus GiB, etc.  After resizing the LV,
you can resize2fs it to fill the volume.
--
Ray Morris
support@bettercgi.com

Strongbox - The next generation in site security:
http://www.bettercgi.com/strongbox/

Throttlebox - Intelligent Bandwidth Control
http://www.bettercgi.com/throttlebox/

Strongbox / Throttlebox affiliate program:
http://www.bettercgi.com/affiliates/user/register.php


On 11/05/2009 12:57:24 PM, Adam Mooz wrote:
> That is correct.  All drives are part of 'fileshare/lv_fileshare',  
> which only has 400GB of data on it at the moment; which I can see  
> reflected in the PFREE columns of the PVS output.  Is there an easy  
> way to force the LVM to rescan it's allocation unit or would I have  
> to remove the drives and re-insert them into the LVM?
> 
> 
> On 2009-11-05, at 10:55 AM, Ray Morris wrote:
> 
>>>  --- Physical Segments ---
>>>  Physical extent 0 to 238343:
>>>    Logical volume	/dev/fileshare/lv_fileshare
>>>    Logical extents	0 to 238343
>> 
>> 
>>  OK according to that both are full of an LV
>> called "lv_fileshare".  Try mounting that and
>> see what, if anything, is on it.  Don't remember
>> creating that?  Try history | grep -10 lv_fileshare
>> for a reminder.
>> --
>> Ray Morris
>> support@bettercgi.com
>> 
>> Strongbox - The next generation in site security:
>> http://www.bettercgi.com/strongbox/
>> 
>> Throttlebox - Intelligent Bandwidth Control
>> http://www.bettercgi.com/throttlebox/
>> 
>> Strongbox / Throttlebox affiliate program:
>> http://www.bettercgi.com/affiliates/user/register.php
>> 
>> 
>> On 11/05/2009 09:36:35 AM, Adam Mooz wrote:
>>> Here it is for both SDA and SDB:
>>> #pvdisplay -m /dev/mapper/cryptsda
>>> File descriptor 4 left open
>>>  --- Physical volume ---
>>>  PV Name               /dev/mapper/cryptsda
>>>  VG Name               fileshare
>>>  PV Size               931.04 GB / not usable 3.87 MB
>>>  Allocatable           yes (but full)
>>>  PE Size (KByte)       4096
>>>  Total PE              238344
>>>  Free PE               0
>>>  Allocated PE          238344
>>>  PV UUID               6OfRxC-R59i-CVjX-igtB-pg4e-2qAw-OdiPSc
>>>  --- Physical Segments ---
>>>  Physical extent 0 to 238343:
>>>    Logical volume	/dev/fileshare/lv_fileshare
>>>    Logical extents	0 to 238343
>>> #pvdisplay -m /dev/mapper/cryptsdb
>>> File descriptor 4 left open
>>>  --- Physical volume ---
>>>  PV Name               /dev/mapper/cryptsdb
>>>  VG Name               fileshare
>>>  PV Size               931.04 GB / not usable 3.87 MB
>>>  Allocatable           yes (but full)
>>>  PE Size (KByte)       4096
>>>  Total PE              238344
>>>  Free PE               0
>>>  Allocated PE          238344
>>>  PV UUID               zCLder-PF5b-fQpy-RdMS-Ayc0-caWh-LA2Esm
>>>  --- Physical Segments ---
>>>  Physical extent 0 to 238343:
>>>    Logical volume	/dev/fileshare/lv_fileshare
>>>    Logical extents	238344 to 476687
>>> On 2009-11-05, at 10:10 AM, Ray Morris wrote:
>>>> What is the output of?:
>>>> pvdisplay -m /dev/mapper/cryptsda
>>>> --
>>>> Ray Morris
>>>> support@bettercgi.com
>>>> Strongbox - The next generation in site security:
>>>> http://www.bettercgi.com/strongbox/
>>>> Throttlebox - Intelligent Bandwidth Control
>>>> http://www.bettercgi.com/throttlebox/
>>>> Strongbox / Throttlebox affiliate program:
>>>> http://www.bettercgi.com/affiliates/user/register.php
>>>> On 11/05/2009 01:57:53 AM, Adam Mooz wrote:
>>>>> Hello List,
>>>>> I have a fileserver that is driving me nuts at the moment.  Setup:
>>>>> 4x 1TB HDD's
>>>>> 1x 320GB HDD
>>>>> They all have the same partition layout:
>>>>> 512MB Swap, rest is LVM data.
>>>>> The LVM only contains ~400GB of data, but 2 of the TB drives  
>>>>> report having 0 free PFree's:
>>>>> PV                   VG        Fmt  Attr PSize   PFree
>>>>> /dev/mapper/cryptsda fileshare lvm2 a-   931.03G      0
>>>>> /dev/mapper/cryptsdb fileshare lvm2 a-   931.03G      0
>>>>> /dev/mapper/cryptsdc fileshare lvm2 a-   297.61G 297.61G
>>>>> /dev/mapper/cryptsdd fileshare lvm2 a-   931.03G 633.42G
>>>>> /dev/mapper/cryptsde           lvm2 --   931.04G 931.04G
>>>>> I've successfully managed to remove SDE from the LVM, but I need  
>>>>> to move the data off SDD onto either SDA or SDB.  When the whole  
>>>>> system is mounted it properly reports having 2.1TB of free space  
>>>>> (931 * 2 + 297). Is there an easy way to fix this issue?
>>>> ------quoted attachment------
>>>>> _______________________________________________
>>>>> linux-lvm mailing list
>>>>> linux-lvm@redhat.com
>>>>> https://www.redhat.com/mailman/listinfo/linux-lvm
>>>>> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>>>> _______________________________________________
>>>> linux-lvm mailing list
>>>> linux-lvm@redhat.com
>>>> https://www.redhat.com/mailman/listinfo/linux-lvm
>>>> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>> 
>> ------quoted attachment------
>>> _______________________________________________
>>> linux-lvm mailing list
>>> linux-lvm@redhat.com
>>> https://www.redhat.com/mailman/listinfo/linux-lvm
>>> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>> 
>> 
>> _______________________________________________
>> linux-lvm mailing list
>> linux-lvm@redhat.com
>> https://www.redhat.com/mailman/listinfo/linux-lvm
>> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
> 

Re: [linux-lvm] PFree is 0 on a drive with nothing on it

[Stuart D. Gathman]

On Thu, 5 Nov 2009, Adam Mooz wrote:

> That is correct.  All drives are part of 'fileshare/lv_fileshare', which only
> has 400GB of data on it at the moment; which I can see reflected in the PFREE
> columns of the PVS output.  Is there an easy way to force the LVM to rescan
> it's allocation unit or would I have to remove the drives and re-insert them
> into the LVM?

It doesn't matter how much space is free in whatever filesystem you 
made on top of lv_fileshare.  The LVM extents are allocated to that 
LV.  LVM doesn't care what you do with the LV after that.  It certainly
doesn't know about all the dozens of different kinds of filesystems you 
might put on the LV.

You could shrink the filesystem, then lvreduce the LV and allocate the
LVM extents to something else.  With most filesystems, you have to
unmount before shrinking - but a few support online shrinking.  (Many more
support online growing.)  You didn't mention what filesystem.

LVM is a block device layer that abstracts block devices so that filesystems
and stuff above the LVM layer don't care about physical drive allocation.

Many of us like this abstraction.  I don't *want* LVM to know anything
about filesystems.  I even have my own database filesystem that can run
on top of an LV.  LVM *should* support things like mirroring
and ordering of block writes to multiple physical devices - but it should never
care about specific filesystems.

If you want an integrated LVM/filesystem, then you should look
at OpenSolaris and ZFS.  There are some advantages to this approach,
but it does mean that you have only one filesystem choice.

-- 
	      Stuart D. Gathman <stuart@bmsi.com>
    Business Management Systems Inc.  Phone: 703 591-0911 Fax: 703 591-6154
"Confutatis maledictis, flammis acribus addictis" - background song for
a Microsoft sponsored "Where do you want to go from here?" commercial.

Re: [linux-lvm] PFree is 0 on a drive with nothing on it

[malahal]

Stuart D. Gathman [stuart@bmsi.com] wrote:
> If you want an integrated LVM/filesystem, then you should look
> at OpenSolaris and ZFS.  There are some advantages to this approach,
> but it does mean that you have only one filesystem choice.

BTRFS is planning on doing similar things, in case you are not planning
on jumping to Solaris yet. Stuart is right, you will be restricted to a
single file system though.

Re: [linux-lvm] PFree is 0 on a drive with nothing on it

[Stuart D. Gathman]

On Thu, 5 Nov 2009, malahal@us.ibm.com wrote:

> Stuart D. Gathman [stuart@bmsi.com] wrote:
> > If you want an integrated LVM/filesystem, then you should look
> > at OpenSolaris and ZFS.  There are some advantages to this approach,
> > but it does mean that you have only one filesystem choice.
> 
> BTRFS is planning on doing similar things, in case you are not planning
> on jumping to Solaris yet. Stuart is right, you will be restricted to a
> single file system though.

Eventually, it might be possible to support arbitrary filesystems that
implement an API with operations like:

 o report extents that could be freed by an online resize
 o report extents that could be freed by an offline resize
 o online resize
 o offline resize

A filesystem could even return failure for resize operations, and the
filesystem aware LVM would then know it can't get free blocks from that
filesystem (which might result in an error message if it can't get them
from anywhere else either).

-- 
	      Stuart D. Gathman <stuart@bmsi.com>
    Business Management Systems Inc.  Phone: 703 591-0911 Fax: 703 591-6154
"Confutatis maledictis, flammis acribus addictis" - background song for
a Microsoft sponsored "Where do you want to go from here?" commercial.

Re: [linux-lvm] PFree is 0 on a drive with nothing on it

[Stuart D. Gathman]

On Thu, 5 Nov 2009, Adam Mooz wrote:

> That is correct.  All drives are part of 'fileshare/lv_fileshare', which only
> has 400GB of data on it at the moment; which I can see reflected in the PFREE
> columns of the PVS output.  Is there an easy way to force the LVM to rescan
> it's allocation unit or would I have to remove the drives and re-insert them
> into the LVM?

Think of LVM as a kind of local SAN.  LVs are "virtual disks".  You allocated
a 2TB virtual disk called /dev/fileshare/lv_fileshare.  Disk drives don't
know anything about filesystems that use them.

-- 
	      Stuart D. Gathman <stuart@bmsi.com>
    Business Management Systems Inc.  Phone: 703 591-0911 Fax: 703 591-6154
"Confutatis maledictis, flammis acribus addictis" - background song for
a Microsoft sponsored "Where do you want to go from here?" commercial.

Re: [linux-lvm] PFree is 0 on a drive with nothing on it

[Adam Mooz]

The problem has been resolved, although what the fix is I'm not sure.   
I resized the LV, ran a PVDISPLAY and SDA and SDB both suddenly had  
931GB of free extents, although I only reduced the LV by 1TB.   
Everything is working now, thanks everyone!


On 2009-11-05, at 2:16 PM, Ray Morris wrote:

>> All drives are part of 'fileshare/lv_fileshare',
>> which only has 400GB of data on it at the moment;
>
>   The FILESYSTEM which you built in lv_fileshare
> has 400GB of data in a 2TB filesystem, probably.
> The lv_fileshare LV itself is around 2TB, so it won't
> fit on a 1TB drive.  You would need to first reduce
> the size of the filesystem, using resize2fs or similar,
> then reduce the size of the LV using lvreduce, then
> move it using pvmove.
>
>  A tip - reduce the filesystem 10%-20% smaller than
> the LV will be on - making it about 800GB, to make sure
> it will fit on a 1000GB volume.  A 1000GB filesystem
> won'yt necesarily fit on a 1000GB volume because of
> rounding, GB versus GiB, etc.  After resizing the LV,
> you can resize2fs it to fill the volume.
> --
> Ray Morris
> support@bettercgi.com
>
> Strongbox - The next generation in site security:
> http://www.bettercgi.com/strongbox/
>
> Throttlebox - Intelligent Bandwidth Control
> http://www.bettercgi.com/throttlebox/
>
> Strongbox / Throttlebox affiliate program:
> http://www.bettercgi.com/affiliates/user/register.php
>
>
> On 11/05/2009 12:57:24 PM, Adam Mooz wrote:
>> That is correct.  All drives are part of 'fileshare/lv_fileshare',  
>> which only has 400GB of data on it at the moment; which I can see  
>> reflected in the PFREE columns of the PVS output.  Is there an easy  
>> way to force the LVM to rescan it's allocation unit or would I have  
>> to remove the drives and re-insert them into the LVM?
>> On 2009-11-05, at 10:55 AM, Ray Morris wrote:
>>>> --- Physical Segments ---
>>>> Physical extent 0 to 238343:
>>>>   Logical volume	/dev/fileshare/lv_fileshare
>>>>   Logical extents	0 to 238343
>>> OK according to that both are full of an LV
>>> called "lv_fileshare".  Try mounting that and
>>> see what, if anything, is on it.  Don't remember
>>> creating that?  Try history | grep -10 lv_fileshare
>>> for a reminder.
>>> --
>>> Ray Morris
>>> support@bettercgi.com
>>> Strongbox - The next generation in site security:
>>> http://www.bettercgi.com/strongbox/
>>> Throttlebox - Intelligent Bandwidth Control
>>> http://www.bettercgi.com/throttlebox/
>>> Strongbox / Throttlebox affiliate program:
>>> http://www.bettercgi.com/affiliates/user/register.php
>>> On 11/05/2009 09:36:35 AM, Adam Mooz wrote:
>>>> Here it is for both SDA and SDB:
>>>> #pvdisplay -m /dev/mapper/cryptsda
>>>> File descriptor 4 left open
>>>> --- Physical volume ---
>>>> PV Name               /dev/mapper/cryptsda
>>>> VG Name               fileshare
>>>> PV Size               931.04 GB / not usable 3.87 MB
>>>> Allocatable           yes (but full)
>>>> PE Size (KByte)       4096
>>>> Total PE              238344
>>>> Free PE               0
>>>> Allocated PE          238344
>>>> PV UUID               6OfRxC-R59i-CVjX-igtB-pg4e-2qAw-OdiPSc
>>>> --- Physical Segments ---
>>>> Physical extent 0 to 238343:
>>>>   Logical volume	/dev/fileshare/lv_fileshare
>>>>   Logical extents	0 to 238343
>>>> #pvdisplay -m /dev/mapper/cryptsdb
>>>> File descriptor 4 left open
>>>> --- Physical volume ---
>>>> PV Name               /dev/mapper/cryptsdb
>>>> VG Name               fileshare
>>>> PV Size               931.04 GB / not usable 3.87 MB
>>>> Allocatable           yes (but full)
>>>> PE Size (KByte)       4096
>>>> Total PE              238344
>>>> Free PE               0
>>>> Allocated PE          238344
>>>> PV UUID               zCLder-PF5b-fQpy-RdMS-Ayc0-caWh-LA2Esm
>>>> --- Physical Segments ---
>>>> Physical extent 0 to 238343:
>>>>   Logical volume	/dev/fileshare/lv_fileshare
>>>>   Logical extents	238344 to 476687
>>>> On 2009-11-05, at 10:10 AM, Ray Morris wrote:
>>>>> What is the output of?:
>>>>> pvdisplay -m /dev/mapper/cryptsda
>>>>> --
>>>>> Ray Morris
>>>>> support@bettercgi.com
>>>>> Strongbox - The next generation in site security:
>>>>> http://www.bettercgi.com/strongbox/
>>>>> Throttlebox - Intelligent Bandwidth Control
>>>>> http://www.bettercgi.com/throttlebox/
>>>>> Strongbox / Throttlebox affiliate program:
>>>>> http://www.bettercgi.com/affiliates/user/register.php
>>>>> On 11/05/2009 01:57:53 AM, Adam Mooz wrote:
>>>>>> Hello List,
>>>>>> I have a fileserver that is driving me nuts at the moment.   
>>>>>> Setup:
>>>>>> 4x 1TB HDD's
>>>>>> 1x 320GB HDD
>>>>>> They all have the same partition layout:
>>>>>> 512MB Swap, rest is LVM data.
>>>>>> The LVM only contains ~400GB of data, but 2 of the TB drives  
>>>>>> report having 0 free PFree's:
>>>>>> PV                   VG        Fmt  Attr PSize   PFree
>>>>>> /dev/mapper/cryptsda fileshare lvm2 a-   931.03G      0
>>>>>> /dev/mapper/cryptsdb fileshare lvm2 a-   931.03G      0
>>>>>> /dev/mapper/cryptsdc fileshare lvm2 a-   297.61G 297.61G
>>>>>> /dev/mapper/cryptsdd fileshare lvm2 a-   931.03G 633.42G
>>>>>> /dev/mapper/cryptsde           lvm2 --   931.04G 931.04G
>>>>>> I've successfully managed to remove SDE from the LVM, but I  
>>>>>> need to move the data off SDD onto either SDA or SDB.  When the  
>>>>>> whole system is mounted it properly reports having 2.1TB of  
>>>>>> free space (931 * 2 + 297). Is there an easy way to fix this  
>>>>>> issue?
>>>>> ------quoted attachment------
>>>>>> _______________________________________________
>>>>>> linux-lvm mailing list
>>>>>> linux-lvm@redhat.com
>>>>>> https://www.redhat.com/mailman/listinfo/linux-lvm
>>>>>> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>>>>> _______________________________________________
>>>>> linux-lvm mailing list
>>>>> linux-lvm@redhat.com
>>>>> https://www.redhat.com/mailman/listinfo/linux-lvm
>>>>> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>>> ------quoted attachment------
>>>> _______________________________________________
>>>> linux-lvm mailing list
>>>> linux-lvm@redhat.com
>>>> https://www.redhat.com/mailman/listinfo/linux-lvm
>>>> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>>> _______________________________________________
>>> linux-lvm mailing list
>>> linux-lvm@redhat.com
>>> https://www.redhat.com/mailman/listinfo/linux-lvm
>>> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>> _______________________________________________
>> linux-lvm mailing list
>> linux-lvm@redhat.com
>> https://www.redhat.com/mailman/listinfo/linux-lvm
>> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/