From owner-freebsd-stable@FreeBSD.ORG Sat Apr 12 13:10:37 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AD4F4680; Sat, 12 Apr 2014 13:10:37 +0000 (UTC) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [46.4.40.135]) by mx1.freebsd.org (Postfix) with ESMTP id 6E3D615B4; Sat, 12 Apr 2014 13:10:37 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:38fe:bc98:65e7:fb6b]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPSA id 9F8824AC2D; Sat, 12 Apr 2014 17:10:29 +0400 (MSK) Date: Sat, 12 Apr 2014 17:09:53 +0400 From: Lev Serebryakov Organization: FreeBSD X-Priority: 3 (Normal) Message-ID: <981154629.20140412170953@serebryakov.spb.ru> To: freebsd-fs@FreeBSD.org, freebsd-stable@freebsd.org Subject: One process which would not die force me to power-cycle server and ALL UFS SUJ FSes are completely broken after that AGAIN! MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: lev@FreeBSD.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Apr 2014 13:10:37 -0000 Hello, Freebsd-fs. On my 10-STABLE (r263965) system transmission-daemon stops to work, could not be killed (waits forever in STOP state after "kill -KILL), kernel reports about overfilled accept TCP queue for its socket (sonewconn: pcb 012345678FFFFFFF: Listen queue overflow). Try "shutdown -r now", process aborted due to process which would not die, nothing could be done: system doesn't react on keyboard after that. Wait one hour (!). No result, only more "Listen queue overflow" messages on console. Power-off. Power-on. All UFS2 filesystems can not be recovered with using of automated fsck, due to journal/softupdate inconsistencies. I need to run "fsck -f" TWICE for each of them (as first run ask to re-run fsck). Please note, they are filesystems on MBR slice + BSD label on simple SATA disk attached to chipset port, no RAID, no "strange" GEOM modules, nothing fancy. Plain and easy install -- MBR with one slice, BSD label, filesystems, it's all. So, there are two questions: (1) Does UFS2 SUJ works at all on STABLE system? Should it?! (2) How could I avoid such situation, how could I reboot system WITHOUT such disaster when one process refuse to die? -- // Black Lion AKA Lev Serebryakov