Bug 2189242

Summary: Filesystem: Improve stopping for large filesystems (RHEL7)
Product: Red Hat Enterprise Linux 7 Reporter: Josef Zimek <pzimek>
Component: resource-agentsAssignee: Oyvind Albrigtsen <oalbrigt>
Status: ASSIGNED --- QA Contact: cluster-qe <cluster-qe>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.9CC: agk, cluster-maint, fdinitto, sbradley
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 2189243 (view as bug list) Environment:
Last Closed: 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: