Re: [CentOS] du hung, wild display in ps
On Wed, May 06, 2020 at 06:24:10PM -0700, Gordon Messmer wrote: > On 5/6/20 12:28 PM, Fred Smith wrote: > >Was running du to examine the sizes of my backups and > >found du hung, > > > /mnt/backup is probably a network-mounted filesystem that is offline > for one reason or another. > > You could try "umount -f /mnt/backup" if you can't get the mount > working by any other means. If that doesn't work, then "umount -l > /mnt/backup" and reboot. Sorry, I forgot to mention it's USB-3 and has been working for a coupla months. A reboot solved it, powering the device off/on made no difference, as did replugging the cable. Afterwards, I recalled that I had run a much belated yum update 2 or 3 days ago and had failed/forgotten to reboot. Probably some necessary item had gotten wedged somehow because of that. (seen it before, but not with a USB device.) Thanks for the reply, though. Fred -- Fred Smith -- fre...@fcshome.stoneham.ma.us - "And he will be called Wonderful Counselor, Mighty God, Everlasting Father, Prince of Peace. Of the increase of his government there will be no end. He will reign on David's throne and over his kingdom, establishing and upholding it with justice and righteousness from that time on and forever." --- Isaiah 9:7 (niv) -- ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] du hung, wild display in ps
On 5/6/20 12:28 PM, Fred Smith wrote: Was running du to examine the sizes of my backups and found du hung, /mnt/backup is probably a network-mounted filesystem that is offline for one reason or another. You could try "umount -f /mnt/backup" if you can't get the mount working by any other means. If that doesn't work, then "umount -l /mnt/backup" and reboot. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] du hung, wild display in ps
Hi! On Centos-7: $ cat /etc/centos-release CentOS Linux release 7.8.2003 (Core) Was running du to examine the sizes of my backups and found du hung, running "ps -eLf /mnt/backup/backups" shows this: # ps -eLf | grep du root 1185 1 1185 01 May01 ?00:00:00 /usr/bin/abrt-watch-log -F Backtrace /var/log/Xorg.0.log -- /usr/bin/abrt-dump-xorg -xD root 1281 1 1281 01 May01 ?00:00:01 /usr/bin/abrt-watch-log -F BUG: WARNING: at WARNING: CPU: INFO: possible recursive locking detected ernel BUG at list_del corruption list_add corruption do_IRQ: stack overflow: ear stack overflow (cur: eneral protection fault nable to handle kernel ouble fault: RTNL: assertion failed eek! page_mapcount(page) went negative! adness at NETDEV WATCHDOG ysctl table check failed : nobody cared IRQ handler type mismatch Kernel panic - not syncing: Machine Check Exception: Machine check events logged divide error: bounds: coprocessor segment overrun: invalid TSS: segment not present: invalid opcode: alignment check: stack segment: fpu exception: simd exception: iret exception: /var/log/messages -- /usr/bin/abrt-dump-oops -xtD root 11090 1 11090 111 15:08 pts/100:01:10 du -s /mnt/backup/backups even after killing the du. there were two DUs shown, I killed the parent (presumably the one I started) but the one that remains seems to be un-killable. This is what the output looked like before I killed du: # ps -eLf | grep du root 1185 1 1185 01 May01 ?00:00:00 /usr/bin/abrt-watch-log -F Backtrace /var/log/Xorg.0.log -- /usr/bin/abrt-dump-xorg -xD root 1281 1 1281 01 May01 ?00:00:01 /usr/bin/abrt-watch-log -F BUG: WARNING: at WARNING: CPU: INFO: possible recursive locking detected ernel BUG at list_del corruption list_add corruption do_IRQ: stack overflow: ear stack overflow (cur: eneral protection fault nable to handle kernel ouble fault: RTNL: assertion failed eek! page_mapcount(page) went negative! adness at NETDEV WATCHDOG ysctl table check failed : nobody cared IRQ handler type mismatch Kernel panic - not syncing: Machine Check Exception: Machine check events logged divide error: bounds: coprocessor segment overrun: invalid TSS: segment not present: invalid opcode: alignment check: stack segment: fpu exception: simd exception: iret exception: /var/log/messages -- /usr/bin/abrt-dump-oops -xtD root 11078 18627 11078 01 15:08 pts/100:00:00 sudo du -s /mnt/backup/backups root 11090 11078 11090 121 15:08 pts/100:01:10 du -s /mnt/backup/backups root 12125 19449 12125 01 15:17 pts/000:00:00 grep --color=auto du Oh, and I never did get the du out put I expected. Anyone got a clue? Thanks in advance! Fred -- Fred Smith -- fre...@fcshome.stoneham.ma.us - "For the word of God is living and active. Sharper than any double-edged sword, it penetrates even to dividing soul and spirit, joints and marrow; it judges the thoughts and attitudes of the heart." Hebrews 4:12 (niv) -- ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
