#124 Issue `closed`: Unable to copy ipv6.ko module¶

Labels: bug

towster opened issue at 2012-07-12 22:13:¶

I have latest version from git. It fails trying to copy the ipv6.ko file.
I do not believe that I am out of space though I guess it is possible.
I have tried pointing at an NFS server with enough space and got the same error.

# rear -v mkrescue
Relax-and-Recover 1.13.0-git201207121301-git201207121301 / 2012-07-12
Using log file: /var/log/rear/rear-hhidberpt02.log
Creating disk layout
Creating root filesystem layout
Copying files and directories
Copying binaries and libraries
Copying kernel modules
ERROR: [ModulesCopyTo] Could not copy 'lib/modules/2.6.32-100.26.2.el5/kernel/net/ipv6/ipv6.ko' to '/tmp/rear.nfDNpAScBjq7039/rootfs'
Aborting due to an error, check /var/log/rear/rear-hhidberpt02.log for details
Terminated
-------------------------- SNIP from logfile ----------------------------------
.....
mkdir: created directory `/tmp/rear.nfDNpAScBjq7039/rootfs//lib/modules/2.6.32-100.26.2.el5/kernel/drivers/infiniband'
mkdir: created directory `/tmp/rear.nfDNpAScBjq7039/rootfs//lib/modules/2.6.32-100.26.2.el5/kernel/drivers/infiniband/core'
`/lib/modules/2.6.32-100.26.2.el5/kernel/drivers/infiniband/core/ib_addr.ko' -> `/tmp/rear.nfDNpAScBjq7039/rootfs//lib/modules/2.6.32-100.26.2.el5/kernel/drivers/infiniband/core/ib_addr.ko'
`/lib/modules/2.6.32-100.26.2.el5/kernel/drivers/infiniband/core/ib_cm.ko' -> `/tmp/rear.nfDNpAScBjq7039/rootfs//lib/modules/2.6.32-100.26.2.el5/kernel/drivers/infiniband/core/ib_cm.ko'
`/lib/modules/2.6.32-100.26.2.el5/kernel/drivers/infiniband/core/ib_core.ko' -> `/tmp/rear.nfDNpAScBjq7039/rootfs//lib/modules/2.6.32-100.26.2.el5/kernel/drivers/infiniband/core/ib_core.ko'
`/lib/modules/2.6.32-100.26.2.el5/kernel/drivers/infiniband/core/ib_mad.ko' -> `/tmp/rear.nfDNpAScBjq7039/rootfs//lib/modules/2.6.32-100.26.2.el5/kernel/drivers/infiniband/core/ib_mad.ko'
`/lib/modules/2.6.32-100.26.2.el5/kernel/drivers/infiniband/core/ib_sa.ko' -> `/tmp/rear.nfDNpAScBjq7039/rootfs//lib/modules/2.6.32-100.26.2.el5/kernel/drivers/infiniband/core/ib_sa.ko'
`/lib/modules/2.6.32-100.26.2.el5/kernel/drivers/infiniband/core/iw_cm.ko' -> `/tmp/rear.nfDNpAScBjq7039/rootfs//lib/modules/2.6.32-100.26.2.el5/kernel/drivers/infiniband/core/iw_cm.ko'
`/lib/modules/2.6.32-100.26.2.el5/kernel/drivers/infiniband/core/rdma_cm.ko' -> `/tmp/rear.nfDNpAScBjq7039/rootfs//lib/modules/2.6.32-100.26.2.el5/kernel/drivers/infiniband/core/rdma_cm.ko'
mkdir: created directory `/tmp/rear.nfDNpAScBjq7039/rootfs//lib/modules/2.6.32-100.26.2.el5/kernel/drivers/infiniband/ulp'
mkdir: created directory `/tmp/rear.nfDNpAScBjq7039/rootfs//lib/modules/2.6.32-100.26.2.el5/kernel/drivers/infiniband/ulp/iser'
`/lib/modules/2.6.32-100.26.2.el5/kernel/drivers/infiniband/ulp/iser/ib_iser.ko' -> `/tmp/rear.nfDNpAScBjq7039/rootfs//lib/modules/2.6.32-100.26.2.el5/kernel/drivers/infiniband/ulp/iser/ib_iser.ko'
cp: cannot stat `lib/modules/2.6.32-100.26.2.el5/kernel/net/ipv6/ipv6.ko': No such file or directory
Trace: 122 StopIfError /usr/share/rear/lib/_input-output-functions.sh
Trace: 141 ModulesCopyTo /usr/share/rear/lib/linux-functions.sh
Trace: 29 source /usr/share/rear/build/GNU/Linux/40_copy_modules.sh
Trace: 40 Source /usr/share/rear/lib/framework-functions.sh
Trace: 79 SourceStage /usr/share/rear/lib/framework-functions.sh
Trace: 37 WORKFLOW_mkrescue /usr/share/rear/lib/mkrescue-workflow.sh
Trace: 245 main /usr/sbin/rear
2012-07-12 16:56:43 ERROR: [ModulesCopyTo] Could not copy 'lib/modules/2.6.32-100.26.2.el5/kernel/net/ipv6/ipv6.ko' to '/tmp/rear.nfDNpAScBjq7039/rootfs'
2012-07-12 16:56:43 Running exit tasks.
2012-07-12 16:56:43 Finished in 9 seconds
2012-07-12 16:56:43 Removing build area /tmp/rear.nfDNpAScBjq7039
rmdir: removing directory, /tmp/rear.nfDNpAScBjq7039
2012-07-12 16:56:43 End of program reached

--- local.conf file :

OUTPUT=USB
BACKUP_URL=usb:///dev/disk/by-label/RELAXRECOVER
BACKUP=NETFS

towster commented at 2012-07-13 16:49:¶

I started looking more closely at the issue. Apparently that module somehow is missing the leading "/" on the full path.
Just as a test I "cd /" and ran rear again. It completed fine. I dont believe I should be required to cd to / before running rear. If you would like me to test further let me know.