Bug 757975 - bug 557989 is still present (erroneously reported dirty filesystems prevent upgrade to FC16)
Summary: bug 557989 is still present (erroneously reported dirty filesystems prevent u...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda-images
Version: 16
Hardware: Unspecified
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Vratislav Podzimek
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-29 05:10 UTC by Rob
Modified: 2013-02-26 14:49 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-26 14:49:14 UTC
Type: ---


Attachments (Terms of Use)
requested files and further information (133.85 KB, application/octet-stream)
2011-11-29 17:55 UTC, Rob
no flags Details

Description Rob 2011-11-29 05:10:03 UTC
Description of problem:

The problem reported over two years ago (bug 557989) in upgrade from FC10 to FC11 still exists.  anaconda erroneously reports a dirty ext4 target filesystem and prevents upgrades, when attempted either via preupgrade package or net install CD.


How reproducible: 

try to upgrade FC16 onto an installation of FC14 that used ext4 filesystems

Comment 1 Chris Lumens 2011-11-29 14:32:14 UTC
Please attach the log files from your installation attempt to this bug report.  There's really not enough information in this bug to do anything with.

Comment 2 Vratislav Podzimek 2011-11-29 15:00:43 UTC
I've just tried preupgrade on F14 to F16 and everything went like a charm. Have
you tried it more times or just once? Could you please try it again and provide
logs from the malfunctioning case?

Comment 3 Rob 2011-11-29 17:55:06 UTC
Created attachment 538158 [details]
requested files and further information

The actual bug doesn't occur until you restart the system using the kernel 3.x installation image.  This is after doing the preupgrade package install.

Attached is a tar file of what relevant log files I could locate after anaconda terminated.  Not sure what log files are needed since Chris wasn't explicit about that above.

Other information about the target machine:

1) Supermicro super-workstation SYS-7046a-t
2) 2 each 2.4gz westemere CPUs
3) 24GB RAM
4) Asus NVidia GTX460
5) Supplemental Highpoint RocketRaid 2310 4 port PCIe-4 SATA card.
6) target upgrade disk is a 64GB SSD on one of the SATA channels from the Intel ICH10X controller.
7) 8 port SATA disk rack in system case
8) Since the upgrade procedure also has problems dealing with my mdadm RAID volumes all other SATA drives are electrically removed from the system before booting the FC16 upgrade image.

Comment 4 Vratislav Podzimek 2011-12-05 12:18:59 UTC
(In reply to comment #3)
> Created attachment 538158 [details]
> requested files and further information
> 
> The actual bug doesn't occur until you restart the system using the kernel 3.x
> installation image.  This is after doing the preupgrade package install.
I went through the whole upgrade process (using preupgrade).

> 
> Attached is a tar file of what relevant log files I could locate after anaconda
> terminated.  Not sure what log files are needed since Chris wasn't explicit
> about that above.
The more logs the better, thank you for providing them. It can be seen in the tmp/program.log (line 558) that calling 'resize2fs -P /dev/sda2' failed. Could you please try this manually before rebooting to the anaconda-upgrade environment (i.e. after running preupgrade)?

Comment 7 Fedora End Of Life 2013-01-16 20:45:05 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 8 Jaroslav Reznik 2013-02-26 14:49:14 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.