Bug 1990905

Summary:	Set filesystem size at create time
Product:	Red Hat Enterprise Linux 9	Reporter:	Dennis Keefe <dkeefe>
Component:	stratisd	Assignee:	Bryan Gurney <bgurney>
Status:	CLOSED ERRATA	QA Contact:	Filip Suba <fsuba>
Severity:	unspecified	Docs Contact:	Kristina Slaveykova <kslaveyk>
Priority:	medium
Version:	9.1	CC:	amulhern, bgurney, cwei, dkeefe, fsuba, kslaveyk, mgandhi
Target Milestone:	beta
Target Release:	9.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	stratisd-3.1.0-2.el9	Doc Type:	Enhancement
Doc Text:	.Stratis now enables setting the file system size upon creation You can now set the required size when creating a file system. Previously, the automatic default size was 1 TiB. With this enhancement, users can set an arbitrary filesystem size. The lower limit must not go below 512 MiB.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-11-15 10:24:49 UTC	Type:	Enhancement
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Dennis Keefe 2021-08-06 14:50:49 UTC

Description of problem:
Currently when creating a filesystem in Stratis the filesystem will be 1TB. 
This bug is being used to track work upstream on a feature to allow users to 
configure the filesystem size at create time. 
 
https://github.com/stratis-storage/project/issues/299

Comment 2 Dennis Keefe 2021-10-13 19:29:19 UTC

Work completed here: https://github.com/stratis-storage/stratisd/pull/2735

Comment 7 Filip Suba 2022-06-20 12:34:21 UTC

Verified with stratisd-3.1.0-2.el9.

Comment 11 errata-xmlrpc 2022-11-15 10:24:49 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (stratisd bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:8124