Bug 163470
Summary: | "bio too big device md1" with data corruption | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Frode Tennebø <frodet> |
Component: | kernel | Assignee: | Dave Jones <davej> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Brian Brock <bbrock> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 5 | CC: | davej, jonstanley, pfrields, wtogami |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | MassClosed | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-01-20 04:39:03 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
Frode Tennebø
2005-07-17 19:33:22 UTC
*** Bug 163469 has been marked as a duplicate of this bug. *** kernel-2.6.12-1.1411_FC4 just got pushed out to updates-testing. This has one block layer fix that could explain this. Sorry - this took some time. Not sure about the data corruption since I've just started the raid reconstruction and this coupled with the inherent Time Before Corruption means that it will take some longer. I just wanted to let you know that the errors (or whatever) are still there: Aug 7 23:26:26 leia kernel: md: bind<md0> Aug 7 23:26:26 leia kernel: RAID1 conf printout: Aug 7 23:26:26 leia kernel: --- wd:1 rd:2 Aug 7 23:26:26 leia kernel: disk 0, wo:0, o:1, dev:sdd1 Aug 7 23:26:26 leia kernel: disk 1, wo:1, o:1, dev:md0 Aug 7 23:26:26 leia kernel: ..<6>md: syncing RAID array md1 Aug 7 23:26:26 leia kernel: md: minimum _guaranteed_ reconstruction speed: 1000 KB/sec/disc. Aug 7 23:26:26 leia kernel: md: using maximum available idle IO bandwith (but not more than 200000 KB/sec) for reconstruction. Aug 7 23:26:26 leia kernel: md: using 128k window, over a total of 35842944 blocks. Aug 7 23:26:26 leia kernel: cfq: depth 4 reached, tagging now on Aug 7 23:26:26 leia kernel: cfq: depth 4 reached, tagging now on : Aug 7 23:34:57 leia kernel: bio too big device md1 (16 > 8) Aug 7 23:40:00 leia kernel: bio too big device md1 (16 > 8) Aug 7 23:45:37 leia kernel: bio too big device md1 (16 > 8) : Mass update to all FC4 bugs: An update has been released (2.6.13-1.1526_FC4) which rebases to a new upstream kernel (2.6.13.2). As there were ~3500 changes upstream between this and the previous kernel, it's possible your bug has been fixed already. Please retest with this update, and update this bug if necessary. Thanks. I still get these: Oct 14 23:49:24 leia kernel: bio too big device md1 (16 > 8) Oct 14 23:49:25 leia kernel: bio too big device md1 (64 > 8) Oct 14 23:49:25 leia kernel: bio too big device md1 (248 > 8) Oct 14 23:49:26 leia last message repeated 12 times Oct 14 23:49:26 leia kernel: bio too big device md1 (136 > 8) Oct 14 23:49:26 leia kernel: bio too big device md1 (136 > 8) Oct 14 23:49:26 leia kernel: bio too big device md1 (248 > 8) Oct 14 23:49:26 leia kernel: bio too big device md1 (144 > 8) Oct 14 23:49:26 leia kernel: bio too big device md1 (184 > 8) Oct 14 23:49:26 leia kernel: bio too big device md1 (248 > 8) Oct 14 23:49:26 leia kernel: bio too big device md1 (248 > 8) Oct 14 23:49:26 leia kernel: bio too big device md1 (152 > 8) Oct 14 23:49:26 leia kernel: bio too big device md1 (248 > 8) Oct 14 23:49:26 leia kernel: bio too big device md1 (248 > 8) Oct 14 23:49:26 leia kernel: bio too big device md1 (88 > 8) Oct 14 23:49:26 leia kernel: bio too big device md1 (192 > 8) Oct 14 23:49:26 leia kernel: bio too big device md1 (136 > 8) Oct 14 23:49:26 leia kernel: bio too big device md1 (40 > 8) Oct 14 23:49:26 leia kernel: bio too big device md1 (248 > 8) : : BTW: I have also recently experienced strange data corruption in a database I use. Though, this could have happened before the update in kernel-2.6.12-1. 1411_FC4 (as mentioned above). I will try to figure this out soonish. 2.6.14-1.1637_FC4 has been released as an update for FC4. Please retest with this update, as a large amount of code has been changed in this release, which may have fixed your problem. Thank you. *** Bug 170964 has been marked as a duplicate of this bug. *** This is a mass-update to all currently open kernel bugs. A new kernel update has been released (Version: 2.6.15-1.1830_FC4) based upon a new upstream kernel release. Please retest against this new kernel, as a large number of patches go into each upstream release, possibly including changes that may address this problem. This bug has been placed in NEEDINFO_REPORTER state. Due to the large volume of inactive bugs in bugzilla, if this bug is still in this state in two weeks time, it will be closed. Should this bug still be relevant after this period, the reporter can reopen the bug at any time. Any other users on the Cc: list of this bug can request that the bug be reopened by adding a comment to the bug. If this bug is a problem preventing you from installing the release this version is filed against, please see bug 169613. Thank you. Closing per previous comment. Sorry for the delay, but life's been busy. I have upgraded to FC5 and stil get: May 11 22:28:27 leia kernel: bio too big device md1 (48 > 8) May 11 22:28:27 leia kernel: bio too big device md1 (16 > 8) May 11 22:28:27 leia kernel: bio too big device md1 (80 > 8) May 11 22:28:27 leia kernel: bio too big device md1 (88 > 8) May 11 22:28:27 leia kernel: bio too big device md1 (32 > 8) May 11 22:28:27 leia kernel: bio too big device md1 (24 > 8) May 11 22:28:27 leia kernel: bio too big device md1 (32 > 8) May 11 22:28:27 leia kernel: bio too big device md1 (24 > 8) May 11 22:28:28 leia kernel: bio too big device md1 (80 > 8) May 11 22:28:28 leia kernel: bio too big device md1 (16 > 8) May 11 22:28:31 leia kernel: bio too big device md1 (24 > 8) May 11 22:28:31 leia kernel: bio too big device md1 (56 > 8) May 11 22:28:31 leia kernel: bio too big device md1 (80 > 8) May 11 22:28:31 leia kernel: bio too big device md1 (16 > 8) May 11 22:29:33 leia kernel: bio too big device md1 (48 > 8) May 11 22:29:33 leia kernel: bio too big device md1 (64 > 8) May 11 22:29:33 leia kernel: bio too big device md1 (24 > 8) May 11 22:29:33 leia kernel: bio too big device md1 (120 > 8) May 11 22:29:33 leia kernel: bio too big device md1 (64 > 8) May 11 22:29:33 leia kernel: bio too big device md1 (64 > 8) May 11 22:29:33 leia kernel: bio too big device md1 (128 > 8) May 11 22:57:47 leia kernel: bio too big device md1 (32 > 8) May 11 22:57:47 leia kernel: bio too big device md1 (24 > 8) May 11 22:58:15 leia kernel: bio too big device md1 (16 > 8) May 11 22:58:15 leia kernel: bio too big device md1 (16 > 8) May 11 22:58:15 leia kernel: bio too big device md1 (24 > 8) May 11 22:58:15 leia kernel: bio too big device md1 (16 > 8) May 11 22:58:15 leia kernel: bio too big device md1 (40 > 8) May 11 22:58:15 leia kernel: bio too big device md1 (16 > 8) I'm running kernel-2.6.16-1.2096_FC5. A new kernel update has been released (Version: 2.6.18-1.2200.fc5) based upon a new upstream kernel release. Please retest against this new kernel, as a large number of patches go into each upstream release, possibly including changes that may address this problem. This bug has been placed in NEEDINFO state. Due to the large volume of inactive bugs in bugzilla, if this bug is still in this state in two weeks time, it will be closed. Should this bug still be relevant after this period, the reporter can reopen the bug at any time. Any other users on the Cc: list of this bug can request that the bug be reopened by adding a comment to the bug. In the last few updates, some users upgrading from FC4->FC5 have reported that installing a kernel update has left their systems unbootable. If you have been affected by this problem please check you only have one version of device-mapper & lvm2 installed. See bug 207474 for further details. If this bug is a problem preventing you from installing the release this version is filed against, please see bug 169613. If this bug has been fixed, but you are now experiencing a different problem, please file a separate bug for the new problem. Thank you. (this is a mass-close to kernel bugs in NEEDINFO state) As indicated previously there has been no update on the progress of this bug therefore I am closing it as INSUFFICIENT_DATA. Please re-open if the issue still occurs for you and I will try to assist in its resolution. Thank you for taking the time to report the initial bug. If you believe that this bug was closed in error, please feel free to reopen this bug. |