From owner-freebsd-stable@FreeBSD.ORG Sat Aug 2 22:07:38 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 23973106566B for ; Sat, 2 Aug 2008 22:07:38 +0000 (UTC) (envelope-from jille@quis.cx) Received: from smtp2.versatel.nl (smtp2.versatel.nl [62.58.50.89]) by mx1.freebsd.org (Postfix) with ESMTP id 8A7C68FC13 for ; Sat, 2 Aug 2008 22:07:37 +0000 (UTC) (envelope-from jille@quis.cx) Received: (qmail 2913 invoked by uid 0); 2 Aug 2008 21:40:55 -0000 Received: from ip83-113-174-82.adsl2.static.versatel.nl (HELO istud.quis.cx) ([82.174.113.83]) (envelope-sender ) by smtp2.versatel.nl (qmail-ldap-1.03) with SMTP for < >; 2 Aug 2008 21:40:55 -0000 Received: from [192.168.1.4] (ille [192.168.1.4]) by istud.quis.cx (Postfix) with ESMTP id E13055C1D; Sat, 2 Aug 2008 23:40:54 +0200 (CEST) Message-ID: <4894D462.5@quis.cx> Date: Sat, 02 Aug 2008 23:40:50 +0200 From: Jille User-Agent: Thunderbird 2.0.0.16 (Windows/20080708) MIME-Version: 1.0 To: Eugene Butusov References: <4894CE6D.2000204@gmail.com> In-Reply-To: <4894CE6D.2000204@gmail.com> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD-STABLE-LIST Subject: Re: 7-STABLE, gjournal and fsck. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Aug 2008 22:07:38 -0000 Hello, I also had those "PARTIALLY ALLOCATED INODE", errors. They only happened on one disk (SATA with PCI SATA converter), and my other ATA disks worked fine. I unplugged my SATA disk, and the ATA's started giving errors. Well, whatever, I screwed up my hardware with a really dumb mistake (don't even dare telling you) and that let it give some quite random errors. So you might want to do some real good hardware checks ;) -- Jille Eugene Butusov schreef: > Hi, > > Recently I've decided to play with gjournal. Main reason was a promise > of avoiding full fsck check after unclean shutdown. I've successfuly > configured gjournal on existing filesystems (all UFS). And then it > happened - my system had a power failure. After boot, it forced me to > run fsck manualy. Nothing special, I did it before... But this time it > failed on gjournaled disks. > > So, when I was dropped to the single-user shell, I tried: > > fsck /dev/ad4s1g.journal > > It said: > > CANNOT READ BLK: xxxx > CONTINUE? [yn] > > I typed 'y' and nothing happened. Here is the log: > > -8<- > Aug 2 19:13:43 matrix kernel: GEOM_JOURNAL: Journal 4059706613: ad4s1g > contains data. > Aug 2 19:13:43 matrix kernel: GEOM_JOURNAL: Journal 4059706613: ad4s1g > contains journal. > Aug 2 19:13:43 matrix kernel: GEOM_JOURNAL: Journal ad4s1g clean. > Aug 2 19:13:43 matrix kernel: GEOM_JOURNAL: Journal 188084099: ad6s1d > contains data. > Aug 2 19:13:43 matrix kernel: GEOM_JOURNAL: Journal 188084099: ad6s1d > contains journal. > Aug 2 19:13:43 matrix kernel: GEOM_JOURNAL: Journal ad6s1d clean. > Aug 2 19:13:43 matrix kernel: GEOM_JOURNAL: Journal 2559963968: ad6s1e > contains data. > Aug 2 19:13:43 matrix kernel: GEOM_JOURNAL: Journal 2559963968: ad6s1e > contains journal. > Aug 2 19:13:43 matrix kernel: GEOM_JOURNAL: Journal ad6s1e clean. > ... > Aug 2 19:13:43 matrix kernel: ** /dev/ad4s1g.journal > Aug 2 19:13:43 matrix kernel: > Aug 2 19:13:43 matrix kernel: CANNOT READ BLK: 727112224 > Aug 2 19:13:43 matrix kernel: CONTINUE? [yn] > Aug 2 19:13:43 matrix kernel: > Aug 2 19:13:43 matrix kernel: THE FOLLOWING DISK SECTORS COULD NOT BE > READ: 727112224, 727112225, 727112226, 727112227, > Aug 2 19:13:43 matrix kernel: /dev/ad4s1g.journal: CANNOT FIGURE OUT > FILE SYSTEM PARTITION > ->8- > > After ctrl+d the system tried to continue boot, and again threw me into > shell because of the same reason: > > -8<- > Aug 2 19:13:43 matrix kernel: > WARNING: R/W mount of /home denied. Filesystem is not clean - run fsck > Aug 2 19:13:43 matrix kernel: mount: > ->8- > > Like I mentioned, only gjournaled filesystems failed to pass fsck. Other > labels passed. I was in a hurry, because the machine acts as a local > file server, and I was standing against the wall, because one of > gjournaled disks was the share itself... > > What I did was mounting gjournaled partitions in ro mode (it warned me > that they were not cleanly unmounted) and doing some backup. Then I > removed gjournal (gjournal clear, tunefs -J disable) from journaled > disks, ran fsck (few errors of type: PARTIALLY ALLOCATED INODE), and > then I was able to turn on softupdates back and mount the fs in rw mode. > I've double checked the disk's SMART results in case of hardware > failure, but they were ok. > > My question is: what could cause such problem? Why only gjournaled fs > are affected? Is there a solution? > > Best regards,