All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ray Morris <support@bettercgi.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] PFree is 0 on a drive with nothing on it
Date: Thu, 05 Nov 2009 09:55:28 -0600	[thread overview]
Message-ID: <1257436528.17792.32@raydesk1.bettercgi.com> (raw)
In-Reply-To: <E6AFA4E4-A03C-4D1D-8A78-5DF2110EFA2E@gmail.com> (from adam.mooz@gmail.com on Thu Nov  5 09:36:35 2009)

>   --- 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/

  reply	other threads:[~2009-11-05 15:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-05  7:57 [linux-lvm] PFree is 0 on a drive with nothing on it Adam Mooz
2009-11-05 15:10 ` Ray Morris
2009-11-05 15:36   ` Adam Mooz
2009-11-05 15:55     ` Ray Morris [this message]
2009-11-05 18:57       ` Adam Mooz
2009-11-05 19:16         ` Ray Morris
2009-11-05 20:49           ` Adam Mooz
2009-11-05 19:24         ` Stuart D. Gathman
2009-11-05 19:52           ` malahal
2009-11-05 20:32             ` Stuart D. Gathman
2009-11-05 20:35         ` Stuart D. Gathman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1257436528.17792.32@raydesk1.bettercgi.com \
    --to=support@bettercgi.com \
    --cc=linux-lvm@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.