Bug 96641
Summary: | Oops in __d_lookup when accessing certain files | ||
---|---|---|---|
Product: | File System | Reporter: | dann frazier (dannf) |
Component: | ext4 | Assignee: | fs_ext4 (fs_ext4) |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | sandeen |
Priority: | P1 | ||
Hardware: | ARM | ||
OS: | Linux | ||
Kernel Version: | 4.0.0 | Subsystem: | |
Regression: | No | Bisected commit-id: |
Description
dann frazier
2015-04-14 18:13:44 UTC
Getting an e2image (with -r or -q) would be a way to preserve the filesystem state for analysis, then you could run fsck on it... -Eric Thanks Eric. Unfortunately I'm unable to reproduce the problem using an image created by e2image - I've tried loop back mounting on both x86 and the same arm64 system (image stored in tmpfs). That said, I'm happy to provide this e2image to someone interested in looking at it (1.8G). Link back to Ubuntu bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1440536 I'm going to mark this as resolved for the following reasons: - I reinstalled the system and the issue persisted. - I was unable to reproduce on another, identically configured system. - After removing one of the two DIMMs, the system is no longer seeing the problem. This all points to a localized hardware failure. fyi, this was root caused to be a firmware bug and has been resolved with the 1.15.22 firmware release. |