| Summary: | xfsdump failing with kernel issues inside vm | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Michael Walton <mike.walton33> |
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 23 | CC: | fedora-kernel-xfs, gansalmon, itamar, jonathan, kernel-maint, labbott, madhu.chinakonda, mchehab, mike.walton33 |
| Target Milestone: | --- | Flags: | labbott:
needinfo?
(mike.walton33) |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-10-26 16:44:32 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Michael Walton
2016-03-14 08:27:11 UTC
There was a known issue compatibility issue with xfsprogs, see http://jwboyer.livejournal.com/52090.html . Please update to the latest xfsprogs (should be 4.3.0) and see if that fixes the issue. I've got a fully up todate system with x(In reply to Laura Abbott from comment #1) > There was a known issue compatibility issue with xfsprogs, see > http://jwboyer.livejournal.com/52090.html . Please update to the latest > xfsprogs (should be 4.3.0) and see if that fixes the issue. I've got a fully up to date system with xfsprogs 4.3.0-1 installed. I've already done an xfs_repair using an up to date xfsprogs on the gparted cd. For anyone interested in this problem I imagine that bumping up vm.swappiness to a high level will help to expose it. I'm still encountering this issue with kernels 4.4.4 and 4.4.5 I was able to do an xfsdump 6 times in a row on the same machine after downgrading to kernel 4.2.3 so AFAICS this is most definitely a regression. I have tried out a bunch of different kernels now. To make a long story short I installed 4.3.6 and encountered no bug and when I unstalled kernel 4.4, I did encounter the bug. I installed kernel 4.3.6 from https://kojipkgs.fedoraproject.org/packages/kernel/4.3.6/201.fc22/ and kernel 4.4 from https://kojipkgs.fedoraproject.org/packages/kernel/4.4.0/1.fc24/ (Neither one was specifically an f23 kernel but I don't think that matters). Therefore, in my holy opinion, the problem was introduced in kernel 4.4. Hi again, I used git bisect on the development kernel (or tried to anyway). Supposing that I haven't screwed up, the commit where things break is: f77cf4e4cc9d40310a7224a1a67c733aeec78836 This isn't an xfs commit so either that commit has a bug or it exposes a bug in xfs or at the very least it subtly breaks xfs somehow (if I haven't screwed up my bisection of course). Thanks, I'm hoping that you guys and look into this now. Sorry posted too soon. I was doing 7 xfsdumps in a row as a test but apparently that's not good enough. I don't think I've bisected this right now. Back to the drawing board. Well, I kept at it. Here where things stand now. Two repeat bisection attempts have landed me at d0164adc89f6bb374d304ffcc375c6d2652fe67d I really can produce the bug here and I really cannot produce it at the previous commit (11 xfsdumps with swappiness at 0 and no kernel errors). *********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 23 kernel bugs. Fedora 23 has now been rebased to 4.7.4-100.fc23. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 24 or 25, and are still experiencing this issue, please change the version to Fedora 24 or 25. If you experience different issues, please open a new bug report for those. *********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 4 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously. |