#461 Issue closed: disk mapping issue after new disk replacement

Labels: enhancement

zsarosi opened issue at 2014-09-18 14:06:

Hi!

I use rear v1.14, but the cause of the problem (mapping script) is the same in v1.16.
Situation:
disk /dev/sda 34359738368 msdos
disk /dev/sdb 34359738368 msdos

In case of emergency, if disk sda is replaced by a different one (size: 51539607552), the disk mapping script(/usr/share/rear/layout/prepare/default/30_map_disks.sh) generates the following mapping:
This is the disk mapping table:
/dev/sda /dev/sdb
/dev/sdb /dev/sdb

Which is clearly a bad idea. Expected would be the keep the mapping for sdb and map sda on the new bigger disk (maybe after asking) or at least quit with an error.

gdha commented at 2014-09-19 06:59:

@zsarosi I do not mind to accept a pull request with better code. We as a community do our best to keep up with the issues, however if you find the time I wouldn't mind to hear your ideas.

zsarosi commented at 2014-09-19 10:56:

Hi gdha! The pull request was a misstake, I dind't want to fork an own git branch, I was just clicking on the false button. Can I undo it?

gdha commented at 2014-09-19 13:00:

I cannot see anything...

On Fri, Sep 19, 2014 at 12:56 PM, zsarosi notifications@github.com wrote:

Hi gdha! The pull request was a misstake, I dind't want to fork an own git
branch, I was just clicking on the false button. Can I undo it?

—
Reply to this email directly or view it on GitHub
https://github.com/rear/rear/issues/461#issuecomment-56163199.

gdha commented at 2014-10-07 11:37:

@zsarosi did you know you can predefine your disk mapping? Just create a file /etc/rear/mappings/disk_deviceswith your preference.

gdha commented at 2016-08-31 12:41:

Outdated issue

[Export of Github issue for rear/rear.]