View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000429 | AlmaLinux-8 | kernel | public | 2023-09-25 23:55 | 2023-09-25 23:55 |
| Reporter | alufmtl | Assigned To | |||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | new | Resolution | open | ||
| Platform | x86_64 | OS | AlmaLinux | OS Version | 8.8 |
| Summary | 0000429: Quotas with EXT4 on AlmaLinux do not get enacted on MD-RAID1 | ||||
| Description | - | ||||
| Steps To Reproduce | I tested an instance in Vmware(with a vanilla installation of AlmaLinux 8.8), and I can confirm that -- for some unknown reason -- I don't need to enable the feature "quota" in ext4. "dumpe2fs -h /dev/md__" in my Vmware informs me there is no "quota" feature, though "quotacheck -ucm -F vfsv1 /" passes. And I can then proceed to using "edquota -u _user_" successfully. I can replicate the same issue again and again with ext4 on md-raid1. in contrary to redhat's official documentation regarding quotas, the redhat site states that "quota" should be enabled in "ext4". ^ So I suppose this is a bug, because here on AlmaLinux, enabling "quota" as a feature in EXT4(and on MD-RAID1), it is preventing the quotas from working. Tested with these two forms in /etcf/fstab -- using stock kernel 4.18.0-477.27.1.el8_8.x86_64 form 1) UUID=__ / ext4 defaults,usrquota,grpquota 0 1 form 2) UUID=__ / ext4 defaults,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv1 0 1 and both are successful. (after applying "quotacheck -cmgu -F vfsv1 / , and later testing with edquota -u user) question: why would "edquota" only work after disabling or not enabling at all "quota" feature embedded into the ext4 metadata? ^ this 100% contradicts the redhat documentation. please take a look. thanks | ||||
| Tags | No tags attached. | ||||
| abrt_hash | |||||
| URL | |||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2023-09-25 23:55 | alufmtl | New Issue |
