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 1327881 - [RHEL7] tail -f doesn't work on m1fs file systems
Summary: [RHEL7] tail -f doesn't work on m1fs file systems
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: coreutils
Version: 7.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Ondrej Vasik
QA Contact: Jakub Prokes
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-17 13:23 UTC by Yigal Korman
Modified: 2016-11-04 07:40 UTC (History)
2 users (show)

Fixed In Version: coreutils-8.22-17.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-04 07:40:27 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2497 0 normal SHIPPED_LIVE coreutils bug fix update 2016-11-03 14:11:50 UTC

Description Yigal Korman 2016-04-17 13:23:03 UTC
"tail -f file" on m1fs file-system reports the following warning:
tail: unrecognized file system type 0x5346314d for ‘file’. please report this to bug-coreutils. reverting to polling.

m1fs is the first file-system to support persistent memory (NVDIMM and others) made by Plexistor Ltd.
A community edition can be downloaded from http://www.plexistor.com/download/

Our customers are reporting the problem above in RHEL7 and we'd like to help fix it.

We've got approval for the fix from the coreutils maintainers:
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=23283
http://git.savannah.gnu.org/cgit/coreutils.git/commit/?id=8faf269250

version:
coreutils-8.22-15.el7_2.1.x86_64

Please let me know if any additional information is required.

Comment 1 Yigal Korman 2016-04-17 13:30:45 UTC
An important note I forgot to mention - m1fs support inotify so reverting to polling is incorrect behavior.

Comment 3 Ondrej Vasik 2016-04-18 10:56:14 UTC
Thanks, revert to polling for unknown filesystems is probably better than staying with inotify. OTOH, the message is over-aggressive in the enterprise operating system with long support.

Comment 4 Ondrej Vasik 2016-04-18 18:55:31 UTC
That being said, my plan is to remove the message about "revert to polling" by default from RHEL 7 coreutils (available in debug mode) and to add m1fs to the list of known local filesystems. Thanks for handling this upstream first btw.

Comment 11 errata-xmlrpc 2016-11-04 07:40:27 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, 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://rhn.redhat.com/errata/RHBA-2016-2497.html


Note You need to log in before you can comment on or make changes to this bug.