From owner-freebsd-fs@FreeBSD.ORG Tue Aug 15 01:46:27 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ADE5F16A510 for ; Tue, 15 Aug 2006 01:46:27 +0000 (UTC) (envelope-from freebsd-afs-request@freebsd.org) Received: from mx1.freebsd.org (p54883CBE.dip0.t-ipconnect.de [84.136.60.190]) by mx1.FreeBSD.org (Postfix) with SMTP id 532DD43D69 for ; Tue, 15 Aug 2006 01:46:21 +0000 (GMT) (envelope-from freebsd-afs-request@freebsd.org) Received: from mx1.freebsd.org by p54883CBE.dip0.t-ipconnect.de (8.13.1/8.13.1) with ESMTP id smfBo9uNlCbaW for ; Tue, 15 Aug 2006 01:52:49 -0300 Received: from [245.170.160.175] by mx1.freebsd.org with ESMTP (8.9.3/8.9.3) id INEdOexBx75V7 for ; Tue, 15 Aug 2006 01:49:54 -0300 From: "freebsd-afs-request@freebsd.org" To: freebsd-fs@freebsd.org Message-Id: <20060815014621.532DD43D69@mx1.FreeBSD.org> Date: Tue, 15 Aug 2006 01:46:21 +0000 (GMT) MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1251" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Feel the size and power with Penis Enlarge Patch. 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, 15 Aug 2006 01:46:27 -0000 [1]http://www.domdvas.com/pt/?108&oiZ2UheOfbYVG Do you w@nt t0 increase your $elf-conf1dence a$ well as y0u dick. Penis Enlarge Patch is one s0lution for two problems. References 1. http://www.domdvas.com/pt/?108&HCPE3Bl0hllCW From owner-freebsd-fs@FreeBSD.ORG Wed Aug 16 13:05:41 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BD5C716A4E8 for ; Wed, 16 Aug 2006 13:05:41 +0000 (UTC) (envelope-from igorr@speechpro.com) Received: from speechpro.ru (speech-tech-2.ip.PeterStar.net [81.3.190.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id F25F843D60 for ; Wed, 16 Aug 2006 13:05:37 +0000 (GMT) (envelope-from igorr@speechpro.com) Received: from [192.168.2.26] (helo=sysadm.stc) by s1.stc with esmtp (Exim 4.53 (FreeBSD)) id 1GDL5U-000A3A-La for freebsd-fs@freebsd.org; Wed, 16 Aug 2006 17:05:36 +0400 Received: from localhost.stc ([127.0.0.1] helo=sysadm.stc) by sysadm.stc with esmtp (Exim 4.62 (FreeBSD)) (envelope-from ) id 1GDL5X-000Juy-GU for freebsd-fs@freebsd.org; Wed, 16 Aug 2006 17:05:39 +0400 Received: (from igorr@localhost) by sysadm.stc (8.13.6/8.13.6/Submit) id k7GD5dCD076567 for freebsd-fs@freebsd.org; Wed, 16 Aug 2006 17:05:39 +0400 (MSD) (envelope-from igorr) Date: Wed, 16 Aug 2006 17:05:39 +0400 From: Igor Robul To: freebsd-fs@freebsd.org Message-ID: <20060816130538.GA76449@sysadm.stc> References: <20060808195202.GA1564@garage.freebsd.pl> <20060809125909.GB67566@uk.tiscali.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060809125909.GB67566@uk.tiscali.com> User-Agent: Mutt/1.5.12-2006-07-14 X-Archived: Yes Subject: Re: GJournal (hopefully) final patches. 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: Wed, 16 Aug 2006 13:05:41 -0000 Hello, I have compiled world with gjournal patches on FreeBSD-AMD64, than I wished to try gjournal, but I'm not brave to try it on real filesystem, also I wished to try it with geom_mirror, so I decided to try it with md(4) devices: # dd if=/dev/zero of=d1 bs=1m count=2000 # dd if=/dev/zero of=d2 bs=1m count=2000 # dd if=/dev/zero of=j1 bs=1m count=100 # mdconfig -a -t vnode -f d1 # mdconfig -a -t vnode -f d2 # mdconfig -a -t vnode -f j1 # gmirror label gm0 /dev/md0 /dev/md1 # gmirror load so far so good # gjournal label /dev/mirror/gm0 /dev/md2 # gjournal load and now I have got panic without kernel dump on my workstation :-( So I have decided to try this in QEMU (so I can take screenshot, and dont lose my files :-) ) I have installed 6.1-AMD64 onto 15Gb qemu hd image, then got -STABLE sources, then patched with gjournal patches ... rebuilt world (around 18 hours in emulated x86_64 :-) ) You can get screenshot of panic at ftp://su.speechpro.com/p/gjournal.png it is md(4) related as I can see: GEOM_JOURNAL: Journal mirror/gm0 clean. panic: wrong BIO_OP in mdstart_vnode Kernel was compiled with options DDB options KDB options KDB_UNATTENDED there was dumpdev enabled, but after panic there is no crashdump creation, so I have hit Ctrl+Alt+ESC to go to ddb. So what can I do? I have done "call doadump()". From owner-freebsd-fs@FreeBSD.ORG Wed Aug 16 13:09:49 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6422116A4DF for ; Wed, 16 Aug 2006 13:09:49 +0000 (UTC) (envelope-from igorr@speechpro.com) Received: from speechpro.ru (speech-tech-2.ip.PeterStar.net [81.3.190.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id CE41A43D45 for ; Wed, 16 Aug 2006 13:09:48 +0000 (GMT) (envelope-from igorr@speechpro.com) Received: from [192.168.2.26] (helo=sysadm.stc) by s1.stc with esmtp (Exim 4.53 (FreeBSD)) id 1GDL9X-000AJT-Qb for freebsd-fs@freebsd.org; Wed, 16 Aug 2006 17:09:47 +0400 Received: from localhost.stc ([127.0.0.1] helo=sysadm.stc) by sysadm.stc with esmtp (Exim 4.62 (FreeBSD)) (envelope-from ) id 1GDL9a-000JvG-RL for freebsd-fs@freebsd.org; Wed, 16 Aug 2006 17:09:50 +0400 Received: (from igorr@localhost) by sysadm.stc (8.13.6/8.13.6/Submit) id k7GD9oAW076585 for freebsd-fs@freebsd.org; Wed, 16 Aug 2006 17:09:50 +0400 (MSD) (envelope-from igorr) Date: Wed, 16 Aug 2006 17:09:50 +0400 From: Igor Robul To: freebsd-fs@freebsd.org Message-ID: <20060816130950.GA76573@sysadm.stc> References: <20060808195202.GA1564@garage.freebsd.pl> <20060809125909.GB67566@uk.tiscali.com> <20060816130538.GA76449@sysadm.stc> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060816130538.GA76449@sysadm.stc> User-Agent: Mutt/1.5.12-2006-07-14 X-Archived: Yes Subject: Re: GJournal (hopefully) final patches. 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: Wed, 16 Aug 2006 13:09:49 -0000 On Wed, Aug 16, 2006 at 05:05:39PM +0400, Igor Robul wrote: > # gjournal label /dev/mirror/gm0 /dev/md2 > # gjournal load > and now I have got panic without kernel dump on my workstation :-( Same panic without gmirror From owner-freebsd-fs@FreeBSD.ORG Wed Aug 16 13:44:58 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C10CB16A4DF for ; Wed, 16 Aug 2006 13:44:58 +0000 (UTC) (envelope-from arne_woerner@yahoo.com) Received: from web30308.mail.mud.yahoo.com (web30308.mail.mud.yahoo.com [209.191.69.70]) by mx1.FreeBSD.org (Postfix) with SMTP id 4ABBC43D4C for ; Wed, 16 Aug 2006 13:44:58 +0000 (GMT) (envelope-from arne_woerner@yahoo.com) Received: (qmail 46570 invoked by uid 60001); 16 Aug 2006 13:44:57 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=mtPgQBPZ2G6ElkXR1WNWrciYKVUxgeR0JRljC11y7RaUd/18TqAcCBGxZCs5pbaDKlioA1OMw1QCKqAqOOd9u/sXyk8ti9RlQvF82rEbHtZI/l+l4PVtuhkbZfJMDMbGpWPDYN40FzzPLVmNelZtI6+lHjIHGjFxv1FTcpo1+2Q= ; Message-ID: <20060816134457.46568.qmail@web30308.mail.mud.yahoo.com> Received: from [213.54.79.182] by web30308.mail.mud.yahoo.com via HTTP; Wed, 16 Aug 2006 06:44:57 PDT Date: Wed, 16 Aug 2006 06:44:57 -0700 (PDT) From: "R. B. Riddick" To: Igor Robul , freebsd-fs@freebsd.org In-Reply-To: <20060816130950.GA76573@sysadm.stc> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: Subject: Re: GJournal (hopefully) final patches. 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: Wed, 16 Aug 2006 13:44:58 -0000 --- Igor Robul wrote: > On Wed, Aug 16, 2006 at 05:05:39PM +0400, Igor Robul wrote: > > # gjournal label /dev/mirror/gm0 /dev/md2 > > # gjournal load > > and now I have got panic without kernel dump on my workstation :-( > Same panic without gmirror > I would expect a correct command line to look like this: # gjournal label fook mirror/fuuk mirror/faak But you do not provide a name for your gjournal device... *sniff* Now I am disturbed... And I do not find the source code of gjournal... By the way: If u do not use a mirrored journal device, u would have to do a fsck (or so) on your data device (if u have a filesystem there) if your journal device dies (because: the journal device has been possibly just half emptied)... -Arne __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From owner-freebsd-fs@FreeBSD.ORG Thu Aug 17 00:11:50 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0B82916A4DF for ; Thu, 17 Aug 2006 00:11:50 +0000 (UTC) (envelope-from arne_woerner@yahoo.com) Received: from web30311.mail.mud.yahoo.com (web30311.mail.mud.yahoo.com [209.191.69.73]) by mx1.FreeBSD.org (Postfix) with SMTP id 36EDA43D5E for ; Thu, 17 Aug 2006 00:11:49 +0000 (GMT) (envelope-from arne_woerner@yahoo.com) Received: (qmail 41503 invoked by uid 60001); 17 Aug 2006 00:11:48 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=ch1zgqRhm32KA7+rD6JdlSdLiRIcvgHQQAVkGKXi2mXUeBYIXo/dGgPdkiJ9Fg+C++ix00jzQfzJH2Rw2SmP8O1GXQjQQTT3K/LRpIj2MFhqFbDo/llyD+H1Jg5U+q3TPwLKB6EFULgk6bdcGxJedrfdp/1qkiChVRhVR25WHq8= ; Message-ID: <20060817001148.41501.qmail@web30311.mail.mud.yahoo.com> Received: from [213.54.79.182] by web30311.mail.mud.yahoo.com via HTTP; Wed, 16 Aug 2006 17:11:48 PDT Date: Wed, 16 Aug 2006 17:11:48 -0700 (PDT) From: "R. B. Riddick" To: Igor Robul , freebsd-fs@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: Subject: Re: GJournal (hopefully) final patches. 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: Thu, 17 Aug 2006 00:11:50 -0000 --- "R. B. Riddick" wrote: > I would expect a correct command line to look like this: > # gjournal label fook mirror/fuuk mirror/faak > > But you do not provide a name for your gjournal device... > I just recalled, that gjournal is not like gmirror in this point. So ur command line is ok... Furthermore I had a look at src/sys/dev/md/md.c and found, that md just likes BIO_READ and BIO_WRITE operations (any other command leads to that panic with BIO_OP...). While gjournal send BIO_FLUSH command, too. Maybe u might want to ask the mailing list freebsd-geom@...? Maybe u want to test with a real disk and not with md? -Arne __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From owner-freebsd-fs@FreeBSD.ORG Thu Aug 17 02:54:45 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CF2C916A4DA; Thu, 17 Aug 2006 02:54:45 +0000 (UTC) (envelope-from anderson@centtech.com) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7070C43D45; Thu, 17 Aug 2006 02:54:43 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [192.168.42.24] (andersonbox4.centtech.com [192.168.42.24]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id k7H2sgWI074632; Wed, 16 Aug 2006 21:54:42 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <44E3DA8A.8060808@centtech.com> Date: Wed, 16 Aug 2006 21:55:06 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5.0.5 (X11/20060802) MIME-Version: 1.0 To: Pawel Jakub Dawidek References: <20060808195202.GA1564@garage.freebsd.pl> <20060810192152.GE57857@europa.expro.pl> <20060810194304.GB1345@garage.freebsd.pl> <20060810200135.GF57857@europa.expro.pl> <20060810223901.GC1389@garage.freebsd.pl> In-Reply-To: <20060810223901.GC1389@garage.freebsd.pl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1673/Wed Aug 16 18:20:48 2006 on mh2.centtech.com X-Virus-Status: Clean Cc: freebsd-fs@freebsd.org, freebsd-geom@freebsd.org Subject: Re: GJournal (hopefully) final patches. 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: Thu, 17 Aug 2006 02:54:45 -0000 On 08/10/06 17:39, Pawel Jakub Dawidek wrote: > On Thu, Aug 10, 2006 at 10:01:35PM +0200, Jan Srzednicki wrote: >> On Thu, Aug 10, 2006 at 09:43:04PM +0200, Pawel Jakub Dawidek wrote: >>> On Thu, Aug 10, 2006 at 09:21:52PM +0200, Jan Srzednicki wrote: >>>> Hello, >>>> >>>> I'd happily perform some testing, only if the aac(4) driver would also >>>> be patched. I know I can run gjournal w/o the BIO_FLUSH feature, but >>>> that would make any performance results rather worthles, wouldn't it? >>> From my tests BIO_FLUSH doesn't have huge impact on performance (if at >>> all), but I suspect it greatly depends on specific HW. >>> >>> Unfortunately I'm not able to implement BIO_FLUSH to all out storage >>> drivers. Currently BIO_FLUSH is supported by ata(4) (/dev/a[dr]X), >>> da(4) and amr(4). >> I see. Does that mean that all CAM-interfaced devices (like asr(4) or >> twa(4)) have this feature fully implemented? > > That's the theory. I'm using standard SCSI commands for this. From the > tests we made it seems that it works ok with twa(4)/twe(4). > I'd still be glad if someone with SCSI/CAM foo could look at the code. > By the way, this is true for at least the QLogic Fiber channel cards (isp). Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-fs@FreeBSD.ORG Thu Aug 17 13:14:19 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5DD8316A4DD; Thu, 17 Aug 2006 13:14:19 +0000 (UTC) (envelope-from anderson@centtech.com) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8299F43F80; Thu, 17 Aug 2006 13:08:40 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id k7HD8Wo5072469; Thu, 17 Aug 2006 08:08:32 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <44E46A68.6080602@centtech.com> Date: Thu, 17 Aug 2006 08:08:56 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5.0.5 (X11/20060802) MIME-Version: 1.0 To: Pawel Jakub Dawidek References: <20060808195202.GA1564@garage.freebsd.pl> In-Reply-To: <20060808195202.GA1564@garage.freebsd.pl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1676/Thu Aug 17 05:45:34 2006 on mh2.centtech.com X-Virus-Status: Clean Cc: freebsd-fs@freebsd.org, freebsd-geom@freebsd.org Subject: Re: GJournal (hopefully) final patches. 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: Thu, 17 Aug 2006 13:14:19 -0000 On 08/08/06 14:52, Pawel Jakub Dawidek wrote: > Hi. > > I'm pleased to announce hopefully the final gjournal patches. [..snip..] > To create journaled UFS file system on ad0s1d partition: > > # gjournal load > # gjournal label ad0s1d > # newfs -J /dev/ad0s1d.journal > # mount -o noatime,async /dev/ad0s1d.journal /mnt > > On reboot 'fsck_ffs -p /dev/ad0s1d.journal' will perform fast check. One > can still run regular check by not giving the -p option. I have a 10TB filesystem I created as above, and recently a crash caused it to now complain about the filesystem being dirty. When I do an fsck -p, here's what I get: # fsck -p /dev/label/vol10 /dev/label/vol10: UNEXPECTED INCONSISTENCY, CANNOT RUN FAST FSCK /dev/label/vol10: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. # geom journal list Geom name: gjournal 647039251 ID: 647039251 Providers: 1. Name: da10.journal Mediasize: 10494183210496 (9.5T) Sectorsize: 512 Mode: r0w0e0 Consumers: 1. Name: da9 Mediasize: 7996964864 (7.4G) Sectorsize: 512 Mode: r1w1e1 Jend: 7996964352 Jstart: 0 Role: Journal 2. Name: da10 Mediasize: 10494183211008 (9.5T) Sectorsize: 512 Mode: r1w1e1 Role: Data GEOM_JOURNAL: Journal 647039251: da9 contains journal. GEOM_JOURNAL: Journal 647039251: da10 contains data. GEOM_JOURNAL: Journal da10 consistent. GEOM_JOURNAL: BIO_FLUSH supported by da9. GEOM_JOURNAL: BIO_FLUSH supported by da10. GEOM_LABEL: Label for provider da10.journal is label/vol10. # tunefs -p /dev/label/vol10 tunefs: ACLs: (-a) disabled tunefs: MAC multilabel: (-l) disabled tunefs: soft updates: (-n) enabled 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) -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-fs@FreeBSD.ORG Thu Aug 17 14:09:17 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EBD0B16A4DD; Thu, 17 Aug 2006 14:09:17 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id ECC2F43D6E; Thu, 17 Aug 2006 14:09:07 +0000 (GMT) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id D0C305138A; Thu, 17 Aug 2006 16:09:05 +0200 (CEST) Received: from localhost (pjd.wheel.pl [10.0.1.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id A3BB251339; Thu, 17 Aug 2006 16:09:00 +0200 (CEST) Date: Thu, 17 Aug 2006 16:08:57 +0200 From: Pawel Jakub Dawidek To: Eric Anderson Message-ID: <20060817140857.GB78978@garage.freebsd.pl> References: <20060808195202.GA1564@garage.freebsd.pl> <44E46A68.6080602@centtech.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="hHWLQfXTYDoKhP50" Content-Disposition: inline In-Reply-To: <44E46A68.6080602@centtech.com> X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 User-Agent: mutt-ng/devel-r804 (FreeBSD) X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-5.9 required=3.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.0.4 Cc: freebsd-fs@freebsd.org, freebsd-geom@freebsd.org Subject: Re: GJournal (hopefully) final patches. 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: Thu, 17 Aug 2006 14:09:18 -0000 --hHWLQfXTYDoKhP50 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Aug 17, 2006 at 08:08:56AM -0500, Eric Anderson wrote: > On 08/08/06 14:52, Pawel Jakub Dawidek wrote: > >Hi. > >I'm pleased to announce hopefully the final gjournal patches. > [..snip..] > >To create journaled UFS file system on ad0s1d partition: > > # gjournal load > > # gjournal label ad0s1d > > # newfs -J /dev/ad0s1d.journal > > # mount -o noatime,async /dev/ad0s1d.journal /mnt > >On reboot 'fsck_ffs -p /dev/ad0s1d.journal' will perform fast check. One > >can still run regular check by not giving the -p option. >=20 > I have a 10TB filesystem I created as above, and recently a crash caused = it to now complain about the filesystem being dirty. When I do an fsck -p,= here's what I get: >=20 > # fsck -p /dev/label/vol10 > /dev/label/vol10: UNEXPECTED INCONSISTENCY, CANNOT RUN FAST FSCK >=20 >=20 > /dev/label/vol10: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. Do you have log from the boot before you saw this? I corrected one bug, but it was only possible to trigger when crash happened early in the boot process. Your crash was during or just after a boot maybe? --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --hHWLQfXTYDoKhP50 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFE5Hh5ForvXbEpPzQRApI3AJ4k8nAJN9knFGuwcs6s9mJXdYFohgCeNATX 637xfew2YT2UEFT8V2dI5bo= =dD5d -----END PGP SIGNATURE----- --hHWLQfXTYDoKhP50-- From owner-freebsd-fs@FreeBSD.ORG Thu Aug 17 14:48:10 2006 Return-Path: X-Original-To: freebsd-fs@FreeBSD.org Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 83CD716A4E0; Thu, 17 Aug 2006 14:48:10 +0000 (UTC) (envelope-from anderson@centtech.com) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2345543D5E; Thu, 17 Aug 2006 14:48:09 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id k7HEm69D088290; Thu, 17 Aug 2006 09:48:08 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <44E481BE.2080408@centtech.com> Date: Thu, 17 Aug 2006 09:48:30 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5.0.5 (X11/20060802) MIME-Version: 1.0 To: Pawel Jakub Dawidek References: <20060808195202.GA1564@garage.freebsd.pl> <44E46A68.6080602@centtech.com> <20060817140857.GB78978@garage.freebsd.pl> In-Reply-To: <20060817140857.GB78978@garage.freebsd.pl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1677/Thu Aug 17 08:56:09 2006 on mh2.centtech.com X-Virus-Status: Clean Cc: freebsd-fs@FreeBSD.org, freebsd-geom@FreeBSD.org Subject: Re: GJournal (hopefully) final patches. 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: Thu, 17 Aug 2006 14:48:10 -0000 On 08/17/06 09:08, Pawel Jakub Dawidek wrote: > On Thu, Aug 17, 2006 at 08:08:56AM -0500, Eric Anderson wrote: >> On 08/08/06 14:52, Pawel Jakub Dawidek wrote: >>> Hi. >>> I'm pleased to announce hopefully the final gjournal patches. >> [..snip..] >>> To create journaled UFS file system on ad0s1d partition: >>> # gjournal load >>> # gjournal label ad0s1d >>> # newfs -J /dev/ad0s1d.journal >>> # mount -o noatime,async /dev/ad0s1d.journal /mnt >>> On reboot 'fsck_ffs -p /dev/ad0s1d.journal' will perform fast check. One >>> can still run regular check by not giving the -p option. >> I have a 10TB filesystem I created as above, and recently a crash caused it to now complain about the filesystem being dirty. When I do an fsck -p, here's what I get: >> >> # fsck -p /dev/label/vol10 >> /dev/label/vol10: UNEXPECTED INCONSISTENCY, CANNOT RUN FAST FSCK >> >> >> /dev/label/vol10: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. > > Do you have log from the boot before you saw this? > I corrected one bug, but it was only possible to trigger when crash > happened early in the boot process. Your crash was during or just after > a boot maybe? > Yes, I have the logs. What should I send you? Also, I just tried newfs'ing a new journaled device, and mounting it, then a few minutes later, crashing the system (not purposely though), and it too gives the same results as the other filesystem (same specs, 10Tb, etc). The first crash was within about 30 minutes of booting, the second one was about the same time-frame. Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-fs@FreeBSD.ORG Thu Aug 17 15:00:21 2006 Return-Path: X-Original-To: freebsd-fs@FreeBSD.org Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 54FA416A4DF; Thu, 17 Aug 2006 15:00:21 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id B513343D5C; Thu, 17 Aug 2006 15:00:18 +0000 (GMT) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id AB5235133B; Thu, 17 Aug 2006 17:00:17 +0200 (CEST) Received: from localhost (pjd.wheel.pl [10.0.1.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 74AF750EA7; Thu, 17 Aug 2006 17:00:05 +0200 (CEST) Date: Thu, 17 Aug 2006 17:00:02 +0200 From: Pawel Jakub Dawidek To: Eric Anderson Message-ID: <20060817150001.GC78978@garage.freebsd.pl> References: <20060808195202.GA1564@garage.freebsd.pl> <44E46A68.6080602@centtech.com> <20060817140857.GB78978@garage.freebsd.pl> <44E481BE.2080408@centtech.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ZmUaFz6apKcXQszQ" Content-Disposition: inline In-Reply-To: <44E481BE.2080408@centtech.com> X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 User-Agent: mutt-ng/devel-r804 (FreeBSD) X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-5.9 required=3.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.0.4 Cc: freebsd-fs@FreeBSD.org, freebsd-geom@FreeBSD.org Subject: Re: GJournal (hopefully) final patches. 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: Thu, 17 Aug 2006 15:00:21 -0000 --ZmUaFz6apKcXQszQ Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Aug 17, 2006 at 09:48:30AM -0500, Eric Anderson wrote: > On 08/17/06 09:08, Pawel Jakub Dawidek wrote: > >On Thu, Aug 17, 2006 at 08:08:56AM -0500, Eric Anderson wrote: > >>On 08/08/06 14:52, Pawel Jakub Dawidek wrote: > >>>Hi. > >>>I'm pleased to announce hopefully the final gjournal patches. > >>[..snip..] > >>>To create journaled UFS file system on ad0s1d partition: > >>> # gjournal load > >>> # gjournal label ad0s1d > >>> # newfs -J /dev/ad0s1d.journal > >>> # mount -o noatime,async /dev/ad0s1d.journal /mnt > >>>On reboot 'fsck_ffs -p /dev/ad0s1d.journal' will perform fast check. O= ne > >>>can still run regular check by not giving the -p option. > >>I have a 10TB filesystem I created as above, and recently a crash cause= d it to now complain about the filesystem being dirty. When I do an fsck -= p, here's what I get: > >> > >># fsck -p /dev/label/vol10 > >>/dev/label/vol10: UNEXPECTED INCONSISTENCY, CANNOT RUN FAST FSCK > >> > >> > >>/dev/label/vol10: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. > >Do you have log from the boot before you saw this? > >I corrected one bug, but it was only possible to trigger when crash > >happened early in the boot process. Your crash was during or just after > >a boot maybe? >=20 > Yes, I have the logs. What should I send you? I just need 'grep -i journal' from them. > Also, I just tried newfs'ing a new journaled device, and mounting it, the= n a few minutes later, crashing the system (not purposely though), and it t= oo gives the same=20 > results as the other filesystem (same specs, 10Tb, etc). >=20 > The first crash was within about 30 minutes of booting, the second one wa= s about the same time-frame. Maybe there was no writes? --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --ZmUaFz6apKcXQszQ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFE5IRxForvXbEpPzQRArZ2AJ9MpJE0PmewY65ziM8n9nHFgabFRgCePMD3 qlD1J0dy7fV/q784cKACAiE= =X7eU -----END PGP SIGNATURE----- --ZmUaFz6apKcXQszQ-- From owner-freebsd-fs@FreeBSD.ORG Thu Aug 17 15:02:47 2006 Return-Path: X-Original-To: freebsd-fs@FreeBSD.org Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 482C916A4DA; Thu, 17 Aug 2006 15:02:47 +0000 (UTC) (envelope-from anderson@centtech.com) Received: from mh1.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 61DC843D8F; Thu, 17 Aug 2006 15:02:27 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh1.centtech.com (8.13.1/8.13.1) with ESMTP id k7HF2QqE091742; Thu, 17 Aug 2006 10:02:26 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <44E4851A.6020904@centtech.com> Date: Thu, 17 Aug 2006 10:02:50 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5.0.5 (X11/20060802) MIME-Version: 1.0 To: Pawel Jakub Dawidek References: <20060808195202.GA1564@garage.freebsd.pl> <44E46A68.6080602@centtech.com> <20060817140857.GB78978@garage.freebsd.pl> <44E481BE.2080408@centtech.com> <20060817150001.GC78978@garage.freebsd.pl> In-Reply-To: <20060817150001.GC78978@garage.freebsd.pl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1677/Thu Aug 17 08:56:09 2006 on mh1.centtech.com X-Virus-Status: Clean Cc: freebsd-fs@FreeBSD.org, freebsd-geom@FreeBSD.org Subject: Re: GJournal (hopefully) final patches. 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: Thu, 17 Aug 2006 15:02:47 -0000 On 08/17/06 10:00, Pawel Jakub Dawidek wrote: > On Thu, Aug 17, 2006 at 09:48:30AM -0500, Eric Anderson wrote: >> On 08/17/06 09:08, Pawel Jakub Dawidek wrote: >>> On Thu, Aug 17, 2006 at 08:08:56AM -0500, Eric Anderson wrote: >>>> On 08/08/06 14:52, Pawel Jakub Dawidek wrote: >>>>> Hi. >>>>> I'm pleased to announce hopefully the final gjournal patches. >>>> [..snip..] >>>>> To create journaled UFS file system on ad0s1d partition: >>>>> # gjournal load >>>>> # gjournal label ad0s1d >>>>> # newfs -J /dev/ad0s1d.journal >>>>> # mount -o noatime,async /dev/ad0s1d.journal /mnt >>>>> On reboot 'fsck_ffs -p /dev/ad0s1d.journal' will perform fast check. One >>>>> can still run regular check by not giving the -p option. >>>> I have a 10TB filesystem I created as above, and recently a crash caused it to now complain about the filesystem being dirty. When I do an fsck -p, here's what I get: >>>> >>>> # fsck -p /dev/label/vol10 >>>> /dev/label/vol10: UNEXPECTED INCONSISTENCY, CANNOT RUN FAST FSCK >>>> >>>> >>>> /dev/label/vol10: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. >>> Do you have log from the boot before you saw this? >>> I corrected one bug, but it was only possible to trigger when crash >>> happened early in the boot process. Your crash was during or just after >>> a boot maybe? >> Yes, I have the logs. What should I send you? > > I just need 'grep -i journal' from them. > >> Also, I just tried newfs'ing a new journaled device, and mounting it, then a few minutes later, crashing the system (not purposely though), and it too gives the same >> results as the other filesystem (same specs, 10Tb, etc). >> >> The first crash was within about 30 minutes of booting, the second one was about the same time-frame. > > Maybe there was no writes? > There were no writes, absolutely. The only part of the fs that was touched, was the superblock (marking clean/dirty). Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-fs@FreeBSD.ORG Thu Aug 17 15:21:12 2006 Return-Path: X-Original-To: freebsd-fs@FreeBSD.org Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D34EB16A4DF; Thu, 17 Aug 2006 15:21:12 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id 22D2043D55; Thu, 17 Aug 2006 15:21:10 +0000 (GMT) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 76C4751392; Thu, 17 Aug 2006 17:21:09 +0200 (CEST) Received: from localhost (pjd.wheel.pl [10.0.1.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 6A0C051339; Thu, 17 Aug 2006 17:21:02 +0200 (CEST) Date: Thu, 17 Aug 2006 17:20:59 +0200 From: Pawel Jakub Dawidek To: Eric Anderson Message-ID: <20060817152059.GD78978@garage.freebsd.pl> References: <20060808195202.GA1564@garage.freebsd.pl> <44E46A68.6080602@centtech.com> <20060817140857.GB78978@garage.freebsd.pl> <44E481BE.2080408@centtech.com> <20060817150001.GC78978@garage.freebsd.pl> <44E4851A.6020904@centtech.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="5p8PegU4iirBW1oA" Content-Disposition: inline In-Reply-To: <44E4851A.6020904@centtech.com> X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 User-Agent: mutt-ng/devel-r804 (FreeBSD) X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-5.9 required=3.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.0.4 Cc: freebsd-fs@FreeBSD.org, freebsd-geom@FreeBSD.org Subject: Re: GJournal (hopefully) final patches. 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: Thu, 17 Aug 2006 15:21:12 -0000 --5p8PegU4iirBW1oA Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Aug 17, 2006 at 10:02:50AM -0500, Eric Anderson wrote: > >Maybe there was no writes? >=20 > There were no writes, absolutely. The only part of the fs that was touch= ed, was the superblock (marking clean/dirty). Ok, so this is the bug. When there was only one journal switch, gjournal will mark device as broken on boot. This is fixed in perforce already. I belive your file system is clean. Do you want to make it write-accessable again? --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --5p8PegU4iirBW1oA Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFE5IlbForvXbEpPzQRAh1WAKDlLyvW6af5WZshCV2oM3LvGC0FnACgjBI0 jzEmu602KDd1KeMSol4vk7g= =+DPp -----END PGP SIGNATURE----- --5p8PegU4iirBW1oA-- From owner-freebsd-fs@FreeBSD.ORG Thu Aug 17 15:25:06 2006 Return-Path: X-Original-To: freebsd-fs@FreeBSD.org Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 36AFC16A4DF; Thu, 17 Aug 2006 15:25:06 +0000 (UTC) (envelope-from anderson@centtech.com) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id B761943D45; Thu, 17 Aug 2006 15:25:05 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id k7HFP5f0094309; Thu, 17 Aug 2006 10:25:05 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <44E48A69.9010108@centtech.com> Date: Thu, 17 Aug 2006 10:25:29 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5.0.5 (X11/20060802) MIME-Version: 1.0 To: Pawel Jakub Dawidek References: <20060808195202.GA1564@garage.freebsd.pl> <44E46A68.6080602@centtech.com> <20060817140857.GB78978@garage.freebsd.pl> <44E481BE.2080408@centtech.com> <20060817150001.GC78978@garage.freebsd.pl> <44E4851A.6020904@centtech.com> <20060817152059.GD78978@garage.freebsd.pl> In-Reply-To: <20060817152059.GD78978@garage.freebsd.pl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1677/Thu Aug 17 08:56:09 2006 on mh2.centtech.com X-Virus-Status: Clean Cc: freebsd-fs@FreeBSD.org, freebsd-geom@FreeBSD.org Subject: Re: GJournal (hopefully) final patches. 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: Thu, 17 Aug 2006 15:25:06 -0000 On 08/17/06 10:20, Pawel Jakub Dawidek wrote: > On Thu, Aug 17, 2006 at 10:02:50AM -0500, Eric Anderson wrote: >>> Maybe there was no writes? >> There were no writes, absolutely. The only part of the fs that was touched, was the superblock (marking clean/dirty). > > Ok, so this is the bug. When there was only one journal switch, gjournal > will mark device as broken on boot. > This is fixed in perforce already. > > I belive your file system is clean. Do you want to make it > write-accessable again? > Yes, I believe it to be clean too. I can mount it rw, but I'd like to be able to 'convince' it that it is truly clean. Also - did you see my other thread about snapshot deadlock? Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-fs@FreeBSD.ORG Thu Aug 17 16:59:20 2006 Return-Path: X-Original-To: freebsd-fs@FreeBSD.ORG Delivered-To: freebsd-fs@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E5FF416A4DE; Thu, 17 Aug 2006 16:59:20 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id A4C3E43D5C; Thu, 17 Aug 2006 16:59:14 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (juzmjk@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id k7HGx1mc066405; Thu, 17 Aug 2006 18:59:06 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id k7HGx1iI066404; Thu, 17 Aug 2006 18:59:01 +0200 (CEST) (envelope-from olli) Date: Thu, 17 Aug 2006 18:59:01 +0200 (CEST) Message-Id: <200608171659.k7HGx1iI066404@lurza.secnetix.de> From: Oliver Fromme To: freebsd-amd64@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG, obrien@FreeBSD.ORG, lehmann@ans-netz.de In-Reply-To: <20060813011836.GE47774@dragon.NUXI.org> X-Newsgroups: list.freebsd-amd64 User-Agent: tin/1.8.0-20051224 ("Ronay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Thu, 17 Aug 2006 18:59:07 +0200 (CEST) Cc: Subject: Re: NFS lockup when copying a "special" file 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: Thu, 17 Aug 2006 16:59:21 -0000 This doesn't seem to be amd64-specific, so I copy freebsd-fs. David O'Brien wrote: > On Thu, Jul 13, 2006 at 08:14:34PM +0200, Oliver Lehmann wrote: > > nfs server www:/mnt/space/www: not responding > > nfs server www:/mnt/space/www: not responding > > nfs server www:/mnt/space/www: not responding That could be an MTU problem. If you have an unusual MTU (check ifconfig(8) output), try lowering it to 1500. If it's already at 1500, try lowering it even further, e.g. to 1492. > I get this all the time now. I started sometime in 2006. The only "fix" > I've found is to use NFS over TPC vs. UDP. For me my NFS server is > i386/bge(4) and the clients are i386/bge, amd64/bge, amd64/nve, > sparc64/hme. I'm had exactly the same problem on an i386/bge client running RELENG_6 of last week (2006-08-09). I can provide dmesg, kernel and other info if required, just ask me. Server is a NetApp Filer. FreeBSD 4.x clients don't have any problem. Symptoms: When trying to copy a certain file to the NFS directory, the whole share hung, the cp(1) process was in diskwait state ("D" in ps, with mwchan "bo_wwa"), and only a reboot could get rid of the hanging share. However, it was possible to mount the very same share a second time to a different mountpoint and continue working there, until you tried to copy that certain file there again. The file size is 1349 bytes, and the contents don't matter, i.e. the problem could be reproduced even with dd: $ dd if=/dev/zero of=/nfsshare/foo bs=1349 count=1 After a few experiments I found out that sizes between 1349 and 1352 exhibit the problem. Solution: Switching to TCP isn't an option because of our setup. However, I noticed that forcing NFSv2 (default is NFSv3) also seems to solve the problem. Since NFSv2 is limited to 2GB file size, I continued looking for other solutions. Then I noticed that the VLAN's parent interface (bge0) had an MTU of 1504 (the NFS mount is from a VLAN on that interface). I have no idea why it was set to 1504. When I lowered it to 1500, the problem was gone. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. C++: "an octopus made by nailing extra legs onto a dog" -- Steve Taylor, 1998 From owner-freebsd-fs@FreeBSD.ORG Fri Aug 18 16:49:11 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 55A5916A4E7; Fri, 18 Aug 2006 16:49:11 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from fw.zoral.com.ua (fw.zoral.com.ua [213.186.206.134]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6187B43D58; Fri, 18 Aug 2006 16:49:10 +0000 (GMT) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by fw.zoral.com.ua (8.13.4/8.13.4) with ESMTP id k7IGn4JO029047 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 18 Aug 2006 19:49:04 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.13.6/8.13.6) with ESMTP id k7IGn4u0085025; Fri, 18 Aug 2006 19:49:04 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.13.6/8.13.6/Submit) id k7IGn3g4085024; Fri, 18 Aug 2006 19:49:03 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Fri, 18 Aug 2006 19:49:03 +0300 From: Konstantin Belousov To: Peter Holm , tegge@freebsd.org Message-ID: <20060818164903.GF20768@deviant.kiev.zoral.com.ua> References: <20060816155310.GA64420@peter.osted.lan> <20060817105155.GC1483@deviant.kiev.zoral.com.ua> <22339.193.3.142.123.1155814154.squirrel@webmail4.pair.com> <20060817113203.GD1483@deviant.kiev.zoral.com.ua> <20060817170314.GA17490@peter.osted.lan> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="nqkreNcslJAfgyzk" Content-Disposition: inline In-Reply-To: <20060817170314.GA17490@peter.osted.lan> User-Agent: Mutt/1.4.2.2i X-Virus-Scanned: ClamAV version 0.88.4, clamav-milter version 0.88.4 on fw.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=1.9 required=5.0 tests=DNS_FROM_RFC_ABUSE, SPF_NEUTRAL,UNPARSEABLE_RELAY autolearn=no version=3.1.4 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.1.4 (2006-07-25) on fw.zoral.com.ua Cc: freebsd-fs@freebsd.org Subject: Deadlock between nfsd and snapshots. [Was: Re: Livelock while accessing /tmp] 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: Fri, 18 Aug 2006 16:49:11 -0000 --nqkreNcslJAfgyzk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Aug 17, 2006 at 07:03:14PM +0200, Peter Holm wrote: >=20 > Ok, I got a new one after some 6 hours of testing with the attached > script + the default stress test: > http://people.freebsd.org/~pho/stress/log/cons205a.html >=20 > - Peter First, big thanks to Peter for helping debugging the problem ! This deadlock happens between processes 764 (nfsd) and 62981 (mksnap_ffs). In fact, deadlock is not specific to nfsd. It happens when ufs_inactive() interposes with ffs_snapshot. Look: db> where 764 Tracing pid 764 tid 100076 td 0xc3fdb870 sched_switch(c3fdb870,0,1) at sched_switch+0x183 mi_switch(1,0) at mi_switch+0x280 sleepq_switch(c40ca57c,c0a0b0b0,0,c092000a,211,...) at sleepq_switch+0xcd sleepq_wait(c40ca57c,0,c0927acf,3f3,c093229c,...) at sleepq_wait+0x46 msleep(c40ca57c,c40ca534,29f,c0927b18,0,...) at msleep+0x27d vn_start_secondary_write(c59bc820,e6586988,1) at vn_start_secondary_write+0= x122 ufs_inactive(e65869b8) at ufs_inactive+0x257 VOP_INACTIVE_APV(c09d9a00,e65869b8) at VOP_INACTIVE_APV+0x7e vinactive(c59bc820,c3fdb870) at vinactive+0x72 vput(c59bc820,c0a0b0c8,1,c0932293,407,...) at vput+0x1b3 nfsrv_read(c4703600,c3f12900,c3fdb870,e6586c40) at nfsrv_read+0xc21 nfssvc_nfsd(c3fdb870) at nfssvc_nfsd+0x409 nfssvc(c3fdb870,e6586d04) at nfssvc+0x18c syscall(3b,3b,3b,1,0,...) at syscall+0x256 Xint0x80_syscall() at Xint0x80_syscall+0x1f db> where 62981 Tracing pid 62981 tid 100135 td 0xc46e3d80 sched_switch(c46e3d80,0,1) at sched_switch+0x183 mi_switch(1,0) at mi_switch+0x280 sleepq_switch(c59bc878,c0a0b0b0,0,c092000a,211,...) at sleepq_switch+0xcd sleepq_wait(c59bc878,0,c59bc89c,b1,c0926903,...) at sleepq_wait+0x46 msleep(c59bc878,c0a0a930,50,c0924f24,0,...) at msleep+0x27d acquire(e66ee5a8,40,60000,c46e3d80,0,...) at acquire+0x76 lockmgr(c59bc878,2002,c59bc89c,c46e3d80) at lockmgr+0x44a ffs_lock(e66ee600) at ffs_lock+0x6e VOP_LOCK_APV(c09d9a00,e66ee600) at VOP_LOCK_APV+0x87 vn_lock(c59bc820,2002,c46e3d80,c59bc820) at vn_lock+0xa8 ffs_snapshot(c40ca510,c3defb60,c3defb60,c401e000,c4016514,...) at ffs_snaps= hot+0x1210 ffs_mount(c40ca510,c46e3d80,20000000,201300,0,...) at ffs_mount+0x927 vfs_domount(c46e3d80,c3dffa80,c3d45b40,1211300,c3f662c0,c0a0b0c8,0,c09268fa= ,2b0) at vfs_domount+0x554 vfs_donmount(c46e3d80,1211300,e66eebac) at vfs_donmount+0x414 kernel_mount(c3fc5690,1211300,bfbfecdc,0,0,...) at kernel_mount+0x6d ffs_cmount(c3fc5690,bfbfe500,1211300,c46e3d80,c09d96e0,...) at ffs_cmount+0= x5d mount(c46e3d80,e66eed04) at mount+0x15e syscall(3b,3b,3b,2816772c,bfbfe4a0,...) at syscall+0x256 mnt_kern_flag =3D 0x2c000000 (MNTK_SUSPEND | MNTK_SUSPEND2 | MNTK_MPSAFE). vn_lock in the ffs_snapshot is called with flags LK_INTERLOCK | LK_EXCLUSIV= E. There is only one such place in the ffs_snapshot.c, at line 541. On the other hand, ufs_inactive calls vn_start_secondary_write(vp, XXX, V_W= AIT). ufs_inactive is running with vnode locked, If happens at the right time, system will deadlock. nfsd is the most vulnerable to the problem due to it oftenly being the only (and last) user of vnode, vput() from nfsd have high chance resulting in vinactive(). Below is the patch that set VI_OWEINACT for the inode if the last call to vn_start_sec_write(..., V_NOWAIT) fails. The return from that point is safe because mp =3D=3D NULL means that no previous code that changes inode was e= xecuted. Please, review and test. Index: sys/ufs/ufs/ufs_inode.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /usr/local/arch/ncvs/src/sys/ufs/ufs/ufs_inode.c,v retrieving revision 1.67 diff -u -r1.67 ufs_inode.c --- sys/ufs/ufs/ufs_inode.c 9 May 2006 22:33:43 -0000 1.67 +++ sys/ufs/ufs/ufs_inode.c 18 Aug 2006 16:42:48 -0000 @@ -147,9 +147,23 @@ mp =3D NULL; ip->i_flag &=3D ~IN_ACCESS; } else { - if (mp =3D=3D NULL) - (void) vn_start_secondary_write(vp, &mp, - V_WAIT); + if (mp =3D=3D NULL) { + loop1: + if (vn_start_secondary_write(vp, &mp, V_NOWAIT)) { + MNT_ILOCK(mp); + if ((mp->mnt_kern_flag & + (MNTK_SUSPEND2 | MNTK_SUSPENDED)) =3D=3D 0) { + MNT_IUNLOCK(mp); + goto loop1; + } + =09 + VI_LOCK(vp); + vp->v_iflag |=3D VI_OWEINACT; + VI_UNLOCK(vp); + MNT_IUNLOCK(mp); + return (0); + } + } UFS_UPDATE(vp, 0); } } --nqkreNcslJAfgyzk Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFE5e9+C3+MBN1Mb4gRAqlxAKCqmgB9LqfeuVA0H5wTihtwDcurBACcCWs7 k+kLvfy3/ko+YS7pDWeagoo= =PGnw -----END PGP SIGNATURE----- --nqkreNcslJAfgyzk-- From owner-freebsd-fs@FreeBSD.ORG Fri Aug 18 18:38:10 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F41E116A4E5 for ; Fri, 18 Aug 2006 18:38:09 +0000 (UTC) (envelope-from uspoerlein@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 23C8243DDE for ; Fri, 18 Aug 2006 18:37:15 +0000 (GMT) (envelope-from uspoerlein@gmail.com) Received: by nz-out-0102.google.com with SMTP id x3so589725nzd for ; Fri, 18 Aug 2006 11:37:14 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:date:from:to:cc:subject:message-id:mail-followup-to:references:mime-version:content-type:content-disposition:in-reply-to; b=MzAP9NqRqcRtUeiP72n4mIXjMDhA7MWJEByuq0kO1119VUhLuH0U++aBpry6jTjX/Ydrm3xLaSKJwz7pYLHdU9+1KevBYrPY6y8NBir7uxTe+KsvZSZlF0a7xxRVinSGvgAxo1pRdHY9V+yyQqpcDRo3DPbcr0QTcGQudyoTddM= Received: by 10.65.154.10 with SMTP id g10mr4140902qbo; Fri, 18 Aug 2006 11:37:14 -0700 (PDT) Received: from roadrunner.q.local ( [217.185.119.164]) by mx.gmail.com with ESMTP id p4sm2227586qba.2006.08.18.11.37.09; Fri, 18 Aug 2006 11:37:12 -0700 (PDT) Received: from roadrunner.q.local (localhost [127.0.0.1]) by roadrunner.q.local (8.13.6/8.13.6) with ESMTP id k7IIb59M001739; Fri, 18 Aug 2006 20:37:05 +0200 (CEST) (envelope-from uspoerlein@gmail.com) Received: (from q@localhost) by roadrunner.q.local (8.13.6/8.13.6/Submit) id k7HJ1rLL002368; Thu, 17 Aug 2006 21:01:53 +0200 (CEST) (envelope-from uspoerlein@gmail.com) Date: Thu, 17 Aug 2006 21:01:38 +0200 From: Ulrich Spoerlein To: Pawel Jakub Dawidek Message-ID: <20060817190138.GB1091@roadrunner.aventurien.local> Mail-Followup-To: Pawel Jakub Dawidek , Craig Boston , freebsd-fs@FreeBSD.org, freebsd-current@FreeBSD.org, freebsd-geom@FreeBSD.org References: <20060808195202.GA1564@garage.freebsd.pl> <20060810184702.GA8567@nowhere> <20060810192841.GA1345@garage.freebsd.pl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060810192841.GA1345@garage.freebsd.pl> Cc: freebsd-fs@FreeBSD.org, Craig Boston , freebsd-current@FreeBSD.org, freebsd-geom@FreeBSD.org Subject: Re: GJournal (hopefully) final patches. 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: Fri, 18 Aug 2006 18:38:10 -0000 Pawel Jakub Dawidek wrote: > On Thu, Aug 10, 2006 at 01:47:23PM -0500, Craig Boston wrote: > I prefer to put gjournal on the top, because it gives consistency to > layers below it. For example I can use geli with bigger sector size > (sector size greater than disk sector size in encryption-only-mode can > be unreliable on power failures, which is not the case when gjournal is > above geli), I can turn off synchronization of gmirror/graid3 after a > power failure, etc. I have been bitten by the bigger sector size + kernel crash, and it is not funny. Could you *please* add a note to the geli and/or gjournal manpages describing the various possibilities and their advantages/drawbacks? Thanks. Ulrich Spoerlein -- A: Yes. >Q: Are you sure? > >A: Because it reverses the logical flow of conversation. > >>Q: Why is top posting frowned upon? From owner-freebsd-fs@FreeBSD.ORG Fri Aug 18 20:20:09 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0D9EE16A4DA; Fri, 18 Aug 2006 20:20:08 +0000 (UTC) (envelope-from Tor.Egge@cvsup.no.freebsd.org) Received: from pil.idi.ntnu.no (pil.idi.ntnu.no [129.241.107.93]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B7E843D4C; Fri, 18 Aug 2006 20:20:05 +0000 (GMT) (envelope-from Tor.Egge@cvsup.no.freebsd.org) Received: from cvsup.no.freebsd.org (c2h5oh.idi.ntnu.no [129.241.103.69]) by pil.idi.ntnu.no (8.13.6/8.13.1) with ESMTP id k7IKK3lX001495 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 18 Aug 2006 22:20:03 +0200 (MEST) Received: from localhost (localhost [127.0.0.1]) by cvsup.no.freebsd.org (8.13.4/8.13.4) with ESMTP id k7IKK2V6013041; Fri, 18 Aug 2006 20:20:02 GMT (envelope-from Tor.Egge@cvsup.no.freebsd.org) Date: Fri, 18 Aug 2006 20:20:01 +0000 (UTC) Message-Id: <20060818.202001.74745664.Tor.Egge@cvsup.no.freebsd.org> To: kostikbel@gmail.com From: Tor Egge In-Reply-To: <20060818164903.GF20768@deviant.kiev.zoral.com.ua> References: <20060817113203.GD1483@deviant.kiev.zoral.com.ua> <20060817170314.GA17490@peter.osted.lan> <20060818164903.GF20768@deviant.kiev.zoral.com.ua> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned-By: mimedefang.idi.ntnu.no, using CLAMD X-SMTP-From: Sender=, Relay/Client=c2h5oh.idi.ntnu.no [129.241.103.69], EHLO=cvsup.no.freebsd.org X-Scanned-By: MIMEDefang 2.48 on 129.241.107.38 X-Scanned-By: mimedefang.idi.ntnu.no, using MIMEDefang 2.48 with local filter 16.42-idi X-Filter-Time: 1 seconds Cc: freebsd-fs@freebsd.org, tegge@freebsd.org Subject: Re: Deadlock between nfsd and snapshots. 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: Fri, 18 Aug 2006 20:20:09 -0000 > First, big thanks to Peter for helping debugging the problem ! > > This deadlock happens between processes 764 (nfsd) and 62981 (mksnap_ffs). > In fact, deadlock is not specific to nfsd. It happens when ufs_inactive() > interposes with ffs_snapshot. [snip] > On the other hand, ufs_inactive calls vn_start_secondary_write(vp, XXX, > V_WAIT). ufs_inactive is running with vnode locked, If happens at the right > time, system will deadlock. > > nfsd is the most vulnerable to the problem due to it oftenly being the > only (and last) user of vnode, vput() from nfsd have high chance resulting > in vinactive(). > > Below is the patch that set VI_OWEINACT for the inode if the last call to > vn_start_sec_write(..., V_NOWAIT) fails. The return from that point is safe > because mp == NULL means that no previous code that changes inode was > executed. > Please, review and test. The deadlock indicates that one or more of IN_CHANGE, IN_MODIFIED or IN_UPDATE was set on the inode, indicating a write operation (e.g. VOP_WRITE(), VOP_RENAME(), VOP_CREATE(), VOP_REMOVE(), VOP_LINK(), VOP_SYMLINK(), VOP_SETATTR(), VOP_MKDIR(), VOP_RMDIR(), VOP_MKNOD()) that was not protected by vn_start_write() or vn_start_secondary_write(). The suspension of the file system should have cleared those flags on all related inodes. Write operations protected by vn_start_write() should have blocked without holding any vnode lock until the file system was resumed while write operations protected by vn_start_secondary_write() should have triggered a retry of the vnode sync loop in ffs_sync(). Such unprotected write operations might render the snapshot inconsistent. Your patch addresses the deadlock symptom but not the cause. - Tor Egge