From owner-freebsd-fs@FreeBSD.ORG Mon May 3 18:19:57 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7A9291065674 for ; Mon, 3 May 2010 18:19:57 +0000 (UTC) (envelope-from to.my.trociny@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.154]) by mx1.freebsd.org (Postfix) with ESMTP id 0E0B88FC12 for ; Mon, 3 May 2010 18:19:56 +0000 (UTC) Received: by fg-out-1718.google.com with SMTP id l26so896639fgb.13 for ; Mon, 03 May 2010 11:19:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:to:subject:organization:from :date:message-id:user-agent:mime-version:content-type; bh=cSAL4towBMRdCk/XxVDJK5yBfAIr59CwZVEiai0sLbE=; b=QJv/IDGTbFeZDtmtdTCIpqm5TyyhtMcmD85gnRf/riE9aSA5ntT5APtkb5kQvamn62 7NzPE1LG7KLxXZRSDl5Jn5k7HAN/QiTJ38GuibqqBfdp1GQyNI9qG5vwWm6fBF+nU8Qe lUVvDveLYETa62YxOuw+LzAJmUFyfRMP7+0l8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=to:subject:organization:from:date:message-id:user-agent :mime-version:content-type; b=GI0NvsQTuPazYIA3MrPrRnXsrAhiHic95G+TBthOMJ8Ef06oqItAzZW3p2/zvo0D9d 8TZJukUGISIIyfHr+q2YgcAwO1gvpIxHLFZFRMMtfIDx6EW0GkDJOd1LtKzXFY7NgHOM b77ky3GH4GFOcPoLJ32wB4QwFnMcAFI3/bo7U= Received: by 10.87.5.30 with SMTP id h30mr10979605fgi.3.1272910795956; Mon, 03 May 2010 11:19:55 -0700 (PDT) Received: from localhost ([95.69.170.5]) by mx.google.com with ESMTPS id 12sm8738976fgg.14.2010.05.03.11.19.54 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 03 May 2010 11:19:55 -0700 (PDT) To: freebsd-fs@FreeBSD.org Organization: Home From: Mikolaj Golub Date: Mon, 03 May 2010 21:19:52 +0300 Message-ID: <86bpcwluev.fsf@kopusha.onet> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Subject: SUJ: fsck_ufs: Sparse journal inode X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 May 2010 18:19:57 -0000 Hi, Experimenting with journaled soft-updates on HAST I observed the error when fscking fs on the secondary after primary "crash": # fsck -y -t ufs /dev/hast/tank ** /dev/hast/tank USE JOURNAL?? yes ** SU+J Recovering /dev/hast/tank ** Reading 33554384 byte journal from inode 4. fsck_ufs: Sparse journal inode 4 (blocks = 16376, numfrags = 16383). (The text between the parentheses is a local modification to the fsck code to output some useful values). So to recover I needed to run fsck and type "no" when prompted "USE JOURNAL?". But I am looking for a way to script automatic recovering from this situation. Currently the only way I have found is to disable journal, run fsck, mount fs somewhere temporary, remove .sujournal, unmount, enable journal. Is this really so complicated or may I just miss something? BTW, I used to observe this error on every "crash" test. And "blocks" value was always the same: 16376. So I changed journal size to 16376 * 2048 = 33538048. It looks like after this the issue has gone. -- Mikolaj Golub