[Bug 750736] New: /sbin/mke2fs: symbol lookup error: /sbin/mke2fs: undefined symbol: set_com_err_gettext
https://bugzilla.novell.com/show_bug.cgi?id=750736 https://bugzilla.novell.com/show_bug.cgi?id=750736#c0 Summary: /sbin/mke2fs: symbol lookup error: /sbin/mke2fs: undefined symbol: set_com_err_gettext Classification: openSUSE Product: openSUSE 12.2 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: per@opensuse.org QAContact: jsrain@suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:8.0.1) Gecko/20100101 Firefox/8.0.1 I was trying to install current Factory when I got a yast popup with this: [YCP] StorageClients.ycp:89 CommitErrorPopup error:-3008 last_action:Formatting partition /dev/cciss/c0d0p1 (8.47 GB) with ext4 extended_message:/sbin/mke2fs -O dir_index -m5.0 -t ext4 -v '/dev/cciss/c0d0p1': /sbin/mke2fs: symbol lookup error: /sbin/mke2fs: undefined symbol: set_com_err_gettext Reproducible: Didn't try -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=750736 https://bugzilla.novell.com/show_bug.cgi?id=750736#c1 Christian Boltz <suse-beta@cboltz.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |suse-beta@cboltz.de AssignedTo|bnc-team-screening@forge.pr |jack@suse.com |ovo.novell.com | --- Comment #1 from Christian Boltz <suse-beta@cboltz.de> 2012-03-09 01:19:00 CET --- Reassigning to e2fsprogs maintainer. (If you thing mke2fs itsself is fine and it's a problem in the installation system only, feel free to reassign ;-) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=750736 https://bugzilla.novell.com/show_bug.cgi?id=750736#c2 --- Comment #2 from Jan Kara <jack@suse.com> 2012-03-12 09:35:22 UTC --- This looks like some issue with com_err library (like if it had a wrong so name or there was missing link or something like that). I don't think it's a general issue with Factory since I'd see more reports when e2fsprogs were generally unusable :) (I just fired off installation to verify). So I suspect it was some repository inconsistency. Can you please try again? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=750736 https://bugzilla.novell.com/show_bug.cgi?id=750736#c3 Jan Kara <jack@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |per@opensuse.org --- Comment #3 from Jan Kara <jack@suse.com> 2012-03-12 09:37:39 UTC --- Forgot to set NEEDINFO... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=750736 https://bugzilla.novell.com/show_bug.cgi?id=750736#c4 Jan Kara <jack@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED InfoProvider|per@opensuse.org | Resolution| |INVALID --- Comment #4 from Jan Kara <jack@suse.com> 2012-03-15 08:50:01 UTC --- I don't see the problem with current Factory install. So I'll close this one. Please reopen if you can reproduce. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=750736 https://bugzilla.novell.com/show_bug.cgi?id=750736#c5 Per Jessen <per@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | --- Comment #5 from Per Jessen <per@opensuse.org> 2012-04-25 07:54:36 UTC --- Hardware: Supermicro, 1UZ, dual-core 2.8GHz, 1024MB RAM, single SATA drive. Booting+installing over PXE+ssh+http. Have just reproduced with current Factory. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=750736 https://bugzilla.novell.com/show_bug.cgi?id=750736#c6 Per Jessen <per@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |CLOSED Resolution| |WORKSFORME --- Comment #6 from Per Jessen <per@opensuse.org> 2012-04-25 08:09:38 UTC --- Ignore that, I had an outdated kernel+initrd on my tftp server. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=750736 https://bugzilla.novell.com/show_bug.cgi?id=750736#c7 Eberhard Mönkeberg <emoenke@gwdg.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |REOPENED CC| |emoenke@gwdg.de Resolution|WORKSFORME | --- Comment #7 from Eberhard Mönkeberg <emoenke@gwdg.de> 2012-05-21 15:02:20 UTC --- I got the same error with /repositories/filesystems/SLE_11_SP2/x86_64/e2fsprogs-1.42.2-28.1.x86_64.rpm: ftp5:6 00:19:37 ~ # mkfs.ext3 -E stride=128k stripe-width=1152k -L X /dev/x/v mkfs.ext3: symbol lookup error: mkfs.ext3: undefined symbol: set_com_err_gettext ftp5:6 00:27:34 ~ # -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=750736 https://bugzilla.novell.com/show_bug.cgi?id=750736#c8 Jan Kara <jack@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED --- Comment #8 from Jan Kara <jack@suse.com> 2012-05-23 22:53:31 UTC --- I've checked this again and your comment actually revealed to me how the breakage can occur. Indeed the problem is that you have e2fsprogs installed without proper version of libcom_err installed. If you also download and install libcom_err2 package from that repository, the error goes away. I've now updated the package to require libcom_err (and libext2fs as well because it's another library closely tied to e2fsprogs) of at least as new version as e2fsprogs themselves. That should prevent such silent breakage for future. Thanks for reporting this. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=750736 https://bugzilla.novell.com/show_bug.cgi?id=750736#c9 --- Comment #9 from Eberhard Mönkeberg <emoenke@gwdg.de> 2012-05-23 23:21:56 UTC --- OK, thanks a lot very much (I really need a filesystem other than XFS with 20 TB and ability to grow), see https://bugzilla.novell.com/show_bug.cgi?id=763348 . So I will hopefully wait that the new version will appear. Currently are all three packages still from Apr-23-2012 for the public - the massive ARM compilations seem to dominate the whole build service again. ;-)) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=750736 https://bugzilla.novell.com/show_bug.cgi?id=750736#c10 --- Comment #10 from Per Jessen <per@opensuse.org> 2012-05-24 06:19:21 UTC --- (In reply to comment #9)
OK, thanks a lot very much (I really need a filesystem other than XFS with 20 TB and ability to grow), see
JFS will help you with that.
Access denied. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=750736 https://bugzilla.novell.com/show_bug.cgi?id=750736#c Swamp Workflow Management <swamp@suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard| |maint:running:50523:low -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=750736 https://bugzilla.novell.com/show_bug.cgi?id=750736#c Swamp Workflow Management <swamp@suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard|maint:running:50523:low |maint:running:50523:moderat | |e -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=750736 https://bugzilla.novell.com/show_bug.cgi?id=750736#c Swamp Workflow Management <swamp@suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard|maint:running:50523:moderat |maint:running:50523:low |e | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=750736 https://bugzilla.novell.com/show_bug.cgi?id=750736#c Swamp Workflow Management <swamp@suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard|maint:running:50523:low |. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=750736 https://bugzilla.novell.com/show_bug.cgi?id=750736#c Swamp Workflow Management <swamp@suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard|. |maint:running:50523:low -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=750736 https://bugzilla.novell.com/show_bug.cgi?id=750736#c14 Liu Shukui <skliu@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |skliu@suse.com --- Comment #14 from Liu Shukui <skliu@suse.com> 2013-01-30 17:29:46 CST --- Cannot run this command because there is no related devices. mkfs.ext3 -E stride=128k stripe-width=1152k -L X /dev/x/v Is there any other testcase to reproduce this bug on sle11sp2? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=750736 https://bugzilla.novell.com/show_bug.cgi?id=750736#c15 --- Comment #15 from Jan Kara <jack@suse.com> 2013-01-30 10:37:34 UTC --- Just any execution of mkfs.ext3 will cause the issue if there's a mismatch between libcomerr or libext2fs version and e2fsprogs version (and there are differences in symbols). In practice this only happens when repositories are inconsistent for a while during rebuild. I assume you could test the problem by installing some rather old libcomerr and then e2fsprogs. Unfixed e2fsprogs rpm should install fine but mkfs.ext3 should fail with error. Fixed e2fsprogs rpm should fail the install because of unmet dependencies. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=750736 https://bugzilla.novell.com/show_bug.cgi?id=750736#c16 --- Comment #16 from Liu Shukui <skliu@suse.com> 2013-01-30 19:35:42 CST --- Thank you, Jan Kara. But I don't konw how to get a "rather old libcomerr". If the bug does not appear on the original version(in the DVD image)of libcomerr and if there is no such "rather old libcomerr" in existing repositories, can we just do some regression tests? I cannot understand why the problem on Comment 7 could happen. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=750736 https://bugzilla.novell.com/show_bug.cgi?id=750736#c17 --- Comment #17 from Jan Kara <jack@suse.com> 2013-01-30 13:11:25 UTC --- OK, I guess I wasn't clear enough and I agree testing this is tricky. So I guess you are testing against SLE11-SP2, right? So take for example e2fsprogs package from openSUSE-11.4, build it against SLE11-SP2 in build service (ask your colleagues how to do that if you don't have experience with it). Then take a test system without e2fsprogs installed and install libcom_err package from your build (install directly using rpm). Then go and try installing the unpatched e2fsprogs in SLE11-SP2. It should succeed. Then prepare the system again and try installing the patched e2fsprogs from SLE11-SP2. The installation should fail complaining there are unmet dependencies on libcom_err. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
OK, I guess I wasn't clear enough and I agree testing this is tricky. So I guess you are testing against SLE11-SP2, right? So take for example e2fsprogs package from openSUSE-11.4, build it against SLE11-SP2 in build service (ask your colleagues how to do that if you don't have experience with it). Then take a test system without e2fsprogs installed and install libcom_err package from your build (install directly using rpm). Then go and try installing the unpatched e2fsprogs in SLE11-SP2. It should succeed. I should have added here: Although the installation succeeded, running mkfs.ext3 will likely fail with the error similar to the one in comment 0 of
https://bugzilla.novell.com/show_bug.cgi?id=750736 https://bugzilla.novell.com/show_bug.cgi?id=750736#c18 --- Comment #18 from Jan Kara <jack@suse.com> 2013-01-30 13:14:17 UTC --- (In reply to comment #17) this bug. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=750736 https://bugzilla.novell.com/show_bug.cgi?id=750736#c19 Swamp Workflow Management <swamp@suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard|maint:running:50523:low |maint:running:50523:low | |maint:released:sle11-sp2:50 | |575 --- Comment #19 from Swamp Workflow Management <swamp@suse.de> 2013-02-01 19:35:49 UTC --- Update released for: e2fsprogs, e2fsprogs-debuginfo, e2fsprogs-debuginfo-32bit, e2fsprogs-debuginfo-64bit, e2fsprogs-debuginfo-x86, e2fsprogs-debugsource, e2fsprogs-devel, libcom_err-devel, libcom_err-devel-32bit, libcom_err2, libcom_err2-32bit, libcom_err2-x86, libext2fs-devel, libext2fs-devel-32bit, libext2fs2, libext2fs2-32bit, libext2fs2-x86 Products: SLE-DEBUGINFO 11-SP2 (i386, ia64, ppc64, s390x, x86_64) SLE-DESKTOP 11-SP2 (i386, x86_64) SLE-SDK 11-SP2 (i386, ia64, ppc64, s390x, x86_64) SLE-SERVER 11-SP2 (i386, ia64, ppc64, s390x, x86_64) SLES4VMWARE 11-SP2 (i386, x86_64) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com