[
https://issues.apache.org/jira/browse/KUDU-1508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15605072#comment-15605072
]
Gordon Gardiner commented on KUDU-1508:
---------------------------------------
It could be several more months before RHEL 6.9 appears. I note that RHEL 6 is
pretty long in the tooth. It was released in November 2010 and is in the
Production 2 stage of its life cycle.
https://access.redhat.com/support/policy/updates/errata
Support for XFS on RHEL 6 requires an additional subscription, albeit very low
cost.
In RHEL 7 XFS support is included and it is the default file system. I'd be
encouraging people in that direction, noting that an in place upgrade to RHEL 7
is possible but in many cases may not be an option.
> Log block manager triggers ext4 hole punching bug in el6
> --------------------------------------------------------
>
> Key: KUDU-1508
> URL: https://issues.apache.org/jira/browse/KUDU-1508
> Project: Kudu
> Issue Type: Bug
> Components: fs
> Affects Versions: 0.9.0
> Reporter: Todd Lipcon
> Priority: Blocker
> Attachments: e9f83e4acef3405f99d01914317351ce.metadata
>
>
> I've experienced many times that when I reboot an el6 node that was running
> Kudu tservers, fsck reports issues like:
> data6 contains a file system with errors, check forced.
> data6: Interior extent node level 0 of inode 5259348:
> Logical start 154699 does not match logical start 2623046 at next level.
> After some investigation, I've determined that this is due to an ext4 kernel
> bug: https://patchwork.ozlabs.org/patch/206123/
> Details in a comment to follow.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
