[rear-devel] [rear/rear] ec8a5c: First attempt to implement layout/save/default/950...

Johannes Meixner noreply at github.com
Tue Mar 5 11:25:21 CET 2019


  Branch: refs/heads/master
  Home:   https://github.com/rear/rear
  Commit: ec8a5c6ffe1a5dc2f0da5c0f2560a94230b21520
      https://github.com/rear/rear/commit/ec8a5c6ffe1a5dc2f0da5c0f2560a94230b21520
  Author: Johannes Meixner <jsmeix at suse.de>
  Date:   2019-02-28 (Thu, 28 Feb 2019)

  Changed paths:
    A usr/share/rear/layout/save/default/950_verify_disklayout_file.sh
    M usr/share/rear/lib/global-functions.sh

  Log Message:
  -----------
  First attempt to implement layout/save/default/950_verify_disklayout_file.sh that verifies the disklayout file


  Commit: 6538177ac564311c16afd7728927e8712bf3c99b
      https://github.com/rear/rear/commit/6538177ac564311c16afd7728927e8712bf3c99b
  Author: Johannes Meixner <jsmeix at suse.de>
  Date:   2019-02-28 (Thu, 28 Feb 2019)

  Changed paths:
    M usr/share/rear/layout/save/default/950_verify_disklayout_file.sh

  Log Message:
  -----------
  Added testing consecutive partitions for MBR partitioning scheme to verify disklayout.conf


  Commit: 4db41676bb0d220d12b573b75d4e1f862a7a3b2c
      https://github.com/rear/rear/commit/4db41676bb0d220d12b573b75d4e1f862a7a3b2c
  Author: Johannes Meixner <jsmeix at suse.de>
  Date:   2019-03-01 (Fri, 01 Mar 2019)

  Changed paths:
    M usr/share/rear/conf/default.conf
    M usr/share/rear/layout/save/default/950_verify_disklayout_file.sh

  Log Message:
  -----------
  Fixed testing for consecutive partitions


  Commit: 561c7482063b9570231f18c44d33058c264dc205
      https://github.com/rear/rear/commit/561c7482063b9570231f18c44d33058c264dc205
  Author: Johannes Meixner <jsmeix at suse.de>
  Date:   2019-03-01 (Fri, 01 Mar 2019)

  Changed paths:
    M usr/share/rear/layout/save/default/950_verify_disklayout_file.sh

  Log Message:
  -----------
  Aviod @gozora OCD suffering ;-)


  Commit: 703d5549ca24ecf2b7b4aaa518746b332e17f1d6
      https://github.com/rear/rear/commit/703d5549ca24ecf2b7b4aaa518746b332e17f1d6
  Author: Johannes Meixner <jsmeix at suse.de>
  Date:   2019-03-01 (Fri, 01 Mar 2019)

  Changed paths:
    M usr/share/rear/layout/save/default/950_verify_disklayout_file.sh

  Log Message:
  -----------
  Fixed testing for non consecutive partitions for GPT (it still needs to be fixed for MBR)


  Commit: 20a3b3bc7caa9a0fd00c7bc3dc7f95185d76e00f
      https://github.com/rear/rear/commit/20a3b3bc7caa9a0fd00c7bc3dc7f95185d76e00f
  Author: Johannes Meixner <jsmeix at suse.de>
  Date:   2019-03-01 (Fri, 01 Mar 2019)

  Changed paths:
    M usr/share/rear/layout/save/default/950_verify_disklayout_file.sh

  Log Message:
  -----------
  Fixed testing for non consecutive partitions for MBR


  Commit: 36073a2f59487741b20fe1a2f7a22fdc14688215
      https://github.com/rear/rear/commit/36073a2f59487741b20fe1a2f7a22fdc14688215
  Author: Johannes Meixner <jsmeix at suse.com>
  Date:   2019-03-05 (Tue, 05 Mar 2019)

  Changed paths:
    M usr/share/rear/conf/default.conf
    A usr/share/rear/layout/save/default/950_verify_disklayout_file.sh
    M usr/share/rear/lib/global-functions.sh

  Log Message:
  -----------
  Merge pull request #2060 from jsmeix/new_verify_disklayout_file_script_issues_1681_and_2006

New verify script layout/save/default/950_verify_disklayout_file.sh
to verify disklayout.conf that was created by "rear mkrescue/mkbackup".
Currently only some very basic verification is implemented: It only verifies that
the 'disk' entries look sytactically correct (only basic value type testing),
the 'part' entries look sytactically correct (only basic value type testing),
the 'part' entries specify consecutive partitions.
The latter is needed to make ReaR more fail-safe in case of sparse partition
schemes (i.e. when there are non-consecutive partitions) because currently
"rear recover" fails when there are non-consecutive partitions,
see https://github.com/rear/rear/issues/1681
and the related https://github.com/rear/rear/issues/1771
In general verification of the created disklayout.conf should help to avoid
that the user gets failures when it is too late when "rear recover" fails. Now
it errors out early when things cannot work during "rear mkrescue/mkbackup",
see https://github.com/rear/rear/issues/2006#issuecomment-458577661
and https://github.com/rear/rear/issues/2006#issuecomment-460646685
and https://github.com/rear/rear/wiki/Developers-Guide


Compare: https://github.com/rear/rear/compare/345c7dec9977...36073a2f5948


More information about the rear-devel mailing list