Your message dated Sun, 4 Aug 2013 15:12:47 +0900
with message-id
<CAH79Gv_Se8QH-4TvKwvnf3WkzqE97zN-BW_NWWC6ju=x2do...@mail.gmail.com>
and subject line Re: Bug#712530: move libunwind7 to / on ia64/wheezy?
has caused the Debian Bug report #712530,
regarding e2fsprogs: fsck.ext3 on ia64 is linked to /usr/lib/libunwind, which
can live on a different partition, breaking boot
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
712530: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712530
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: e2fsprogs
Version: 1.42.5-1.1
Severity: grave
Justification: renders package unusable
This bug affects wheezy. Trying to upgrade one of my ia64 boxes from squeeze
to wheezy turned into a non-booting system because:
Checking root file system...fsck from util-linux 2.20.1
fsck.ext3: error while loading shared libraries: libunwind.so.7: cannot open
shared object file: No such file or directory
fsck died with exit status 127
failed (code 127).
An automatic file system check (fsck) of the root filesystem failed. A manual
fsck must be performed, then the system restarted. The fsck should be performed
in maintenance mode with the root filesystem mounted in read-only mode. ...
failed!
The root filesystem is currently mounted in read-only mode. A maintenance shell
will now be started. After performing system maintenance, press CONTROL-D to
terminate the maintenance shell and restart the system. ... (warning).
Give root password for maintenance
(or type Control-D to continue):
And then the problem is that:
ldd /sbin/fsck.ext3
linux-gate.so.1 => (0xa000000000000000)
libext2fs.so.2 => /lib/ia64-linux-gnu/libext2fs.so.2
(0x2000000800054000)
libcom_err.so.2 => /lib/ia64-linux-gnu/libcom_err.so.2
(0x20000008000e8000)
libblkid.so.1 => /lib/ia64-linux-gnu/libblkid.so.1 (0x2000000800100000)
libuuid.so.1 => /lib/ia64-linux-gnu/libuuid.so.1 (0x2000000800160000)
libe2p.so.2 => /lib/ia64-linux-gnu/libe2p.so.2 (0x2000000800178000)
HERE -> libunwind.so.7 => /usr/lib/libunwind.so.7 (0x200000080019c000)
libc.so.6.1 => /lib/ia64-linux-gnu/libc.so.6.1 (0x20000008001e8000)
libpthread.so.0 => /lib/ia64-linux-gnu/libpthread.so.0
(0x2000000800478000)
/lib/ld-linux-ia64.so.2 (0x2000000800000000)
(don't ask me why it links libunwind, btw)
The problem is that fsck is a program that lives in /sbin, and it links a
library that lives in /usr, which can (and in this particular case does) reside
on a different filesystem, which will no be mounted at the time of the rootfs
filesystem check. That's an obvious violation of everything sacred, it kills
kittens, etc.
Please fix.
T-Bone
PS: sending this report from another machine as reportbug still ignores
http_proxy whenever it pleases.
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: ia64
Kernel: Linux 2.6.27.39 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
Closed.
Daigo
On Sat, Jul 27, 2013 at 5:35 PM, Daigo Moriwaki <da...@debian.org> wrote:
> This issue has been solved by e2fsprogs (#708307), which I think is the
> best way because a way to build fsck.ext3 is the source of the problem.
>
> I'd like to close this bug.
> If you find any issues in the libunwind package, please let me know.
>
--
Daigo Moriwaki <daigo at debian dot org>
--- End Message ---
