YaST Development January 2018

yast-devel@lists.opensuse.org

7 participants
28 discussions

Start a nNew thread

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 22 Jan '18

22 Jan '18

1 0

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 19 Jan '18

19 Jan '18

1 0

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 18 Jan '18

18 Jan '18

1 0

[yast-devel] Alignment of the last partition
by Ancor Gonzalez Sosa 17 Jan '18

17 Jan '18

This question has been raised in IRC many times during storage-ng development, with no satisfactory answer so far. But now we need to take a decision at last. Storage-ng always tries to align the start and end of all new and resized partitions for optimal performance. In addition to that, there is also a given alignment that has to be respected for the whole thing to work (leaving performance aside). See [1] for more info. For example, in the case of a typical GPT partition table in a typical disk, the REQUIRED grain would be 1B (so we can create a partition of any size), but the OPTIMAL grain is 1MiB (so we try to only distribute the space in virtual "disk slices" of 1MiB). In DASD, the typical REQUIRED grain is 48KiB, so no way we can create a partition whose size is not divisible by that number. In addition, the OPTIMAL grain is 3MiB. The point is that I'm not so sure whether aligning the end makes that much sense from the performance POV if a given partition is at the very end of the partition table. Two cases: ========== 1) GPT partition tables. In GPT the last 16.5KiB are always reserved (a backup of the partition table). Let's say the user decides to create a partition using all the available space at the end (or simply a big partition using the whole disk). A very common scenario. What should we do? Persist in our attempt to have everything aligned and leave a gap of 1007.5Kib at the end or really use the space up until the end? If GPT is designed to always have those 16.5KiB stripped from the useful space, I would assume that having a last "slice" of 1007.5Kib instead of 1MiB shouldn't imply a performance penalty. Otherwise, the GPT design is rather... well... not-smart. 2) DASD partition tables. A similar thing happens with DASD. In many situations, the remaining space at the end of the disk is not divisible by 3MiB. Do we want to leave the remainder space unused? If we decide to use also those, let's say, 2MiB at the end of the disk, would we be introducing a performance problem or that rule does not apply to partitions at the end of the disk? Even further, it is possible than the remainder is not divisible by the REQUIRED grain of 48KiB? I wouldn't expect that to happen, but these eyes have seen so many things... ;-) In short: ========= For a partition trying to use the space at the end of the disk: 1) Should we give up on optimal alignment and use REQUIRED alignment for that case? If we do so, would it have any performance impact? 2) Should we, instead, stick to the OPTIMAL alignment also for that final partition and leave gaps at the end of all GPT and many (most) DASDs? 3) Should we even go further than (1) and completely ignore alignment (even the REQUIRED one) assuming that partition tables can always be used up to the end? (Who would build a disk with unusable space after all ;-) ). Thanks guys for the replies. https://github.com/openSUSE/libstorage-ng/blob/master/doc/alignment.md -- Ancor González Sosa YaST Team at SUSE Linux GmbH -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

5 6

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 17 Jan '18

17 Jan '18

1 0

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 16 Jan '18

