I have tried to kill the process:
sam@sam-desktop:~$ ps -aux|grep sda
Warning: bad ps syntax, perhaps a bogus '-'? See http://procps.sf.net/faq.html
root 2898 0.0 0.0 0 0 ? S 11:39 0:00 [jbd2/sda6-8]
root 2899 0.0 0.0 2300 716 ? D 11:39 0:00 mount -t ext4 -o uhelper=udisks,nodev,nosuid /dev/sda6 /media/634bad56-5543-40fe-843b-cd31f4a95dba_
sam 2973 0.0 0.0 3328 876 pts/0 S+ 14:13 0:00 grep --color=auto sda
sam@sam-desktop:~$ sudo kill -9 2898
sam@sam-desktop:~$ sudo kill -9 2899
sam@sam-desktop:~$ sudo killall -9 2898
2898: no process found
sam@sam-desktop:~$ sudo killall -9 2899
2899: no process found
sam@sam-desktop:~$ ps -aux|grep sda
Warning: bad ps syntax, perhaps a bogus '-'? See http://procps.sf.net/faq.html
root 2898 0.0 0.0 0 0 ? S 11:39 0:00 [jbd2/sda6-8]
root 2899 0.0 0.0 2300 716 ? D 11:39 0:00 mount -t ext4 -o uhelper=udisks,nodev,nosuid /dev/sda6 /media/634bad56-5543-40fe-843b-cd31f4a95dba_
sam 2987 0.0 0.0 3328 872 pts/0 S+ 14:22 0:00 grep --color=auto sda
sam@sam-desktop:~$
After suggestions I tried:
sam@sam-desktop:~$ sudo umount -f /media/634bad56-5543-40fe-843b-cd31f4a95dba_
umount2: Invalid argument
umount: /media/634bad56-5543-40fe-843b-cd31f4a95dba_: not mounted
sam@sam-desktop:~$ sudo umount -l /media/634bad56-5543-40fe-843b-cd31f4a95dba_
umount: /media/634bad56-5543-40fe-843b-cd31f4a95dba_: not mounted
sam@sam-desktop:~$
A few points:
killall
only takes process names so your syntax there was incorrect.[bracketed]
processes are kernel threads which aren't going to respond to being killed by a userspace program likekill
.Something like
mount
is waiting for the kernel to respond. It should mount and then close. The only time it hangs is when the mount can't go through, AFAIK. Consider using-v
in your mount options to see the exact problem.I think you want to try
sudo umount -f /media/634bad56-5543-40fe-843b-cd31f4a95dba_
and if that doesn't work:sudo umount -l /media/634bad56-5543-40fe-843b-cd31f4a95dba_
. I would hope the kernel would see the unmount and would stop the previous mount operation.Also if this is a mount from your
/etc/fstab
, you might want to consider using UUIDs instead of "/dev/sdxn
" devices which can change name between boots.The process is in an uninterruptible sleep and therefore cannot be killed.
From wikipedia
So I would check the hard disk and partition for errors.
I believe that processes in brackets are ones that are started by kernel threads and as such are critical to system function. In this case, jbd2 is the journaling block device, which is required if you want to use your hard drive.
Why do you want to kill this process?