Bug 488343
| Summary: | ext4: EXT4-fs error (device sdc1): ext4_add_entry: bad entry in directory #12: rec_len % 4 != 0 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Sergey <sergey_bogomolov> |
| Component: | kernel | Assignee: | Eric Sandeen <esandeen> |
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | low | ||
| Version: | 10 | CC: | dmbuvi+bugzilla, kernel-maint, quintela, sergey_bogomolov |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-05-21 02:00:53 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
Sergey
2009-03-03 19:50:10 UTC
Would you be willing to provide an "e2image -r" image of the source filesystem, either as an attachment or in private? That way I can probably reproduce and narrow down the problem. If so, a dumpe2fs -h of the target filesystem after you've mkfs'd it would help too. Thanks, -Eric Ok, I got the e2image; unfortunately so far I cannot reproduce it. however, my target filesystem is a bit smaller, I'll try again with one of the proper size and same geometry. I've had no luck reproducing this. Did you see it more than once? My best guess at this point is perhaps some memory corruption... ext4_add_entry: bad entry in directory #12: rec_len % 4 != 0 - offset=0, inode=2027203910, rec_len=36069, name_len=145 looks like a real mess; your inode nr should probably not be that high, the record length cannot(?) be that long, and I don't think any of your names are that long either... -Eric No, i tried only once :( Needed to return one of old disk in the same day. I'll try copy files from 500GB to other 500GB disk this week. If you do hit it, you might try it again on a -debug kernel variant, if it is memory corruption it might get caught sooner, or with more info. thanks, -Eric No, I cant reproduce it. I tried 2 times without any problem in the same configuration (files from 500GB disk to 1500GB disk with active ktorrents/aMule), only kernel upgraded to 2.6.27.19-170.2.35.fc10.x86_64. I was able to reproduce this on Fedora 12 Kernel 2.6.31.6-166.fc12.i686.PAE . I added a 256 MB DDR SDRAM module to my system and on rebooting, got the above error twice. Removing the RAM module resulted in normal booting. The RAM module was a defective one hence the issue was due to corrupt memory. |