16 Jan '18

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-add-on: - [WIP] Ask when the added repository is unsigned (bsc#1009127) (342 days) https://github.com/yast/yast-add-on/pull/37 Pending requests in repository yast-bootloader: - don't create grub_installdevice and let perl-Bootloader run grub2-install (286 days) https://github.com/yast/yast-bootloader/pull/413 Pending requests in repository yast-branding: - This repo is obsoleted by yast-theme (47 days) https://github.com/yast/yast-branding/pull/4 Pending requests in repository yast-country: - Keyboard rewrite: Load keyboard layouts (31 days) https://github.com/yast/yast-country/pull/144 Pending requests in repository yast-installation: - Disable plymouth by a no affend method, it will not block tty device activation at first time user login(bsc#1042554). (147 days) https://github.com/yast/yast-installation/pull/584 Pending requests in repository yast-ldap: - Manipulate system LDAP configuration rather than application LDAP configuration (286 days) https://github.com/yast/yast-ldap/pull/26 Pending requests in repository yast-live-installer: - - Use /etc/products.d/openSUSE.prod as /etc/products.d/baseproduct (215 days) https://github.com/yast/yast-live-installer/pull/14 Pending requests in repository yast-mail: - [WIP] return back MailTable to yast2-mail module from yast2 module (285 days) https://github.com/yast/yast-mail/pull/25 Pending requests in repository yast-multipath: - fix ycp killing bug with changing \r with space (203 days) https://github.com/yast/yast-multipath/pull/19 Pending requests in repository yast-network: - Drop replace direct access to LanItems::Items whenever it is possible. (54 days) https://github.com/yast/yast-network/pull/588 - Improved device name collision recognition in autoinstallation (35 days) https://github.com/yast/yast-network/pull/583 Pending requests in repository yast-packager: - Display the product license at upgrade (bsc#1069124) (26 days) https://github.com/yast/yast-packager/pull/305 - [WIP] Ask when the added repository is unsigned (bsc#1009127) (341 days) https://github.com/yast/yast-packager/pull/230 Pending requests in repository yast-security: - [WIP] refactoring autoconverted ruby code into ruby code (278 days) https://github.com/yast/yast-security/pull/40 Pending requests in repository yast-storage: - fixed missing changes (109 days) https://github.com/yast/yast-storage/pull/292 - Bsc 1049108 sle12 sp3 (179 days) https://github.com/yast/yast-storage/pull/283 Pending requests in repository yast-users: - Reduce perl (286 days) https://github.com/yast/yast-users/pull/137 Pending requests in repository yast-yast2: - log calculated proposal in yaml format into separate files (fate#318196) (77 days) https://github.com/yast/yast-yast2/pull/633 - Fall back to smaller and/or hicolor icon if the icon can't be found. (138 days) https://github.com/yast/yast-yast2/pull/616 - Point users of CWMServiceStart to the replacement API. (125 days) https://github.com/yast/yast-yast2/pull/602 - [WIP] Drop perl (287 days) https://github.com/yast/yast-yast2/pull/540 - [WIP] Support for unsigned repositories (bsc#1009127) (285 days) https://github.com/yast/yast-yast2/pull/537 Pending requests in repository yast-rear: - [PoC] Travis integration tests (83 days) https://github.com/yast/yast-rear/pull/8 Pending requests in repository yast-samba-client: - add checkbox for the net ads join --no-dns-updates switch (285 days) https://github.com/yast/yast-samba-client/pull/48 - update idmap config syntax (285 days) https://github.com/yast/yast-samba-client/pull/47 Pending requests in repository yast-services-manager: - fix setting default target from control file (bsc#1064876) (77 days) https://github.com/yast/yast-services-manager/pull/134 - [WIP] AutoYaST X11 test (185 days) https://github.com/yast/yast-services-manager/pull/125 Pending requests in repository skelcd-control-openSUSE: - Use $releasever in repo urls (boo#853820) (28 days) https://github.com/yast/skelcd-control-openSUSE/pull/101 - /var/lib/ceph as btrfs subvolume with CoW disabled (bsc#1013011) (25 days) https://github.com/yast/skelcd-control-openSUSE/pull/99 Pending requests in repository skelcd-control-SLES: - Display the product license at upgrade (bsc#1069124) (26 days) https://github.com/yast/skelcd-control-SLES/pull/100 Pending requests in repository skelcd-control-SLED: - Display the product license at upgrade (bsc#1069124) (26 days) https://github.com/yast/skelcd-control-SLED/pull/70 - /var/lib/ceph as btrfs subvolume with CoW disabled (bsc#1013011) (25 days) https://github.com/yast/skelcd-control-SLED/pull/67 Pending requests in repository yast-auth-server: - Drop ca mgm (287 days) https://github.com/yast/yast-auth-server/pull/21 Pending requests in repository yast-docker: - Hw15/enavarro (27 days) https://github.com/yast/yast-docker/pull/14 Pending requests in repository yast-vpn: - Remove integration with SUSEFirewall in preparation for working with … (66 days) https://github.com/yast/yast-vpn/pull/6 Pending requests in repository yast-storage-ng: - Legacy boot flag in proposal (187 days) https://github.com/yast/yast-storage-ng/pull/307 Pending requests in repository aytests-tests: - [WIP] Added test for product selection when explicitly set in the profile (69 days) https://github.com/yast/aytests-tests/pull/102 - update fix (236 days) https://github.com/yast/aytests-tests/pull/71 ERROR: API query limit exceeded -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 15 Jan '18

15 Jan '18

1 0

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 12 Jan '18

12 Jan '18

1 0

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 11 Jan '18

11 Jan '18

1 0

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 10 Jan '18

10 Jan '18

1 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

YaST Development January 2018