ClearOS Bug Tracker


View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0000704ClearOSanaconda - Installerpublic2012-08-10 05:582018-10-09 09:49
Reportertimb80 
Assigned Toslords 
PrioritynormalSeveritymajorReproducibilityhave not tried
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version6.3.0 
Target Version6.6.0Fixed in Version6.6.0 
Summary0000704: Default install results in LVM reserving too much space for lv_home volume
DescriptionSee forum threads for details for reported issue
http://www.clearfoundation.com/component/option,com_kunena/Itemid,232/catid,18/func,view/id,44685/ [^]
http://www.clearfoundation.com/component/option,com_kunena/Itemid,232/catid,39/func,view/id,43029/limit,10/limitstart,70/#44605 [^]

This is a problem because most of ClearOS file storage occurs at /var/flexshare not /home

(As an aside my VM test install created only the lv_root volume, so yet to determine at which point in the install it creates a seperate /home volume and mount point)

Work around is manual partition / mount point configuration during install
TagsNo tags attached.
Attached Filespatch file icon anaconda-13.21.195-nohome.patch [^] (911 bytes) 2013-10-16 10:02 [Show Content]

- Relationships
related to 0001137closeduser2 Default partitioning is less than ideal 

-  Notes
(0000548)
timb80 (developer)
2012-08-12 16:16

Only seems to affect systems with larger drives... not seen on VM install < 10GB. Forum user notes issue with 300GB drive.
(0000549)
dloper (administrator)
2012-08-15 21:26

I'll try and find out why this is happening. There is a workaround for this but it requires some command line work. I know that Peter and I have been working to make a method whereby the OS is largely located on '/' and all other data devices are located in '/store'. For example, if you have additional partitions, NAS devices, USB attached storage, iSCSI SAN or what have you, then you simply mount all of this data in /store. (data0, usb0, iscsi0, iscsi1, et al.)

From here you bind mount the data to the new drive. This is a workaround but I will have a guide tomorrow written up to resize your LVM on ClearOS. The beauty of LVM is that you can shrink and grow the partitions. Until then (and even if you do the LVM thing) you might want to consider making the data structure you need in the /home partition and then simply bindmounting it over to /var/flexshare/shares.

www.clearfoundation.com/docs/developer/a...ized_user_data/start

- Issue History
Date Modified Username Field Change
2012-08-10 05:58 timb80 New Issue
2012-08-10 05:58 timb80 Product Version => 6.3.0
2012-08-10 05:58 timb80 Summary Default partitioning results in LVM reserving too much space for lv_home volume => Default install results in LVM reserving too much space for lv_home volume
2012-08-12 16:16 timb80 Note Added: 0000548
2012-08-15 01:18 user2 Assigned To => dloper
2012-08-15 01:18 user2 Status new => assigned
2012-08-15 21:26 dloper Note Added: 0000549
2013-10-16 09:16 user2 Relationship added related to 0001137
2013-10-16 10:02 user2 File Added: anaconda-13.21.195-nohome.patch
2013-10-16 10:03 user2 Assigned To dloper => slords
2013-10-16 10:03 user2 Target Version => 6.5.0
2013-12-16 20:17 user2 Target Version 6.5.0 => 6.6.0 Beta 1
2014-04-22 13:37 user2 Target Version 6.6.0 Beta 1 => 6.6.0
2015-01-19 08:42 user2 Target Version 6.6.0 => 6.7.0 Beta 1
2015-01-25 15:56 user2 Fixed in Version => 6.6.0
2015-01-25 15:56 user2 Target Version 6.7.0 Beta 1 => 6.6.0
2018-10-09 09:49 dloper Status assigned => closed
2018-10-09 09:49 dloper Resolution open => fixed