Bug 98310
Summary: | up2date causes corrupt filesystem | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 2.1 | Reporter: | Bryan Che <bche> |
Component: | up2date | Assignee: | Adrian Likins <alikins> |
Status: | CLOSED WORKSFORME | QA Contact: | Fanny Augustin <fmoquete> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 2.1 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-01-14 21:24:12 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
Bryan Che
2003-06-30 21:48:07 UTC
I dont really see how this is an up2date issue? File system corruption is more or less always a kernel issue, and up2date doesnt touch fstab. It's possible one of the packages in the transaction set may of had problems. What about this case of filesystem corruption makes it appear to be a up2date issue? |