search for: killable

...-compiled 2.4.19 + acl patches, self compiled samba 2.2.6, 100 Mbps NIC this server is right now in a pre-prod status and is currently used only by very few users while loading several +100 MB files on a share from a NT 4 wks 100 Mbps, we got several "session cancelled" messages, and un-killable D-state smbd processes on the server. setting "oplocks = no" on the share and rebooting (the only way to remove D-state processes in this case) solved the problem oplocks are definitively a nightmire for us here... - * - * - * - * - * - * - Bien s?r que je suis perfectionniste ! M...

...ve tried using smbmount and auto.fs to mount both samba and windows shares. They all mount successfully. However, in a terminal window or in Nautilus when I am trying to access the shares (even an ls command in terminal window) will completly hang the share point. This process then becomes an un-killable process. Other systems can connect to the share point and use it fine while this is going on. Anyone have any ideas how to fix/get around this problem? Thanks, Brian __________________________________ Do you Yahoo!? Friends. Fun. Try the all-new Yahoo! Messenger. http://messenger.yahoo....

...ractically unusable because all CPU > > resource will be wasted for unsuccessful memory reclaim attempts) > > unless the OOM killer is invoked. > > 20171016-default.log.xz continued printing "puff" messages until kernel > panic caused by somebody else killing all OOM killable processes via > GFP_KERNEL allocation requests. Although fill_balloon() was printing > a lot of noises due to __GFP_NORETRY, the system made forward progress > in the form of kernel panic triggered by no more OOM killable processes. > > ---------- > [ 88.270838] virtio_balloon...

...ck screen when loggin in windows. In such a situation there always is a process of the user in question in the process state "D" on the smb server. The nfs-mount for this user on the smb-server is however available without problems. Since the process is in state "D" its not killable and the only solution is a reboot of the samba server itself which of course is an "ugly" solution. I cannot find anything special in the logs. The samba.conf is included below. Any ideas? Thanks Rainer ------------------ smb.conf: [global] workgroup = UNI server...

...9 30695 0 01:55 ? 00:00:02 rsync -va --delete --timeout=180 --no-detach /server_ro/ /sicherungen/2007/02/02/01.41/ root 30730 30729 0 01:55 ? 00:00:00 [rsync] <defunct> The last thing the log says is: "building file list ..." Since the processes seem not to be killable, the only "remedy" is to reboot the backup- server. Then it will work for a few days, until it hangs again. Installed are two SuSE 9.3 EE Linuxes, both fully updated. I'm not sure which kernel versions, but both sh?uld be 2.6.x I think. If that is important please tell me how I c...

...after starting the server, users start complaining that they can no longer open documents on their share. Upon inspection, I find several, sometimes nearly a dozen smb processes owned by a single user, on top of those run under root. Stopping the service does not stop these processes. They are only killable with SIGKILL, and after that, a service restart does not result in a functioning service, i.e. connections are refused, which can be verified easily with smbclient. The only cure is a server reboot. And it is not the same user id every time it happens. Useful logs of any type are not available. I...

...messages (and guest1 is practically unusable because all CPU > resource will be wasted for unsuccessful memory reclaim attempts) > unless the OOM killer is invoked. 20171016-default.log.xz continued printing "puff" messages until kernel panic caused by somebody else killing all OOM killable processes via GFP_KERNEL allocation requests. Although fill_balloon() was printing a lot of noises due to __GFP_NORETRY, the system made forward progress in the form of kernel panic triggered by no more OOM killable processes. ---------- [ 88.270838] virtio_balloon virtio3: Out of puff! Can'...

...messages (and guest1 is practically unusable because all CPU > resource will be wasted for unsuccessful memory reclaim attempts) > unless the OOM killer is invoked. 20171016-default.log.xz continued printing "puff" messages until kernel panic caused by somebody else killing all OOM killable processes via GFP_KERNEL allocation requests. Although fill_balloon() was printing a lot of noises due to __GFP_NORETRY, the system made forward progress in the form of kernel panic triggered by no more OOM killable processes. ---------- [ 88.270838] virtio_balloon virtio3: Out of puff! Can'...

...93522 10 - - bad And the inode in question on /home/mnt5 is a dot-nfs file, indicating stale lock: bash# ls -li | grep 9010290 9010290 -rw------- 1 302870 42 1493 Apr 3 18:05 .nfs.0668c236.6d524.4 ktrace on the pid shows absolutely no activity. The pop3 process is un-killable, and I end up stacking up pop3 processes from the user, as well as deliver to the user. Not healthy.. I was under the impression that POP3 would exit when a lock is set, preventing more than one pop3 processes pr. user, but it doesn't seem to be the case. Stopping dovecot entirely, leaves the...

...ot be corrected due backport problems (I looked at the kernel code and the official patch is for a later kernel version, and the base code has changed a lot). It makes unloading the iptables modules impossible, when the Infiniband network is running... (the modprobe process stucks at 100%, not killable). Is there any Xen Dom0 kernel maintained, witch can be used to the Redhat/Centos 5.4? I do not want to totally wanted to go to an Debian based as the Ubuntu LTS, as I read it does not support the Xen out of the box as OpenSuse or Redhat does. Has anybody experience with that? Has the Debian ver...

