From owner-freebsd-fs@FreeBSD.ORG Sun Jan 20 19:12:47 2008 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A017216A46D for ; Sun, 20 Jan 2008 19:12:47 +0000 (UTC) (envelope-from matt@gsicomp.on.ca) Received: from daisy2.compar.com (mail1.compar.com [216.208.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 788F013C459 for ; Sun, 20 Jan 2008 19:12:47 +0000 (UTC) (envelope-from matt@gsicomp.on.ca) Received: from localhost (localhost.compar.com [127.0.0.1]) by daisy2.compar.com (Postfix) with ESMTP id E689D13C418 for ; Sun, 20 Jan 2008 13:47:47 -0500 (EST) X-Virus-Scanned: amavisd-new at compar.com Received: from unknown by localhost (amavisd-new, unix socket) id IGYThKIMnIls for ; Sun, 20 Jan 2008 13:47:45 -0500 (EST) Received: from hermes (CPE00062566c7bb-CM001ac3584898.cpe.net.cable.rogers.com [99.236.43.116]) by daisy2.compar.com (Postfix) with SMTP id 5404313C40A for ; Sun, 20 Jan 2008 13:47:45 -0500 (EST) Message-ID: <000801c85b94$f3a58ea0$1200a8c0@hermes> From: "Matt Emmerton" To: Date: Sun, 20 Jan 2008 13:47:47 -0500 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0005_01C85B6B.0A881D60" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 Subject: Looking for help to reconstruct a corrupted UFS2 filesystem 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: Sun, 20 Jan 2008 19:12:47 -0000 This is a multi-part message in MIME format. ------=_NextPart_000_0005_01C85B6B.0A881D60 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit Hi folks, Before anyone points out the obvious, yes, I did take backups. For reasons I won't get into here, the backup filesystem got symlinked to a location on the source drive (mere hours before the drive crapped out), which rendered my backups useless. The drive containing the corrupted filesystem is detected as ad1. This drive has two *different* partition tables on it -- /dev/ad1 shows a NTFS filesystem using the whole disk, and /dev/ad1s1 shows a FreeBSD filesystem using the whole disk. I mistakenly thought this was a disk that I had brought over from a Windows machine and proceeded to boot Windows and "repaired" the NTFS filesystem. Oops. After that failed, I realized that the disk really contained a FreeBSD filesystem on /dev/ad1s1. Attempts to reconstruct this have failed miserably. Using newfs -N, I located alternate superblocks. The majority of the superblocks are identical, with a couple being corrupted or all-zeros (including the primary superblock at 160). Using dd I copied a "good" superblock over all of the "bad" superblocks, and now all superblocks contain the same information. Now, using fsck_ufs -b /dev/ad1s1, it churns away, and eventually brings up some garbage data and fails attempting to allocate 4GB of memory. (See attached file - fsck.out). What are my options at this point? Since all the superblocks are identical, fsck always behaves the same. I suspect that one of the key blocks that the superblock points to is corrupted. Is any of this data replicated on disk? Can I troll the disk looking for intermediate blocks and easily chain together portions of directory trees? Regards, -- Matt Emmerton ------=_NextPart_000_0005_01C85B6B.0A881D60 Content-Type: application/octet-stream; name="fsck.out" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="fsck.out" Alternate super block location: 15430592=0A= ** /dev/ad1s1=0A= ** Last Mounted on =0A= ** Phase 1 - Check Blocks and Sizes=0A= -1 BAD I=3D424769=0A= 1 DUP I=3D424769=0A= 2 DUP I=3D424769=0A= 3 DUP I=3D424769=0A= 4 DUP I=3D424769=0A= 5 DUP I=3D424769=0A= 6 DUP I=3D424769=0A= -1 BAD I=3D424769=0A= 1 DUP I=3D424769=0A= 2 DUP I=3D424769=0A= 3 DUP I=3D424769=0A= 4 DUP I=3D424769=0A= 5 DUP I=3D424769=0A= EXCESSIVE DUP BLKS I=3D424769=0A= CONTINUE? [yn] =0A= INCORRECT BLOCK COUNT I=3D424769 (2172864 should be 1246296)=0A= CORRECT? [yn] fsck_ufs: cannot alloc 4294967292 bytes for inoinfo=0A= =0A= ------=_NextPart_000_0005_01C85B6B.0A881D60-- From owner-freebsd-fs@FreeBSD.ORG Sun Jan 20 19:53:54 2008 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E723516A420 for ; Sun, 20 Jan 2008 19:53:54 +0000 (UTC) (envelope-from frank@exit.com) Received: from tinker.exit.com (tinker.exit.com [206.223.0.1]) by mx1.freebsd.org (Postfix) with ESMTP id 73E9013C447 for ; Sun, 20 Jan 2008 19:53:54 +0000 (UTC) (envelope-from frank@exit.com) Received: from jill.exit.com (jill.exit.com [206.223.0.4]) by tinker.exit.com (8.14.1/8.14.1) with ESMTP id m0KJI4rh055499; Sun, 20 Jan 2008 11:18:04 -0800 (PST) (envelope-from frank@exit.com) DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=exit.com; s=tinker; t=1200856684; bh=PlKLEdFXIPjmoDmkWbqribNhWdg=; h=X-Authentication-Warning:Subject:From:Reply-To:To:Cc:In-Reply-To: References:Content-Type:Content-Transfer-Encoding:Organization: Date:Message-Id:Mime-Version:X-Mailer; b=dQRiIkzyQQzmwEOCR8ub1z1Pj /5rIE50DaE+CHvaIzWjDJjZIYNGHxV06ECy7MitRGaEwS1zv04Mgsl+Uy9ZmMvpzlqh D+ZWqlrbVH/fFxMiRCkxXyEPrXIbeQWZdkFkq4DLbGAsS/aapG6qnuxPyc59c8lLt6S DyHK0o3RLCoI= Received: from jill.exit.com (localhost [127.0.0.1]) by jill.exit.com (8.14.1/8.14.1) with ESMTP id m0KJMAo4011783; Sun, 20 Jan 2008 11:22:10 -0800 (PST) (envelope-from frank@exit.com) Received: (from frank@localhost) by jill.exit.com (8.14.1/8.14.2/Submit) id m0KJMAQQ011782; Sun, 20 Jan 2008 11:22:10 -0800 (PST) (envelope-from frank@exit.com) X-Authentication-Warning: jill.exit.com: frank set sender to frank@exit.com using -f From: Frank Mayhar To: Matt Emmerton In-Reply-To: <000801c85b94$f3a58ea0$1200a8c0@hermes> References: <000801c85b94$f3a58ea0$1200a8c0@hermes> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Exit Consulting Date: Sun, 20 Jan 2008 11:22:10 -0800 Message-Id: <1200856930.9818.2.camel@jill.exit.com> Mime-Version: 1.0 X-Mailer: Evolution 2.12.3 FreeBSD GNOME Team Port Cc: freebsd-fs@freebsd.org Subject: Re: Looking for help to reconstruct a corrupted UFS2 filesystem X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: frank@exit.com List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Jan 2008 19:53:55 -0000 On Sun, 2008-01-20 at 13:47 -0500, Matt Emmerton wrote: > What are my options at this point? Since all the superblocks are identical, > fsck always behaves the same. I suspect that one of the key blocks that the > superblock points to is corrupted. Is any of this data replicated on disk? > Can I troll the disk looking for intermediate blocks and easily chain > together portions of directory trees? This kind of thing is why I put ports/sysutils/ffs2recov together. You won't be able to recover everything but you should be able to get a lot of it back. -- Frank Mayhar frank@exit.com http://www.exit.com/ Exit Consulting http://www.gpsclock.com/ http://www.exit.com/blog/frank/ http://www.zazzle.com/fmayhar* From owner-freebsd-fs@FreeBSD.ORG Sun Jan 20 22:46:07 2008 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 364C016A498 for ; Sun, 20 Jan 2008 22:46:07 +0000 (UTC) (envelope-from matt@gsicomp.on.ca) Received: from daisy2.compar.com (mail1.compar.com [216.208.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 04E2813C4D5 for ; Sun, 20 Jan 2008 22:46:06 +0000 (UTC) (envelope-from matt@gsicomp.on.ca) Received: from localhost (localhost.compar.com [127.0.0.1]) by daisy2.compar.com (Postfix) with ESMTP id 0F8DF13C46D; Sun, 20 Jan 2008 17:46:06 -0500 (EST) X-Virus-Scanned: amavisd-new at compar.com Received: from unknown by localhost (amavisd-new, unix socket) id tPOyDIf9EpbZ; Sun, 20 Jan 2008 17:46:03 -0500 (EST) Received: from hermes (CPE00062566c7bb-CM001ac3584898.cpe.net.cable.rogers.com [99.236.43.116]) by daisy2.compar.com (Postfix) with SMTP id 0BD7F13C424; Sun, 20 Jan 2008 17:46:02 -0500 (EST) Message-ID: <002201c85bb6$3d2a7fb0$1200a8c0@hermes> From: "Matt Emmerton" To: References: <000801c85b94$f3a58ea0$1200a8c0@hermes> <1200856930.9818.2.camel@jill.exit.com> Date: Sun, 20 Jan 2008 17:46:04 -0500 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 Cc: freebsd-fs@freebsd.org Subject: Re: Looking for help to reconstruct a corrupted UFS2 filesystem 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: Sun, 20 Jan 2008 22:46:07 -0000 > On Sun, 2008-01-20 at 13:47 -0500, Matt Emmerton wrote: >> What are my options at this point? Since all the superblocks are >> identical, >> fsck always behaves the same. I suspect that one of the key blocks that >> the >> superblock points to is corrupted. Is any of this data replicated on >> disk? >> Can I troll the disk looking for intermediate blocks and easily chain >> together portions of directory trees? > > This kind of thing is why I put ports/sysutils/ffs2recov together. You > won't be able to recover everything but you should be able to get a lot > of it back. Thanks Frank. I'm playing around with this tool now. Something must be really hosed since I'm getting a lot of segfaults. For example, ffs2recov -s /dev/ad1s1 segfaults after finding 3 superblocks, and these superblocks aren't close to anything that newfs -N dumps out (except the one at offset 160). It also attempts to read blk 18445195961337644512, which is clearly wrong. (I'm 99% sure that I used the newfs defaults when I created this filesystem, so why would ffs2recov be looking for superblocks in different locations?) ffs2rrecov -p also segfaults after dumping part of cg 3, and ffs2recov -d segfaults after hitting inode 8331. ffs2recov -a and ffs2recov -r do a lot of complaining regarding failure to allocate large amount (or negative) memory. I'm guessing that it's starting off with bad data, and that's not helping. I'm doing some brute force work with ffs2recov -i to sniff out good inodes and will start from there. Regards, -- Matt From owner-freebsd-fs@FreeBSD.ORG Mon Jan 21 11:06:59 2008 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F32DC16A420 for ; Mon, 21 Jan 2008 11:06:58 +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 E3EED13C4D3 for ; Mon, 21 Jan 2008 11:06:58 +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 m0LB6wIw046986 for ; Mon, 21 Jan 2008 11:06:58 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m0LB6w6G046982 for freebsd-fs@FreeBSD.org; Mon, 21 Jan 2008 11:06:58 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 21 Jan 2008 11:06:58 GMT Message-Id: <200801211106.m0LB6w6G046982@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-fs@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-fs@FreeBSD.org 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: Mon, 21 Jan 2008 11:06:59 -0000 Current FreeBSD problem reports Critical problems Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/112658 fs [smbfs] [patch] smbfs and caching problems (resolves b o kern/114676 fs [ufs] snapshot creation panics: snapacct_ufs2: bad blo o kern/116170 fs [panic] Kernel panic when mounting /tmp 3 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/114847 fs [ntfs] [patch] dirmask support for NTFS ala MSDOSFS o bin/118249 fs mv(1): moving a directory changes its mtime 2 problems total. From owner-freebsd-fs@FreeBSD.ORG Mon Jan 21 14:43:12 2008 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C0AF016A417; Mon, 21 Jan 2008 14:43:12 +0000 (UTC) (envelope-from gdt@ir.bbn.com) Received: from fnord.ir.bbn.com (fnord.ir.bbn.com [192.1.100.210]) by mx1.freebsd.org (Postfix) with ESMTP id 8D26C13C455; Mon, 21 Jan 2008 14:43:12 +0000 (UTC) (envelope-from gdt@ir.bbn.com) Received: by fnord.ir.bbn.com (Postfix, from userid 10853) id 0B2D752F1; Mon, 21 Jan 2008 09:24:30 -0500 (EST) From: Greg Troxel To: Robert Watson References: <18CC5A4A2AC36D7FF57615EE@ganymede.hub.org> <478AF6BC.8050604@highperformance.net> <20080114142124.Y55696@fledge.watson.org> <20080116085630.GA32361@pappardelle.tekno.chalmers.se> <20080117080359.U51764@fledge.watson.org> <20080118073445.GA30721@pappardelle.tekno.chalmers.se> <20080118095652.GC30721@pappardelle.tekno.chalmers.se> <20080118103952.D18977@fledge.watson.org> <20080118210621.GF7898@cs.cmu.edu> <20080118211556.T46437@fledge.watson.org> <20080119005938.Q53920@fledge.watson.org> X-Hashcash: 1:20:080121:freebsd-fs@freebsd.org::aQMwbdXc7+I8snkB:0000000000000000000000000000000000000001f1x X-Hashcash: 1:20:080121:jaharkes@cs.cmu.edu::SG1aAPDtiQkB6QBR:0000000000000000000000000000000000000000002Q9X X-Hashcash: 1:20:080121:rwatson@freebsd.org::aQMwbdXc7+I8snkB:0000000000000000000000000000000000000000004ILv Date: Mon, 21 Jan 2008 09:24:30 -0500 In-Reply-To: <20080119005938.Q53920@fledge.watson.org> (Robert Watson's message of "Sat, 19 Jan 2008 01:01:04 +0000 (GMT)") Message-ID: User-Agent: Gnus/5.110007 (No Gnus v0.7) Emacs/22.1 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-fs@freebsd.org, Jan Harkes Subject: Re: Coda on FreeBSD problem reports? 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: Mon, 21 Jan 2008 14:43:12 -0000 Coda support in NetBSD (-current and netbsd-4 branch) is mostly ok, so you may want to glance at that for reference while working on the FreeBSD support. From owner-freebsd-fs@FreeBSD.ORG Mon Jan 21 20:40:31 2008 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 62F3116A47A for ; Mon, 21 Jan 2008 20:40:31 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id 43EC713C4D3 for ; Mon, 21 Jan 2008 20:40:31 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id C7E2547396; Mon, 21 Jan 2008 15:40:30 -0500 (EST) Date: Mon, 21 Jan 2008 20:40:30 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Greg Troxel In-Reply-To: Message-ID: <20080121203838.G4194@fledge.watson.org> References: <18CC5A4A2AC36D7FF57615EE@ganymede.hub.org> <478AF6BC.8050604@highperformance.net> <20080114142124.Y55696@fledge.watson.org> <20080116085630.GA32361@pappardelle.tekno.chalmers.se> <20080117080359.U51764@fledge.watson.org> <20080118073445.GA30721@pappardelle.tekno.chalmers.se> <20080118095652.GC30721@pappardelle.tekno.chalmers.se> <20080118103952.D18977@fledge.watson.org> <20080118210621.GF7898@cs.cmu.edu> <20080118211556.T46437@fledge.watson.org> <20080119005938.Q53920@fledge.watson.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-fs@freebsd.org, Jan Harkes Subject: Re: Coda on FreeBSD problem reports? 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: Mon, 21 Jan 2008 20:40:31 -0000 On Mon, 21 Jan 2008, Greg Troxel wrote: > Coda support in NetBSD (-current and netbsd-4 branch) is mostly ok, so you > may want to glance at that for reference while working on the FreeBSD > support. Greg, I was looking at the NetBSD Coda parts over the weekend, but it seemed that most of the bugs in the FreeBSD code were due to gradual rot as VFS evolved and our Coda module source didn't remain code up. I notice that NetBSD still supports CODA_COMPAT_5 as well -- is there any reason to keep on doing this, really? I understand originally it was because Coda 5 remained under the BSD license and Coda 6 was under GPL, but it's been a while since anyone did anything with Coda 5. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-fs@FreeBSD.ORG Mon Jan 21 21:04:06 2008 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 240E116A41B; Mon, 21 Jan 2008 21:04:06 +0000 (UTC) (envelope-from jaharkes@cs.cmu.edu) Received: from delft.aura.cs.cmu.edu (unknown [IPv6:2002:8002:ce58::1]) by mx1.freebsd.org (Postfix) with ESMTP id D73E513C4D5; Mon, 21 Jan 2008 21:04:05 +0000 (UTC) (envelope-from jaharkes@cs.cmu.edu) Received: from jaharkes by delft.aura.cs.cmu.edu with local (Exim 4.68) (envelope-from ) id 1JH3oL-0003lt-9q; Mon, 21 Jan 2008 16:04:05 -0500 Date: Mon, 21 Jan 2008 16:04:05 -0500 From: Jan Harkes To: Robert Watson Message-ID: <20080121210405.GB9253@cs.cmu.edu> Mail-Followup-To: Robert Watson , Greg Troxel , freebsd-fs@FreeBSD.org References: <20080116085630.GA32361@pappardelle.tekno.chalmers.se> <20080117080359.U51764@fledge.watson.org> <20080118073445.GA30721@pappardelle.tekno.chalmers.se> <20080118095652.GC30721@pappardelle.tekno.chalmers.se> <20080118103952.D18977@fledge.watson.org> <20080118210621.GF7898@cs.cmu.edu> <20080118211556.T46437@fledge.watson.org> <20080119005938.Q53920@fledge.watson.org> <20080121203838.G4194@fledge.watson.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080121203838.G4194@fledge.watson.org> User-Agent: Mutt/1.5.17 (2007-12-11) Cc: freebsd-fs@FreeBSD.org Subject: Re: Coda on FreeBSD problem reports? 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: Mon, 21 Jan 2008 21:04:06 -0000 On Mon, Jan 21, 2008 at 08:40:30PM +0000, Robert Watson wrote: > On Mon, 21 Jan 2008, Greg Troxel wrote: > >> Coda support in NetBSD (-current and netbsd-4 branch) is mostly ok, so >> you may want to glance at that for reference while working on the >> FreeBSD support. > > I was looking at the NetBSD Coda parts over the weekend, but it seemed > that most of the bugs in the FreeBSD code were due to gradual rot as VFS > evolved and our Coda module source didn't remain code up. > > I notice that NetBSD still supports CODA_COMPAT_5 as well -- is there any > reason to keep on doing this, really? I understand originally it was > because Coda 5 remained under the BSD license and Coda 6 was under GPL, > but it's been a while since anyone did anything with Coda 5. Actually it was Coda 4 that remained under the BSD license. The difference between Coda 5 and 6 was the introduction of realms. So instead of going to /coda/usr/jaharkes, I now have to access /coda/coda.cs.cmu.edu/usr/jaharkes. The important kernel difference is that we went from 96-bit file identifiers to 128-bit by adding a 32-bit realm-id. Aside from the inconvenience of having longer pathnames the initial versions with the dynamic root were not neccesarily as stable. I think it took at least 5 or 6 iterations before we got to a point that was somewhat comparable in stability. Same thing with coda-6.9.x clients, which use only write-disconnected operation and although that code has been around for a long time, we were never forced to really to rely on it 100%, so all those little nagging problems that have been around for a long time but were hard to reproduce or pin down are now pretty much unavoidable. Jan From owner-freebsd-fs@FreeBSD.ORG Tue Jan 22 01:04:32 2008 Return-Path: Delivered-To: fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 373C616A418 for ; Tue, 22 Jan 2008 01:04:32 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id 0820E13C45D for ; Tue, 22 Jan 2008 01:04:31 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id A931B46CEC; Mon, 21 Jan 2008 20:04:31 -0500 (EST) Date: Tue, 22 Jan 2008 01:04:31 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Rune , Jan Harkes In-Reply-To: <20080119165056.E3375@fledge.watson.org> Message-ID: <20080122010003.B29737@fledge.watson.org> References: <20080119165056.E3375@fledge.watson.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: fs@FreeBSD.org Subject: Re: Various FreeBSD Coda fixes 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, 22 Jan 2008 01:04:32 -0000 On Sat, 19 Jan 2008, Robert Watson wrote: > I'm not sure if these can be MFC'd before 7.0, but will ask re@ if we can > fit them in. Certainly, it's better than panicking, which is a relatively > likely scenario with what's currently in RELENG_7. I've merged these, and a couple more since then, to RLEENG_7, and will request an MFC to RELENG_7_0 to include them in the forthcoming FreeBSD 7.0. It would be very helpful, if you have a 7.x box, if you could update to the head of RELENG_7 to pick up these fixes, and test with Coda with them. I'm aware of four outstanding problems: - Rune has reported a hang with X11 and Coda, but we haven't yet been able to track it down much yet -- might not be related to Coda. - Linux binaries have problems listing directories in Coda under Linux emulation. Won't be fixed for 7.0. - ".." and "." sometimes appear to have problems in the root directory of the root volume of a realm (i.e., /coda/testserver.coda.cs.cmu.edu). I'm not sure if this is a Coda client bug or a kernel bug, quite possibly the latter. This most likely won't be fixed for 7.0 unless it jumps out at me tomorrow. - getpwd() appears to have problems, possibly related to the previous bug if it's unable to recurse to the root. Because Coda doesn't use the global VFS namecache, the __getcwd() system call which is often able to resolve the current directly doesn't work with Coda; the userspace implementation walks to the root looking for the child directory in each parent, which can have problems if stat() and inode numbers are inconsistent, or if there's a broken ".." step. Ditto on this most likely not being fixed for 7.0. Any other problems, especially panics with the backport of the other fixes to RELENG_7, are very much fair game, but having the reports by the end of Tuesday would be extremely helpful. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-fs@FreeBSD.ORG Tue Jan 22 04:02:54 2008 Return-Path: Delivered-To: fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4248516A421; Tue, 22 Jan 2008 04:02:54 +0000 (UTC) (envelope-from jaharkes@cs.cmu.edu) Received: from delft.aura.cs.cmu.edu (unknown [IPv6:2002:8002:ce58::1]) by mx1.freebsd.org (Postfix) with ESMTP id DC04213C43E; Tue, 22 Jan 2008 04:02:53 +0000 (UTC) (envelope-from jaharkes@cs.cmu.edu) Received: from jaharkes by delft.aura.cs.cmu.edu with local (Exim 4.68) (envelope-from ) id 1JHALd-0006G8-3c; Mon, 21 Jan 2008 23:02:53 -0500 Date: Mon, 21 Jan 2008 23:02:52 -0500 From: Jan Harkes To: Robert Watson Message-ID: <20080122040252.GI30266@cs.cmu.edu> References: <20080119165056.E3375@fledge.watson.org> <20080122010003.B29737@fledge.watson.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080122010003.B29737@fledge.watson.org> User-Agent: Mutt/1.5.17 (2007-12-11) Cc: fs@FreeBSD.org, Rune Subject: Re: Various FreeBSD Coda fixes 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, 22 Jan 2008 04:02:54 -0000 On Tue, Jan 22, 2008 at 01:04:31AM +0000, Robert Watson wrote: > I've merged these, and a couple more since then, to RLEENG_7, and will > request an MFC to RELENG_7_0 to include them in the forthcoming FreeBSD > 7.0. It would be very helpful, if you have a 7.x box, if you could > update to the head of RELENG_7 to pick up these fixes, and test with Coda > with them. I will upgrade my vm and test. > - Rune has reported a hang with X11 and Coda, but we haven't yet been able to > track it down much yet -- might not be related to Coda. He does tend to run pretty much everything out of Coda, and is very good at triggering bugs which can be very hard to reproduce in isolation. Wouldn't surprise me if this is somehow a Coda bug he manages to trigger. > - ".." and "." sometimes appear to have problems in the root directory of the > root volume of a realm (i.e., /coda/testserver.coda.cs.cmu.edu). I'm not > sure if this is a Coda client bug or a kernel bug, quite possibly the > latter. This most likely won't be fixed for 7.0 unless it jumps out at me > tomorrow. Known Coda client problem. Across the volume mount we have 2 different objects, the root of the volume and the mountlink object on which is it mounted. If you do a low-level readdir on the parent you see the identifier of the mountlink and not the volume root. So stat('.') in the volume root cannot be found in the readdir('..') information, the only way to match it up right now is to stat() every entry you got back from readdir. > - getpwd() appears to have problems, possibly related to the previous bug if > it's unable to recurse to the root. Because Coda doesn't use the global Correct. I really see this as a Coda client issue, although is has been fixed in the Linux kernel module by peeking in the in-kernel directory cache. Effectively similar to calling stat(2) on all children as long as they are cached, and the components of the path we're looking up are guaranteed to be cached because they are held pinned down by the cwd reference of the process that calls getcwd. Jan From owner-freebsd-fs@FreeBSD.ORG Tue Jan 22 09:34:22 2008 Return-Path: Delivered-To: fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 74D3916A473 for ; Tue, 22 Jan 2008 09:34:22 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id 304BD13C4E1 for ; Tue, 22 Jan 2008 09:34:22 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id DA3934A5D3; Tue, 22 Jan 2008 04:34:21 -0500 (EST) Date: Tue, 22 Jan 2008 09:34:21 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Jan Harkes In-Reply-To: <20080122040252.GI30266@cs.cmu.edu> Message-ID: <20080122092743.J58270@fledge.watson.org> References: <20080119165056.E3375@fledge.watson.org> <20080122010003.B29737@fledge.watson.org> <20080122040252.GI30266@cs.cmu.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: fs@FreeBSD.org, Rune Subject: Re: Various FreeBSD Coda fixes 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, 22 Jan 2008 09:34:22 -0000 On Mon, 21 Jan 2008, Jan Harkes wrote: >> - ".." and "." sometimes appear to have problems in the root directory of the >> root volume of a realm (i.e., /coda/testserver.coda.cs.cmu.edu). I'm not >> sure if this is a Coda client bug or a kernel bug, quite possibly the >> latter. This most likely won't be fixed for 7.0 unless it jumps out at me >> tomorrow. > > Known Coda client problem. Across the volume mount we have 2 different > objects, the root of the volume and the mountlink object on which is it > mounted. If you do a low-level readdir on the parent you see the identifier > of the mountlink and not the volume root. So stat('.') in the volume root > cannot be found in the readdir('..') information, the only way to match it > up right now is to stat() every entry you got back from readdir. Well, there are two problems -- one is the lack of matching inode numbers causing problems for getcwd(), the other is that sometimes stat("..") fails with ENOENT in /coda/testserver.coda.cs.cmu.edu. I was assuming that was a namecache or related bug in the FreeBSD version of the module, and should take a look and see if something similar was fixed in NetBSD. >> - getpwd() appears to have problems, possibly related to the previous bug >> if >> it's unable to recurse to the root. Because Coda doesn't use the global > > Correct. I really see this as a Coda client issue, although is has been > fixed in the Linux kernel module by peeking in the in-kernel directory > cache. Effectively similar to calling stat(2) on all children as long as > they are cached, and the components of the path we're looking up are > guaranteed to be cached because they are held pinned down by the cwd > reference of the process that calls getcwd. It used to be the case that the "inode number" exposed by Coda was a hash of the viceid, which reduced 96 bits (now more) to 32 bits, leading to two problems: (a) that if a vnode spanned two volumes, it had two viceid's representing the historic "mounted on" and "mounted over", and (b) the possibility of colliding inode numbers. Maintaining a database of viceids to inode numbers is undesirable both because of the size and general feasibility of such a database, but have you thought about maintaining a special database of mapped inode numbers for just the volume grafting points? There are quite a lot fewer of them running around so they could perhaps be generated and used specifically. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-fs@FreeBSD.ORG Tue Jan 22 14:51:58 2008 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 61F8C16A41B for ; Tue, 22 Jan 2008 14:51:58 +0000 (UTC) (envelope-from bra@fsn.hu) Received: from people.fsn.hu (people.fsn.hu [195.228.252.137]) by mx1.freebsd.org (Postfix) with ESMTP id 2EF7313C455 for ; Tue, 22 Jan 2008 14:51:57 +0000 (UTC) (envelope-from bra@fsn.hu) Received: from japan.t-online.private (people [192.168.2.4]) by people.fsn.hu (Postfix) with ESMTP id 5A16813C908 for ; Tue, 22 Jan 2008 15:36:09 +0100 (CET) Message-ID: <4795FF59.7010708@fsn.hu> Date: Tue, 22 Jan 2008 15:36:09 +0100 From: Attila Nagy User-Agent: Thunderbird 2.0.0.9 (X11/20071204) MIME-Version: 1.0 To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit Subject: Redundant NFS with ZFS 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, 22 Jan 2008 14:51:58 -0000 Hello, I have some machines running FreeBSD as redundant NFS servers (using CARP). The way they work is the following: - I have a master (content) machine on which I maintain an UFS filesystem image on an UFS - I have this image mounted through md - there are (any) number of NFS servers, one that is the master (from the client PoV) and the others as slaves - everytime I need changes in the content of the image, I make them, then do a mount -o ro -u /nfs and issue an rsync to the NFS (slave) servers, then I switch over the master and do a sync to there too This works wonderfully, although the image distribution is slow and painful (thanks to rsync). With ZFS there is a more simple oppurtunity: make snapshots on the content master and distribute them via zfs send&receive. However there's a little problem: the fsids are not in sync and the clients get stale NFS filehandle errors. This is solved in the current scenario by distributing whole UFS images with their static fsids, but I don't know how it would be possible with ZFS. Currently I see two possibilities: - changing the NFS server, so it can be manually set (like in Linux, where it's possible to give an fsid parameter in exports) - synchronize ZFS fsids across the machines The second would be perfect for me, I just couldn't figure out how could I do this (a cursory glance on the ZFS source didn't result a clean and simple solution). Any ideas on this? (I've seen some discussions on this topic in a ZFS list, but there was no solution, just a little misunderstanding with shared storages and Sun clusters) Thanks, -- Attila Nagy e-mail: Attila.Nagy@fsn.hu Free Software Network (FSN.HU) phone: +3630 306 6758 http://www.fsn.hu/ From owner-freebsd-fs@FreeBSD.ORG Wed Jan 23 13:12:02 2008 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 78DC116A41A for ; Wed, 23 Jan 2008 13:12:02 +0000 (UTC) (envelope-from freebsd-fs@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id 1F6F613C457 for ; Wed, 23 Jan 2008 13:12:01 +0000 (UTC) (envelope-from freebsd-fs@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1JHfOX-0007gm-7N for freebsd-fs@freebsd.org; Wed, 23 Jan 2008 13:11:57 +0000 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 23 Jan 2008 13:11:57 +0000 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 23 Jan 2008 13:11:57 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-fs@freebsd.org From: Ivan Voras Date: Wed, 23 Jan 2008 14:11:50 +0100 Lines: 31 Message-ID: References: <18CC5A4A2AC36D7FF57615EE@ganymede.hub.org> <478AF6BC.8050604@highperformance.net> <20080114142124.Y55696@fledge.watson.org> <20080116085630.GA32361@pappardelle.tekno.chalmers.se> <20080117080359.U51764@fledge.watson.org> <20080118073445.GA30721@pappardelle.tekno.chalmers.se> <20080118095652.GC30721@pappardelle.tekno.chalmers.se> <20080118103952.D18977@fledge.watson.org> <20080118210621.GF7898@cs.cmu.edu> <20080118211556.T46437@fledge.watson.org> <20080119005938.Q53920@fledge.watson.org> <20080121203838.G4194@fledge.watson.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigCCFBA18DB5F6156BCD49BDFA" X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Thunderbird 2.0.0.6 (X11/20071022) In-Reply-To: <20080121203838.G4194@fledge.watson.org> X-Enigmail-Version: 0.95.0 Sender: news Subject: Re: Coda on FreeBSD problem reports? 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, 23 Jan 2008 13:12:02 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigCCFBA18DB5F6156BCD49BDFA Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Robert Watson wrote: > I was looking at the NetBSD Coda parts over the weekend, but it seemed > that most of the bugs in the FreeBSD code were due to gradual rot as VF= S > evolved and our Coda module source didn't remain code up. I see a lot of CODA patches merged to RELENG_7_0 - can you write up a short overview of what is it's current state in FreeBSD - what works and what doesn't? --------------enigCCFBA18DB5F6156BCD49BDFA 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.6 (GNU/Linux) iD8DBQFHlz0WldnAQVacBcgRAs8sAKD23O6VkZ+4p/xfFBJLnMpRyOFtpACfaJZc 5J5MLnEhmX2pJXT9qMRTbEA= =SqpL -----END PGP SIGNATURE----- --------------enigCCFBA18DB5F6156BCD49BDFA-- From owner-freebsd-fs@FreeBSD.ORG Wed Jan 23 23:11:06 2008 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 453CC16A41B for ; Wed, 23 Jan 2008 23:11:06 +0000 (UTC) (envelope-from freebsd-fs@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id 0FC7A13C4EB for ; Wed, 23 Jan 2008 23:11:05 +0000 (UTC) (envelope-from freebsd-fs@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1JHokJ-0008Q0-Bn for freebsd-fs@freebsd.org; Wed, 23 Jan 2008 23:11:03 +0000 Received: from host71-40-static.74-81-b.business.telecomitalia.it ([81.74.40.71]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 23 Jan 2008 23:11:03 +0000 Received: from lapo by host71-40-static.74-81-b.business.telecomitalia.it with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 23 Jan 2008 23:11:03 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-fs@freebsd.org From: Lapo Luchini Date: Thu, 24 Jan 2008 00:10:52 +0100 Lines: 19 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: host71-40-static.74-81-b.business.telecomitalia.it User-Agent: Thunderbird 2.0.0.9 (X11/20071228) X-Enigmail-Version: 0.95.0 OpenPGP: id=C8F252FB Sender: news Subject: can GELI wait for da0 to appear in order to load keys from it? 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, 23 Jan 2008 23:11:06 -0000 Dear Pawel (et al), when GELI is used in 'boot mode' (geli init -b), can it wait for the file system specified in loader.conf to appear? I have a key on a SD card and it gets probed just after GELI complained that "Found no key files in loader.conf for ad4s1d"... I'm trying to load the encrypted devices from loader.conf instead of rc.conf because there is a ZFS-on-root on these, so they must load before root mount is attempted... there's also the problem that that is before fstab is even taken into account, but I (think I) solved that part of the problem using a (single-sector) partition of that SD card to hold the key, so I can use da0s2 as a key without mounting anything (as far as command line "geom attach -p -k /dev/da0s2" goes, it works perfectly; I wonder if it can work before root, though). Or any other idea to achieve the same result? (i.e. having the "as much as possible" on ZFS+GELI) Lapo From owner-freebsd-fs@FreeBSD.ORG Thu Jan 24 11:54:54 2008 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BF44B16A419; Thu, 24 Jan 2008 11:54:54 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id 95A1513C500; Thu, 24 Jan 2008 11:54:54 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 3A13148496; Thu, 24 Jan 2008 06:54:54 -0500 (EST) Date: Thu, 24 Jan 2008 11:54:54 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Ivan Voras In-Reply-To: Message-ID: <20080124115046.O18050@fledge.watson.org> References: <18CC5A4A2AC36D7FF57615EE@ganymede.hub.org> <478AF6BC.8050604@highperformance.net> <20080114142124.Y55696@fledge.watson.org> <20080116085630.GA32361@pappardelle.tekno.chalmers.se> <20080117080359.U51764@fledge.watson.org> <20080118073445.GA30721@pappardelle.tekno.chalmers.se> <20080118095652.GC30721@pappardelle.tekno.chalmers.se> <20080118103952.D18977@fledge.watson.org> <20080118210621.GF7898@cs.cmu.edu> <20080118211556.T46437@fledge.watson.org> <20080119005938.Q53920@fledge.watson.org> <20080121203838.G4194@fledge.watson.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-fs@freebsd.org Subject: Re: Coda on FreeBSD problem reports? 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, 24 Jan 2008 11:54:54 -0000 On Wed, 23 Jan 2008, Ivan Voras wrote: > Robert Watson wrote: > >> I was looking at the NetBSD Coda parts over the weekend, but it seemed that >> most of the bugs in the FreeBSD code were due to gradual rot as VFS evolved >> and our Coda module source didn't remain code up. > > I see a lot of CODA patches merged to RELENG_7_0 - can you write up a short > overview of what is it's current state in FreeBSD - what works and what > doesn't? Previously Coda in 7.0 would likely panic on trivial use. Now it seems to frequently work on non-trivial use. I do not consider the FreeBSD Coda kernel module productionable in its current state in that it was largely useless on 7.0 prior to three or four days ago, which means that it's only had 2-3 days of testing in its more usable state. :-) I'd like to think that a reasonable goal for 7.1 would be to have Coda no less production-worthy than it is on Linux, the primary development platform for Coda, and to make significant progress on resolving the AFS situation (which will be something to write home about). Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-fs@FreeBSD.ORG Thu Jan 24 14:58:41 2008 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 59D9716A418 for ; Thu, 24 Jan 2008 14:58:41 +0000 (UTC) (envelope-from bra@fsn.hu) Received: from people.fsn.hu (people.fsn.hu [195.228.252.137]) by mx1.freebsd.org (Postfix) with ESMTP id BB87313C46A for ; Thu, 24 Jan 2008 14:58:39 +0000 (UTC) (envelope-from bra@fsn.hu) Received: from japan.t-online.private (people [192.168.2.4]) by people.fsn.hu (Postfix) with ESMTP id ABDCC14034D; Thu, 24 Jan 2008 15:58:06 +0100 (CET) Message-ID: <4798A77E.1030308@fsn.hu> Date: Thu, 24 Jan 2008 15:58:06 +0100 From: Attila Nagy User-Agent: Thunderbird 2.0.0.9 (X11/20071204) MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <200801241348.m0ODmKZu057100@repoman.freebsd.org> In-Reply-To: <200801241348.m0ODmKZu057100@repoman.freebsd.org> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit Cc: Ruslan Ermilov Subject: Re: cvs commit: src/share/man/man4 sched_4bsd.4 sched_ule.4 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, 24 Jan 2008 14:58:41 -0000 On 01/24/08 14:48, Ruslan Ermilov wrote: > ru 2008-01-24 13:48:20 UTC > > FreeBSD src repository > > Modified files: > share/man/man4 sched_4bsd.4 sched_ule.4 > Log: > - sched_4bsd is no longer a default system scheduler on some > architectures, so call it "traditional" instead. > > - sched_ule is no longer buggy or experimental (according to > rev. 1.7 of sched_ule(4)), so don't call it experimental > (reported by a user on stable@). > I've tried ULE+ZFS on two machines recently (on 7-STABLE). One desktop and one server. Both of them froze (for example on the server an already running top kept running, but if I exited from that, I couldn't do anything anymore. On the desktop, the window manager stops (no mouse, no keyboard), but the clock applet remained active). I thought it's ZFS, because all of these popped out while there were increased disk activity, but on monday I've switched both of them to SCHED_4BSD and since that no freeze happened. Anyone out there with ULE+ZFS (I ran them on i386 with 1 GB of RAM, SMP systems)? (BTW, ULE was a little bit sluggish while playing music and overall) -- Attila Nagy e-mail: Attila.Nagy@fsn.hu Free Software Network (FSN.HU) phone: +3630 306 6758 http://www.fsn.hu/ From owner-freebsd-fs@FreeBSD.ORG Thu Jan 24 15:57:45 2008 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6848F16A419; Thu, 24 Jan 2008 15:57:45 +0000 (UTC) (envelope-from gary.jennejohn@freenet.de) Received: from mout2.freenet.de (mout2.freenet.de [IPv6:2001:748:100:40::2:4]) by mx1.freebsd.org (Postfix) with ESMTP id CB50313C45D; Thu, 24 Jan 2008 15:57:44 +0000 (UTC) (envelope-from gary.jennejohn@freenet.de) Received: from [195.4.92.15] (helo=5.mx.freenet.de) by mout2.freenet.de with esmtpa (Exim 4.68) (envelope-from ) id 1JI4SV-0001BZ-SU; Thu, 24 Jan 2008 16:57:43 +0100 Received: from x0202.x.pppool.de ([89.59.2.2]:54392 helo=peedub.jennejohn.org) by 5.mx.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port 25) (Exim 4.68 #9) id 1JI4SV-0006r3-Jt; Thu, 24 Jan 2008 16:57:43 +0100 Date: Thu, 24 Jan 2008 16:57:42 +0100 From: Gary Jennejohn To: Attila Nagy Message-ID: <20080124165742.14696477@peedub.jennejohn.org> In-Reply-To: <4798A77E.1030308@fsn.hu> References: <200801241348.m0ODmKZu057100@repoman.freebsd.org> <4798A77E.1030308@fsn.hu> X-Mailer: Claws Mail 3.0.2 (GTK+ 2.10.14; amd64-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org, Ruslan Ermilov Subject: Re: cvs commit: src/share/man/man4 sched_4bsd.4 sched_ule.4 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gary.jennejohn@freenet.de List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jan 2008 15:57:45 -0000 On Thu, 24 Jan 2008 15:58:06 +0100 Attila Nagy wrote: > On 01/24/08 14:48, Ruslan Ermilov wrote: > > ru 2008-01-24 13:48:20 UTC > > > > FreeBSD src repository > > > > Modified files: > > share/man/man4 sched_4bsd.4 sched_ule.4 > > Log: > > - sched_4bsd is no longer a default system scheduler on some > > architectures, so call it "traditional" instead. > > > > - sched_ule is no longer buggy or experimental (according to > > rev. 1.7 of sched_ule(4)), so don't call it experimental > > (reported by a user on stable@). > > > I've tried ULE+ZFS on two machines recently (on 7-STABLE). One desktop > and one server. Both of them froze (for example on the server an already > running top kept running, but if I exited from that, I couldn't do > anything anymore. On the desktop, the window manager stops (no mouse, no > keyboard), but the clock applet remained active). > I thought it's ZFS, because all of these popped out while there were > increased disk activity, but on monday I've switched both of them to > SCHED_4BSD and since that no freeze happened. > > Anyone out there with ULE+ZFS (I ran them on i386 with 1 GB of RAM, SMP > systems)? > I'm running ULE+ZFS on a system with AMD64 X2 (AM2) and 3GB of memory with kmem_size cranked up to 1GB (64-bit installation). I rarely see hangs when accessing a ZFS file system. As an example I was watching a movie in a ZFS pool yesterday with vlc when it just stopped. top showed that vlc was waiting on umtxn for a mutex and it never left that state. I could kill it, however. After that I was able to watch a movie from the same ZFS pool without a problem. Since I had X running I couldn't easily get into ddb. I've also seen other apparently ZFS-related hangs in the past, but I can't remember the details any more. I do remember that one hang was so bad that I had to reset the box to recover. --- Gary Jennejohn