Sven Schnelle 41108c98aa zipl: move mkfs to ngdump prepare script ...

The current code first assembles the ngdump init ramdisk, and creates
the filesystem on the dump disk afterwards. ngdump uses uuids to mount
the dump device. Because the filesystem uuid is changing with the final
mkfs, ngdump has to use the partuuid of the device. This does work for
nvme, but not for dasds. Another problem is that dryrun likely wouldn't
work if there's no partition table on the dump device. To fix these
issues, move the mkfs to the ngdump helper script so we can use the
filesystem uuid. When --dryrun is specified the script passes /dev/null
as ngdump device to make mkinitramfs happy. As the initramdisk is never
used in this case, this shouldn't be a problem.

Signed-off-by: Sven Schnelle <svens@linux.ibm.com>
Acked-by: Stefan Haberland <sth@linux.ibm.com>
Signed-off-by: Steffen Eiden <seiden@linux.ibm.com>

2023-05-26 12:21:04 +02:00

..

hooks

zipl: Add initramfs-tools module for NGDump

2022-06-20 13:14:05 +02:00

scripts/init-premount

zipl: Add initramfs-tools module for NGDump

2022-06-20 13:14:05 +02:00

Makefile

zipl: Implement zipl helper script for NGDump

2022-06-20 13:14:05 +02:00

zipl_helper.prepare-ngdump

zipl: move mkfs to ngdump prepare script

2023-05-26 12:21:04 +02:00