From owner-freebsd-fs@FreeBSD.ORG Tue Dec 13 13:51:34 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5B795106564A for ; Tue, 13 Dec 2011 13:51:34 +0000 (UTC) (envelope-from siur.vvm@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 165F28FC0C for ; Tue, 13 Dec 2011 13:51:33 +0000 (UTC) Received: by vcbfk1 with SMTP id fk1so7909243vcb.13 for ; Tue, 13 Dec 2011 05:51:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=jK3n4pjCxjo107LNaEdAN3I32Kj1tEl7nhXY/K99vgE=; b=C7M816xhCuMv6ZwBhgBjSFUChlLMGt0q/YO8bVpf98/gXRX09SnaMCVnwzdo/Sn2iK FIBmUgYnyOPAmVwC2DLQLe6LGLs4th9rolpA1AP7Fn8RcU7oxBegxjWGqnvC9YbOMqPq QUdVjqdLOXZIwC4Hw+Awg+UzJnMax664VWIEg= MIME-Version: 1.0 Received: by 10.52.35.70 with SMTP id f6mr1262563vdj.84.1323784293324; Tue, 13 Dec 2011 05:51:33 -0800 (PST) Received: by 10.52.28.8 with HTTP; Tue, 13 Dec 2011 05:51:33 -0800 (PST) In-Reply-To: <4996422587176353892@unknownmsgid> References: <4996422587176353892@unknownmsgid> Date: Tue, 13 Dec 2011 17:51:33 +0400 Message-ID: From: siur To: =?UTF-8?Q?=C5=A0imun_Mikecin?= Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-fs@freebsd.org" Subject: Re: epic UFS crash 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: Tue, 13 Dec 2011 13:51:34 -0000 > That is what could happen if you are using RAID controller in > write-back mode without battery-backed RAM for write-back. > What kind of UFS is it? UFS1 or UFS2? > UFS+SU? GEOM Journaling? Why RAID-controller could write data only in a cache for almost a year?? It was UFS2, without journaling.