Bug 86035
| Summary: | Assertion Failure in do_get_write_access() | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Kris Reilly <kar> |
| Component: | kernel | Assignee: | Stephen Tweedie <sct> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Brian Brock <bbrock> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.3 | CC: | bitto |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2004-09-10 12:16:46 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
Kris Reilly
2003-03-12 19:16:15 UTC
Not sure if this is related, but I am using redhat advance server and getting LOTS of disk crashes. Below is taken from my logs and I have messages.1 and messages.2 are fuull of these messages, and messages.3 is where they start. I've got a dual PIII 600 box that is one of our dev boxes running Linux swallow.mccue.com 2.4.9-e.35enterprise #1 SMP Tue Dec 23 00:06:16 EST 2003 i686 unknown ###################################### from /var/log/messages.3 ###################################### Dec 18 11:42:01 swallow kernel: attempt to access beyond end of device Dec 18 11:42:01 swallow kernel: 03:09: rw=0, want=970312140, limit=81923436 Dec 18 11:42:01 swallow kernel: EXT3-fs error (device ide0(3,9)): ext3_get_inode_loc: unable to read inode block - inode=32769, bloc k=779448946 Dec 18 11:42:01 swallow kernel: attempt to access beyond end of device Dec 18 11:42:01 swallow kernel: 03:09: rw=0, want=970312140, limit=81923436 Dec 18 11:42:01 swallow kernel: EXT3-fs error (device ide0(3,9)): ext3_get_inode_loc: unable to read inode block - inode=32769, bloc k=779448946 Dec 18 11:42:01 swallow kernel: EXT3-fs error (device ide0(3,9)) in ext3_reserve_inode_write: IO failure Dec 18 11:58:38 swallow kernel: attempt to access beyond end of device Dec 18 11:58:38 swallow kernel: 03:09: rw=0, want=970312140, limit=81923436 Dec 18 11:58:38 swallow kernel: EXT3-fs error (device ide0(3,9)): ext3_get_inode_loc: unable to read inode block - inode=32769, bloc k=779448946 The "transaction.c:737" assert failure should be fixed in all current kernels. The root problem was that ext3's internal debugging was making assumptions about the "uptodate" flag which are broken in the presence of IO errors. These assert failures have been downgraded to warnings in later kernels. |