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