From owner-freebsd-geom@FreeBSD.ORG Mon Aug 25 11:06:50 2008 Return-Path: Delivered-To: freebsd-geom@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BDBDA106568B for ; Mon, 25 Aug 2008 11:06:50 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id C035A8FC21 for ; Mon, 25 Aug 2008 11:06:50 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m7PB6of3027755 for ; Mon, 25 Aug 2008 11:06:50 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m7PB6o8Y027751 for freebsd-geom@FreeBSD.org; Mon, 25 Aug 2008 11:06:50 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 25 Aug 2008 11:06:50 GMT Message-Id: <200808251106.m7PB6o8Y027751@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-geom@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-geom@FreeBSD.org X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Aug 2008 11:06:50 -0000 Current FreeBSD problem reports Critical problems Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- s kern/73177 geom kldload geom_* causes panic due to memory exhaustion o kern/84556 geom [geom] GBDE-encrypted swap causes panic at shutdown o kern/87544 geom [gbde] mmaping large files on a gbde filesystem deadlo s kern/89102 geom [geom] [panic] panic when forced unmount FS from unplu o kern/89546 geom [geom] GEOM error a kern/89660 geom [vinum] [patch] [panic] due to g_malloc returning null o bin/90093 geom fdisk(8) incapable of altering in-core geometry o kern/90582 geom [geom] [panic] Restore cause panic string (ffs_blkfree o kern/98034 geom [geom] dereference of NULL pointer in acd_geom_detach o kern/104389 geom [geom] [patch] sys/geom/geom_dump.c doesn't encode XML o kern/113419 geom [geom] geom fox multipathing not failing back o kern/113957 geom [gmirror] gmirror is intermittently reporting a degrad o kern/120021 geom net-p2p/qbittorrent crashes system when it works thoug o kern/120231 geom [geom] GEOM_CONCAT error adding second drive o kern/121364 geom [gmirror] Removing all providers create a "zombie" mir o kern/122067 geom [panic]: Geom crashed during boot f kern/122415 geom [geom] UFS labels are being constantly created and rem o kern/123122 geom [geom] GEOM / gjournal kernel lock o kern/123962 geom [panic] gjournal(8): gjournal (455Gb data, 8Gb journal o kern/124130 geom [gmirror][usb] gmirror fails to start usb devices that o kern/124294 geom [geom] gmirror(8) have inappropriate logic when workin o kern/124969 geom gvinum(8): gvinum raid5 plex does not detect missing s 22 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o bin/78131 geom gbde(8) "destroy" not working. o kern/79035 geom [vinum] gvinum unable to create a striped set of mirro o kern/79251 geom [2TB] newfs fails on 2.6TB gbde device o kern/94632 geom [geom] Kernel output resets input while GELI asks for o kern/107707 geom [geom] [patch] [request] add new class geom_xbox360 to p bin/110705 geom gmirror(8) control utility does not exit with correct o kern/113837 geom [geom] unable to access 1024 sector size storage o kern/113885 geom [gmirror] [patch] improved gmirror balance algorithm o kern/114532 geom [geom] GEOM_MIRROR shows up in kldstat even if compile f kern/115547 geom [geom] [patch] [request] let GEOM Eli get password fro o kern/119743 geom [geom] geom label for cds is keeped after dismount and o kern/120044 geom [msdosfs] [geom] incorrect MSDOSFS label fries adminis o kern/121559 geom [patch] [geom] geom label class allows to create inacc o kern/123630 geom [patch] [gmirror] gmirror doesnt allow the original dr o kern/124973 geom [gjournal] [patch] boot order affects geom_journal con 15 problems total. From owner-freebsd-geom@FreeBSD.ORG Thu Aug 28 14:27:08 2008 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7CA8A106567F for ; Thu, 28 Aug 2008 14:27:08 +0000 (UTC) (envelope-from bjmccann@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.177]) by mx1.freebsd.org (Postfix) with ESMTP id 39EFE8FC08 for ; Thu, 28 Aug 2008 14:27:08 +0000 (UTC) (envelope-from bjmccann@gmail.com) Received: by py-out-1112.google.com with SMTP id p76so244498pyb.10 for ; Thu, 28 Aug 2008 07:27:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=sSS/NauB282XXfQC59bIHKLV6S49SnALDZu5XIfRlM4=; b=VPuF4ueBL/Y+sOeK2wGdjMeJ7I0xNWR5Hv2Xg+skRhekcZp2TxVKqqx2wyrz2UEnpy Y0p2Vw6IDE5Nn2h/h7R77YkQBUmqQJ//GzakxQNutYfiQXWfzV4MiKqyUk5DJ4FDGJ0z /IBGH4w3mfZJ/iE/FuBDZYat8hT9+thfggCyg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=bbvxDIxFZEpZ5VIQub8lvN2VhhnR7+FJtcBH6bEtrfzKWUNX0Wo+nNZWObisDPKXDw 6PBxJ1WWOK4W0VESrwBba9IpP0W5CLEMnCffEEE3bBNULNPcOA+FbRRRQhdmbp1A0RGB uzwKMgqMgqWG30u6PR8r5qB0Y0C01frs9l6ms= Received: by 10.141.162.6 with SMTP id p6mr755861rvo.121.1219932334317; Thu, 28 Aug 2008 07:05:34 -0700 (PDT) Received: by 10.140.207.5 with HTTP; Thu, 28 Aug 2008 07:05:34 -0700 (PDT) Message-ID: <2b5f066d0808280705y3454c188v768efe46b388864b@mail.gmail.com> Date: Thu, 28 Aug 2008 10:05:34 -0400 From: "Brian McCann" To: freebsd-questions , freebsd-geom@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: Subject: gjournal & fsck X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Aug 2008 14:27:08 -0000 Hi all. I'm having some problems with several servers I've built recently (7.0-RELEASE) that are using gjournal. I had two reboot a few days ago (un-related to FreeBSD problems I think)...but when they came back up, the file systems wouldn't mount since they were not clean. Now, I understand that UFS knows nothing about the fact that it's journaled, and the journaling knows nothing about UFS...but it's my understanding that by using gjournal, you should really never need to fsck a file system. However, the only way to get them to mount is by doing the fsck. Is there something else I should be doing instead of fsck? And since I know it will probably come up, I built the file systems using the instructions and notes at http://www.freebsd.org/cgi/man.cgi?query=gjournal&apropos=0&sektion=0&manpath=FreeBSD+7.0-RELEASE&format=html. Any help would be greatly appreciated! Thanks! --Brian -- _-=-_-=-_-=-_-=-_-=-_-=-_-=-_-=-_-=-_-=-_-=-_ Brian McCann "I don't have to take this abuse from you -- I've got hundreds of people waiting to abuse me." -- Bill Murray, "Ghostbusters" From owner-freebsd-geom@FreeBSD.ORG Thu Aug 28 14:43:59 2008 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 872B71065684 for ; Thu, 28 Aug 2008 14:43:59 +0000 (UTC) (envelope-from bjmccann@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.236]) by mx1.freebsd.org (Postfix) with ESMTP id 5DB728FC1B for ; Thu, 28 Aug 2008 14:43:59 +0000 (UTC) (envelope-from bjmccann@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so547120rvf.43 for ; Thu, 28 Aug 2008 07:43:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=y49Ol0OvVkr5vG6tLX/UIpSAPsLOzHe3QPbDuQNgisI=; b=tkw6vHyPlrKiOFPkffT4EzlaWwhNDWXR6HT6srm6ibHT/ZJhlnokg2KtHYEN0s8g1Y YLQkl7WOXT+HHe9SB60U5iPp2JLOfKp9uopxAzvj7BQNpXzG91BKWH0cpbL8dpiJYqKl U+YomWwpgtfR8vUK/gLY99ziMXEn0ZOZMf4n4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=sslZIcu/NV1O+u2pK8ZLbZ6IfJD7rgxBe/QBLSt0slDsQcYiHaHYwL0M8O/60lj0hn 34qDTNu/0exbJam22xg2vbz07Dl3yjyTmtfQHq8mjBDJSuRdp6jgeGGK6tjxRmTuvUFV /iSBala5ETwOczbRW2Ez8ReMp2u5MBzvbhf2M= Received: by 10.140.177.15 with SMTP id z15mr797975rve.52.1219934638465; Thu, 28 Aug 2008 07:43:58 -0700 (PDT) Received: by 10.140.207.5 with HTTP; Thu, 28 Aug 2008 07:43:58 -0700 (PDT) Message-ID: <2b5f066d0808280743g69c32d1rd30aee0ca276125@mail.gmail.com> Date: Thu, 28 Aug 2008 10:43:58 -0400 From: "Brian McCann" To: "Ivan Voras" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2b5f066d0808280705y3454c188v768efe46b388864b@mail.gmail.com> Cc: freebsd-questions@freebsd.org, freebsd-geom@freebsd.org Subject: Re: gjournal & fsck X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Aug 2008 14:43:59 -0000 On Thu, Aug 28, 2008 at 10:34 AM, Ivan Voras wrote: > Brian McCann wrote: >> Hi all. I'm having some problems with several servers I've built >> recently (7.0-RELEASE) that are using gjournal. I had two reboot a >> few days ago (un-related to FreeBSD problems I think)...but when they >> came back up, the file systems wouldn't mount since they were not >> clean. Now, I understand that UFS knows nothing about the fact that >> it's journaled, and the journaling knows nothing about UFS...but it's > > Actually UFS needs to know about gjournal for just this purpose. There's > a special option to newfs that tells the file system to be aware of > gjournal and it should request fscks. > >> my understanding that by using gjournal, you should really never need >> to fsck a file system. However, the only way to get them to mount is >> by doing the fsck. Is there something else I should be doing instead >> of fsck? > > man 8 tunefs > Yes...I apologize...I did that when I built the file system with "newfs -J". Here's the tunefs -p output for one of the file systems: # tunefs -p /dev/da2.journal tunefs: ACLs: (-a) disabled tunefs: MAC multilabel: (-l) disabled tunefs: soft updates: (-n) disabled tunefs: gjournal: (-J) enabled tunefs: maximum blocks per file in a cylinder group: (-e) 2048 tunefs: average file size: (-f) 16384 tunefs: average number of files in a directory: (-s) 64 tunefs: minimum percentage of free space: (-m) 8% tunefs: optimization preference: (-o) time tunefs: volume label: (-L) I'm concerned about this because the ones I've had problems with recently are 1.1TB arrays...I've got 2 8.6TB arrays that are journaled as well...and if I ever have to fsck them...that could take 1/2 the day... Any other thoughts? Thanks for the help so far Ivan! --Brian From owner-freebsd-geom@FreeBSD.ORG Thu Aug 28 14:57:24 2008 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 121F4106567C for ; Thu, 28 Aug 2008 14:57:24 +0000 (UTC) (envelope-from bjmccann@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.232]) by mx1.freebsd.org (Postfix) with ESMTP id DD2C38FC24 for ; Thu, 28 Aug 2008 14:57:23 +0000 (UTC) (envelope-from bjmccann@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so553996rvf.43 for ; Thu, 28 Aug 2008 07:57:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=ju8kdotsCmn96Z+MD0p0fBaHRQLZvKZy1EcA4tZasKU=; b=qjFOE7C9MmsoDqOOSyv7fAhIDZPNInHQmO7HDZuTptbblEMdVgfKt5+wj/Ib8ecOKN kXkAUR8UGpPjQ/5ixmGN1ZXDNVTOV5rk3gotAGtXJkxkoh3+aus+DOH82w8uzfhEx30X np63wRiCsYcH6tCxOheqqKdpyqjH9y+AmFOm8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=wB4CmP8nepV9Z6y0cuSRSh8x1eZuzVLfwe96vVD3nI+5PT580jzpGfEms8oNP2z+Lt HsK1jFpInXQbEjq4IAx8wNpVTmFYpeKd1+9o8ZFfWyFRWKJ8tM0/qihvNXdQ4xt2xDH/ RIs+qn89ovPs2E2em11qI45Az1y3zKZqlXxEo= Received: by 10.140.201.4 with SMTP id y4mr803857rvf.86.1219935443377; Thu, 28 Aug 2008 07:57:23 -0700 (PDT) Received: by 10.140.207.5 with HTTP; Thu, 28 Aug 2008 07:57:23 -0700 (PDT) Message-ID: <2b5f066d0808280757h6caeffa8h13d45dd668434156@mail.gmail.com> Date: Thu, 28 Aug 2008 10:57:23 -0400 From: "Brian McCann" To: "Manolis Kiagias" In-Reply-To: <48B6B9D0.8060302@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2b5f066d0808280705y3454c188v768efe46b388864b@mail.gmail.com> <48B6B9D0.8060302@gmail.com> Cc: freebsd-questions , freebsd-geom@freebsd.org Subject: Re: gjournal & fsck X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Aug 2008 14:57:24 -0000 > > You may wish to have a look at this article: > > http://www.freebsd.org/doc/en_US.ISO8859-1/articles/gjournal-desktop Great article...thanks. Bookmarked for future use too! > In particular, you should make sure you use tunefs to enable Journaling and > disable soft update on the journaled filesystems, i.e.: > > tunefs -J enable -n disable /dev/ad0s1f.journal I was mistaken...I did this when I made the file system...I just posted a message to the thread showing the output of tunefs -p, but soft-updates are off, and journaling does show as on. > > Mount them using the async option: > > /dev/ad0s1f.journal /usr ufs rw,async 2 2 Here's my fstab line: /dev/da1.journal /files6/array2 ufs rw,async,nosuid,noatime 2 2 > > Note that the pass # still indicates the filesystem should be checked. While > I was writing the article, I was trying several scenarios were I had the > pass # set to 0, thinking that a gjournaled filesystem would not need fsck > at all. I would then press the reset button. In most cases, the system would > refuse to mount them. However with the pass # set, the fsck would finish > almost immediately, since the actual consistency check takes place when the > gjournal module is loaded (you will get a "journal consistent" after a bad > reboot) and before fstab is even parsed. All fsck does in this case is > simply confirm to the system it is a clean volume. > > In short, leaving the pass # to something that would cause an fsck is the > safe way to go. The fsck will be almost instant anyway. > > The file system is about 1.1TB, and I've got 2 of them that are journaled on this particular server. One is currently empty, and fsck's in about 10-15 mins, while the other is 31% used, and takes about 45 mins. Thanks for your help thus far! --Brian From owner-freebsd-geom@FreeBSD.ORG Thu Aug 28 15:03:49 2008 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EEAD5106564A for ; Thu, 28 Aug 2008 15:03:49 +0000 (UTC) (envelope-from bjmccann@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.236]) by mx1.freebsd.org (Postfix) with ESMTP id C47708FC21 for ; Thu, 28 Aug 2008 15:03:49 +0000 (UTC) (envelope-from bjmccann@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so557196rvf.43 for ; Thu, 28 Aug 2008 08:03:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=FX6aUpxlLF1SauMlNKo9fjF5teXYq+EAFFY9CgjzIrs=; b=d9Ieq+qdmyzgKcj4lvurRqNHzgiVOE2KvW1EFW9qBtgGHrYeUc5Ig/2Pm+r2IRcd6u K+M6tmfMckLfBrsP/kTU1u5Ign336i+RtKP7aZuvhGnfD+Oo4Osu+7OHWfdO729MB3mS Z5VIIlEHDljgAS/HGGX7tLbr+ntOT9Iy/Tf5s= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=Qaud6+YtLTT56N/UhPYSXPimLAaYM2w4i3SirC5tu2yQ+bRvk9cYOobtYjuGUEGObF 1Jbeq+kbJl0xo3bR1NAiCg2aHlBZQ2dT2XduenvUnHTGDwMpoHUgFXeRqDVgNMFlFxTQ YRk9E6qdIo438tgQTYC0T04kypcBE8BuPCL+A= Received: by 10.141.63.20 with SMTP id q20mr776300rvk.291.1219935829174; Thu, 28 Aug 2008 08:03:49 -0700 (PDT) Received: by 10.140.207.5 with HTTP; Thu, 28 Aug 2008 08:03:49 -0700 (PDT) Message-ID: <2b5f066d0808280803ibca3f61xbb167bce384f228@mail.gmail.com> Date: Thu, 28 Aug 2008 11:03:49 -0400 From: "Brian McCann" To: "Ivan Voras" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2b5f066d0808280705y3454c188v768efe46b388864b@mail.gmail.com> <2b5f066d0808280743g69c32d1rd30aee0ca276125@mail.gmail.com> Cc: freebsd-questions@freebsd.org, freebsd-geom@freebsd.org Subject: Re: gjournal & fsck X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Aug 2008 15:03:50 -0000 On Thu, Aug 28, 2008 at 10:51 AM, Ivan Voras wrote: > > Does gjournal complain about your drive, for example that it doesn't > support BIOFLUSH? Actually yes...I meant to post them in my last message, but hit send too early...here's my output from boot (from dmesg.boot) GEOM_JOURNAL: Journal 478661671: da1 contains data. GEOM_JOURNAL: Journal 478661671: da1 contains journal. GEOM_JOURNAL: Journal da1 clean. (da1:mly0:4:1:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 (da1:mly0:4:1:0): CAM Status: SCSI Status Error (da1:mly0:4:1:0): SCSI Status: Check Condition (da1:mly0:4:1:0): ILLEGAL REQUEST asc:24,0 (da1:mly0:4:1:0): Invalid field in CDB (da1:mly0:4:1:0): Unretryable error GEOM_JOURNAL: BIO_FLUSH not supported by da1. GEOM_JOURNAL: Journal 3065355517: da2 contains data. GEOM_JOURNAL: Journal 3065355517: da2 contains journal. GEOM_JOURNAL: Journal da2 clean. (da2:mly1:4:0:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 (da2:mly1:4:0:0): CAM Status: SCSI Status Error (da2:mly1:4:0:0): SCSI Status: Check Condition (da2:mly1:4:0:0): ILLEGAL REQUEST asc:24,0 (da2:mly1:4:0:0): Invalid field in CDB (da2:mly1:4:0:0): Unretryable error GEOM_JOURNAL: BIO_FLUSH not supported by da2. > > Also, did fsck actually do something when it was started (did it find > anything corrupted)? > No...it didn't find anything wrong / anything to fix. (and one of the file systems was being written to at the time...so at least journaling appears to be working) Something else I noticed...Manolis' article says it should say "journal xxxx consistent"...whereas mine says "Journal xxxx clean". I don't know what the differences mean, or what the BIO_FLUSH means...but I'm hoping you can tell me. :) Thanks again! --Brian From owner-freebsd-geom@FreeBSD.ORG Thu Aug 28 15:06:00 2008 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 225F91065670 for ; Thu, 28 Aug 2008 15:06:00 +0000 (UTC) (envelope-from bjmccann@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.236]) by mx1.freebsd.org (Postfix) with ESMTP id E98A58FC19 for ; Thu, 28 Aug 2008 15:05:59 +0000 (UTC) (envelope-from bjmccann@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so558143rvf.43 for ; Thu, 28 Aug 2008 08:05:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=SjNKx4bOSBLl06LHt+ARFvEfoz8T7mjOjALz3HfaNMg=; b=MoiJZs8DrsJsfeg9jGw4P2R5Xtyh/ZxQfxe2oM2iwqv8JZXEYOC4/zT5T2euzn7uKu vRCEocuEvGLlZRFvFpGScVDehSTWwjIw557Z8wdJ6QNst7KBtelyjR4zrJDKyy34Bl20 4UaVyOCIpa/Vkzqm/nWqEr26zzuW0OGHWeD2s= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=CUL6bVYcsdYokEa8ngwxSPXKUrSeyZdi1K6foBOMyjWIUnZfGuqhswJMEmJpVjOMts f0sl9sXbU4Ux6itfbmIB4T0L2hWlFRJQweKKIeQtUqIRFjgXZtEEiLLw9JB8HQnmuGqb FIKUIb59GLsmXkRoAkYd/tu0Hl3lEmbv7BJuA= Received: by 10.141.142.15 with SMTP id u15mr817214rvn.51.1219935959595; Thu, 28 Aug 2008 08:05:59 -0700 (PDT) Received: by 10.140.207.5 with HTTP; Thu, 28 Aug 2008 08:05:59 -0700 (PDT) Message-ID: <2b5f066d0808280805t4c5f7051i60d02c7396c5f06d@mail.gmail.com> Date: Thu, 28 Aug 2008 11:05:59 -0400 From: "Brian McCann" To: "Ivan Voras" In-Reply-To: <2b5f066d0808280803ibca3f61xbb167bce384f228@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2b5f066d0808280705y3454c188v768efe46b388864b@mail.gmail.com> <2b5f066d0808280743g69c32d1rd30aee0ca276125@mail.gmail.com> <2b5f066d0808280803ibca3f61xbb167bce384f228@mail.gmail.com> Cc: freebsd-questions@freebsd.org, freebsd-geom@freebsd.org Subject: Re: gjournal & fsck X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Aug 2008 15:06:00 -0000 On Thu, Aug 28, 2008 at 11:03 AM, Brian McCann wrote: > On Thu, Aug 28, 2008 at 10:51 AM, Ivan Voras wrote: >> >> Does gjournal complain about your drive, for example that it doesn't >> support BIOFLUSH? > > Actually yes...I meant to post them in my last message, but hit send > too early...here's my output from boot (from dmesg.boot) > > GEOM_JOURNAL: Journal 478661671: da1 contains data. > GEOM_JOURNAL: Journal 478661671: da1 contains journal. > GEOM_JOURNAL: Journal da1 clean. > (da1:mly0:4:1:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 > (da1:mly0:4:1:0): CAM Status: SCSI Status Error > (da1:mly0:4:1:0): SCSI Status: Check Condition > (da1:mly0:4:1:0): ILLEGAL REQUEST asc:24,0 > (da1:mly0:4:1:0): Invalid field in CDB > (da1:mly0:4:1:0): Unretryable error > GEOM_JOURNAL: BIO_FLUSH not supported by da1. > GEOM_JOURNAL: Journal 3065355517: da2 contains data. > GEOM_JOURNAL: Journal 3065355517: da2 contains journal. > GEOM_JOURNAL: Journal da2 clean. > (da2:mly1:4:0:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 > (da2:mly1:4:0:0): CAM Status: SCSI Status Error > (da2:mly1:4:0:0): SCSI Status: Check Condition > (da2:mly1:4:0:0): ILLEGAL REQUEST asc:24,0 > (da2:mly1:4:0:0): Invalid field in CDB > (da2:mly1:4:0:0): Unretryable error > GEOM_JOURNAL: BIO_FLUSH not supported by da2. > >> >> Also, did fsck actually do something when it was started (did it find >> anything corrupted)? >> > No...it didn't find anything wrong / anything to fix. (and one of the > file systems was being written to at the time...so at least journaling > appears to be working) Something else I noticed...Manolis' article > says it should say "journal xxxx consistent"...whereas mine says > "Journal xxxx clean". I don't know what the differences mean, or what > the BIO_FLUSH means...but I'm hoping you can tell me. :) > > Thanks again! > --Brian > I should probably also mention that this is on a Mylex 2000 RAID controller...with a RAID-5 array and using write-caching. Thanks --Brian From owner-freebsd-geom@FreeBSD.ORG Thu Aug 28 15:17:03 2008 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 683751065678 for ; Thu, 28 Aug 2008 15:17:03 +0000 (UTC) (envelope-from sonic2000gr@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.157]) by mx1.freebsd.org (Postfix) with ESMTP id E99A18FC22 for ; Thu, 28 Aug 2008 15:17:02 +0000 (UTC) (envelope-from sonic2000gr@gmail.com) Received: by fg-out-1718.google.com with SMTP id l26so315456fgb.35 for ; Thu, 28 Aug 2008 08:17:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=bdUEcSnnnq8mz97oo6fHZpJrkEWJOC8sahOX9RdOafk=; b=vPIQjR9re6r728z0ZFM7ZNm4GEtTlmetldU4ahDgVuW6JqK/SQ73Rdv1ekyX7hb+IV L+0Eu8SNkFBeLDCX7u496oJqxlraJtoiK/BZlWYufdB4vRSSleMHvtHJt8IMxHDXRxsu WToyIRxsZrFPbLhII34buP1W8KZxP5b4lCZNo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=wmEV2ey30l3/EPZqra608wKvV7G7peinPH2UcrzPxFD9BXEPT8bGm7P5eexnTgQSUn p/Og7s84wP2Raug4PFhIRw04vGB4U7r4TmjZG2sCX+IxC7sDorSw39jIfxytfPfC3bCy iLOw21Xx5edbqiwr168Jxc0HiNjFl4hGkfs18= Received: by 10.180.240.10 with SMTP id n10mr2232425bkh.69.1219934675923; Thu, 28 Aug 2008 07:44:35 -0700 (PDT) Received: from atlantis.dyndns.org ( [87.203.65.104]) by mx.google.com with ESMTPS id 12sm845974fks.9.2008.08.28.07.44.34 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 28 Aug 2008 07:44:35 -0700 (PDT) Message-ID: <48B6B9D0.8060302@gmail.com> Date: Thu, 28 Aug 2008 17:44:32 +0300 From: Manolis Kiagias User-Agent: Thunderbird 2.0.0.14 (X11/20080703) MIME-Version: 1.0 To: Brian McCann References: <2b5f066d0808280705y3454c188v768efe46b388864b@mail.gmail.com> In-Reply-To: <2b5f066d0808280705y3454c188v768efe46b388864b@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-questions , freebsd-geom@freebsd.org Subject: Re: gjournal & fsck X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Aug 2008 15:17:03 -0000 Brian McCann wrote: > Hi all. I'm having some problems with several servers I've built > recently (7.0-RELEASE) that are using gjournal. I had two reboot a > few days ago (un-related to FreeBSD problems I think)...but when they > came back up, the file systems wouldn't mount since they were not > clean. Now, I understand that UFS knows nothing about the fact that > it's journaled, and the journaling knows nothing about UFS...but it's > my understanding that by using gjournal, you should really never need > to fsck a file system. However, the only way to get them to mount is > by doing the fsck. Is there something else I should be doing instead > of fsck? > > And since I know it will probably come up, I built the file systems > using the instructions and notes at > http://www.freebsd.org/cgi/man.cgi?query=gjournal&apropos=0&sektion=0&manpath=FreeBSD+7.0-RELEASE&format=html. > > Any help would be greatly appreciated! > Thanks! > --Brian > > You may wish to have a look at this article: http://www.freebsd.org/doc/en_US.ISO8859-1/articles/gjournal-desktop In particular, you should make sure you use tunefs to enable Journaling and disable soft update on the journaled filesystems, i.e.: tunefs -J enable -n disable /dev/ad0s1f.journal Mount them using the async option: /dev/ad0s1f.journal /usr ufs rw,async 2 2 Note that the pass # still indicates the filesystem should be checked. While I was writing the article, I was trying several scenarios were I had the pass # set to 0, thinking that a gjournaled filesystem would not need fsck at all. I would then press the reset button. In most cases, the system would refuse to mount them. However with the pass # set, the fsck would finish almost immediately, since the actual consistency check takes place when the gjournal module is loaded (you will get a "journal consistent" after a bad reboot) and before fstab is even parsed. All fsck does in this case is simply confirm to the system it is a clean volume. In short, leaving the pass # to something that would cause an fsck is the safe way to go. The fsck will be almost instant anyway. From owner-freebsd-geom@FreeBSD.ORG Thu Aug 28 15:25:39 2008 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CCBAD1065678 for ; Thu, 28 Aug 2008 15:25:39 +0000 (UTC) (envelope-from sonic2000gr@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.157]) by mx1.freebsd.org (Postfix) with ESMTP id 578CB8FC1C for ; Thu, 28 Aug 2008 15:25:39 +0000 (UTC) (envelope-from sonic2000gr@gmail.com) Received: by fg-out-1718.google.com with SMTP id l26so317560fgb.35 for ; Thu, 28 Aug 2008 08:25:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=OfTVUZMDc/3dVxJdNsC8NhD516aBqG9kOHVsF3mMDls=; b=MfQ09g1IorcHDJCaX0SHOC3b/mvqfN72Ca1oYjeJXfu8furVSFvNJKfLPnRFfOMhiu VR9P60cn/ChcnnNL0eTTciSVBncwTmo0y5abz693USUgZB9U7XB7NwIsfQsjxYmHp0iL RosKvoryNHlWu9SMKzLQEDYwQ5j30Oqyzjv1c= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=J7tyadoRofdHCet9wOtF4jEfXhiGo9qEjrU//jq74/sbrgW0SXPr4Wid/lAANqCY2e 3500aCZrLlYS8g88Zs9g5MSEjL4TNLTkK5LKs9cBtD3rxmj76PXOVX1KFy8nuUcx8eKz pwiVfilKGm3xs69CZgor1WBv43Thu70iNCiXk= Received: by 10.181.37.11 with SMTP id p11mr2277875bkj.101.1219937137981; Thu, 28 Aug 2008 08:25:37 -0700 (PDT) Received: from joshua.freebsdgr.org ( [79.129.166.74]) by mx.google.com with ESMTPS id p9sm892453fkb.5.2008.08.28.08.25.36 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 28 Aug 2008 08:25:37 -0700 (PDT) Message-ID: <48B6C36E.4040502@gmail.com> Date: Thu, 28 Aug 2008 18:25:34 +0300 From: Manolis Kiagias User-Agent: Thunderbird 2.0.0.16 (X11/20080806) MIME-Version: 1.0 To: Brian McCann References: <2b5f066d0808280705y3454c188v768efe46b388864b@mail.gmail.com> <2b5f066d0808280743g69c32d1rd30aee0ca276125@mail.gmail.com> <2b5f066d0808280803ibca3f61xbb167bce384f228@mail.gmail.com> <2b5f066d0808280805t4c5f7051i60d02c7396c5f06d@mail.gmail.com> In-Reply-To: <2b5f066d0808280805t4c5f7051i60d02c7396c5f06d@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-geom@freebsd.org, Ivan Voras , freebsd-questions@freebsd.org Subject: Re: gjournal & fsck X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Aug 2008 15:25:40 -0000 Brian McCann wrote: > On Thu, Aug 28, 2008 at 11:03 AM, Brian McCann wrote: > >> On Thu, Aug 28, 2008 at 10:51 AM, Ivan Voras wrote: >> >>> Does gjournal complain about your drive, for example that it doesn't >>> support BIOFLUSH? >>> >> Actually yes...I meant to post them in my last message, but hit send >> too early...here's my output from boot (from dmesg.boot) >> >> GEOM_JOURNAL: Journal 478661671: da1 contains data. >> GEOM_JOURNAL: Journal 478661671: da1 contains journal. >> GEOM_JOURNAL: Journal da1 clean. >> (da1:mly0:4:1:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 >> (da1:mly0:4:1:0): CAM Status: SCSI Status Error >> (da1:mly0:4:1:0): SCSI Status: Check Condition >> (da1:mly0:4:1:0): ILLEGAL REQUEST asc:24,0 >> (da1:mly0:4:1:0): Invalid field in CDB >> (da1:mly0:4:1:0): Unretryable error >> GEOM_JOURNAL: BIO_FLUSH not supported by da1. >> GEOM_JOURNAL: Journal 3065355517: da2 contains data. >> GEOM_JOURNAL: Journal 3065355517: da2 contains journal. >> GEOM_JOURNAL: Journal da2 clean. >> (da2:mly1:4:0:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 >> (da2:mly1:4:0:0): CAM Status: SCSI Status Error >> (da2:mly1:4:0:0): SCSI Status: Check Condition >> (da2:mly1:4:0:0): ILLEGAL REQUEST asc:24,0 >> (da2:mly1:4:0:0): Invalid field in CDB >> (da2:mly1:4:0:0): Unretryable error >> GEOM_JOURNAL: BIO_FLUSH not supported by da2. >> >> >>> Also, did fsck actually do something when it was started (did it find >>> anything corrupted)? >>> >>> >> No...it didn't find anything wrong / anything to fix. (and one of the >> file systems was being written to at the time...so at least journaling >> appears to be working) Something else I noticed...Manolis' article >> says it should say "journal xxxx consistent"...whereas mine says >> "Journal xxxx clean". I don't know what the differences mean, or what >> the BIO_FLUSH means...but I'm hoping you can tell me. :) >> >> Thanks again! >> --Brian >> >> > > I should probably also mention that this is on a Mylex 2000 RAID > controller...with a RAID-5 array and using write-caching. > > Thanks > --Brian > I don't have any "exotic" hardware myself - the article was written with standard SATA disks as examples. As I understand, the "consistent" message comes up when the journal is actually used to return the filesystem to a consistent state (what would happen after a power failure, when the filesystem is "dirty") and the "clean" message means there was no inconsistency between the filesystem and journal (a normat shutdown of the filesystem). If it comes up as "clean", I wonder why fsck kicks in at all... From owner-freebsd-geom@FreeBSD.ORG Thu Aug 28 15:58:42 2008 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 18AAF106567A for ; Thu, 28 Aug 2008 15:58:42 +0000 (UTC) (envelope-from bjmccann@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.238]) by mx1.freebsd.org (Postfix) with ESMTP id DE37B8FC22 for ; Thu, 28 Aug 2008 15:58:41 +0000 (UTC) (envelope-from bjmccann@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so582288rvf.43 for ; Thu, 28 Aug 2008 08:58:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=+JlIcYH4Y0MiF7hbjczxAIHJxnAvrOXaBL0TeaFio3c=; b=iSK1PXaaqafRKxrIKwnEpMNLcjoJqtWlz0ijVSDJhLRAS8UVyuYn49E8QW4jzUVu7t fpuhf+V6mUlw9qeaJIgUgG90h+jLewOR1eQUvYIZIbgEr8LqvlCEEFtjnDxYTYwnebXN nCb/ZAj3y7Ic0mMmc6NRoVVlky9spVmPWMSPs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=bNNqm84dLzCgT3SPnSsAKFW44grZ/rdVdZV07V8kFKAwfku5ep666YONXof15pa0eb 2DbAY49g3OqkPReQWmdpT2EGTXiXvPYJWC0em+NYbOPsgPKsKBkg7AobNjqjBpT5ftXg HRzv1aHqzNJalHtOBTYrG+P9ZKwffc1PNaa34= Received: by 10.141.180.5 with SMTP id h5mr827423rvp.240.1219939121129; Thu, 28 Aug 2008 08:58:41 -0700 (PDT) Received: by 10.140.207.5 with HTTP; Thu, 28 Aug 2008 08:58:41 -0700 (PDT) Message-ID: <2b5f066d0808280858k74118385rbf49c4da292958af@mail.gmail.com> Date: Thu, 28 Aug 2008 11:58:41 -0400 From: "Brian McCann" To: "Manolis Kiagias" In-Reply-To: <48B6C36E.4040502@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2b5f066d0808280705y3454c188v768efe46b388864b@mail.gmail.com> <2b5f066d0808280743g69c32d1rd30aee0ca276125@mail.gmail.com> <2b5f066d0808280803ibca3f61xbb167bce384f228@mail.gmail.com> <2b5f066d0808280805t4c5f7051i60d02c7396c5f06d@mail.gmail.com> <48B6C36E.4040502@gmail.com> Cc: freebsd-geom@freebsd.org, Ivan Voras , freebsd-questions@freebsd.org Subject: Re: gjournal & fsck X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Aug 2008 15:58:42 -0000 On Thu, Aug 28, 2008 at 11:25 AM, Manolis Kiagias wrote: >> > > I don't have any "exotic" hardware myself - the article was written with > standard SATA disks as examples. > As I understand, the "consistent" message comes up when the journal is > actually used to return the filesystem to a consistent state (what would > happen after a power failure, when the filesystem is "dirty") and the > "clean" message means there was no inconsistency between the filesystem and > journal (a normat shutdown of the filesystem). If it comes up as "clean", I > wonder why fsck kicks in at all... > The only thing I can think of is the "dirty bit" is still set on the file system, so it insists on fsck'ing it...but I'm obviously fuzzy on the whole thing. Interestingly enough...I checked dmesg.boot on one of the 8.6TB machines (which is running a completely different controller...a 3Ware 9550)...and I didn't get those BIO_FLUSH errors... Again, thanks for your help! If you think of anything, please let me know...this is getting old fast since the box has hung twice this week now. --Brian From owner-freebsd-geom@FreeBSD.ORG Thu Aug 28 16:04:05 2008 Return-Path: Delivered-To: freebsd-geom@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C9CE71065756; Thu, 28 Aug 2008 16:04:04 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 1E2A88FC23; Thu, 28 Aug 2008 16:04:04 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from freefall.freebsd.org (gavin@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m7SG43Cu006146; Thu, 28 Aug 2008 16:04:03 GMT (envelope-from gavin@freefall.freebsd.org) Received: (from gavin@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m7SG43iq006142; Thu, 28 Aug 2008 16:04:03 GMT (envelope-from gavin) Date: Thu, 28 Aug 2008 16:04:03 GMT Message-Id: <200808281604.m7SG43iq006142@freefall.freebsd.org> To: jchambers@ucla.edu, gavin@FreeBSD.org, gavin@FreeBSD.org, freebsd-geom@FreeBSD.org From: gavin@FreeBSD.org Cc: Subject: Re: kern/126902: [geom] [geom_label] Kernel panic during install boot X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Aug 2008 16:04:05 -0000 Old Synopsis: [geom] Kernel panic during install boot New Synopsis: [geom] [geom_label] Kernel panic during install boot State-Changed-From-To: feedback->open State-Changed-By: gavin State-Changed-When: Thu Aug 28 16:02:47 UTC 2008 State-Changed-Why: Feedback was recceived Responsible-Changed-From-To: gavin->freebsd-geom Responsible-Changed-By: gavin Responsible-Changed-When: Thu Aug 28 16:02:47 UTC 2008 Responsible-Changed-Why: This looks to be a GEOM problem, possibly with geom_label. Over to maintainers. http://www.freebsd.org/cgi/query-pr.cgi?pr=126902 From owner-freebsd-geom@FreeBSD.ORG Thu Aug 28 17:05:03 2008 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AEB7810656A4 for ; Thu, 28 Aug 2008 17:05:03 +0000 (UTC) (envelope-from gcubfg-freebsd-geom@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id 5B4BB8FC0C for ; Thu, 28 Aug 2008 17:05:02 +0000 (UTC) (envelope-from gcubfg-freebsd-geom@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1KYjms-0001CE-88 for freebsd-geom@freebsd.org; Thu, 28 Aug 2008 15:51:55 +0000 Received: from 78-0-86-69.adsl.net.t-com.hr ([78.0.86.69]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 28 Aug 2008 15:51:54 +0000 Received: from ivoras by 78-0-86-69.adsl.net.t-com.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 28 Aug 2008 15:51:54 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-geom@freebsd.org From: Ivan Voras Date: Thu, 28 Aug 2008 17:51:46 +0200 Lines: 81 Message-ID: References: <2b5f066d0808280705y3454c188v768efe46b388864b@mail.gmail.com> <2b5f066d0808280743g69c32d1rd30aee0ca276125@mail.gmail.com> <2b5f066d0808280803ibca3f61xbb167bce384f228@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig0AC348193C0055E248E3DFF2" X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 78-0-86-69.adsl.net.t-com.hr User-Agent: Thunderbird 2.0.0.16 (Windows/20080708) In-Reply-To: <2b5f066d0808280803ibca3f61xbb167bce384f228@mail.gmail.com> X-Enigmail-Version: 0.95.7 Sender: news Cc: freebsd-questions@freebsd.org Subject: Re: gjournal & fsck X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Aug 2008 17:05:03 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig0AC348193C0055E248E3DFF2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Brian McCann wrote: > On Thu, Aug 28, 2008 at 10:51 AM, Ivan Voras wrote= : >> Does gjournal complain about your drive, for example that it doesn't >> support BIOFLUSH? >=20 > Actually yes...I meant to post them in my last message, but hit send > too early...here's my output from boot (from dmesg.boot) >=20 > GEOM_JOURNAL: Journal 478661671: da1 contains data. > GEOM_JOURNAL: Journal 478661671: da1 contains journal. > GEOM_JOURNAL: Journal da1 clean. > (da1:mly0:4:1:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 > (da1:mly0:4:1:0): CAM Status: SCSI Status Error > (da1:mly0:4:1:0): SCSI Status: Check Condition > (da1:mly0:4:1:0): ILLEGAL REQUEST asc:24,0 > (da1:mly0:4:1:0): Invalid field in CDB > (da1:mly0:4:1:0): Unretryable error > GEOM_JOURNAL: BIO_FLUSH not supported by da1. > GEOM_JOURNAL: Journal 3065355517: da2 contains data. > GEOM_JOURNAL: Journal 3065355517: da2 contains journal. > GEOM_JOURNAL: Journal da2 clean. > (da2:mly1:4:0:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 > (da2:mly1:4:0:0): CAM Status: SCSI Status Error > (da2:mly1:4:0:0): SCSI Status: Check Condition > (da2:mly1:4:0:0): ILLEGAL REQUEST asc:24,0 > (da2:mly1:4:0:0): Invalid field in CDB > (da2:mly1:4:0:0): Unretryable error > GEOM_JOURNAL: BIO_FLUSH not supported by da2. >> Also, did fsck actually do something when it was started (did it find >> anything corrupted)? >> > No...it didn't find anything wrong / anything to fix. (and one of the > file systems was being written to at the time...so at least journaling > appears to be working) Something else I noticed...Manolis' article > says it should say "journal xxxx consistent"...whereas mine says > "Journal xxxx clean". I don't know what the differences mean, or what > the BIO_FLUSH means...but I'm hoping you can tell me. :) Ok, this is most probably the cause of your fsck. BIO_FLUSH is a catch-all name for operations that synchronize (commit) the drive and controller caches. It is used to synchronize the file system state after it's been committed from the journal - if BIO_FLUSH succeeds the data is guaranteed (or should be guaranteed) by hardware that it's safely written. Since your controller doesn't support it you have a problem here. Your best bet is to ask the author of the driver for your controller (according to the "mly" man page this is Michael Smith ) if he knows anything that can help you here (maybe the driver simply needs to implement it or fix it). Other than that, you might disable write caching on your controller. This should significantly reduce the cases where fsck would need to be called on reboot, but probably not eliminate them completely. It will also slow down the commit operation (from the journal to the active file system) but if the server doesn't constantly write to the file system it won't be a big problem. --------------enig0AC348193C0055E248E3DFF2 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAki2yZIACgkQldnAQVacBcgtWwCgyV58q9PNCyz4blM71NALZj5p h04An3IooHWDOzH9XZORuM/ZZjKFti8E =dYtV -----END PGP SIGNATURE----- --------------enig0AC348193C0055E248E3DFF2-- From owner-freebsd-geom@FreeBSD.ORG Thu Aug 28 19:26:28 2008 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E9C7D1065670; Thu, 28 Aug 2008 19:26:28 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (chello087206045140.chello.pl [87.206.45.140]) by mx1.freebsd.org (Postfix) with ESMTP id 51AA68FC26; Thu, 28 Aug 2008 19:26:28 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 1FD7645CA6; Thu, 28 Aug 2008 21:04:24 +0200 (CEST) Received: from localhost (chello087206045140.chello.pl [87.206.45.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id D687F45B36; Thu, 28 Aug 2008 21:04:17 +0200 (CEST) Date: Thu, 28 Aug 2008 21:04:29 +0200 From: Pawel Jakub Dawidek To: Brian McCann Message-ID: <20080828190429.GB2292@garage.freebsd.pl> References: <2b5f066d0808280705y3454c188v768efe46b388864b@mail.gmail.com> <2b5f066d0808280743g69c32d1rd30aee0ca276125@mail.gmail.com> <2b5f066d0808280803ibca3f61xbb167bce384f228@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="7iMSBzlTiPOCCT2k" Content-Disposition: inline In-Reply-To: <2b5f066d0808280803ibca3f61xbb167bce384f228@mail.gmail.com> User-Agent: Mutt/1.4.2.3i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 8.0-CURRENT i386 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-2.6 required=3.0 tests=BAYES_00 autolearn=ham version=3.0.4 Cc: freebsd-geom@freebsd.org, Ivan Voras , freebsd-questions@freebsd.org Subject: Re: gjournal & fsck X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Aug 2008 19:26:29 -0000 --7iMSBzlTiPOCCT2k Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Aug 28, 2008 at 11:03:49AM -0400, Brian McCann wrote: > On Thu, Aug 28, 2008 at 10:51 AM, Ivan Voras wrote: > > > > Does gjournal complain about your drive, for example that it doesn't > > support BIOFLUSH? >=20 > Actually yes...I meant to post them in my last message, but hit send > too early...here's my output from boot (from dmesg.boot) >=20 > GEOM_JOURNAL: Journal 478661671: da1 contains data. > GEOM_JOURNAL: Journal 478661671: da1 contains journal. > GEOM_JOURNAL: Journal da1 clean. > (da1:mly0:4:1:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 > (da1:mly0:4:1:0): CAM Status: SCSI Status Error > (da1:mly0:4:1:0): SCSI Status: Check Condition > (da1:mly0:4:1:0): ILLEGAL REQUEST asc:24,0 > (da1:mly0:4:1:0): Invalid field in CDB > (da1:mly0:4:1:0): Unretryable error > GEOM_JOURNAL: BIO_FLUSH not supported by da1. > GEOM_JOURNAL: Journal 3065355517: da2 contains data. > GEOM_JOURNAL: Journal 3065355517: da2 contains journal. > GEOM_JOURNAL: Journal da2 clean. > (da2:mly1:4:0:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 > (da2:mly1:4:0:0): CAM Status: SCSI Status Error > (da2:mly1:4:0:0): SCSI Status: Check Condition > (da2:mly1:4:0:0): ILLEGAL REQUEST asc:24,0 > (da2:mly1:4:0:0): Invalid field in CDB > (da2:mly1:4:0:0): Unretryable error > GEOM_JOURNAL: BIO_FLUSH not supported by da2. >=20 > > > > Also, did fsck actually do something when it was started (did it find > > anything corrupted)? > > > No...it didn't find anything wrong / anything to fix. (and one of the > file systems was being written to at the time...so at least journaling > appears to be working) Something else I noticed...Manolis' article > says it should say "journal xxxx consistent"...whereas mine says > "Journal xxxx clean". I don't know what the differences mean, or what > the BIO_FLUSH means...but I'm hoping you can tell me. :) Don't worry about those if you have memory-backed RAID card. BIO_FLUSH is there to tell the disk to flush its write caches, but if it is memory-backed, there is low risk on losing unwritted data. This is not the cause of your problem. BTW. "journal ... clean" means that there was clean shutdown and there was no need to replay journal, while "journal ... consistent" means that there was unclean shutdown and journal replay was successful. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --7iMSBzlTiPOCCT2k Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFItva9ForvXbEpPzQRApSKAKDVg9/RaOXdb2z87MrYAXUQ20a3MwCbBlB8 yEo7XLlB92i0GRkxZL0V9X8= =T+aP -----END PGP SIGNATURE----- --7iMSBzlTiPOCCT2k-- From owner-freebsd-geom@FreeBSD.ORG Thu Aug 28 19:26:29 2008 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 19EAC1065674; Thu, 28 Aug 2008 19:26:29 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (chello087206045140.chello.pl [87.206.45.140]) by mx1.freebsd.org (Postfix) with ESMTP id 585A68FC29; Thu, 28 Aug 2008 19:26:28 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id D994F45C9B; Thu, 28 Aug 2008 20:59:09 +0200 (CEST) Received: from localhost (chello087206045140.chello.pl [87.206.45.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id C4B23456AB; Thu, 28 Aug 2008 20:59:04 +0200 (CEST) Date: Thu, 28 Aug 2008 20:59:16 +0200 From: Pawel Jakub Dawidek To: Manolis Kiagias Message-ID: <20080828185916.GA2292@garage.freebsd.pl> References: <2b5f066d0808280705y3454c188v768efe46b388864b@mail.gmail.com> <48B6B9D0.8060302@gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="FCuugMFkClbJLl1L" Content-Disposition: inline In-Reply-To: <48B6B9D0.8060302@gmail.com> User-Agent: Mutt/1.4.2.3i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 8.0-CURRENT i386 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-2.6 required=3.0 tests=BAYES_00 autolearn=ham version=3.0.4 Cc: Brian McCann , freebsd-questions , freebsd-geom@freebsd.org Subject: Re: gjournal & fsck X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Aug 2008 19:26:29 -0000 --FCuugMFkClbJLl1L Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Aug 28, 2008 at 05:44:32PM +0300, Manolis Kiagias wrote: > Brian McCann wrote: > >Hi all. I'm having some problems with several servers I've built > >recently (7.0-RELEASE) that are using gjournal. I had two reboot a > >few days ago (un-related to FreeBSD problems I think)...but when they > >came back up, the file systems wouldn't mount since they were not > >clean. Now, I understand that UFS knows nothing about the fact that > >it's journaled, and the journaling knows nothing about UFS...but it's > >my understanding that by using gjournal, you should really never need > >to fsck a file system. However, the only way to get them to mount is > >by doing the fsck. Is there something else I should be doing instead > >of fsck? > > > >And since I know it will probably come up, I built the file systems > >using the instructions and notes at > >http://www.freebsd.org/cgi/man.cgi?query=3Dgjournal&apropos=3D0&sektion= =3D0&manpath=3DFreeBSD+7.0-RELEASE&format=3Dhtml. > > > >Any help would be greatly appreciated! > >Thanks! > >--Brian > > > > =20 >=20 > You may wish to have a look at this article: >=20 > http://www.freebsd.org/doc/en_US.ISO8859-1/articles/gjournal-desktop >=20 > In particular, you should make sure you use tunefs to enable Journaling= =20 > and disable soft update on the journaled filesystems, i.e.: >=20 > tunefs -J enable -n disable /dev/ad0s1f.journal >=20 > Mount them using the async option: >=20 > /dev/ad0s1f.journal /usr ufs rw,async 2 2 >=20 > Note that the pass # still indicates the filesystem should be checked.=20 > While I was writing the article, I was trying several scenarios were I=20 > had the pass # set to 0, thinking that a gjournaled filesystem would not= =20 > need fsck at all. I would then press the reset button. In most cases,=20 > the system would refuse to mount them. However with the pass # set, the= =20 > fsck would finish almost immediately, since the actual consistency check= =20 > takes place when the gjournal module is loaded (you will get a "journal= =20 > consistent" after a bad reboot) and before fstab is even parsed. All=20 > fsck does in this case is simply confirm to the system it is a clean volu= me. >=20 > In short, leaving the pass # to something that would cause an fsck is=20 > the safe way to go. The fsck will be almost instant anyway. Not exactly. Gjournal handles all inconsistencies, except one - orphaned files. An orphaned file is a file that some open, deleted, but haven't closed. If you have panic or power failure at this point, there will be unreferenced file. When fsck detects that it operates on gjournaled file system, it will do a very fast lookup of such orphaned files. It is optimized so that total number of such files is kept in superblock - if this counter is 0, we're done. If it is not zero, then fsck scans only cylinder groups headers, there is another counter in each header says how many orphaned files is in this CG. If CG's counter is 0, the whole CG can be skipped. Once we found X dirty CGs (X is stored in superblock) we can also stop earlier. All in all, there are very few such files (if any), so fsck is way, way faster with gjournal (eg. ~1 minute instead of ~8 hours on huge file system). --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --FCuugMFkClbJLl1L Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFItvWDForvXbEpPzQRAo6kAKD4+K9FKcmJRVYGYTTi0nNaanH9ngCgxOaf ahtll7dsptXXBI9Y3Nh5wwE= =+IBQ -----END PGP SIGNATURE----- --FCuugMFkClbJLl1L-- From owner-freebsd-geom@FreeBSD.ORG Thu Aug 28 19:26:29 2008 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F04B4106567D; Thu, 28 Aug 2008 19:26:29 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (chello087206045140.chello.pl [87.206.45.140]) by mx1.freebsd.org (Postfix) with ESMTP id 466A28FC19; Thu, 28 Aug 2008 19:26:29 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 6C9F245C9F; Thu, 28 Aug 2008 21:05:51 +0200 (CEST) Received: from localhost (chello087206045140.chello.pl [87.206.45.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 92AEC45CD8; Thu, 28 Aug 2008 21:05:39 +0200 (CEST) Date: Thu, 28 Aug 2008 21:05:51 +0200 From: Pawel Jakub Dawidek To: Brian McCann Message-ID: <20080828190550.GC2292@garage.freebsd.pl> References: <2b5f066d0808280705y3454c188v768efe46b388864b@mail.gmail.com> <2b5f066d0808280743g69c32d1rd30aee0ca276125@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="TiqCXmo5T1hvSQQg" Content-Disposition: inline In-Reply-To: <2b5f066d0808280743g69c32d1rd30aee0ca276125@mail.gmail.com> User-Agent: Mutt/1.4.2.3i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 8.0-CURRENT i386 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-2.6 required=3.0 tests=BAYES_00 autolearn=ham version=3.0.4 Cc: freebsd-geom@freebsd.org, Ivan Voras , freebsd-questions@freebsd.org Subject: Re: gjournal & fsck X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Aug 2008 19:26:30 -0000 --TiqCXmo5T1hvSQQg Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Aug 28, 2008 at 10:43:58AM -0400, Brian McCann wrote: > On Thu, Aug 28, 2008 at 10:34 AM, Ivan Voras wrote: > > Brian McCann wrote: > >> Hi all. I'm having some problems with several servers I've built > >> recently (7.0-RELEASE) that are using gjournal. I had two reboot a > >> few days ago (un-related to FreeBSD problems I think)...but when they > >> came back up, the file systems wouldn't mount since they were not > >> clean. Now, I understand that UFS knows nothing about the fact that > >> it's journaled, and the journaling knows nothing about UFS...but it's > > > > Actually UFS needs to know about gjournal for just this purpose. There's > > a special option to newfs that tells the file system to be aware of > > gjournal and it should request fscks. > > > >> my understanding that by using gjournal, you should really never need > >> to fsck a file system. However, the only way to get them to mount is > >> by doing the fsck. Is there something else I should be doing instead > >> of fsck? > > > > man 8 tunefs > > >=20 >=20 > Yes...I apologize...I did that when I built the file system with > "newfs -J". Here's the tunefs -p output for one of the file systems: >=20 > # tunefs -p /dev/da2.journal > tunefs: ACLs: (-a) disabled > tunefs: MAC multilabel: (-l) disabled > tunefs: soft updates: (-n) disabled > tunefs: gjournal: (-J) enabled > tunefs: maximum blocks per file in a cylinder group: (-e) 2048 > tunefs: average file size: (-f) 16384 > tunefs: average number of files in a directory: (-s) 64 > tunefs: minimum percentage of free space: (-m) 8% > tunefs: optimization preference: (-o) time > tunefs: volume label: (-L) >=20 > I'm concerned about this because the ones I've had problems with > recently are 1.1TB arrays...I've got 2 8.6TB arrays that are journaled > as well...and if I ever have to fsck them...that could take 1/2 the > day... >=20 > Any other thoughts? Everything looks good. Do you have 'fsck_y_enable' in your rc.conf by any chance? gjournal mode in fsck is only used for -p option, AFAIR. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --TiqCXmo5T1hvSQQg Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFItvcOForvXbEpPzQRAq2dAJ9rDDlK+/21oskAZG/FFZ0W89f01ACdFpTt pB039ICtp4uzBL+RtViHSBs= =dWBq -----END PGP SIGNATURE----- --TiqCXmo5T1hvSQQg--