summaryrefslogtreecommitdiffstats
path: root/storage
Commit message (Collapse)AuthorAgeFilesLines
...
* Improve disklabel's name attr so we don't have to hide them anymore.David Lehman2009-12-091-2/+10
|
* Hide devices with certain formatting in the main partitioning UI.David Lehman2009-12-094-0/+9
| | | | We don't want to show biosraid, multipath, &c disks in the GUI.
* Automatic partitioning support for whole-disk formatting.David Lehman2009-12-091-29/+51
| | | | | | | | When using the entire disk, whole-disk formats are replaced with a new disklabel. When replacing existing linux installations, linux- native whole-disk formats are replaced with a new disklabel. Disks containing whole-disk formatting are not offered as bootloader installation targets.
* Add support for whole-disk formatting.David Lehman2009-12-094-86/+104
| | | | Whole-disk formats are recognized but cannot be edited in any way.
* Don't crash if there's no intf passed to getLUKSPassphrase.David Lehman2009-12-081-0/+3
|
* Use selinux python module for file context operations.David Lehman2009-12-081-4/+6
|
* Obtain device alignment information from parted. (#529051)David Lehman2009-12-081-1/+10
|
* Handle roots with or without trailing "/" in FileDevice.path. (#541473)David Lehman2009-12-081-1/+5
|
* Nothing sets flags.setupFilesystems anymore, so it can go too.Chris Lumens2009-12-031-2/+1
|
* Remove test mode.Chris Lumens2009-12-032-28/+25
| | | | | | | This is yet another way of running anaconda that gets extremely limited use, no testing, and no consideration during development to making sure it still works. Again, we need to stop pretending and get rid of modes that we don't support.
* Whenever storage code tries to log a method call, do so into the ↵Ales Kozumplik2009-12-0312-15/+31
| | | | | | | '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.
* Log storage in the same format as the main anaconda log (a part of #524980)Ales Kozumplik2009-12-021-13/+3
| | | | | | | The entry format and date format is standardized: do not show date but always show miliseconds. Includes a cleanup in the storage/storage_log.py code to use AnacondaLog.
* Fix devicelibs.dm.device_is_multipath support for new udev rules.Peter Jones2009-11-302-2/+17
| | | | | | | | | | New udev rules for DM stuff use 'MAJOR' and 'MINOR' instead of 'DM_MAJOR' and 'DM_MINOR', so we need devicelibs.dm.device_is_multipath() to check for them instead. For now, this code will work with either variety. This also makes devicelibs.dm.device_is_multipath() take the whole info blob and do what it needs with it, rather than splitting it up in the calling function.
* Display progress or wait window when creating devices.David Lehman2009-11-301-58/+107
| | | | | | For devices created using an external utility we can display a pulsing progressWindow. For devices created using a python module we display a waitWindow.
* Display progress or wait window when formatting devices.David Lehman2009-11-304-26/+67
| | | | | | 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.
* Add optional progress windows to devicelibs create functions.David Lehman2009-11-303-23/+23
|
* Force mkswap to do its job.David Lehman2009-11-301-1/+3
| | | | | | There's some broken hueristic in mkswap that leads it to sometimes mistake a logical volume for a disk and hence refuse to format it, citing something about bootblocks. Nonsense.
* Don't try to get dm node or update sysfs path for lvm vgs.David Lehman2009-11-301-4/+3
|
* Add support for DCB to fcoe.py (#513011)Hans de Goede2009-11-261-8/+42
|
* Add RAID4 support (#541433)Alexandre Oliva2009-11-262-0/+11
|
* Clear a partition's BOOT flag when formatting itHans de Goede2009-11-261-4/+3
| | | | | | The BOOT flag of a partition indicates that it can be used to boot the OS from. Surely this is no longer true after we've formatted it. Note that we will set the BOOT flag on /boot later on.
* Do not set boot flag when there is already a partition with the flag (#533658)Hans de Goede2009-11-261-0/+13
| | | | | | | | | | | In F-10 and before we did not set the boot flag for /boot on msdos labels, this could lead to issues when asked to install grub into a partition, or with certain BIOS's which won't boot from a disk when there are no active partitions on the disk. However our new behavior of always setting the boot flag for /boot is wrong for msdos labels too, and is causing various issues, see (amongst others) bug 533658, 530894 and: http://forums.fedoraforum.org/showthread.php?t=231421 http://forums.fedoraforum.org/showthread.php?t=2348
* Don't attempt to get the size of a filesystem unless it's supported (#540598).Chris Lumens2009-11-241-1/+1
| | | | | | | 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.
* Add a function that determines which devices match a given shell glob.Chris Lumens2009-11-201-0/+19
| | | | | | | | | | | | | | This is handy for large configurations so you can specify: clearpart --drives=sda? Instead of: clearpart --drives=sdaa,sdab,sdac,sdad,sdae,sdaf,... All shell globs are supported here, and all the DEVLINKS are checked against the glob. This means you can use /dev/disk/by-path paths without knowing the whole big thing.
* Extend udev_resolve_devspec to allow specifying devices in more ways.Chris Lumens2009-11-201-3/+7
| | | | | | | This allows specifying by anything that could be in DEVLINKS, which includes stuff like UUID a second way, physical device path on the system, serial number, and perhaps other methods depending on what kinds of devices are installed. The next step is making this work throughout kickstart.
* Log calls to DiskLabel's commit and commitToDisk methods.David Lehman2009-11-121-0/+4
|
* Fix DiskLabel.status so it returns True, not self.partedDisk, when active.David Lehman2009-11-121-1/+2
|
* Write /etc/dasd.conf to target system on s390 (#533833).David Cantrell2009-11-124-3/+31
| | | | | | | Similar to what we have to do for zFCP, write /etc/dasd.conf to the target system for all DASD devices that have been used during installation. The device address as well as flags that can be set via sysfs.
* Latest dracut has new syntax for rd_DASD.David Cantrell2009-11-121-23/+5
| | | | | | | | | | | | Upstream accepted my patch to change rd_DASD to specify a single device. If multiple devices need to be brought up at boot time, just give multiple rd_DASD arguments. Syntax is (from dracut.8): rd_DASD=<CCW address>[,readonly=X][,use_diag=X][,erplog=X][,failfast=X] The old rd_DASD has been renamed rd_DASD_MOD and is the same syntax as the dasd kernel module parameter. However, you can only specify a single rd_DASD_MOD parameter at boot time.
* Handle case of not enough space in VG more gracefully. (#533797)David Lehman2009-11-121-1/+5
|
* Make sure partitioning-related drive lists are sorted properly. (#534065)David Lehman2009-11-122-1/+3
|
* Leave one free logical block before each logical partition.David Lehman2009-11-111-0/+6
|
* Use Chunk's geometry attr to access the parted Geometry.David Lehman2009-11-111-1/+2
|
* Fix sorting of requests by mountpoint. It was backwards.David Lehman2009-11-111-1/+1
|
* Align logical partitions' start sector up one logical block for metadata.David Lehman2009-11-111-18/+4
|
* Use parted.Device's sectorSize attr instead of physicalSectorSize.David Lehman2009-11-111-6/+6
|
* Select partition layout based on potential for growth.David Lehman2009-11-111-19/+99
| | | | | | For each partition, choose the free space region that provides the greatest amount of combined growth for the partitions allocated up to that point.
* Reimplement partition growing.David Lehman2009-11-111-180/+411
| | | | | Use Request and Chunk instances to calculate growth for all partitions, then recreates and add the partitions to disk with new geometries.
* Create and use a function to obtain a parted alignment for a disk.David Lehman2009-11-111-0/+19
| | | | | Once the bits are in pyparted this function can be made to actually retrieve a meaningful alignment.
* Create and use a new function to create and add new partitions to disk.David Lehman2009-11-111-29/+38
|
* Make and use a new function to remove non-existent partitions.David Lehman2009-11-111-19/+35
|
* Disable parted's cylinder alignment code.David Lehman2009-11-111-13/+5
| | | | | This also eliminates the need for the min/max constraint when adding a new partition.
* Use new functions for conversion between size and sector count.David Lehman2009-11-111-11/+28
|
* Consider whether a partition is growable when choosing free space.David Lehman2009-11-111-8/+22
| | | | | | For fixed-size requests, choose the smallest suitable region. For growable requests, choose the largest suitable region. For bootable requests, as before, choose the first suitable region.
* Allocate fixed-size requests before growable requests.David Lehman2009-11-111-4/+9
| | | | Also give a little bump based on mountpoint.
* Set boot flag for /boot on mdraid 1 array too (#533533).Radek Vykydal2009-11-111-5/+11
|
* Report no media present for cpqarray controllers with no disks attachedHans de Goede2009-11-111-1/+7
| | | | | | Some drivers (cpqarray <blegh>) make block device nodes for controllers with no disks attached and then report a 0 size, treat this as no media present.
* When creating a new md array check we have enough members (#533027)Hans de Goede2009-11-101-0/+6
| | | | | | | | | Make MDRaidArrayDevice.__init__ raise a value exception when creating a new (so non existing) raid set and there are not enough members for the requested raid level. And catch this value exception in the GUI raid dialog and kickstart raid commands.
* Don't activate / de-activate dmraid sets on setup / teardownHans de Goede2009-11-091-19/+4
| | | | | | | | | | | | | | | | | Since BIOS RAID sets never change there is no need to deactivate them and later activate them again. This also fixes problems in case the followng happens: 1) raid sets get activated, pyblock creates device-mappings for partitions on the set. 2) The partition table changes while exectuing actions 3) the raid sets gets de-activated, because of devicetree.processActions() tearing down everything in response to a disklabel commit error caused by lvm or mdraid using a partiton 4) pyblock tries to remove the partition mappings as it has created them, but the partition table has changed, and when parted commits partition table changes of a dmraid set to disk, it also modifies the partitions device-mappings. pyblock tries to remove a non existing mapping -> backtrace.
* Remove previous mdadm bug 523334 workaorundHans de Goede2009-11-091-12/+1
| | | | | | Since we are no longer stopping / re-starting mdraid container arrays, we no longer need the workaround for the mdadm --stop on containers bug in the MDRaidArrayDevice teardown method.
generated by cgit (git 2.34.1) at 2025-09-01 10:23:12 +0000