Problem with iso generation (long time and wrong size)

Marco Marino <[email protected]>
Newsgroups gmane.linux.mondo.devel
Message-ID <CAFHVVuJkTziGPQ6OibM2rvazTtx2QHqXkO_bNB-O-tHBLb+EZw@mail.gmail.com>
Hi, I'm new to mondoarchive/mondorescue so I'm sorry if this is a stupid
question.
I'm trying to use mondo archive with (in a perl script)

system 'mondoarchive -O -6 -s 4400m -n
nfs://backup.myserver.org:/storage/iso/smtpserver
-d /iso_'.$dt.'  -E
"/tmp|/mnt/nfs|/mnt/cdrom|/var/MailRoot/spool|/var/MailRoot/logs"';

but I have some questions:

1) it seems that .iso size is only 2.3G and not 4.4 as indicated by -s .
Why?
2) I have a message: ---progress-form---4--- TASK:  [*...................]
  1% done; 2076:54 to go

It seems a long time for a disk like this:
[root@smtp ~]# df -Th
Filesystem    Type    Size  Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol01
              ext3    456G   51G  382G  12% /
/dev/sda1     ext3    122M   38M   78M  33% /boot
tmpfs        tmpfs   1013M     0 1013M   0% /dev/shm
backup.myserver.org:/storage/iso/smtpserver
               nfs    7.2T  5.9T  957G  87% /mnt/nfs
[root@smtp ~]#


more than 30 hours for the iso?? on other servers with similar size it
needs only 4/6 hours...  why?

3) In mondoarchive.log I have a lot of
File descriptor 5 (/var/log/mondoarchive.log) leaked on lvm invocation.
Parent PID 19620: /bin/bash
File descriptor 6 (/var/log/mondoarchive.log) leaked on lvm invocation.
Parent PID 19620: /bin/bash
File descriptor 3 (/tmp/mondo.tmp.DON0A7 (deleted)) leaked on lvm
invocation. Parent PID 19972: /bin/bash
File descriptor 4 (/tmp/mondo.scratch.TsrFvu (deleted)) leaked on lvm
invocation. Parent PID 19972: /bin/bash
File descriptor 5 (/var/log/mondoarchive.log) leaked on lvm invocation.
Parent PID 19972: /bin/bash
File descriptor 6 (/var/log/mondoarchive.log) leaked on lvm invocation.
Parent PID 19972: /bin/bash
File descriptor 3 (/tmp/mondo.tmp.DON0A7 (deleted)) leaked on lvm
invocation. Parent PID 19991: /bin/bash
File descriptor 4 (/tmp/mondo.scratch.TsrFvu (deleted)) leaked on lvm
invocation. Parent PID 19991: /bin/bash
File descriptor 5 (/var/log/mondoarchive.log) leaked on lvm invocation.
Parent PID 19991: /bin/bash
File descriptor 6 (/var/log/mondoarchive.log) leaked on lvm invocation.
Parent PID 19991: /bin/bash
File descriptor 3 (/tmp/mondo.tmp.DON0A7 (deleted)) leaked on lvm
invocation. Parent PID 20339: /bin/bash
File descriptor 4 (/tmp/mondo.scratch.TsrFvu (deleted)) leaked on lvm
invocation. Parent PID 20339: /bin/bash
File descriptor 5 (/var/log/mondoarchive.log) leaked on lvm invocation.
Parent PID 20339: /bin/bash
File descriptor 6 (/var/log/mondoarchive.log) leaked on lvm invocation.
Parent PID 20339: /bin/bash
File descriptor 3 (/tmp/mondo.tmp.DON0A7 (deleted)) leaked on lvm
invocation. Parent PID 20339: /bin/bash
File descriptor 4 (/tmp/mondo.scratch.TsrFvu (deleted)) leaked on lvm
invocation. Parent PID 20339: /bin/bash
File descriptor 5 (/var/log/mondoarchive.log) leaked on lvm invocation.
Parent PID 20339: /bin/bash
File descriptor 6 (/var/log/mondoarchive.log) leaked on lvm invocation.
Parent PID 20339: /bin/bash


Is this a problem? Why this happens on this server and not on other with
same rpm versions?


mondo = 3.2.2-1.rhel5
mindi = 3.0.2-1.rhel5
mindi-busybox = 1.21.1-1.rhel5
mkisofs = 2.01-10.7.el5
kernel  2.6.18-371.12.1.el5  (CentOS 5.11)


Thank you

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot

_______________________________________________
Mondo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mondo-devel
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.