Smaller boot disk requirements
Shiori
86 Posts
February 14, 2019, 4:30 pmQuote from Shiori on February 14, 2019, 4:30 pmI understand the whole point of the 64GB boot drive, but for those of us using SD cards this leaves us putting in a very large and wasted 128GB card.
I would like a smaller boot drive requirement that would allow the use of a 64GB (60GB once formatted correctly) SD card as the install and boot drive.
Please do not respond off handedly with this is not recommended. This is done in enterprise systems all the time.
I understand the whole point of the 64GB boot drive, but for those of us using SD cards this leaves us putting in a very large and wasted 128GB card.
I would like a smaller boot drive requirement that would allow the use of a 64GB (60GB once formatted correctly) SD card as the install and boot drive.
Please do not respond off handedly with this is not recommended. This is done in enterprise systems all the time.
admin
2,921 Posts
February 14, 2019, 5:17 pmQuote from admin on February 14, 2019, 5:17 pmThe current limit is 64 GB, this is a block level size not dependent on net format size.
If you feel reducing slightly to 60 GB will be of benefit, sure we can probably do this.
The problem is we cannot reduce it to say 32GB. Beside the os partition, management nodes require space to store the ceph monitor database ( which can grow to 20 GB or more in case of large cluster ) + storage of the stats data.
The current limit is 64 GB, this is a block level size not dependent on net format size.
If you feel reducing slightly to 60 GB will be of benefit, sure we can probably do this.
The problem is we cannot reduce it to say 32GB. Beside the os partition, management nodes require space to store the ceph monitor database ( which can grow to 20 GB or more in case of large cluster ) + storage of the stats data.
Shiori
86 Posts
February 14, 2019, 5:37 pmQuote from Shiori on February 14, 2019, 5:37 pmI understand the limitations and requirements and that the monitors and logs use a lot of space, I have seen this on my current nodes.
Shrinking slightly would allow for a 64GB SD card which is now very common and cheap.
Another possibility would be to have the installer be able to split the OS and the monitor logs into separate partitions that could be on separate mediums. Say two SD cards or an SD card and a USB HDD. This vould all be done after install too, if it would install onto a 64GB or smaller card.
This would also help others whom are using more commodity hardware to free up an ever important SAS/SATA channel.
Thanks!
I understand the limitations and requirements and that the monitors and logs use a lot of space, I have seen this on my current nodes.
Shrinking slightly would allow for a 64GB SD card which is now very common and cheap.
Another possibility would be to have the installer be able to split the OS and the monitor logs into separate partitions that could be on separate mediums. Say two SD cards or an SD card and a USB HDD. This vould all be done after install too, if it would install onto a 64GB or smaller card.
This would also help others whom are using more commodity hardware to free up an ever important SAS/SATA channel.
Thanks!
Smaller boot disk requirements
Shiori
86 Posts
Quote from Shiori on February 14, 2019, 4:30 pmI understand the whole point of the 64GB boot drive, but for those of us using SD cards this leaves us putting in a very large and wasted 128GB card.
I would like a smaller boot drive requirement that would allow the use of a 64GB (60GB once formatted correctly) SD card as the install and boot drive.
Please do not respond off handedly with this is not recommended. This is done in enterprise systems all the time.
I understand the whole point of the 64GB boot drive, but for those of us using SD cards this leaves us putting in a very large and wasted 128GB card.
I would like a smaller boot drive requirement that would allow the use of a 64GB (60GB once formatted correctly) SD card as the install and boot drive.
Please do not respond off handedly with this is not recommended. This is done in enterprise systems all the time.
admin
2,921 Posts
Quote from admin on February 14, 2019, 5:17 pmThe current limit is 64 GB, this is a block level size not dependent on net format size.
If you feel reducing slightly to 60 GB will be of benefit, sure we can probably do this.
The problem is we cannot reduce it to say 32GB. Beside the os partition, management nodes require space to store the ceph monitor database ( which can grow to 20 GB or more in case of large cluster ) + storage of the stats data.
The current limit is 64 GB, this is a block level size not dependent on net format size.
If you feel reducing slightly to 60 GB will be of benefit, sure we can probably do this.
The problem is we cannot reduce it to say 32GB. Beside the os partition, management nodes require space to store the ceph monitor database ( which can grow to 20 GB or more in case of large cluster ) + storage of the stats data.
Shiori
86 Posts
Quote from Shiori on February 14, 2019, 5:37 pmI understand the limitations and requirements and that the monitors and logs use a lot of space, I have seen this on my current nodes.
Shrinking slightly would allow for a 64GB SD card which is now very common and cheap.
Another possibility would be to have the installer be able to split the OS and the monitor logs into separate partitions that could be on separate mediums. Say two SD cards or an SD card and a USB HDD. This vould all be done after install too, if it would install onto a 64GB or smaller card.
This would also help others whom are using more commodity hardware to free up an ever important SAS/SATA channel.
Thanks!
I understand the limitations and requirements and that the monitors and logs use a lot of space, I have seen this on my current nodes.
Shrinking slightly would allow for a 64GB SD card which is now very common and cheap.
Another possibility would be to have the installer be able to split the OS and the monitor logs into separate partitions that could be on separate mediums. Say two SD cards or an SD card and a USB HDD. This vould all be done after install too, if it would install onto a 64GB or smaller card.
This would also help others whom are using more commodity hardware to free up an ever important SAS/SATA channel.
Thanks!