From owner-freebsd-current@FreeBSD.ORG Tue Aug 28 13:05:56 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E492C16A41A for ; Tue, 28 Aug 2007 13:05:56 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from ns.trinitel.com (186.161.36.72.static.reverse.ltdomains.com [72.36.161.186]) by mx1.freebsd.org (Postfix) with ESMTP id B6CCA13C45A for ; Tue, 28 Aug 2007 13:05:56 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from proton.local (209-163-168-124.static.twtelecom.net [209.163.168.124]) (authenticated bits=0) by ns.trinitel.com (8.14.1/8.14.1) with ESMTP id l7SD5ofF086476; Tue, 28 Aug 2007 08:05:51 -0500 (CDT) (envelope-from anderson@freebsd.org) Message-ID: <46D41DAE.5010501@freebsd.org> Date: Tue, 28 Aug 2007 08:05:50 -0500 From: Eric Anderson User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Ivan Voras References: <200708261948.05750.qpadla@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.7 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on ns.trinitel.com Cc: freebsd-current@freebsd.org Subject: Re: Repeated UFS panics? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Aug 2007 13:05:57 -0000 Ivan Voras wrote: > Nikolay Pavlov wrote: > >> Is this similar as this one? >> http://docs.freebsd.org/cgi/mid.cgi?200708202327.03951.qpadla > > No: > - it happens with and without gjournal > - it happens during "regular" system usage during IO intensive periods > > It looks like a UFS corruption: as I said, I was able to provoke it > regularly by doing heavy IO on a clean newfs-ed file system (I can't > after an update to a newer kernel+world, now it seems to happen randomly). > > By any chance, are there some oddly named directories? I found that UFS will panic with a ufs_dirbad if there are some strange chars in the dir name. My directories were copied with rsync, from one UFS partition to another. It could be the way rsync translated it or the way UFS sent it to rsync during read, I'm not certain. I still have the bad file system, corresponding core file, etc. I even ran fsdb on the fs to track down the offending directory, and I think I found it. Of course, I could rename it in fsdb, but that would remove my test case. I stopped debugging it when I got busy, but if there is an interested person willing to help be with some debug ideas, I can go back into it. Eric