| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
xfs_admin expects -L <label> <device>.
|
|
|
|
|
| |
iutil.execWithRedirect() stopped doing anything with searchPath in 2006
when clumens committed d0dec24. Remove these silly vestigal bits.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I've been running pylint on a subset of anaconda:
booty storage iw/*.py platform.py
And it has found various errors this commit fixes:
- Restore line accidently dropped from iscsi.py
- execWithPulseProgress should propagate the return value of
execWithCallback
- storage.formats.fs:535 (FS.doCheck): self.intf should be just intf
- storage.formats.fs: add missing "import sys" (for sys.exit)
- advanced_config.py add missing import for NetworkConfigurator
- lvm_dialog_gui.py: VolumeGroupEditor.editLogicalVolume dev was renamed to d
- partition_gui.py: remove an unneeded semicolon
- partition_gui.py: PartitionWindow.createCB rc should be dialog_rc
- storage.FSSet.write: put docstring in the proper place
- platform.Sparc.minimumSector: sectors should be sector
|
| |
|
|
|
|
|
|
|
| |
This attribute is a dict that describes the device or format instance
with considerable detail. It is intended that the dict will be
pickled using the shelve module, so values should be picklable objects.
Keys should be descriptive strings.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
In F11 and F12 the command line option to enable btrfs during the installer was
"icantbelieveitsnotbtr". Unfortunately I can't spell believe the first time
every time, and btrfs has come quite a ways since F11 and is stable enough to
start being tested on a larger scale. So change the command line option to
"btrfs" in keeping with tradition and to make it a bit simpler for those who
want to take it for a test spin in F13. Thanks,
Signed-off-by: Josef Bacik <josef@redhat.com>
|
| |
|
|
|
|
|
|
|
| |
'tmp/storage.log' file. (a part of #524980)
Previously, the method call was logged into 'tmp/anaconda.log' which made the
file harder to do anything useful with.
|
|
|
|
|
|
| |
If we are using an external utility to create the format we can use
iutil.execWithPulseProgress. For formats we create using a python
module we can only put up a waitWindow.
|
|
|
|
|
|
|
| |
We're not guaranteed to have the _infofs program on every platform, so we
need to make sure the filesystem is supported before making an attempt. For
now this is only showing up on NTFS volumes on ppc, but it's possible to
come up in other places.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The following install test case has been failing:
https://fedoraproject.org/wiki/QA:Testcase_Anaconda_autopart_%28shrink%29_install
The problem was with the minSize property in Ext2FS. We use resize2fs
to get the minSize for ext2/3/4 filesystems, which is good because
resize2fs accounts for additional things an extX volume may need. The
problem is the value it reports is in blocks. We have to convert those
blocks to bytes, then to megabytes, then round up to account for any
fractional megabytes. Use dumpe2fs to get the block size and use
resize2fs as we have been, but modify the calculation of size.
Also the _setTargetSize() method in FS needed a change. minSize can be
less than or equal to newsize, not just less than.
|
|
|
|
|
|
|
|
| |
If fsck fails with a return code indicating errors we can't
automatically fix, give the user a more descriptive error dialog before
exiting. There's not much we can do if the filesystem is beyond
automatic repair, so tell the user to repair the filesystem under rescue
mode or something similar.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The playing around with partedPartition flags only allows us to determine
the partition table entry for certain usuages which are deemed special
by parted. For normal FS usuage, parted will default to the type for the FS
it has detected (for pre-existing partitions) or to Linux (83) for new
partitions.
This means that for example reformatting a vfat partition as ext3, or a new
partition as vfat will lead to incorrect partition type entries in the
partition table. This patch fixes this.
This patch is intended for both master and F-12.
|
| |
|
|
|
|
| |
Rounding errors when computing the existing size of NTFS volumes.
|
|
|
|
|
|
| |
If a label is set on a filesystem (e.g., the --label switch on a part
command in a kickstart file), make sure it is set during the filesystem
creation.
|
|
|
|
| |
Remove unused fsFromConfig method, it is not used and has syntax errors in it.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
As the bug indicates, the kernel module is still available. I'm not
really interested in supporting installation to reiserfs, but I think we
should be able to recognize the filesystems in the partitioning UI as
well as let people shrink existing reiserfs filesystems to make room for
Fedora on more sane filesystems.
Detection works as is, but users have to pass 'reiserfs' on the command
line to enable installation to reiserfs volumes or to enable resize
support.
|
| |
|
|
|
|
|
| |
We have lots of strings that we display to users which are unclear or
contain poor usage and grammar. That's bad.
|
| |
|
|
|
|
|
|
|
| |
It appears that the migratable property in the FS class was using
FS._isMigratable when we'd overridden that method in Ext3FS. This fix
prevents the upgrade migrate fs screen from showing up unless ext4migrate
is on the cmdline, like intended.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
The _getExistingSize() method in class FS will using the filesystem
info/dump utility to figure out the size of the filesystem. Each
filesystem must define _infofs, _defaultInfoOptions, and
_existingSizeFields.
|
|
|
|
|
|
|
|
| |
Noticed that ext4 filesystems were presenting users with a 'migrate to'
combo box with 'ext4' as the only entry. Tracked down the problem to
the migratable property override in Ext3FS. Changed it around to use
helper functions with property() and the UI is working more sanely now.
Users cannot select ext4 as the migration target for ext4.
|
| |
|
| |
|
|
|
|
|
| |
Resizing can introduce errors too, so for paranoia, we should
check afterwards
|
| |
|
|
|
|
|
|
| |
We need to pass the mountpoint and the chroot in separately so everything
doesn't end up under /mnt/sysimage. Doing that results in the contexts
being set to mnt_t, which causes all sorts of problems on reboot.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This way we won't have to setup complex devices every time the
maxSize attribute is accessed. The device's minimum size should
never change without the user doing something that triggers a
storage reset/rescan, so there is no reason to expect that caching
the minimum size will lead to new failures. We know that the device
is already setup when the constructor is called, so it is a perfect
time to obtain the minimum size and be done with it.
|
|
|
|
|
| |
For fake filesystems types like EFI that are really vfat underneath, we
want to pass "vfat" to all the commands that expect a type.
|
| |
|
|
|
|
|
| |
These should either get a min size or return a reasonable default.
Crashing the installer for something like this is not reasonable.
|
|
|
|
|
|
|
| |
Instead of loading filesystem modules all at once in loader, load them as
needed from the filesystem format __init__ methods. The intention here is to
remove a lot of the special code from loader and avoid kernel errors in
modules that the user never even wants to have involved.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Ow, turned xfs to unsupported *and* no cmdline override, bummer.
-Eric
Signed-off-by: Eric Sandeen <sandeen@redhat.com>
|
| |
|
|
|
|
|
| |
This will make the fstype combo contain only the filesystems it
should.
|
|
|
|
| |
If its none there is no need to parse it.
|
| |
|