Bug 769874
Summary: | tail: fix --follow on FhGFS remote file systems | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Sven Breuner <sven.breuner> |
Component: | coreutils | Assignee: | Ondrej Vasik <ovasik> |
Status: | CLOSED ERRATA | QA Contact: | qe-baseos-daemons |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.4 | CC: | asersen, azelinka, meyering, plazonic, pope_svr4, prc |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | coreutils-8.4-17.el6 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-06-20 14:34:22 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Sven Breuner
2011-12-22 15:39:09 UTC
Thanks for report, I'm aware of it. Btw. I think the same should be done with GPFS (http://git.savannah.gnu.org/cgit/coreutils.git/commit/?id=d191bfe8a688d40aac0e3626b434b54ddbafd072 and http://git.savannah.gnu.org/cgit/coreutils.git/commit/?id=473b4fc1e8842ad99f544832683699539da5828d ) Indeed - please consider adding support for detecting GPFS - we have just hit that issue and it is defaulting to inotify use on GPFS file systems (and therefore failing miserably). The strace is indicating the right magic number (from above coreutils commits) so adding those commits would fix it. Thanks! *** Bug 809828 has been marked as a duplicate of this bug. *** When is an updated coreutils rpm going to be released to support GPFS? I found a workaround by using the "---disable-inotify" option but would prefer an updated version of tail. At the moment the fix is planned for RHEL-6.3 minor update. I can't give any promise but it is very likely that this will be fixed in that update. 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. http://rhn.redhat.com/errata/RHBA-2012-0933.html |