Bug#170635: libc6 2.3.1-3 to 2.3.1-5 upgrade breaks
On Monday, December 2, 2002, at 09:27 AM, Rene Engelhard wrote: I got the same message too on a previous upgrade (IIRC on 2.2.5-x). / was ext3. After resetting / to ext2 it worked. I did not know whz then, and I do not know if that is a bug in glibc, dpkg or kernel. If unlink on the file fails, I'd definitely go for kernel. Especially since changing back to ext2 fixes it.
Bug#170635: libc6 2.3.1-3 to 2.3.1-5 upgrade breaks
Hi, Magnus Danielson wrote: > > > I got the "Device or resource busy" message as a reply. It's because the > > > file > > > is in use by many tools: > > > > That shouldn't happen. "File in use" != "name in use". rm removes names, > > not files. [...] > > > And you using something weird as your root file system? That is > > something besides ext[23] or reiserfs? > > EXT3. No strange options or anything. I can't think of any specific things > other than over-generous selection of Debian/unstable packages. I got the same message too on a previous upgrade (IIRC on 2.2.5-x). / was ext3. After resetting / to ext2 it worked. I did not know whz then, and I do not know if that is a bug in glibc, dpkg or kernel. Regards, Rene -- .''`. Rene Engelhard -- Debian GNU/Linux Developer : :' : http://www.debian.org | http://people.debian.org/~rene/ `. `' [EMAIL PROTECTED] | GnuPG-Key ID: 248AEB73 `- Fingerprint: 41FA F208 28D4 7CA5 19BB 7AD9 F859 90B0 248A EB73
Bug#170635: libc6 2.3.1-3 to 2.3.1-5 upgrade breaks
On Monday, December 2, 2002, at 09:27 AM, Rene Engelhard wrote: I got the same message too on a previous upgrade (IIRC on 2.2.5-x). / was ext3. After resetting / to ext2 it worked. I did not know whz then, and I do not know if that is a bug in glibc, dpkg or kernel. If unlink on the file fails, I'd definitely go for kernel. Especially since changing back to ext2 fixes it. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#170635: libc6 2.3.1-3 to 2.3.1-5 upgrade breaks
Hi, Magnus Danielson wrote: > > > I got the "Device or resource busy" message as a reply. It's because the file > > > is in use by many tools: > > > > That shouldn't happen. "File in use" != "name in use". rm removes names, > > not files. [...] > > > And you using something weird as your root file system? That is > > something besides ext[23] or reiserfs? > > EXT3. No strange options or anything. I can't think of any specific things > other than over-generous selection of Debian/unstable packages. I got the same message too on a previous upgrade (IIRC on 2.2.5-x). / was ext3. After resetting / to ext2 it worked. I did not know whz then, and I do not know if that is a bug in glibc, dpkg or kernel. Regards, Rene -- .''`. Rene Engelhard -- Debian GNU/Linux Developer : :' : http://www.debian.org | http://people.debian.org/~rene/ `. `' [EMAIL PROTECTED] | GnuPG-Key ID: 248AEB73 `- Fingerprint: 41FA F208 28D4 7CA5 19BB 7AD9 F859 90B0 248A EB73 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#170635: libc6 2.3.1-3 to 2.3.1-5 upgrade breaks
From: Anthony DeRobertis <[EMAIL PROTECTED]> Subject: Re: Bug#170635: libc6 2.3.1-3 to 2.3.1-5 upgrade breaks Date: 02 Dec 2002 01:17:27 -0500 > On Sun, 2002-12-01 at 21:19, Magnus Danielson wrote: > > > rm /lib/ld-2.3.1.so > > > > I got the "Device or resource busy" message as a reply. It's because the > > file > > is in use by many tools: > > That shouldn't happen. "File in use" != "name in use". rm removes names, > not files. Exactly! I know... it's even traditional UNIX AFAIK. > And you using something weird as your root file system? That is > something besides ext[23] or reiserfs? EXT3. No strange options or anything. I can't think of any specific things other than over-generous selection of Debian/unstable packages. Cheers, Magnus
Bug#170635: libc6 2.3.1-3 to 2.3.1-5 upgrade breaks
From: Anthony DeRobertis <[EMAIL PROTECTED]> Subject: Re: Bug#170635: libc6 2.3.1-3 to 2.3.1-5 upgrade breaks Date: 02 Dec 2002 01:17:27 -0500 > On Sun, 2002-12-01 at 21:19, Magnus Danielson wrote: > > > rm /lib/ld-2.3.1.so > > > > I got the "Device or resource busy" message as a reply. It's because the file > > is in use by many tools: > > That shouldn't happen. "File in use" != "name in use". rm removes names, > not files. Exactly! I know... it's even traditional UNIX AFAIK. > And you using something weird as your root file system? That is > something besides ext[23] or reiserfs? EXT3. No strange options or anything. I can't think of any specific things other than over-generous selection of Debian/unstable packages. Cheers, Magnus -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#170635: libc6 2.3.1-3 to 2.3.1-5 upgrade breaks
On Sun, 2002-12-01 at 21:19, Magnus Danielson wrote: > rm /lib/ld-2.3.1.so > > I got the "Device or resource busy" message as a reply. It's because the file > is in use by many tools: That shouldn't happen. "File in use" != "name in use". rm removes names, not files. And you using something weird as your root file system? That is something besides ext[23] or reiserfs? signature.asc Description: This is a digitally signed message part
Bug#170635: libc6 2.3.1-3 to 2.3.1-5 upgrade breaks
On Sun, 2002-12-01 at 21:19, Magnus Danielson wrote: > rm /lib/ld-2.3.1.so > > I got the "Device or resource busy" message as a reply. It's because the file > is in use by many tools: That shouldn't happen. "File in use" != "name in use". rm removes names, not files. And you using something weird as your root file system? That is something besides ext[23] or reiserfs? signature.asc Description: This is a digitally signed message part
Bug#170635: libc6 2.3.1-3 to 2.3.1-5 upgrade breaks
From: Jeff Bailey <[EMAIL PROTECTED]> Subject: Re: Bug#170635: libc6 2.3.1-3 to 2.3.1-5 upgrade breaks Date: 25 Nov 2002 06:58:16 -0500 Hi Jeff, > On Mon, 2002-11-25 at 02:03, Magnus Danielson wrote: > > > Package: libc6 > > Version: 2.3.1-5 > > Severity: critical > > > > On upgrading my Debian/unstable system (oddly called heaven) from libc6 > > 2.3.1-3 > > to 2.3.1-5 it halts the installation with this text: > > I've done -3 to -5 upgrades on many i386 systems, and 2.2.5 to 2.3.1-5 > upgrades > hurd-i386 and sparc and never seen this message. I need more details. OK. This is what happend: When the dpkg wanted to remove /lib/ld-2.3.1.so in order to insert it's own (identical) this was not possible since the rm command got: rm /lib/ld-2.3.1.so I got the "Device or resource busy" message as a reply. It's because the file is in use by many tools: # lsof | grep ld-2.3.1.so bash 907 magnus memREG3,1 83504 1208304 /lib/ld-2.3.1.so startx1005 magnus memREG3,1 83504 1208304 /lib/ld-2.3.1.so xinit 1016 magnus memREG3,1 83504 1208304 /lib/ld-2.3.1.so fvwm2 1021 magnus memREG3,1 83504 1208304 /lib/ld-2.3.1.so xsnow 1023 magnus memREG3,1 83504 1208304 /lib/ld-2.3.1.so xterm 1024 magnus memREG3,1 83504 1208304 /lib/ld-2.3.1.so xterm 1025 magnus memREG3,1 83504 1208304 /lib/ld-2.3.1.so xterm 1026 magnus memREG3,1 83504 1208304 /lib/ld-2.3.1.so bubblefis 1027 magnus memREG3,1 83504 1208304 /lib/ld-2.3.1.so bash 1028 magnus memREG3,1 83504 1208304 /lib/ld-2.3.1.so bash 1029 magnus memREG3,1 83504 1208304 /lib/ld-2.3.1.so bash 1030 magnus memREG3,1 83504 1208304 /lib/ld-2.3.1.so FvwmPager 1031 magnus memREG3,1 83504 1208304 /lib/ld-2.3.1.so emacs 3834 magnus memREG3,1 83504 1208304 /lib/ld-2.3.1.so lsof 6487 magnus memREG3,1 83504 1208304 /lib/ld-2.3.1.so grep 6488 magnus memREG3,1 83504 1208304 /lib/ld-2.3.1.so lsof 6489 magnus memREG3,1 83504 1208304 /lib/ld-2.3.1.so However, it is fishy that I should run into that problem... libc6 updates should run smoothly and they have before. Now, the trick around this problem is to do cp /lib/ld-2.3.1.so /lib/ld-2.3.1.so.foo rm /lib/ld-linux.so.2 ldconfig Since the copied file which is more recent and ldconfig will fetch the later. However, the bindings to the old one remains, so a reboot is the only cure, but then the bindings will point to the .foo variant at next time, so a new attempt to install will now work. What ever caused this problem, I don't know. I've run pretty tight updates to unstable on this machine and this is one of the few hickups I've had. Now I have put these troubles behind me, but someone should figure out how to handle this problem, both on how it could occur (I haven't fiddle with that file prior to this!) and when it occurs. If you fuck up the libc6 installation a lot of other stuff falls right off. Cheers, Magnus
Bug#170635: libc6 2.3.1-3 to 2.3.1-5 upgrade breaks
From: Jeff Bailey <[EMAIL PROTECTED]> Subject: Re: Bug#170635: libc6 2.3.1-3 to 2.3.1-5 upgrade breaks Date: 25 Nov 2002 06:58:16 -0500 Hi Jeff, > On Mon, 2002-11-25 at 02:03, Magnus Danielson wrote: > > > Package: libc6 > > Version: 2.3.1-5 > > Severity: critical > > > > On upgrading my Debian/unstable system (oddly called heaven) from libc6 2.3.1-3 > > to 2.3.1-5 it halts the installation with this text: > > I've done -3 to -5 upgrades on many i386 systems, and 2.2.5 to 2.3.1-5 upgrades > hurd-i386 and sparc and never seen this message. I need more details. OK. This is what happend: When the dpkg wanted to remove /lib/ld-2.3.1.so in order to insert it's own (identical) this was not possible since the rm command got: rm /lib/ld-2.3.1.so I got the "Device or resource busy" message as a reply. It's because the file is in use by many tools: # lsof | grep ld-2.3.1.so bash 907 magnus memREG3,1 83504 1208304 /lib/ld-2.3.1.so startx1005 magnus memREG3,1 83504 1208304 /lib/ld-2.3.1.so xinit 1016 magnus memREG3,1 83504 1208304 /lib/ld-2.3.1.so fvwm2 1021 magnus memREG3,1 83504 1208304 /lib/ld-2.3.1.so xsnow 1023 magnus memREG3,1 83504 1208304 /lib/ld-2.3.1.so xterm 1024 magnus memREG3,1 83504 1208304 /lib/ld-2.3.1.so xterm 1025 magnus memREG3,1 83504 1208304 /lib/ld-2.3.1.so xterm 1026 magnus memREG3,1 83504 1208304 /lib/ld-2.3.1.so bubblefis 1027 magnus memREG3,1 83504 1208304 /lib/ld-2.3.1.so bash 1028 magnus memREG3,1 83504 1208304 /lib/ld-2.3.1.so bash 1029 magnus memREG3,1 83504 1208304 /lib/ld-2.3.1.so bash 1030 magnus memREG3,1 83504 1208304 /lib/ld-2.3.1.so FvwmPager 1031 magnus memREG3,1 83504 1208304 /lib/ld-2.3.1.so emacs 3834 magnus memREG3,1 83504 1208304 /lib/ld-2.3.1.so lsof 6487 magnus memREG3,1 83504 1208304 /lib/ld-2.3.1.so grep 6488 magnus memREG3,1 83504 1208304 /lib/ld-2.3.1.so lsof 6489 magnus memREG3,1 83504 1208304 /lib/ld-2.3.1.so However, it is fishy that I should run into that problem... libc6 updates should run smoothly and they have before. Now, the trick around this problem is to do cp /lib/ld-2.3.1.so /lib/ld-2.3.1.so.foo rm /lib/ld-linux.so.2 ldconfig Since the copied file which is more recent and ldconfig will fetch the later. However, the bindings to the old one remains, so a reboot is the only cure, but then the bindings will point to the .foo variant at next time, so a new attempt to install will now work. What ever caused this problem, I don't know. I've run pretty tight updates to unstable on this machine and this is one of the few hickups I've had. Now I have put these troubles behind me, but someone should figure out how to handle this problem, both on how it could occur (I haven't fiddle with that file prior to this!) and when it occurs. If you fuck up the libc6 installation a lot of other stuff falls right off. Cheers, Magnus -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#170635: libc6 2.3.1-3 to 2.3.1-5 upgrade breaks
On Mon, 2002-11-25 at 02:03, Magnus Danielson wrote: > Package: libc6 > Version: 2.3.1-5 > Severity: critical > > On upgrading my Debian/unstable system (oddly called heaven) from libc6 > 2.3.1-3 > to 2.3.1-5 it halts the installation with this text: I've done -3 to -5 upgrades on many i386 systems, and 2.2.5 to 2.3.1-5 upgrades hurd-i386 and sparc and never seen this message. I need more details. -- When you get to the heart, use a knife and fork. - From instructions on how to eat an artichoke. signature.asc Description: This is a digitally signed message part
Bug#170635: libc6 2.3.1-3 to 2.3.1-5 upgrade breaks
On Mon, 2002-11-25 at 02:03, Magnus Danielson wrote: > Package: libc6 > Version: 2.3.1-5 > Severity: critical > > On upgrading my Debian/unstable system (oddly called heaven) from libc6 2.3.1-3 > to 2.3.1-5 it halts the installation with this text: I've done -3 to -5 upgrades on many i386 systems, and 2.2.5 to 2.3.1-5 upgrades hurd-i386 and sparc and never seen this message. I need more details. -- When you get to the heart, use a knife and fork. - From instructions on how to eat an artichoke. signature.asc Description: This is a digitally signed message part
Bug#170635: libc6 2.3.1-3 to 2.3.1-5 upgrade breaks
Package: libc6 Version: 2.3.1-5 Severity: critical On upgrading my Debian/unstable system (oddly called heaven) from libc6 2.3.1-3 to 2.3.1-5 it halts the installation with this text: Preparing to replace libc6 2.3.1-3 (using .../libc6_2.3.1-5_i386.deb) ... Unpacking replacement libc6 ... dpkg: error processing /var/cache/apt/archives/libc6_2.3.1-5_i386.deb (--unpack): unable to install new version of `./lib/ld-2.3.1.so': Device or resource busy dpkg-deb: subprocess paste killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libc6_2.3.1-5_i386.deb When the file is to be replaced, it is being used by a heap of different tools. "lsof | grep ld-" gives a pretty good idea where the trouble is. This have worked before, new upgrade routines in the libc6 package? Cheers, Magnus
Bug#170635: libc6 2.3.1-3 to 2.3.1-5 upgrade breaks
Package: libc6 Version: 2.3.1-5 Severity: critical On upgrading my Debian/unstable system (oddly called heaven) from libc6 2.3.1-3 to 2.3.1-5 it halts the installation with this text: Preparing to replace libc6 2.3.1-3 (using .../libc6_2.3.1-5_i386.deb) ... Unpacking replacement libc6 ... dpkg: error processing /var/cache/apt/archives/libc6_2.3.1-5_i386.deb (--unpack): unable to install new version of `./lib/ld-2.3.1.so': Device or resource busy dpkg-deb: subprocess paste killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libc6_2.3.1-5_i386.deb When the file is to be replaced, it is being used by a heap of different tools. "lsof | grep ld-" gives a pretty good idea where the trouble is. This have worked before, new upgrade routines in the libc6 package? Cheers, Magnus -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
