Bug 2189242

Summary:	Filesystem: Improve stopping for large filesystems (RHEL7)
Product:	Red Hat Enterprise Linux 7	Reporter:	Josef Zimek <pzimek>
Component:	resource-agents	Assignee:	Oyvind Albrigtsen <oalbrigt>
Status:	CLOSED MIGRATED	QA Contact:	cluster-qe <cluster-qe>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.9	CC:	agk, cluster-maint, fdinitto, lucas.blenkhorn, sbradley
Target Milestone:	rc	Keywords:	MigratedToJIRA
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	2189243 (view as bug list)		Environment:
Last Closed:	2023-09-22 20:15:41 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:
Bug Depends On:
Bug Blocks:	2189243, 2207567

Description Josef Zimek 2023-04-24 13:52:39 UTC

Description of problem:

On high-end production workload systems with huge amount of (write-cache) RAM and big XFS file systems >= 8 TiB the unmount operation itself may take longer then 10 minutes on each attempt (even if it fails as processes are still utilizing it). In case login shells of users sit on the Filesystem resource then these do no respond  to SIGTERM, just to SIGHUP so when resource is stopping it deliberately fails to unmount and causes stop operation to fail/timeout.


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

resource-agents-4.1.1-61.el7_9.15.x86_64

How reproducible:
repeatedly


Steps to Reproduce:
1. Create large filesystem resource with potentially long dirty unmount cycles (+- 30 minutes) with login shells on it
2. re-login during the long stop operation (login shells on any HA FS RA managed file system does not fail all standard FS RA stop operation)


Actual results:
unmount fails resulting stop operation to fail

Expected results:
unmount succeeds

Additional info:

Comment 8 RHEL Program Management 2023-09-22 20:14:45 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 9 RHEL Program Management 2023-09-22 20:15:41 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.