From owner-freebsd-current@FreeBSD.ORG Mon Apr 26 14:04:27 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 86EBF106566B for ; Mon, 26 Apr 2010 14:04:27 +0000 (UTC) (envelope-from dikshie@gmail.com) Received: from mail-pz0-f201.google.com (mail-pz0-f201.google.com [209.85.222.201]) by mx1.freebsd.org (Postfix) with ESMTP id 5E98B8FC14 for ; Mon, 26 Apr 2010 14:04:27 +0000 (UTC) Received: by pzk39 with SMTP id 39so581037pzk.7 for ; Mon, 26 Apr 2010 07:04:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:content-type; bh=Z34mvtJpZTvT5HK/z95hMD6QKYjug2e+3BNCxh19qLA=; b=hiIXFjK/1CPMo4wqthMbMNZGAxmAWQ6txMR2iKN3RJ35jNfJbxIDdHBxilGom3ZBWW MFDWai7psYkQbKURIaWJDOflXfVKyfiRL09OqBzsAPmSrTJ16+exaLS6Lk8lbOejl3xX 1JlhxcnLUbP4zz0yOV/L4eOo9w02tp0nInNpQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; b=GSVDBROwOzcYTOwaB0y+H0ggnr/WHJOOFcd5MTn635pFgj/ivjF0DrJpuxTm54DiMt ieN2Z1Q5p+k/7vi+TQ9qmIrvNj+/JFqjqcPEchVrHJEtSYwVxByM4h8k2Up62hUYfJ82 EUbeWcHCRFnc3qLT7cZ0taf0RYUCGwNm6tlrg= Received: by 10.143.193.8 with SMTP id v8mr1793461wfp.162.1272289344101; Mon, 26 Apr 2010 06:42:24 -0700 (PDT) MIME-Version: 1.0 Received: by 10.143.168.6 with HTTP; Mon, 26 Apr 2010 06:42:04 -0700 (PDT) In-Reply-To: References: From: dikshie Date: Mon, 26 Apr 2010 22:42:04 +0900 Message-ID: To: current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: Subject: Re: HEADS UP: SUJ Going in to head today X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Apr 2010 14:04:27 -0000 Hi Jeff, thanks for SUJ. btw, why there is nan% utilization? and what does it mean? -------------- ** SU+J Recovering /dev/ad0s1g ** Reading 33554432 byte journal from inode 4. ** Building recovery table. ** Resolving unreferenced inode list. ** Processing journal entries. ** 0 journal records in 0 bytes for nan% utilization <==== ** Freed 0 inodes (0 dirs) 0 blocks, and 0 frags. -------------- thanks! -dikshie-