From nobody@FreeBSD.org  Wed Jan 11 01:39:43 2012
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 4D8D2106567A
	for <freebsd-gnats-submit@FreeBSD.org>; Wed, 11 Jan 2012 01:39:43 +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 388E28FC1B
	for <freebsd-gnats-submit@FreeBSD.org>; Wed, 11 Jan 2012 01:39:43 +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 q0B1dgiV021860
	for <freebsd-gnats-submit@FreeBSD.org>; Wed, 11 Jan 2012 01:39:42 GMT
	(envelope-from nobody@red.freebsd.org)
Received: (from nobody@localhost)
	by red.freebsd.org (8.14.4/8.14.4/Submit) id q0B1dgDH021859;
	Wed, 11 Jan 2012 01:39:42 GMT
	(envelope-from nobody)
Message-Id: <201201110139.q0B1dgDH021859@red.freebsd.org>
Date: Wed, 11 Jan 2012 01:39:42 GMT
From: Eugen Konkov <kes-kes@yandex.ru>
To: freebsd-gnats-submit@FreeBSD.org
Subject: rebooting while fsck in progress cause start fsck again
X-Send-Pr-Version: www-3.1
X-GNATS-Notify:

>Number:         164005
>Category:       misc
>Synopsis:       rebooting while fsck in progress cause start fsck again
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Jan 11 01:40:08 UTC 2012
>Closed-Date:    Mon Mar 12 15:41:11 UTC 2012
>Last-Modified:  Mon Mar 12 15:41:11 UTC 2012
>Originator:     Eugen Konkov
>Release:        
>Organization:
ISP FreeLine
>Environment:
>Description:
when you reboot server while fsck_background  in progress system is locked up until fsck is completed, but after reboot it starts fsck in backgroup again because of fsck is late to save data about successfull check complete

1. system does not reboot because of it can not syncing while fsck lock filesystem
2. fsck can not write info about successfull ckeck because of reboot in progress and starts immediately after fsck unlock filesystem
>How-To-Repeat:
hard turnoff power
log in
reboot
 after this sytem is locked
 
 after reboot fsck starts again.
>Fix:


>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: jh 
State-Changed-When: Mon Mar 12 15:39:30 UTC 2012 
State-Changed-Why:  
This works as intended. File system operations are suspended while 
fsck_ffs(8) creates a snapshot. File system operations resume when the 
snapshot has been created but it doesn't mean that the actual file 
system checking has been completed. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=164005 
>Unformatted:
