multiCD package
I'm trying to use multiCD (for the first time) to do some backups with. I
think I've configured everything correctly but I'm seeing a strange error
message causing the backup to fail.
Here is the multiCD output:
# multiCD
-- Options --
Files to backup:
'/backup'
Files to exclude:
'/root/disks/mount'
'/root/multiCD_imageA'
'/root/multiCD_imageB'
All the rest:
addfiles: '0'
cd_dev: '/dev/burner'
cd_done: 'cdrecord dev=1,1,0 -eject'
cd_mount: '/root/disks/mount'
cd_size: '681574400'
cdrecord: 'cdrecord -v blank=fast speed=8 dev=1,1,0 -data'
check_config: '0'
first_disc: '0'
fs_type: 'ext2'
help: '0'
image_file1: '/root/multiCD_imageA'
image_file2: '/root/multiCD_imageB'
image_mount: '/root/disks/mount/'
mkfs_opts: '-m 0 -b 1024'
multi: '0'
noburn: '1'
only_one: '0'
-- Options --
Creating a new image file. This takes a while...
Creating ext2 filesystem on image file...
mke2fs 1.25 (20-Sep-2001)
/root/multiCD_imageA1 is not a block special device.
Proceed anyway? (y,n) Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
83312 inodes, 665600 blocks
0 blocks (0.00%) reserved for the super user
First data block=1
82 block groups
8192 blocks per group, 8192 fragments per group
1016 inodes per group
Superblock backups stored on blocks:
8193, 24577, 40961, 57345, 73729, 204801, 221185, 401409, 663553
Writing inode tables: done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 32 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
ioctl: LOOP_SET_FD: Device or resource busy
ioctl: LOOP_SET_FD: Device or resource busy
ioctl: LOOP_SET_FD: Device or resource busy
ioctl: LOOP_SET_FD: Device or resource busy
Copying files to CD image...
umount: /root/disks/mount/: not mounted
couldn't umount /root/disks/mount/
#
At this point it has stopped without doing the backup. It looks to me
like it failed to mount the CD image as a loopback device but I have no
clue why this would be happening.
I should probably mention that this system is using alot of loopback
devices already. See:
# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 55G 41G 12G 77% /
/debian/binary1.iso 640M 641M 0 100% /debian/binary1
/debian/binary2.iso 643M 644M 0 100% /debian/binary2
/debian/binary3.iso 553M 553M 0 100% /debian/binary3
/debian/source1.iso 643M 644M 0 100% /debian/source1
/debian/source2.iso 645M 646M 0 100% /debian/source2
/debian/source3.iso 638M 639M 0 100% /debian/source3
#
# ll /dev/loop*
brw-rw---- 1 root disk 7, 0 Dec 10 17:38 /dev/loop0
brw-rw---- 1 root disk 7, 1 Dec 10 17:38 /dev/loop1
brw-rw---- 1 root disk 7, 2 Dec 10 17:38 /dev/loop2
brw-rw---- 1 root disk 7, 3 Dec 10 17:38 /dev/loop3
brw-rw---- 1 root disk 7, 4 Dec 10 17:38 /dev/loop4
brw-rw---- 1 root disk 7, 5 Dec 10 17:38 /dev/loop5
brw-rw---- 1 root disk 7, 6 Dec 10 17:38 /dev/loop6
brw-rw---- 1 root disk 7, 7 Dec 10 17:38 /dev/loop7
#
# ll /debian
total 3.7G
-rw-r--r-- 1 root root 943 May 3 2001 CONTENTS
-rw-r--r-- 1 root root 907 May 3 2001 CONTENTS.old
dr-xr-xr-x 10 root root 4.0k Dec 7 2000 binary1/
-rw-r--r-- 1 root root 640M Mar 24 2001 binary1.iso
dr-xr-xr-x 6 root root 2.0k Dec 7 2000 binary2/
-rw-r--r-- 1 root root 643M Mar 24 2001 binary2.iso
dr-xr-xr-x 5 root root 2.0k Dec 7 2000 binary3/
-rw-r--r-- 1 root root 553M Mar 24 2001 binary3.iso
dr-xr-xr-x 5 root root 2.0k Dec 7 2000 source1/
-rw-r--r-- 1 root root 643M Mar 25 2001 source1.iso
dr-xr-xr-x 5 root root 2.0k Dec 7 2000 source2/
-rw-r--r-- 1 root root 645M Mar 25 2001 source2.iso
dr-xr-xr-x 5 root root 2.0k Dec 7 2000 source3/
-rw-r--r-- 1 root root 638M Mar 25 2001 source3.iso
#
Anyone got a clue what is happening to me?
Thanks in advance,
Shawn Yarbrough
shawn@nailstorm.com
Reply to: