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
"rear recover" can re-create overlapping partitions in case of an extended partition #1718
Comments
attached the full restore log |
Be aware SLES 10 is not official supported anymore by ReaR. |
I think what is missing in general in ReaR are various verification tests In particular there are tests missing that verify |
Only FYI: Also Ubuntu 10.X is not officially supported For me the main question here is if it is worth the effort |
@jsmeix a discussion point for us at Fosdem |
I close it as "won't fix" because while I was working This does of course not mean that I would reject a GitHub pull request that It only means that from my current point of view it looks too complicated |
I think I see now and I can understand what actually went wrong in On the original system the partitions do not overlap The reason is a (from my point of view severe) bug in how One bug was that the extended partition size was not correctly detected Because of the former bug the next bug was that during "rear recover" Accordingly I think this issue here is a real (severe) bug @abbbi In default.conf read the sections about MIGRATION_MODE |
I tested the latest ReaR GitHub master code On my original system I have this sdb # parted -s /dev/sdb unit MiB print Model: ATA QEMU HARDDISK (scsi) Disk /dev/sdb: 2048MiB Sector size (logical/physical): 512B/512B Partition Table: msdos Number Start End Size Type File system Flags 1 8.00MiB 808MiB 800MiB primary ext2 type=83 2 808MiB 1208MiB 400MiB primary linux-swap(v1) type=82 3 1208MiB 1708MiB 500MiB extended lba, type=0f 5 1209MiB 1300MiB 91.0MiB logical ext2 type=83 6 1400MiB 1600MiB 200MiB logical ext2 type=83 4 1800MiB 2000MiB 200MiB primary ext2 type=83 # parted -s /dev/sdb unit B print Model: ATA QEMU HARDDISK (scsi) Disk /dev/sdb: 2147483648B Sector size (logical/physical): 512B/512B Partition Table: msdos Number Start End Size Type File system Flags 1 8388608B 847249407B 838860800B primary ext2 type=83 2 847249408B 1266679807B 419430400B primary linux-swap(v1) type=82 3 1266679808B 1790967807B 524288000B extended lba, type=0f 5 1267728384B 1363148799B 95420416B logical ext2 type=83 6 1468006400B 1677721599B 209715200B logical ext2 type=83 4 1887436800B 2097151999B 209715200B primary ext2 type=83 On the replacement system I have a sdb with same size (also 2 GiB) RESCUE d57:~ # parted -s /dev/sdb unit MiB print Model: ATA QEMU HARDDISK (scsi) Disk /dev/sdb: 2048MiB Sector size (logical/physical): 512B/512B Partition Table: msdos Number Start End Size Type File system Flags 1 8.00MiB 808MiB 800MiB primary type=83 2 808MiB 1208MiB 400MiB primary type=83 3 1208MiB 1708MiB 500MiB extended lba, type=0f 5 1209MiB 1300MiB 91.0MiB logical type=83 6 1400MiB 1600MiB 200MiB logical ext2 type=83 4 1800MiB 2000MiB 200MiB primary ext2 type=83 RESCUE d57:~ # parted -s /dev/sdb unit B print Model: ATA QEMU HARDDISK (scsi) Disk /dev/sdb: 2147483648B Sector size (logical/physical): 512B/512B Partition Table: msdos Number Start End Size Type File system Flags 1 8388608B 847249407B 838860800B primary type=83 2 847249408B 1266679807B 419430400B primary type=83 3 1266679808B 1790967807B 524288000B extended lba, type=0f 5 1267728384B 1363148799B 95420416B logical type=83 6 1468006400B 1677721599B 209715200B logical ext2 type=83 4 1887436800B 2097151999B 209715200B primary ext2 type=83 On the original system only /dev/sdb4 and /dev/sdb6 are mounted # mount | grep sdb /dev/sdb4 on /data.primary4 type ext2 (rw) /dev/sdb6 on /data.logical2 type ext2 (rw) which is the reason why no other filesystems were re-created |
hi,
this should be more a discussion as a issue.
Rear 2.3
Ubuntu 10.X (very old, i know)
While moving a system to another host using REAR i came along this interesting disk layout.
The original disk is formatted like this:
disklayout.conf for this device looks like this:
However, the disk layout recration script fails with:
the commands beeing used are:
i was able to recreate the disks partitions by editing the recovery script and giving it
clear assigments, thus the partitions not overlapping.
The main question here for me is: clearly the disk is partitioned in a very strange way:
either warn the user about a strange disk layout, or even fail? I think that would better than leaving the user with a frustrating situation during restore.
The text was updated successfully, but these errors were encountered: