From nobody@FreeBSD.org  Tue May 31 11:43:39 2011
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id E91751065670
	for <freebsd-gnats-submit@FreeBSD.org>; Tue, 31 May 2011 11:43:39 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from red.freebsd.org (red.freebsd.org [IPv6:2001:4f8:fff6::22])
	by mx1.freebsd.org (Postfix) with ESMTP id C0FA78FC1A
	for <freebsd-gnats-submit@FreeBSD.org>; Tue, 31 May 2011 11:43:39 +0000 (UTC)
Received: from red.freebsd.org (localhost [127.0.0.1])
	by red.freebsd.org (8.14.4/8.14.4) with ESMTP id p4VBhdcE084542
	for <freebsd-gnats-submit@FreeBSD.org>; Tue, 31 May 2011 11:43:39 GMT
	(envelope-from nobody@red.freebsd.org)
Received: (from nobody@localhost)
	by red.freebsd.org (8.14.4/8.14.4/Submit) id p4VBhcI9084533;
	Tue, 31 May 2011 11:43:39 GMT
	(envelope-from nobody)
Message-Id: <201105311143.p4VBhcI9084533@red.freebsd.org>
Date: Tue, 31 May 2011 11:43:39 GMT
From: Eugen Konkov <kes-kes@yandex.ru>
To: freebsd-gnats-submit@FreeBSD.org
Subject: system hungup while fsck background check
X-Send-Pr-Version: www-3.1
X-GNATS-Notify:

>Number:         157460
>Category:       i386
>Synopsis:       system hungup while fsck background check
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-i386
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue May 31 11:50:04 UTC 2011
>Closed-Date:    Tue May 31 17:45:51 UTC 2011
>Last-Modified:  Fri Dec  9 05:50:04 UTC 2011
>Originator:     Eugen Konkov
>Release:        9-0 Current
>Organization:
ISP FreeLine
>Environment:
# uname -a
FreeBSD flux 9.0-CURRENT FreeBSD 9.0-CURRENT #1: Wed May 18 23:23:04 UTC 2011     @:/usr/obj/usr/src/sys/PAE_KES  i386

>Description:
after hard reboot system hungup by fsck.

Disks   ad0                                        221724 wire
KB/t  16.00                                         35632 act
tps      74                                       1434204 inact
MB/s   1.16                                          2612 cache
%busy   100                                       2297564 free


# top
last pid: 57757;  load averages:  0.00,  0.00,  0.03    up 0+02:10:39  14:34:04
51 processes:  1 running, 49 sleeping, 1 zombie
CPU:  0.0% user,  0.0% nice,  0.5% system,  0.5% interrupt, 99.1% idle
Mem: 35M Active, 1401M Inact, 217M Wired, 2612K Cache, 112M Buf, 2243M Free
Swap: 4096M Total, 4096M Free

  PID USERNAME  THR PRI NICE   SIZE    RES STATE   C   TIME   WCPU COMMAND
 1464 root        1  36    0  9568K  1196K snaprd  3   0:10  0.00% fsck_ufs
 1443 adm         1  36    0 15696K  4860K select  2   0:03  0.00% sshd
 1451 root        1  36    0 13136K  5084K select  1   0:01  0.00% mc
 2210 adm         1  36    0 15696K  4792K select  3   0:00  0.00% sshd
 1345 root        1  36    0 11336K  3520K select  2   0:00  0.00% sendmail
 2199 root        1  36    0 15696K  4780K sbwait  3   0:00  0.00% sshd
 1439 root        1  36    0 15696K  4760K sbwait  1   0:00  0.00% sshd
57753 root        1  36    0  9952K  2080K CPU1    1   0:00  0.00% top
57679 root        1  36    0  8032K   820K snaplk  3   0:00  0.00% config
57728 root        1  37    0 15696K  4780K sbwait  2   0:00  0.00% sshd
 2214 root        1  36    0 10896K  3004K ppwait  1   0:00  0.00% csh
57731 adm         1  36    0 15696K  4788K select  2   0:00  0.00% sshd
 1452 root        1  36    0 10896K  3008K pause   0   0:00  0.00% csh
 1013 root        1  36    0  9624K  1460K select  0   0:00  0.00% syslogd

flux# kill -TERM 1464
flux# kill -TERM 1464
flux#
flux#
flux# kill -TERM 1464
flux#
flux#
flux# kill -TERM 1464
flux# kill -TERM 1464
flux# kill -TERM 1464
flux# kill -TERM 1464
flux# kill -TERM 1464
# man kill


