Bug 474269
Summary: | Resize (shrink) old partition, but the filesystem data is not shrunk to match. | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Donald Arseneau <asnd> | ||||||
Component: | anaconda | Assignee: | Jeremy Katz <katzj> | ||||||
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
Severity: | high | Docs Contact: | |||||||
Priority: | low | ||||||||
Version: | 10 | CC: | anaconda-maint-list | ||||||
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: | 2009-02-16 20:32:51 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: | |||||||||
Attachments: |
|
Description
Donald Arseneau
2008-12-03 01:44:13 UTC
We definitely do shrink the filesystem as well. Can you attach /var/log/anaconda.log and /var/log/anaconda.syslog to this bug report? Created attachment 325635 [details]
anaconda.log
Here is anaconda.log. The file's time-stamp looks correct,
but the times on each entry don't correspond to anything
I know... maybe they are UTC time.
I don't recognize any resizing or creation of partitions,
but do see creation of filesystems.
/dev/VolGroup00/LogVol03 is the new main partition,
created from free space in the installation.
/dev/sda1 was an existing (non-LVM) partition that
I shrunk, and which wound up damaged.
/dev/sda3 is the new /boot partition that I put into
the space freed up by shrinking /dev/sda1.
Created attachment 325636 [details]
anaconda.syslog
There aren't any of the log messages that we definitely output on a resize. How did you select to do the resize? There is uncertainty in this because I was not keeping notes as I installed (of course). I selected "Create Custom" double-click on /dev/sda1 resize double-click on free space select mountpoint /boot check-off Force primary (this would be /dev/sda3) double-click free space in LVM section select mount point / for it click through warning about small /boot But two (probably critical) disruptions happened, and I don't recall at what stage: I had to "back" at one point There was a complaint about the free space being not enough for the new /dev/sda3 boot partition, which surprised me a lot. I clicked it smaller by one increment (whatever those increments are in the gui) and it then proceeded. The only thing I can think of is that possibly you got into a state where we changed teh size of the device but without changing the size of the partition. I've put a couple of checks into the code so that hopefully if someone hits this case in the future, we'll at least raise an exception before something wrong happens. |