http://qa.mandrakesoft.com/show_bug.cgi?id=4166
Product: glibc
Component: glibc
Summary: glibc/pthreads breaks Mondo Rescue with tape media
Product: glibc
Version: 2.3.2-4mdk
Platform: PC
URL: http://www.mondorescue.org/download/contribute.html
OS/Version: All
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: glibc
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
Mondo is a truly amazing bare metal disaster recovery and
backup/restore program. It's capable of rebuilding a down system
via rescue media and a set of backup media. The result is a
completely usable system with recovered data, configuration and
devices. Basicly the system looks _exactly_ like it did at the
last backup.
But, Mondo will not work with tape media on Mandrake as of
Mandrake's 9.0 release. I'm told that Mondo works fine with CD-R
media, but I can't realisticly backup 9-10GB of data onto CD-R.
The reason that the Mondo team gives for the problem is given on
http://www.mondorescue.org/download/contribute.html and repeated
here:
Some of the latest Linux distributions contain severely
flawed glibc binaries and libraries.
The default Mandrake 9.0, SuSE 8.0, SuSE 8.1 distributions
contain buggy glibc packages. If you find that Mondo does
not function properly on your computer and you are running
on of these distributions, especially if the errors involve
tape handling or pthreads then please file a bug report
against your glibc/pthreads library with the vendor of your
Linux distribution. Until the vendors fix the bugs, there is
nothing I can do.
One symptom of the problem is that doing the bare metal restore
fails and leaves the system completely unusable, needing to be
rescued by tomsrbt or similar boot floppy.
It could be that Red Hat is enhancing their glibc/pthreads
implementation. I've heard rumors to that effect, and looking at
their package, I would suspect that this could be true.
Thanks....
--
Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