^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C
****CONSOLE HUNGS UP ((((
any disk usage cause program to stop. It is even impossible to kill -KILL that process.

It is impossible to shutdown computer. It syncyng disks foreever.
>How-To-Repeat:
hard reboot. HDD is sumsung 2TB

>Fix:


>Release-Note:
>Audit-Trail:

From: Remko Lodder <remko@elvandar.org>
To: Eugen Konkov <kes-kes@yandex.ru>
Cc: freebsd-gnats-submit@FreeBSD.org
Subject: Re: i386/157460: system hungup while fsck background check
Date: Tue, 31 May 2011 16:16:40 +0200

 >=20
 
 
 Hello,
 
 I got rid of the initial report since this will be logged to GNATS as =
 well it's not needed to reduplicate the info. I have seen this behaviour
 a few times when there were things to fix and it slowed down my system =
 for a little (I dont have that big disks) after which it continued to
 work.
 
 Can you define what you mean with "Syncing forever", how much time did =
 you wait for thinking this? Remember that a 2TB disk is rather
 big and that an FSCK takes a lot of time on those kind of disks. Please =
 wait a little longer to allow the diskcheck to clear before continueing.
 (and one more thing, at least you have access to the system if you have =
 this with lets say WinXP the system will not start before doing the
 check, letting you wait for a long period of time if you are unlucky).
 
 Thanks
 Remko
 
 --=20
 /"\   Best regards,                        | remko@FreeBSD.org
 \ /   Remko Lodder                      |
 X    http://www.evilcoder.org/    | Quis custodiet ipsos custodes
 / \   ASCII Ribbon Campaign    | Against HTML Mail and News
 
 
 
 

From: =?windows-1251?B?yu7t/Oru4iDF4uPl7ejp?= <kes-kes@yandex.ru>
To: bug-followup@FreeBSD.org, kes-kes@yandex.ru
Cc:  
Subject: Re: i386/157460: system hungup while fsck background check
Date: Tue, 31 May 2011 20:39:43 +0300

 Hi.
 I wait about one an hour.
 as you can see.
 #man kill
 does not show any info. it is locked, as I think, by fsck (see top)
 very interesting fack that
 #kill -KILL
 #kill -ABRT
 #kill -TERM
 those do not! kill a process, not 'man', not 'fsck'
 I just press CTRL+ALT+DEL and see that system stale on
 'syncing disks 22 2 2 2 2 2 2 2 2 2 1 timeout 291
 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 1 1 1 1 2 timeout
 291 '
 I wait one an hour yet, but nothing happen.
 
 I 'reset' computer. go to single mode.
 fsck -y
 it take about 10min to clean the disk.
 I reboto and get system to work.
 
 I think that 'fsck' do interactive fscking in backgroupd.
 so I add 'fsck_y_enable="YES"' to rc.conf as I did for my other
 systems.
 
 -- 
  ,
                            mailto:kes-kes@yandex.ru
 
State-Changed-From-To: open->closed 
State-Changed-By: remko 
State-Changed-When: Tue May 31 17:45:50 UTC 2011 
State-Changed-Why:  
I do not think this is a problem, you let the system not properly check 
itself and think that it will be recovered within 10 minutes (on a 2TB 
disk). 

http://www.freebsd.org/cgi/query-pr.cgi?pr=157460 

From: =?windows-1251?B?yu7t/Oru4iDF4uPl7ejp?= <kes-kes@yandex.ru>
To: bug-followup@FreeBSD.org, kes-kes@yandex.ru
Cc:  
Subject: Re: i386/157460: system hungup while fsck background check
Date: Tue, 31 May 2011 21:16:30 +0300

 Hi.
 
 How about that other processes is locked out and I can not do
 anything? you have saw that processes are unkillable.
 
 Remko. tell me please where I can post photos or, may be, videos
 what is coming on when this happen?
 

From: =?windows-1251?B?yu7t/Oru4iDF4uPl7ejp?= <kes-kes@yandex.ru>
To: bug-followup@FreeBSD.org, kes-kes@yandex.ru
Cc:  
Subject: Re: i386/157460: system hungup while fsck background check
Date: Fri, 9 Dec 2011 06:14:44 +0200

 I  think this is like same
 
 ia64/149208: mksnap_ffs hang/deadlock
 
 system utiliies flood IO stack so other programms can not do anything
 
 -- 
  ,
                            mailto:kes-kes@yandex.ru
 

From: =?windows-1251?B?yu7t/Oru4iDF4uPl7ejp?= <kes-kes@yandex.ru>
To: bug-followup@FreeBSD.org, kes-kes@yandex.ru
Cc:  
Subject: Re: i386/157460: system hungup while fsck background check
Date: Fri, 9 Dec 2011 07:44:53 +0200

 another yet comment
 
 this process (fsck) does not allow even READ operation on disk.
 so system in deadlock until fsck complete
 
 
>Unformatted:
