Bug 76381
Summary: | while writing LILO, ext3 complains | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Pavel Urban <fc-bugzilla> |
Component: | kernel | Assignee: | Stephen Tweedie <sct> |
Status: | CLOSED NOTABUG | QA Contact: | Brian Brock <bbrock> |
Severity: | low | Docs Contact: | |
Priority: | medium | ||
Version: | 7.3 | ||
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: | 2002-10-21 07:59:13 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
Pavel Urban
2002-10-21 06:15:57 UTC
That warning occurs when some external program modifies a block that is under ext3 control. In this case it's probably because you're running LILO with the boot sector one one of your partitions, rather than on the MBR of the disk. There's just no way around it --- if you do this, LILO ends up modifying one of the filesystem blocks which contains critical fs metadata (the superblock in this case). Of course, a journaling filesystem's correctness depends utterly on it getting the write order on disk exactly correct, and finding buffers unexpectedly dirty can indicate that that has gone wrong, which would be a potentially-data-corrupting error. So ext3 has the choice of warning about this or ignoring it. Given the potentially severe result of any ext3 bug which gets the write order wrong, it's better to leave the warning present, but the side-effect is that this particular LILO operation will result in a warning if you use it on an active, live filesystem. |