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 0 1 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 0 1 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 11 1 15:08 pts/1 00: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 0 1 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 0 1 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 0 1 15:08 pts/1 00:00:00 sudo du -s /mnt/backup/backups root 11090 11078 11090 12 1 15:08 pts/1 00:01:10 du -s /mnt/backup/backups root 12125 19449 12125 0 1 15:17 pts/0 00: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
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.
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 -
Gordon Messmer