On Sat, Oct 14, 2017 at 01:41:14AM +0900, Tetsuo Handa wrote: > Michael S. Tsirkin wrote: > > On Tue, Oct 10, 2017 at 07:47:37PM +0900, Tetsuo Handa wrote: > > > In leak_balloon(), mutex_lock(&vb->balloon_lock) is called in order to > > > serialize against fill_balloon(). But in fill_balloon(), > > > alloc_page(GFP_HIGHUSER[_MOVABLE] | __GFP_NOMEMALLOC |

On Sat, Oct 14, 2017 at 01:41:14AM +0900, Tetsuo Handa wrote: > Michael S. Tsirkin wrote: > > On Tue, Oct 10, 2017 at 07:47:37PM +0900, Tetsuo Handa wrote: > > > In leak_balloon(), mutex_lock(&vb->balloon_lock) is called in order to > > > serialize against fill_balloon(). But in fill_balloon(), > > > alloc_page(GFP_HIGHUSER[_MOVABLE] | __GFP_NOMEMALLOC |

...diskimages/root /dev/mfid0s1a (dump) 75404 p0 S+ 0:00.96 dump -a0Lf /backup/diskimages/root /dev/mfid0s1a (dump) 75405 p0 S+ 0:00.86 dump -a0Lf /backup/diskimages/root /dev/mfid0s1a (dump) But it just stops at a random percentage, the system continues to run and the processes are killable? Perhaps I'm using dump incorrectly if anyone could help would be greatly appreciated. Regards -- David Peall :: IT Manager e-Schools' Network :: http://www.esn.org.za/ <http://www.esn.org.za/> Phone +27 (021) 674-9140

Hello, I am having a problem with my dovecot-daemon. It is forking one or more (I saw up to perhaps 8 of them) imap processes under my user name. These processes are consuming a lot of CPU time and are not killable: > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND > 8616 arno 20 0 2900 1600 1204 R 98 0.2 1196:38 imap Stopping dovecot does not quit these processes. Killing them (even "kill -9" as root) is not possible. The only solution to get rid of them is...

...patch series: > The guest sets virtio_balloon.oom_pages=100000. When the host requests > to inflate 7.9G of an 8G idle guest, the guest can still run normally > since OOM can guarantee at least 100000 pages (400MB) for the guest. > Without the above patches, the guest will kill all the killable > processes and fall into kernel panic finally. > > Wei Wang (3): > virtio-balloon: replace the coarse-grained balloon_lock > virtio-balloon: deflate up to oom_pages on OOM > virtio-balloon: stop inflating when OOM occurs > > drivers/virtio/virtio_balloon.c | 149 ++...

...erver, users start > complaining that they can no longer open documents on their share. Upon > inspection, I find several, sometimes nearly a dozen smb processes owned > by a single user, on top of those run under root. Stopping the service does > not stop these processes. They are only killable with SIGKILL, and after that, a > service restart does not result in a functioning service, i.e. connections are > refused, which can be verified easily with smbclient. The only cure is a server > reboot. And it is not the same user id every time it happens. Useful logs of > any type ar...

Hi, since we have upgraded to CentOS 7.5 (from CentOS 7.4), we experience frequent, but not reproducible, freezes of various applications: Thunderbird, Firefox, LibreOffice. Usually the application process keeps running with PPID 1 w/o being killable (not even with SIGKILL). Freezes of Thunderbird are usually followed by Firefox crashing a few minutes later. The only possible solution we found is a complete workstation reboot :-(. Other problems are that many Gnome extensions are not working any more and also cannot be installed from exte...

...t all of a sudden this setup (nfsserver+samba-client) fails, where it has worked for 10 years without any trouble. Thanks Rainer Am 01.02.23 um 11:38 schrieb Ralph Boehme via samba: > On 2/1/23 10:18, Rainer Krienke via samba wrote: >> Since the process is in state "D" its not killable and the only >> solution is a reboot of the samba server itself which of course is an >> "ugly" solution. > > as for "D" state: ask the the kernel, that's out of Samba's control. You > can start with a /proc/PID/stack to find out where in the kerne...

...puter.". No share was mapped. Logged out and in and tried the same again 2) \\oberon\linux has been mapped without problems. Logged out and in and tried the same again 3) the same error message, no share was mapped. Relogged, tried again 4) without problems 5) OK 6) OK 7) OK. Tried killing all killable connection with SWAT (why can't I kill those IPC connections with SWAT?). 8) OK. Shutdown, RESET of the PC 9) the error message occurs when mere clicking on OBERON, preventing me even from clicking on the linux share. relogging. 10) OK 11) OK 12) OK. Rebooting 13) OK How can I determine wha...

I am writing a small documentation on reason(s) : why kernel panic happen !! and possible (crisp) solution(s) googling out this error throws me very hazy solutions .. if some one could suggest the possible reasons and crispy solution it would be of great documentation help to many . one great link i found was this (