Custom Query (684 matches)
Results (40 - 42 of 684)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#74 | fixed | Mondo hangs at at libmondo-devices.c:1631 in mount_CDROM_here | ||
Description |
I run Mondo on several servers daily. This probably is mostly seen on one server, but I've seen it on another server too. The first symptom of the problem is that /var is filling up. Why? Because since I run mondo via cron, the output is sent by e-mail. So a very big file can be found in /var/spool/clientmqueue. If I check the content of this big file, I find this: ---promptstring---1--- CD-ROM device ---promptstring---2--- Please enter your CD-ROM's /dev device ---promptstring---Q--- --> ASSERTION FAILED: `device[0]!='\0'' at libmondo-devices.c:1631 in mount_CDROM_here (I)gnore, ignore (A)ll, (D)ebug, a(B)ort, or (E)xit? Invalid choice. Invalid choice. Invalid choice. Invalid choice. Invalid choice. Invalid choice. Invalid choice. In /var/log/message, there is: Sep 13 02:01:07 bibitte kernel: attempt to access beyond end of device Sep 13 02:01:08 bibitte kernel: loop0: rw=0, want=1230356, limit=82328 Sep 13 02:01:09 bibitte kernel: Buffer I/O error on device loop0, logical block 307588 Sep 13 02:01:10 bibitte kernel: attempt to access beyond end of device Sep 13 02:01:13 bibitte kernel: loop0: rw=0, want=1230360, limit=82328 Sep 13 02:01:13 bibitte kernel: Buffer I/O error on device loop0, logical block 307589 Sep 13 02:01:14 bibitte kernel: attempt to access beyond end of device Sep 13 02:01:16 bibitte kernel: loop0: rw=0, want=1230236, limit=82328 Sep 13 02:01:17 bibitte kernel: Buffer I/O error on device loop0, logical block 307558 Sep 13 02:01:17 bibitte kernel: attempt to access beyond end of device Sep 13 02:01:17 bibitte kernel: loop0: rw=0, want=1230240, limit=82328 Sep 13 02:01:17 bibitte kernel: Buffer I/O error on device loop0, logical block 307559 Sep 13 02:01:17 bibitte kernel: cdrom: open failed. Sep 13 02:01:17 bibitte kernel: cdrom: open failed. The command line is: mondoarchive -e -Oi -9 -F -d /data/images/daily/`date +%A` -E "/data" I also verify afterwards with: /usr/sbin/mondoarchive -e -Vi -d /data/images/daily/`date +%A` I have tried: -adding the -e switch to avoid ejection -upgraded mondo and mindo to the latest release (.09). The problem is still there... |
|||
#77 | fixed | Add support for mdv2007.0 | ||
Description |
We should generate packages for the new mdv2007.0 |
|||
#79 | fixed | tools/svn2build fails on CentOS 4.4 x86_64 | ||
Description |
I wanted to build mondorescue stable branch from svn today, but it failed with the following messages: [rpmbuilder@samson mondorescue]$ svn checkout svn://svn.mondorescue.org/mondorescue/branches/stable Checked out revision 866. [rpmbuilder@samson mondorescue]$ stable/tools/svn2build cat: /home/rpmbuilder/mondo/svn/branches/stable/mondo/VERSION: No such file or directory stable/tools/svn2build: line 35: cd: /home/rpmbuilder/mondo/svn: No such file or directory cat: branches/stable/mondo-doc/VERSION: No such file or directory Management of mondo-doc -1 (rev 866) svn: 'branches/stable' is not a working copy stable/tools/svn2build: line 43: mondo-doc-/REVISION: No such file or directory Generating SVN log file ... stable/tools/svn2build: line 45: mondo-doc-/svn.log: No such file or directory Generating build files for mandrake (10.1) Unable to build the RPM specfile for this distro. Please report to authors [rpmbuilder@samson mondorescue]$ I know CentOS 4.4 isn't directly supported, however, it is just a respin of RHEL 4, so I think it should work with RHEL 4 specfiles. I'm really eager to test new versions of mondorescue leading up to the 2.2.0 release. |