Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1687974

Summary: stratisd may not extend XFS when filesystem space is low
Product: Red Hat Enterprise Linux 8 Reporter: Todd Gill <tgill>
Component: stratisdAssignee: mulhern <amulhern>
Status: CLOSED WONTFIX QA Contact: Filip Suba <fsuba>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: ---CC: amulhern, dkeefe, ingo.thierack, rhandlin
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: 8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-02-01 07:39:26 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Todd Gill 2019-03-12 19:32:08 UTC
Description of problem:

If stratisd is blocked by a slow running task - it may not extend the filesystem as needed.

Version-Release number of selected component (if applicable):


How reproducible:

%80 with the right hardware

Steps to Reproduce:
1. create a stratis pool/filesystem on slow storage (use mdadm to create a RAID 5 device) - run the following while mdadm is building the RAID set.
2. create a stratis pool/filesystem on fast storage
3. write a file to the fast storage that is a couple TB
   mount /stratis/pool-fast/fs1 /tmp/mp
   xfs_mkfile 2500G /tmp/mp/big.file
4. monitor the pool utilization
5. when the fast-pool is just below 1 TB - create a filesystem in the slow pool

The slow pool filesystem creation will block the stratisd main thread and prevent it from dealing with the need to extend XFS as needed.

Actual results:

Write to stratis filesystem fails when there is additional space avaliable

Expected results:

stratisd extends the filesystem before the application fails to write

Additional info:

Comment 1 Dennis Keefe 2019-08-12 16:54:13 UTC
Stratis can be blocked while IO is being processed.  This is due to the fact that Stratis is single threaded in some areas.  
A RFE has been open to improve upon this design, the bug number is 1740328.

Comment 2 Jakub Krysl 2019-10-02 11:32:58 UTC
Mass migration to Guangwu.

Comment 5 RHEL Program Management 2021-02-01 07:39:26 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.