#219 Issue closed: Unable to Find Start for dm-1¶
Labels: waiting for info, support / question
LuckyLeavell opened issue at 2013-04-05 18:38:¶
ReaR version: 1.14
OS: RHEL5.9
Envronment: Multipath boot from SAN
Contents of /etc/rear/local.conf:
# Create Relax-and-Recover rescue media as ISO image
OUTPUT=ISO
BACKUP=NBU
AUTOEXCLUDE_MULTIPATH=
EXCLUDE_MOUNTPOINTS=()
AUTOEXCLUDE_PATH=( /media /mnt /external )
PROGS=( multipath multipathd scsi_id )
COPY_AS_IS=( /etc/multipath/bindings )
From /var/log/rear/rear-nbutestb.log with debugging turned on:
++ partition_name=/dev/mapper/mpath0p1
++ partition_name=mapper/mpath0p1
++ partition_name=mpath0p1
+++ echo mpath0p1
+++ grep -E -o '[0-9]+$'
++ partition_nr=1
++ partition_prefix=mpath0p
+++ get_disk_size dm-1
+++ local disk_name=dm-1
++++ get_block_size dm-1
++++ '[' -r /sys/block/dm-1/queue/logical_block_size ']'
++++ echo 512
+++ local block_size=512
+++ '[' -r /sys/block/dm-1/size ']'
+++ BugIfError 'Could not determine size of disk dm-1, please file a bug.'
+++ (( 0 != 0 ))
+++ local nr_blocks=530082
+++ local disk_size=271401984
+++ echo 271401984
++ size=271401984
++ [[ -r /sys/block/dm-1/start ]]
++ Log 'Could not determine start of partition mpath0p1.'
++ test 1 -gt 0
+++ Stamp
+++ date '+%Y-%m-%d %H:%M:%S '
++ echo '2013-04-04 16:14:19 Could not determine start of partition mpath0p1.'
2013-04-04 16:14:19 Could not determine start of partition mpath0p1.
There is no start parameter for /sys/block/dm-1:
[root@nbutestb ~]# ll /sys/block/dm-1/
total 0
-r--r--r-- 1 root root 4096 Apr 4 14:37 dev
drwxr-xr-x 2 root root 0 Apr 4 14:37 holders
-r--r--r-- 1 root root 4096 Apr 4 14:37 range
-r--r--r-- 1 root root 4096 Apr 4 14:37 removable
-r--r--r-- 1 root root 4096 Apr 4 14:37 size
drwxr-xr-x 2 root root 0 Apr 4 14:37 slaves
-r--r--r-- 1 root root 4096 Apr 4 14:37 stat
lrwxrwxrwx 1 root root 0 Apr 4 14:37 subsystem -> ../../block
--w------- 1 root root 4096 Apr 4 14:37 uevent
There are several BugIfError lines. I can upload the entire log file but do not know how.
gdha commented at 2013-06-12 06:55:¶
Seems this issue was hidden - sorry - didn't catch it.
Can you execute ll /dev/disk/by-* ? And show the content of
ls -l /dev/mapper
dagwieers commented at 2013-06-29 08:19:¶
@LuckyLeavell To clarify, the BugIfError is not a problem, it is only a problem when the previous statement failed. So these statements are markers for us where we check if the previous statement worked correctly, and if not we escalate the problem. Pretty much like how the assert statement works in some programming languages (although this function only considers the return code).
gdha commented at 2013-10-11 13:56:¶
@LuckyLeavell is this still relevant? Perhaps try the latest snapshot as there a patch in it for finding the real multipath device. Would be nice to hear if it works or not?
gdha commented at 2013-11-04 15:32:¶
seems a dead issue - I'll close it - if required please re-open it.
[Export of Github issue for rear/rear.]