New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem with making backup on S390X architecture #781

Closed
phracek opened this Issue Feb 17, 2016 · 2 comments

Comments

Projects
None yet
2 participants
@phracek
Contributor

phracek commented Feb 17, 2016

I have run the backup like obvious rear -v mkbackup but it doesn 't create a ISO image at all.
rear version:
rear-1.17.2-4.el6.s390x

# uname -a
Linux ibm-z10-52.rhts.eng.bos.redhat.com 2.6.32-573.el6.s390x #1 SMP Wed Jul 1 18:26:59 EDT 2015 s390x s390x s390x GNU/Linux
#

As you can see genisoimage binary is available on my S390X system:

# ls -la /usr/bin/mkisofs
lrwxrwxrwx. 1 root root 25 Feb 16 03:28 /usr/bin/mkisofs -> /etc/alternatives/mkisofs
# ls -la /etc/alternatives/mkisofs
lrwxrwxrwx. 1 root root 20 Feb 16 03:28 /etc/alternatives/mkisofs -> /usr/bin/genisoimage
# 

I have found that the last messages from log are from ./lib/framwork-functions.sh
Logs from backup.

# rear -v mkbackup
Relax-and-Recover 1.17.2 / Git
Using log file: /var/log/rear/rear-ibm-z10-52.log
Creating disk layout
Creating root filesystem layout
Copying files and directories
Copying binaries and libraries
Copying kernel modules
Creating initramfs
# 

The problematic parts which I have found from log file are:

2016-02-17 03:40:25 Including layout/save/default/45_check_bootloader_files.sh
cat: /var/lib/rear/recovery/bootloader: No such file or directory
2016-02-17 03:40:25 Including layout/save/default/45_check_network_files.sh
2016-02-17 03:40:26 Including rescue/GNU/Linux/50_clone_keyboard_mappings.sh
Couldn't get a file descriptor referring to the console
2016-02-17 03:40:26 Including rescue/default/50_ssh.sh
2016-02-17 03:18:50 Including backup/default/00_valid_backup_methods.sh
2016-02-17 03:18:50 Finished running 'backup' stage in 0 seconds
2016-02-17 03:18:50 Finished running mkbackup workflow
2016-02-17 03:18:50 Running exit tasks.
rmdir: removing directory, `/tmp/rear.cjkmgymviIqDVNL/outputfs'
rmdir: failed to remove `/tmp/rear.cjkmgymviIqDVNL/outputfs': Directory not empty
2016-02-17 03:18:50 Finished in 15 seconds
2016-02-17 03:18:50 Removing build area /tmp/rear.cjkmgymviIqDVNL
rmdir: removing directory, `/tmp/rear.cjkmgymviIqDVNL'
2016-02-17 03:18:50 End of program reached

Do you know what's going on?

It seems that it is relevant only for S390X architecture.

I will send you a PR soon.
But ISO image is not generated at all.

@phracek phracek changed the title from Problem with making backup to Problem with making backup on S390X architecture Feb 17, 2016

@phracek

This comment has been minimized.

Show comment
Hide comment
@phracek

phracek Feb 17, 2016

Contributor

Pull Request for this is #782

Contributor

phracek commented Feb 17, 2016

Pull Request for this is #782

@gdha gdha added the enhancement label Feb 17, 2016

@gdha

This comment has been minimized.

Show comment
Hide comment
@gdha

gdha Feb 17, 2016

Member

@phracek The problem is that there is nothing yet written to create an ISO image for ARCH = Linux-s390x. If we compare Linux-i386:

Source prep/ISO/default/30_check_iso_dir.sh
Source prep/ISO/default/32_check_cdrom_size.sh
Source prep/ISO/GNU/Linux/32_verify_mkisofs.sh
Source prep/ISO/Linux-i386/33_find_isolinux.sh
Source prep/ISO/GNU/Linux/34_add_isofs_module.sh
Source output/ISO/Linux-i386/20_mount_efibootimg.sh
Source output/ISO/Linux-i386/25_populate_efibootimg.sh
Source output/ISO/Linux-i386/30_create_isolinux.sh
Source output/ISO/Linux-i386/70_umount_efibootimg.sh
Source output/ISO/Linux-i386/80_create_isofs.sh
Source output/ISO/Linux-i386/81_prepare_multiple_iso.sh
Source output/ISO/Linux-i386/82_create_iso_image.sh
Source output/ISO/Linux-i386/85_check_for_errors.sh

with Linux-s390x we have:

Source prep/ISO/default/30_check_iso_dir.sh
Source prep/ISO/default/32_check_cdrom_size.sh
Source prep/ISO/GNU/Linux/32_verify_mkisofs.sh
Source prep/ISO/GNU/Linux/34_add_isofs_module.sh

Unfortunately, I have no experience with building bootable ISO images on a Linux-s390x architecture. I guess within RedHat there must be some-one who knows, no?
I was able to see this via LinuxOne OpenStack infrastructure (however, cannot test any recover).

PS: did you inspect the /var/lib/rear/layout/disklayout.conf file? Does it look sane? If not, perhaps open another issue to keep this separate.

Member

gdha commented Feb 17, 2016

@phracek The problem is that there is nothing yet written to create an ISO image for ARCH = Linux-s390x. If we compare Linux-i386:

Source prep/ISO/default/30_check_iso_dir.sh
Source prep/ISO/default/32_check_cdrom_size.sh
Source prep/ISO/GNU/Linux/32_verify_mkisofs.sh
Source prep/ISO/Linux-i386/33_find_isolinux.sh
Source prep/ISO/GNU/Linux/34_add_isofs_module.sh
Source output/ISO/Linux-i386/20_mount_efibootimg.sh
Source output/ISO/Linux-i386/25_populate_efibootimg.sh
Source output/ISO/Linux-i386/30_create_isolinux.sh
Source output/ISO/Linux-i386/70_umount_efibootimg.sh
Source output/ISO/Linux-i386/80_create_isofs.sh
Source output/ISO/Linux-i386/81_prepare_multiple_iso.sh
Source output/ISO/Linux-i386/82_create_iso_image.sh
Source output/ISO/Linux-i386/85_check_for_errors.sh

with Linux-s390x we have:

Source prep/ISO/default/30_check_iso_dir.sh
Source prep/ISO/default/32_check_cdrom_size.sh
Source prep/ISO/GNU/Linux/32_verify_mkisofs.sh
Source prep/ISO/GNU/Linux/34_add_isofs_module.sh

Unfortunately, I have no experience with building bootable ISO images on a Linux-s390x architecture. I guess within RedHat there must be some-one who knows, no?
I was able to see this via LinuxOne OpenStack infrastructure (however, cannot test any recover).

PS: did you inspect the /var/lib/rear/layout/disklayout.conf file? Does it look sane? If not, perhaps open another issue to keep this separate.

@gdha gdha closed this in 757b57b Feb 17, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment