From owner-freebsd-fs@FreeBSD.ORG Sun Mar 25 07:33:49 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4B5FA16A401 for ; Sun, 25 Mar 2007 07:33:49 +0000 (UTC) (envelope-from duane@dwlabs.ca) Received: from smtpout.eastlink.ca (smtpout.eastlink.ca [24.222.0.30]) by mx1.freebsd.org (Postfix) with ESMTP id 1218813C46E for ; Sun, 25 Mar 2007 07:33:48 +0000 (UTC) (envelope-from duane@dwlabs.ca) Received: from ip02.eastlink.ca ([24.222.10.10]) by mta01.eastlink.ca (Sun Java System Messaging Server 6.2-4.03 (built Sep 22 2005)) with ESMTP id <0JFG00FIX69W8FM1@mta01.eastlink.ca> for freebsd-fs@freebsd.org; Sun, 25 Mar 2007 04:03:32 -0300 (ADT) Received: from blk-224-199-230.eastlink.ca (HELO dwpc.dwlabs.ca) ([24.224.199.230]) by ip02.eastlink.ca with ESMTP; Sun, 25 Mar 2007 04:03:41 -0300 Received: from dwpc.dwlabs.ca (www.dwlabs.ca [192.168.0.10]) by dwpc.dwlabs.ca (8.13.8/8.13.8) with ESMTP id l2P6x8Tc096109; Sun, 25 Mar 2007 03:59:14 -0300 (ADT envelope-from duane@dwpc.dwlabs.ca) Received: (from duane@localhost) by dwpc.dwlabs.ca (8.13.8/8.13.8/Submit) id l2P6x70D096108; Sun, 25 Mar 2007 03:59:07 -0300 (ADT envelope-from duane) Date: Sun, 25 Mar 2007 03:59:07 -0300 From: Duane Whitty In-reply-to: <55882.43410.qm@web63013.mail.re1.yahoo.com> To: Gore Jarold Message-id: <20070325065907.GB84676@dwpc.dwlabs.ca> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ao8CAN27BUYY4MfmdGdsb2JhbACPYQE X-IronPort-AV: i="4.14,325,1170648000"; d="scan'208"; a="132219846:sNHT28991907" X-Virus-Scanned: ClamAV 0.88.6/2921/Sat Mar 24 09:52:12 2007 on dwpc.dwlabs.ca X-Virus-Status: Clean X-Spam-Checker-Version: SpamAssassin 3.1.4 (2006-07-25) on dwpc.dwlabs.ca References: <03bf01c76c1d$b4a74160$b3db87d4@multiplay.co.uk> <55882.43410.qm@web63013.mail.re1.yahoo.com> User-Agent: Mutt/1.4.2.2i X-Spam-Status: No, score=-2.1 required=5.0 tests=AWL,BAYES_00, UNPARSEABLE_RELAY autolearn=ham version=3.1.4 Cc: freebsd-fs@freebsd.org Subject: Re: phantom quota usage for user with no files ... ? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-fs@freebsd.org List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Mar 2007 07:33:49 -0000 On Saturday, 24 March 2007 at 9:16:12 -0700, Gore Jarold wrote: > > Thanks, that is very helpful. > > Steven Hartland wrote: Files which where open at the time and hence still have references > similar to how deleted files still take up space until the last > handle is closed. > > > Can you tell me, how do I: > > a) see those handles (ps auxw|grep USERNAME showed nothing) > > b) remove/clear them ? > > > (I _do_ have lsof installed, but lsof|grep USERNAME also showed nothing...) > > > --------------------------------- > Sucker-punch spam with award-winning protection. > Try the free Yahoo! Mail Beta. > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" Try fstat(1) fstat -u username --Duane Whitty From owner-freebsd-fs@FreeBSD.ORG Mon Mar 26 11:11:57 2007 Return-Path: X-Original-To: freebsd-fs@FreeBSD.ORG Delivered-To: freebsd-fs@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9434016A404 for ; Mon, 26 Mar 2007 11:11:57 +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 1D91D13C45A for ; Mon, 26 Mar 2007 11:11:56 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (wfgjaj@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id l2QBBort009057; Mon, 26 Mar 2007 13:11:55 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id l2QBBo7L009056; Mon, 26 Mar 2007 13:11:50 +0200 (CEST) (envelope-from olli) Date: Mon, 26 Mar 2007 13:11:50 +0200 (CEST) Message-Id: <200703261111.l2QBBo7L009056@lurza.secnetix.de> From: Oliver Fromme To: freebsd-fs@FreeBSD.ORG, Steven Hartland , gore_jarold@yahoo.com In-Reply-To: <55882.43410.qm@web63013.mail.re1.yahoo.com> X-Newsgroups: list.freebsd-fs User-Agent: tin/1.8.2-20060425 ("Shillay") (UNIX) (FreeBSD/4.11-STABLE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Mon, 26 Mar 2007 13:11:56 +0200 (CEST) Cc: Subject: Re: phantom quota usage for user with no files ... ? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-fs@FreeBSD.ORG, Steven Hartland , gore_jarold@yahoo.com List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Mar 2007 11:11:57 -0000 Gore Jarold wrote: > Steven Hartland wrote: > > Files which where open at the time and hence still have references > > similar to how deleted files still take up space until the last > > handle is closed. > > Can you tell me, how do I: > > a) see those handles (ps auxw|grep USERNAME showed nothing) You can easily use lsof for that. To list deleted open files with link count 0, use this command: lsof +L1 > b) remove/clear them ? That depends on the programs that keep the files open. Some programs close the file handles when you send them a SIGHUP signal (i.e. "kill -HUP "). The PIDs are displayed by the lsof command above. If that doesn't help, terminate the processes forcibly, if necessary. When a process terminates, all of its file desciptors are closed automatically. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd We're sysadmins. To us, data is a protocol-overhead. From owner-freebsd-fs@FreeBSD.ORG Tue Mar 27 01:42:11 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0BDE116A400 for ; Tue, 27 Mar 2007 01:42:11 +0000 (UTC) (envelope-from freebsd@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.freebsd.org (Postfix) with ESMTP id C742113C44C for ; Tue, 27 Mar 2007 01:42:10 +0000 (UTC) (envelope-from freebsd@hub.org) Received: from localhost (unknown [200.46.204.182]) by hub.org (Postfix) with ESMTP id 7BA1885C8DF for ; Mon, 26 Mar 2007 22:20:02 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-new, port 10024) with ESMTP id 66969-01 for ; Mon, 26 Mar 2007 22:20:02 -0300 (ADT) Received: from ganymede.hub.org (blk-89-241-126.eastlink.ca [24.89.241.126]) by hub.org (Postfix) with ESMTP id 77CF285C8C4 for ; Mon, 26 Mar 2007 22:20:01 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id D650A34A88 for ; Mon, 26 Mar 2007 22:20:11 -0300 (ADT) Date: Mon, 26 Mar 2007 22:20:11 -0300 From: "Marc G. Fournier" To: freebsd-fs@freebsd.org Message-ID: <6F52125FD798AC9E4A28A778@ganymede.hub.org> X-Mailer: Mulberry/4.0.7 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: TDFS ... or other distributed file system technologies for FreeBSD? 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, 27 Mar 2007 01:42:11 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I posted this on -questions the other day, and got a pointer to: http://tdfs.sourceforge.net/ The developer is hoping to get his project accepted into SoC so that he can continue with it, but I'm curious as to whether or not: a. anyone is using his current code at all? b. are there any other similar technologies available for FreeBSD? I've heard of ggate/gmirror, but the big thing with tdfs that I'm looking for is: - -m : Specify local directory that will be distributed. I don't want to do the *whole* file system, only certain directories within a file system ... Thanks ... - ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFGCHFL4QvfyHIvDvMRApCaAKDOKTCZwyt+4WagrjmaRxBk5RWojACdHLi1 yeETqfZhjHNLP8ddW/wOO0k= =LBLo -----END PGP SIGNATURE----- From owner-freebsd-fs@FreeBSD.ORG Tue Mar 27 08:56:19 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 25B0E16A40D for ; Tue, 27 Mar 2007 08:56:19 +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 D906A13C4CE for ; Tue, 27 Mar 2007 08:56:18 +0000 (UTC) (envelope-from freebsd-fs@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1HW7TQ-0001tf-QJ for freebsd-fs@freebsd.org; Tue, 27 Mar 2007 10:56:12 +0200 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 ; Tue, 27 Mar 2007 10:56:12 +0200 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 27 Mar 2007 10:56:12 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-fs@freebsd.org From: Ivan Voras Date: Tue, 27 Mar 2007 10:55:57 +0200 Lines: 12 Message-ID: References: <6F52125FD798AC9E4A28A778@ganymede.hub.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Thunderbird 1.5.0.10 (X11/20060911) In-Reply-To: <6F52125FD798AC9E4A28A778@ganymede.hub.org> Sender: news Subject: Re: TDFS ... or other distributed file system technologies for FreeBSD? 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, 27 Mar 2007 08:56:19 -0000 Marc G. Fournier wrote: > a. anyone is using his current code at all? Judging by the feedback I got (i.e. practically none), I doubt anyone's using it. > b. are there any other similar technologies available for FreeBSD? Another proposal is for something similar to it but in kernel instead of FUSE. Even if it passes, it won't be done soon as it's much more complicated and sensitive. From owner-freebsd-fs@FreeBSD.ORG Tue Mar 27 11:02:27 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id F0CA116A404 for ; Tue, 27 Mar 2007 11:02:27 +0000 (UTC) (envelope-from cedric@decemplex.net) Received: from mail.decemplex.net (mail.decemplex.net [80.237.247.202]) by mx1.freebsd.org (Postfix) with ESMTP id A69C813C487 for ; Tue, 27 Mar 2007 11:02:27 +0000 (UTC) (envelope-from cedric@decemplex.net) Received: from localhost (mail.decemplex.net [80.237.247.202]) by mail.decemplex.net (Postfix) with ESMTP id B6B1E7D1F5C; Tue, 27 Mar 2007 13:02:26 +0200 (CEST) X-Virus-Scanned: amavisd-new at decemplex.net Received: from mail.decemplex.net ([80.237.247.202]) by localhost (mail.decemplex.net [80.237.247.202]) (amavisd-new, port 10024) with LMTP id XCGt1xMOd33T; Tue, 27 Mar 2007 13:02:26 +0200 (CEST) Received: from luna.decemplex.loc (119-186-112-217.dyn.adsl.belcenter.be [217.112.186.119]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.decemplex.net (Postfix) with ESMTP id 957EF7D1F31; Tue, 27 Mar 2007 13:02:25 +0200 (CEST) Date: Tue, 27 Mar 2007 13:02:08 +0200 From: =?ISO-8859-1?Q?C=E9dric?= Jonas To: Julian Elischer Message-ID: <20070327130208.400a0310@luna> In-Reply-To: <4601763E.2050309@elischer.org> References: <20070321175253.54b4b1ed@ganymed> <4601763E.2050309@elischer.org> X-Mailer: Claws Mail 2.8.1 (GTK+ 2.10.11; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: multipart/signed; boundary=Sig_GN.zMBXLIIhHajQT7lI_KUw; protocol="application/pgp-signature"; micalg=PGP-SHA1 Cc: freebsd-fs@freebsd.org, Robert Watson Subject: Re: ACL's doesn't work with SUIDDIR 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, 27 Mar 2007 11:02:28 -0000 --Sig_GN.zMBXLIIhHajQT7lI_KUw Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Wed, 21 Mar 2007 11:15:26 -0700 Julian Elischer wrote: > C=E9dric Jonas wrote: > > Hi all, > >=20 > >=20 > > thanks to correct me. > >=20 > > PS: Please CC me, I'm not on the list. >=20 > SUIDDIR is probably mot widely used so it may not have ever=20 > been tested with ACL (also not widely used) is is possible=20 > that you are the first person to have ever tried this combination :-) >=20 > I suggest that the ACL guys take a look as they i think have some > shared code with other OS's which probably don't have SUIDDIR, which > is a FreeBSD only option. Typical for me :-( But however, it seems that I'm not the very first one who tries this. I found this in the freebsd-stable archive from February 2005: http://lists.freebsd.org/pipermail/freebsd-stable/2005-February/011786.html http://lists.freebsd.org/pipermail/freebsd-stable/2005-February/011797.html It it can help... I also filled in a PR: misc/110915 Let me know if you need further informations. --=20 C=E9dric Jonas cedric@decemplex.net Mobile Phone: (32-494) 08 92 64 GPG ID: 30CCFE8D GPG Key: http://box.decemplex.net/~cedric/cedric.key.asc GPG Fingerprint: CF03 E1FD 9428 1B6B E971 B107 9044 AA99 30CC FE8D Jabber-ID: cedric@decemplex.net --Sig_GN.zMBXLIIhHajQT7lI_KUw Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFGCPmxkESqmTDM/o0RAiYaAJsEEE/mg0XhKrHkInStMhSMP66ZrwCfdOeQ j6DNQ9s7AkaenbErHGOea5o= =EuXI -----END PGP SIGNATURE----- --Sig_GN.zMBXLIIhHajQT7lI_KUw-- From owner-freebsd-fs@FreeBSD.ORG Tue Mar 27 14:57:30 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0B5A016A400 for ; Tue, 27 Mar 2007 14:57:30 +0000 (UTC) (envelope-from lists@stringsutils.com) Received: from zoraida.natserv.net (p65-147.acedsl.com [66.114.65.147]) by mx1.freebsd.org (Postfix) with ESMTP id C65FC13C468 for ; Tue, 27 Mar 2007 14:57:29 +0000 (UTC) (envelope-from lists@stringsutils.com) Received: from zoraida.natserv.net (localhost.natserv.net [127.0.0.1]) by zoraida.natserv.net (Postfix) with ESMTP id 6C8BBC31A for ; Tue, 27 Mar 2007 10:25:37 -0400 (EDT) Received: by zoraida.natserv.net (Postfix, from userid 58) id 31E00C317; Tue, 27 Mar 2007 10:25:37 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on zoraida.natserv.net X-Spam-Level: X-Spam-Status: No, score=1.0 required=4.0 tests=RCVD_IN_FIVETENSRC,SPF_PASS autolearn=disabled version=3.1.7 X-Spam-Report: * -0.0 SPF_PASS SPF: sender matches SPF record * 1.0 RCVD_IN_FIVETENSRC RBL: Received via a relay in Five Ten block list * [66.114.65.147 listed in blackholes.five-ten-sg.com] Received: from zoraida.natserv.net (zoraida.natserv.net [66.114.65.147]) by zoraida.natserv.net (Postfix) with ESMTP id 3101EC2AF; Tue, 27 Mar 2007 10:25:31 -0400 (EDT) References: <6F52125FD798AC9E4A28A778@ganymede.hub.org> Message-ID: X-Mailer: http://www.courier-mta.org/cone/ From: Francisco Reyes To: Ivan Voras Date: Tue, 27 Mar 2007 10:25:30 -0400 Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="US-ASCII" Content-Disposition: inline Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-fs@freebsd.org Subject: Re: TDFS ... or other distributed file system technologies for FreeBSD? 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, 27 Mar 2007 14:57:30 -0000 Ivan Voras writes: >> a. anyone is using his current code at all? > > Judging by the feedback I got (i.e. practically none), I doubt anyone's > using it. Perhaps not many people are aware of it. Is there a new version planned? I see the last revision was on Jan 2006. > > b. are there any other similar technologies available for FreeBSD? > > Another proposal is for something similar to it but in kernel instead of > FUSE. Even if it passes, it won't be done soon as it's much more > complicated and sensitive. Do you have a URL for that other project? From owner-freebsd-fs@FreeBSD.ORG Tue Mar 27 15:46:30 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 822C216A402 for ; Tue, 27 Mar 2007 15:46:30 +0000 (UTC) (envelope-from freebsd@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.freebsd.org (Postfix) with ESMTP id 48E8813C46C for ; Tue, 27 Mar 2007 15:46:30 +0000 (UTC) (envelope-from freebsd@hub.org) Received: from localhost (unknown [200.46.204.182]) by hub.org (Postfix) with ESMTP id 11DD185C8F8; Tue, 27 Mar 2007 12:46:22 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-new, port 10024) with ESMTP id 01377-05; Tue, 27 Mar 2007 12:46:21 -0300 (ADT) Received: from ganymede.hub.org (blk-89-241-126.eastlink.ca [24.89.241.126]) by hub.org (Postfix) with ESMTP id 1DBD985C8C5; Tue, 27 Mar 2007 12:46:09 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 8F43E36491; Tue, 27 Mar 2007 12:46:14 -0300 (ADT) Date: Tue, 27 Mar 2007 12:46:13 -0300 From: "Marc G. Fournier" To: Ivan Voras , freebsd-fs@freebsd.org Message-ID: <4746DA006C148BC0FF1241C6@ganymede.hub.org> X-Mailer: Mulberry/4.0.7 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: Subject: Re: TDFS ... or other distributed file system technologies for FreeBSD? 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, 27 Mar 2007 15:46:30 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 - --On Tuesday, March 27, 2007 10:55:57 +0200 Ivan Voras wrote: > Another proposal is for something similar to it but in kernel instead of > FUSE. Even if it passes, it won't be done soon as it's much more complicated > and sensitive. Just curious, but what is the difference between FUSE and 'in kernel'? Reading the 'Performance' section on the web site, will it cut down the current 7 'steps' down to 3, or somewhere in between? Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFGCTxG4QvfyHIvDvMRAm2MAJ9WtTqudxUt3hljcpBEHStz6ENv8ACfQFK/ MBBiJ97hbbRgbehy2tw09nY= =11cE -----END PGP SIGNATURE----- From owner-freebsd-fs@FreeBSD.ORG Tue Mar 27 15:57:06 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E616716A406 for ; Tue, 27 Mar 2007 15:57: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 A1E2013C4C4 for ; Tue, 27 Mar 2007 15:57:06 +0000 (UTC) (envelope-from freebsd-fs@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1HWE2O-0007pD-Rq for freebsd-fs@freebsd.org; Tue, 27 Mar 2007 17:56:44 +0200 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 ; Tue, 27 Mar 2007 17:56:44 +0200 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 27 Mar 2007 17:56:44 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-fs@freebsd.org From: Ivan Voras Date: Tue, 27 Mar 2007 17:56:32 +0200 Lines: 32 Message-ID: References: <4746DA006C148BC0FF1241C6@ganymede.hub.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig35E6A0FD67800158D419E6E4" X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Thunderbird 1.5.0.10 (X11/20060911) In-Reply-To: <4746DA006C148BC0FF1241C6@ganymede.hub.org> X-Enigmail-Version: 0.94.2.0 Sender: news Subject: Re: TDFS ... or other distributed file system technologies for FreeBSD? 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, 27 Mar 2007 15:57:07 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig35E6A0FD67800158D419E6E4 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Marc G. Fournier wrote: > Just curious, but what is the difference between FUSE and 'in kernel'? = Reading=20 > the 'Performance' section on the web site, will it cut down the current= 7=20 > 'steps' down to 3, or somewhere in between? If you mean context switches then yes, down to something like a normal=20 file system, 2 or 3. --------------enig35E6A0FD67800158D419E6E4 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.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFGCT6wldnAQVacBcgRAn1IAKCcpCJZGF/g1UiCae1qjFtnTqzauQCgw76a e5VcOz+KdrjoQn1Fi9BxpLU= =BSgu -----END PGP SIGNATURE----- --------------enig35E6A0FD67800158D419E6E4-- From owner-freebsd-fs@FreeBSD.ORG Tue Mar 27 17:51:01 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2A0EE16A403 for ; Tue, 27 Mar 2007 17:51:01 +0000 (UTC) (envelope-from freebsd@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.freebsd.org (Postfix) with ESMTP id E5DDB13C4D5 for ; Tue, 27 Mar 2007 17:51:00 +0000 (UTC) (envelope-from freebsd@hub.org) Received: from localhost (unknown [200.46.204.187]) by hub.org (Postfix) with ESMTP id 4AFFE85C8FD; Tue, 27 Mar 2007 14:50:53 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-new, port 10024) with ESMTP id 58733-08; Tue, 27 Mar 2007 14:50:58 -0300 (ADT) Received: from ganymede.hub.org (blk-89-241-126.eastlink.ca [24.89.241.126]) by hub.org (Postfix) with ESMTP id D544885C8E8; Tue, 27 Mar 2007 14:50:52 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id AA56E35D91; Tue, 27 Mar 2007 14:51:00 -0300 (ADT) Date: Tue, 27 Mar 2007 14:51:00 -0300 From: "Marc G. Fournier" To: Ivan Voras , freebsd-fs@freebsd.org Message-ID: <45CCECCB7ECB612F504211F3@ganymede.hub.org> In-Reply-To: References: <4746DA006C148BC0FF1241C6@ganymede.hub.org> X-Mailer: Mulberry/4.0.7 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: Subject: Re: TDFS ... or other distributed file system technologies for FreeBSD? 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, 27 Mar 2007 17:51:01 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 - --On Tuesday, March 27, 2007 17:56:32 +0200 Ivan Voras wrote: > Marc G. Fournier wrote: > >> Just curious, but what is the difference between FUSE and 'in kernel'? >> Reading the 'Performance' section on the web site, will it cut down the >> current 7 'steps' down to 3, or somewhere in between? > > If you mean context switches then yes, down to something like a normal file > system, 2 or 3. 'k ... now, you have a 'proof-of-concept' already, using FUSE ... how much more would be involved in the kernel module? I'm just wondering if it would be time better spent polishing off the FUSE implementation and pushing that for now, get ppl deploying it, testing it, etc ... and then work on the 'performance enhanced kernel module'? Then again, from the other side of the coin ... what are the chances that a kernel module would get into the main stream distribution vs the FUSE module? As a stop-gap, have you considered submitting a TDFS port, to give it a bit more profile? - ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFGCVmE4QvfyHIvDvMRAuxIAKDjuoBu82XojyBkZXFJeUGvYoW1WQCgpNgW AxBEFdET1WAZfl2t3WxFa20= =lQzV -----END PGP SIGNATURE----- From owner-freebsd-fs@FreeBSD.ORG Tue Mar 27 18:11:01 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9F78616A404 for ; Tue, 27 Mar 2007 18:11:01 +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 2D18C13C487 for ; Tue, 27 Mar 2007 18:11:01 +0000 (UTC) (envelope-from freebsd-fs@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1HWG83-00030l-3e for freebsd-fs@freebsd.org; Tue, 27 Mar 2007 20:10:43 +0200 Received: from 83-131-174-33.adsl.net.t-com.hr ([83.131.174.33]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 27 Mar 2007 20:10:43 +0200 Received: from ivoras by 83-131-174-33.adsl.net.t-com.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 27 Mar 2007 20:10:43 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-fs@freebsd.org From: Ivan Voras Date: Tue, 27 Mar 2007 20:10:05 +0200 Lines: 58 Message-ID: References: <4746DA006C148BC0FF1241C6@ganymede.hub.org> <45CCECCB7ECB612F504211F3@ganymede.hub.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig28E7029D3A88E3EFA082ACAC" X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 83-131-174-33.adsl.net.t-com.hr User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) In-Reply-To: <45CCECCB7ECB612F504211F3@ganymede.hub.org> X-Enigmail-Version: 0.94.1.2 Sender: news Subject: Re: TDFS ... or other distributed file system technologies for FreeBSD? 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, 27 Mar 2007 18:11:01 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig28E7029D3A88E3EFA082ACAC Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Marc G. Fournier wrote: > 'k ... now, you have a 'proof-of-concept' already, using FUSE ... how m= uch more=20 > would be involved in the kernel module? Much more. Currently, I know only the very basics of the VFS system. > I'm just wondering if it would be time better spent polishing off the F= USE=20 > implementation and pushing that for now, get ppl deploying it, testing = it, etc=20 > ... and then work on the 'performance enhanced kernel module'? If time to deployment is in question, TDFS is the way to go, and this would be what I prefer. Another idea of mine for this is that maybe they could be made compatible in the network protocol... lots of ideas, little time. > Then again, from the other side of the coin ... what are the chances th= at a=20 > kernel module would get into the main stream distribution vs the FUSE m= odule? Since FUSE is (L)GPL'ed, chances of getting it into base are slim. Then there's the question of who would be responsible for it, since the developer of the FUSE BSD module was also a SoC student and I don't know if he's interested in maintaining it that way - I'll go ask him. > As a stop-gap, have you considered submitting a TDFS port, to give it a= bit=20 > more profile? That is a good idea, I'll try to do it soon. (though it's not complicated to compile & try it by hand). --------------enig28E7029D3A88E3EFA082ACAC 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.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGCV39ldnAQVacBcgRAuLcAJ4iQMc1jiOrZFpE3dJ9IpTm0UAq7QCdG54V 0UdLCuj04MRxcj00wpBmCE4= =TizQ -----END PGP SIGNATURE----- --------------enig28E7029D3A88E3EFA082ACAC-- From owner-freebsd-fs@FreeBSD.ORG Tue Mar 27 23:42:18 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9BE5016A402 for ; Tue, 27 Mar 2007 23:42:18 +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 591DF13C469 for ; Tue, 27 Mar 2007 23:42:18 +0000 (UTC) (envelope-from freebsd-fs@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1HWLIp-0001TH-1T for freebsd-fs@freebsd.org; Wed, 28 Mar 2007 01:42:11 +0200 Received: from 83-131-174-33.adsl.net.t-com.hr ([83.131.174.33]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 28 Mar 2007 01:42:11 +0200 Received: from ivoras by 83-131-174-33.adsl.net.t-com.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 28 Mar 2007 01:42:11 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-fs@freebsd.org From: Ivan Voras Date: Wed, 28 Mar 2007 01:42:02 +0200 Lines: 37 Message-ID: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigC1CEE51A83E1EC8CD91ACF76" X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 83-131-174-33.adsl.net.t-com.hr User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) X-Enigmail-Version: 0.94.1.2 Sender: news Subject: gvirstor & UFS 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, 27 Mar 2007 23:42:18 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigC1CEE51A83E1EC8CD91ACF76 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I'm having trouble recovering from "ENOSPC" situation in gvirstor - when there's enough space on the virtual device, but not enough physical space. No matter what I return to the upper layers (UFS), including EIO, it seems to keep on retrying, spitting enormous amounts of messages to the kernel log in g_vfs_done (and during this the console is stuck). This is the same problems reported by testers some time ago. Maybe the solution is as simple as sticking a check for ENOSPC somewhere in UFS code to make it a special case, but I doubt it's that simple. The required behaviour is to, if this condition is reached, drop the current IO request (returning appropriate errno to the application) and stop retrying (or at least ignore further error messages) until the condition is cleared. Any suggestions? --------------enigC1CEE51A83E1EC8CD91ACF76 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.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGCavKldnAQVacBcgRAqScAKComZ5PWje39yVP7j4OLL+Kjr1vzgCgkaRE jIiann3K4V3ugbw8jyH0Ngo= =ZSzl -----END PGP SIGNATURE----- --------------enigC1CEE51A83E1EC8CD91ACF76-- From owner-freebsd-fs@FreeBSD.ORG Wed Mar 28 01:38:50 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 334D616A4D5 for ; Wed, 28 Mar 2007 01:38:50 +0000 (UTC) (envelope-from bde@zeta.org.au) Received: from mailout2.pacific.net.au (mailout2-3.pacific.net.au [61.8.2.226]) by mx1.freebsd.org (Postfix) with ESMTP id A6EF213C46C for ; Wed, 28 Mar 2007 01:38:49 +0000 (UTC) (envelope-from bde@zeta.org.au) Received: from mailproxy2.pacific.net.au (mailproxy2.pacific.net.au [61.8.2.163]) by mailout2.pacific.net.au (Postfix) with ESMTP id 991E410B298; Wed, 28 Mar 2007 11:38:43 +1000 (EST) Received: from besplex.bde.org (katana.zip.com.au [61.8.7.246]) by mailproxy2.pacific.net.au (Postfix) with ESMTP id A488B27429; Wed, 28 Mar 2007 11:38:46 +1000 (EST) Date: Wed, 28 Mar 2007 11:38:44 +1000 (EST) From: Bruce Evans X-X-Sender: bde@besplex.bde.org To: Ivan Voras In-Reply-To: Message-ID: <20070328100536.S6916@besplex.bde.org> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-fs@freebsd.org Subject: Re: gvirstor & UFS 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, 28 Mar 2007 01:38:50 -0000 On Wed, 28 Mar 2007, Ivan Voras wrote: > I'm having trouble recovering from "ENOSPC" situation in gvirstor - when > there's enough space on the virtual device, but not enough physical > space. No matter what I return to the upper layers (UFS), including EIO, > it seems to keep on retrying, spitting enormous amounts of messages to > the kernel log in g_vfs_done (and during this the console is stuck). > This is the same problems reported by testers some time ago. > > Maybe the solution is as simple as sticking a check for ENOSPC somewhere > in UFS code to make it a special case, but I doubt it's that simple. The > required behaviour is to, if this condition is reached, drop the current > IO request (returning appropriate errno to the application) and stop > retrying (or at least ignore further error messages) until the condition > is cleared. The following old patch may help. vfs retries too hard after write errors. Retrying after EIO is bad enough (since most parts of the kernel still expect the old treatment of not retrying), but retrying after a non-recoverable error is just a bug. %%% Index: vfs_bio.c =================================================================== RCS file: /home/ncvs/src/sys/kern/vfs_bio.c,v retrieving revision 1.436 diff -u -2 -r1.436 vfs_bio.c --- vfs_bio.c 17 Jun 2004 17:16:49 -0000 1.436 +++ vfs_bio.c 17 Apr 2005 05:00:21 -0000 @@ -1222,19 +1312,16 @@ s = splbio(); - if (bp->b_iocmd == BIO_WRITE && - (bp->b_ioflags & BIO_ERROR) && - !(bp->b_flags & B_INVAL)) { + if (bp->b_iocmd == BIO_WRITE && (bp->b_ioflags & BIO_ERROR) && + (bp->b_flags & B_INVAL) == 0 && + (bp->b_error == EIO || bp->b_error == 0)) { /* * Failed write, redirty. Must clear BIO_ERROR to prevent - * pages from being scrapped. If B_INVAL is set then - * this case is not run and the next case is run to - * destroy the buffer. B_INVAL can occur if the buffer - * is outside the range supported by the underlying device. + * pages from being scrapped. */ bp->b_ioflags &= ~BIO_ERROR; bdirty(bp); } else if ((bp->b_flags & (B_NOCACHE | B_INVAL)) || - (bp->b_ioflags & BIO_ERROR) || - bp->b_iocmd == BIO_DELETE || (bp->b_bufsize <= 0)) { + bp->b_ioflags & BIO_ERROR || + bp->b_iocmd == BIO_DELETE || bp->b_bufsize <= 0) { /* * Either a failed I/O or we were asked to free or not %%% The main point here is to only redirty if the error is EIO. Other changes: - also redirty if the error is 0 (but BIO_ERROR is set). This case shouldn't happen, but if it does then there is no way to determine the error type, so play safe and retry. - fix some style bugs. - remove the comments about B_INVAL handling. This is probably wrong. However, at least with the check of b_error, the special handling of B_INVAL is probably unnecessary -- the code that set B_INVAL can just set b_error to something like EINVAL to avoid the redirtying, and this might already happen. Lower layers could also avoid the redirtying by setting B_INVAL, but I think they mostly aren't at a level that can know when to do this. I think B_INVAL is set mainly by nfs, and nfs can know when to do this better than most places because all its layers are combined. This patch at least used to help in at least one case, where an error is returned for writes beyond EOF in the case of non-virtual disks. Old versions of FreeBSD return the bogus errno EINVAL for reads and writes strictly beyond the end of the disk, so the above helps. The current version of FreeBSD returns the even more bogus errno EIO for reads and writes strictly beyond the end of the disk, so the above won't help (for non-virtual disks). Old and current versions of FreeBSD return the bogus non-error of 0 for both reads writes exactly at the end of the disk. write(2) cannot return 0, but does due to this error. dd treats this non-error as EOF and doesn't retry. The correct behaviour is to return 0 (EOF/no error) for reads at or beyond the end of the disk, and ENOSPC for writes at or beyond the end of the disk, the same as happens for regular files (non-extendible ones for the case of writes). For virtual disks, there is some chance of getting the correct error (ENOSPC) for writes beyond the end and for this error to be passed up to the vfs layer, so the above would help. I once debugged error handling near this for vnode-backed md disks: o a bug in ffs (operating on a file system on the md disk) resulted in garbage block numbers (for the backing vnode) o bounds checking in geom was apparently broken (probably due to an overflow bug in geom or md), so the I/O request got as far as ffs o ffs (operating on the backing vnode) detected the garbage and returned EFBIG o without the above patch, writing of blocks with garbage block numbers was retried endlessly. The ffs bug is fixed now, and if the bounds checking in geom is fixed too then the I/O request won't get as far as ffs -- g_io_check() will return the bogus errno of EIO, and the above patch won't help. Bruce From owner-freebsd-fs@FreeBSD.ORG Wed Mar 28 12:54:46 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2CDE816A404 for ; Wed, 28 Mar 2007 12:54:46 +0000 (UTC) (envelope-from ivoras@fer.hr) Received: from pinus.cc.fer.hr (pinus.cc.fer.hr [161.53.73.18]) by mx1.freebsd.org (Postfix) with ESMTP id AF6BF13C48A for ; Wed, 28 Mar 2007 12:54:45 +0000 (UTC) (envelope-from ivoras@fer.hr) Received: from [161.53.72.113] (lara.cc.fer.hr [161.53.72.113]) by pinus.cc.fer.hr (8.12.2/8.12.2) with ESMTP id l2SD2bLT020013; Wed, 28 Mar 2007 15:02:37 +0200 (MEST) Message-ID: <460A6592.3040308@fer.hr> Date: Wed, 28 Mar 2007 14:54:42 +0200 From: Ivan Voras User-Agent: Thunderbird 1.5.0.10 (X11/20060911) MIME-Version: 1.0 To: Greg Troxel References: <4746DA006C148BC0FF1241C6@ganymede.hub.org> <45CCECCB7ECB612F504211F3@ganymede.hub.org> In-Reply-To: X-Enigmail-Version: 0.94.2.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig2C3E0AB31D9E8E614263480B" Cc: freebsd-fs@freebsd.org Subject: Re: TDFS ... or other distributed file system technologies for FreeBSD? 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, 28 Mar 2007 12:54:46 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig2C3E0AB31D9E8E614263480B Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Greg Troxel wrote: > I've been playing with Coda for a long time, originally in FreeBSD > 2.2, 3 and 4, and more recently in NetBSD. My problems have been all > correctness issues, both in coda's handling of conflicts and in the > kernel vfs locking code. Coda has not yet worked reliably enough that > I've been worried about performance. Once you put a network and > another system in the path, the round trip to user space is not that > big a deal. Yes, I suspected that locking will one of the big problems. > It is truly hard to get the vfs locking issues right (lock one vnode, > release another, do it in the right order, reference counts, follow > the rules exactly). FUSE should (and probably is) taking care of this > for you. Yes, but it doesn't support file locking (flock()), which is kind of=20 required for serious work. > The other thing people could do is import puffs and librefuse from > NetBSD (also originally an SoC project). puffs is like FUSE, but aims > to be a richer interface. librefuse uses puffs to provide a > FUSE-compatible interface, so you can run FUSE filesystems linked > against librefuse, and there's no GPL/LGPL code in the base system. Interesting. I'll look into that. It's too late for SoC but it's nice=20 having something like it. > Porting it to FreeBSD should mostly be straightforward, but I think > the VFS locking rules have diverged, particularly in how .. locking is > handled in vfs_lookup. So making puffs work in FreeBSD will require > cycles from someone who groks the vfs layer. Thanks for the information. --------------enig2C3E0AB31D9E8E614263480B 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.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFGCmWSldnAQVacBcgRAtBwAKDic50nucGAt+rZ5Y7gc1NMheoXsQCgkWwW lMxis2EnwDZ3ds4hWtBfxjY= =gw6L -----END PGP SIGNATURE----- --------------enig2C3E0AB31D9E8E614263480B-- From owner-freebsd-fs@FreeBSD.ORG Wed Mar 28 13:01:07 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BC01816A501 for ; Wed, 28 Mar 2007 13:01:07 +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 7B78913C458 for ; Wed, 28 Mar 2007 13:01:07 +0000 (UTC) (envelope-from gdt@ir.bbn.com) Received: by fnord.ir.bbn.com (Postfix, from userid 10853) id 2724052A0; Wed, 28 Mar 2007 08:29:53 -0400 (EDT) From: Greg Troxel To: Ivan Voras References: <4746DA006C148BC0FF1241C6@ganymede.hub.org> <45CCECCB7ECB612F504211F3@ganymede.hub.org> X-Hashcash: 1:20:070328:freebsd-fs@freebsd.org::10aCvtfJlSlX9EI5:0000000000000000000000000000000000000002jq2 X-Hashcash: 1:20:070328:ivoras@fer.hr::10aCvtfJlSlX9EI5:00004efp Date: Wed, 28 Mar 2007 08:29:49 -0400 In-Reply-To: (Ivan Voras's message of "Tue\, 27 Mar 2007 20\:10\:05 +0200") Message-ID: User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (berkeley-unix) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" Cc: freebsd-fs@freebsd.org Subject: Re: TDFS ... or other distributed file system technologies for FreeBSD? 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, 28 Mar 2007 13:01:07 -0000 --=-=-= Ivan Voras writes: > Marc G. Fournier wrote: > >> I'm just wondering if it would be time better spent polishing off >> the FUSE implementation and pushing that for now, get ppl deploying >> it, testing it, etc ... and then work on the 'performance enhanced >> kernel module'? > > If time to deployment is in question, TDFS is the way to go, and this > would be what I prefer. Another idea of mine for this is that maybe they > could be made compatible in the network protocol... lots of ideas, > little time. I've been playing with Coda for a long time, originally in FreeBSD 2.2, 3 and 4, and more recently in NetBSD. My problems have been all correctness issues, both in coda's handling of conflicts and in the kernel vfs locking code. Coda has not yet worked reliably enough that I've been worried about performance. Once you put a network and another system in the path, the round trip to user space is not that big a deal. It is truly hard to get the vfs locking issues right (lock one vnode, release another, do it in the right order, reference counts, follow the rules exactly). FUSE should (and probably is) taking care of this for you. So, I'd go for FUSE, and I think it will be a long time before performance is a big issue. >> Then again, from the other side of the coin ... what are the >> chances that a kernel module would get into the main stream >> distribution vs the FUSE module? > > Since FUSE is (L)GPL'ed, chances of getting it into base are > slim. Then there's the question of who would be responsible for it, > since the developer of the FUSE BSD module was also a SoC student > and I don't know if he's interested in maintaining it that way - > I'll go ask him. The other thing people could do is import puffs and librefuse from NetBSD (also originally an SoC project). puffs is like FUSE, but aims to be a richer interface. librefuse uses puffs to provide a FUSE-compatible interface, so you can run FUSE filesystems linked against librefuse, and there's no GPL/LGPL code in the base system. puffs is not yet mature; it's not even included in the build of NetBSD-current unless you put MKPUFF=yes in mk.conf. But I've run a puffs ssh filesystem under it, and a FUSE http filesystem, and it's mostly stable. Porting it to FreeBSD should mostly be straightforward, but I think the VFS locking rules have diverged, particularly in how .. locking is handled in vfs_lookup. So making puffs work in FreeBSD will require cycles from someone who groks the vfs layer. PUFFS(3) NetBSD Library Functions Manual PUFFS(3) NAME libpuffs -- Pass-to-Userspace Framework File System development interface --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (NetBSD) iD8DBQFGCl+9+vesoDJhHiURAoIkAKCN5/RTDgTMBdaODSwRwDzAL2b8XgCfduOr TGOgoNXfMmJa+77DTl3wjy4= =ZznB -----END PGP SIGNATURE----- --=-=-=-- From owner-freebsd-fs@FreeBSD.ORG Wed Mar 28 13:41:45 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EB38916A402 for ; Wed, 28 Mar 2007 13:41:45 +0000 (UTC) (envelope-from ivoras@fer.hr) Received: from pinus.cc.fer.hr (pinus.cc.fer.hr [161.53.73.18]) by mx1.freebsd.org (Postfix) with ESMTP id 0CFAE13C44B for ; Wed, 28 Mar 2007 13:41:44 +0000 (UTC) (envelope-from ivoras@fer.hr) Received: from [161.53.72.113] (lara.cc.fer.hr [161.53.72.113]) by pinus.cc.fer.hr (8.12.2/8.12.2) with ESMTP id l2REtILT005578; Tue, 27 Mar 2007 16:55:19 +0200 (MEST) Message-ID: <46092E7E.402@fer.hr> Date: Tue, 27 Mar 2007 16:47:26 +0200 From: Ivan Voras User-Agent: Thunderbird 1.5.0.10 (X11/20060911) MIME-Version: 1.0 To: Francisco Reyes References: <6F52125FD798AC9E4A28A778@ganymede.hub.org> In-Reply-To: X-Enigmail-Version: 0.94.2.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigFFC880E003F154188E10B5E5" Cc: freebsd-fs@freebsd.org Subject: Re: TDFS ... or other distributed file system technologies for FreeBSD? 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, 28 Mar 2007 13:41:46 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigFFC880E003F154188E10B5E5 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Francisco Reyes wrote: > Ivan Voras writes: >=20 >>> a. anyone is using his current code at all? >> >> Judging by the feedback I got (i.e. practically none), I doubt=20 >> anyone's using it. >=20 > Perhaps not many people are aware of it. I've mentioned it many times to get attention :) > Is there a new version planned? I see the last revision was on Jan 2006= =2E No, due to reasons I mentioned before: lack of time on my part, lack of=20 interest from others - this was something I did because it interests me, = but I don't need it (yet...) in production, so - it's where it is. (I didn't abandon it - the problem still interests me and I hope I will=20 re-visit it some time). > Do you have a URL for that other project? No, but the idea is to make a nullfs-like thing that exports file OPs=20 remotely. Way more complex than TDFS. --------------enigFFC880E003F154188E10B5E5 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.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFGCS5+ldnAQVacBcgRAlRAAKC7Pr7iuHKm6LHlfrZFDkApPf1V7gCfRHkA m8ztVETcT+MIsbs2lwOjMl0= =7RYm -----END PGP SIGNATURE----- --------------enigFFC880E003F154188E10B5E5-- From owner-freebsd-fs@FreeBSD.ORG Wed Mar 28 17:46:20 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BF57916A402 for ; Wed, 28 Mar 2007 17:46:20 +0000 (UTC) (envelope-from bohra@cs.rutgers.edu) Received: from mail.nec-labs.com (mail.nec-labs.com [138.15.200.209]) by mx1.freebsd.org (Postfix) with ESMTP id 85CBA13C48C for ; Wed, 28 Mar 2007 17:46:20 +0000 (UTC) (envelope-from bohra@cs.rutgers.edu) Received: from mail.nec-labs.com (localhost.localdomain [127.0.0.1]) by mail.nec-labs.com (8.13.6/8.13.6) with ESMTP id l2SHMsos012278 for ; Wed, 28 Mar 2007 13:22:54 -0400 Received: from mailer.nec-labs.com (mailer.nec-labs.com [138.15.108.3]) by mail.nec-labs.com (8.13.6/8.13.6) with ESMTP id l2SHMrmq012272; Wed, 28 Mar 2007 13:22:54 -0400 Received: from [138.15.109.80] ([138.15.109.80] unverified) by mailer.nec-labs.com with Microsoft SMTPSVC(5.0.2195.6713); Wed, 28 Mar 2007 13:22:54 -0400 Message-ID: <460AA411.3010904@cs.rutgers.edu> Date: Wed, 28 Mar 2007 13:21:21 -0400 From: Aniruddha Bohra User-Agent: Thunderbird 1.5.0.9 (X11/20070217) MIME-Version: 1.0 To: freebsd-fs@freebsd.org, =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 28 Mar 2007 17:22:54.0046 (UTC) FILETIME=[B8402FE0:01C7715D] Cc: Subject: Pseudofs question 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, 28 Mar 2007 17:46:20 -0000 Hi, Pseudofs handles the fileno allocation and deallocation using alloc_unr() and free_unr(). The fileno is allocated on demand when vn_readdir is called (pseudofs_vnops.c). However, I could not find the deallocation in pseudofs. So, when I unload my fs module, I get a crash with the unit busy: kern/subr_unit.c:321 KASSERT(uh->busy == 0, ("unrhdr has %u allocations", uh->busy)); This is a good kassert as the pfs_fileno_free is never called. Actually, the module unload function calls _fsname_uninit() which calls pfs_uninit() which calls pfs_fileno_uninit(pi) without first destroying the file system or deallocating any allocated unit numbers. Am I missing something obvious in my implementation since I do not see a similar crash with procfs :( Thanks Aniruddha From owner-freebsd-fs@FreeBSD.ORG Thu Mar 29 00:16:41 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3611716A46C for ; Thu, 29 Mar 2007 00:16:41 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outC.internet-mail-service.net (outC.internet-mail-service.net [216.240.47.226]) by mx1.freebsd.org (Postfix) with ESMTP id 2370A13C4B0 for ; Thu, 29 Mar 2007 00:16:41 +0000 (UTC) (envelope-from julian@elischer.org) Received: from mx0.idiom.com (HELO idiom.com) (216.240.32.160) by out.internet-mail-service.net (qpsmtpd/0.32) with ESMTP; Wed, 28 Mar 2007 16:47:40 -0700 Received: from [10.251.22.38] (nat.ironport.com [63.251.108.100]) by idiom.com (Postfix) with ESMTP id 28C3C125B1D; Wed, 28 Mar 2007 17:16:40 -0700 (PDT) Message-ID: <460B0567.40706@elischer.org> Date: Wed, 28 Mar 2007 17:16:39 -0700 From: Julian Elischer User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221) MIME-Version: 1.0 To: Ivan Voras References: <6F52125FD798AC9E4A28A778@ganymede.hub.org> <46092E7E.402@fer.hr> In-Reply-To: <46092E7E.402@fer.hr> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: TDFS ... or other distributed file system technologies for FreeBSD? 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, 29 Mar 2007 00:16:41 -0000 Ivan Voras wrote: > Francisco Reyes wrote: >> Ivan Voras writes: >> >>>> a. anyone is using his current code at all? >>> >>> Judging by the feedback I got (i.e. practically none), I doubt >>> anyone's using it. >> >> Perhaps not many people are aware of it. > > I've mentioned it many times to get attention :) > >> Is there a new version planned? I see the last revision was on Jan 2006. > > No, due to reasons I mentioned before: lack of time on my part, lack of > interest from others - this was something I did because it interests me, > but I don't need it (yet...) in production, so - it's where it is. > > (I didn't abandon it - the problem still interests me and I hope I will > re-visit it some time). > >> Do you have a URL for that other project? > > No, but the idea is to make a nullfs-like thing that exports file OPs > remotely. Way more complex than TDFS. > I believe Matt Dillon has taken this to extremes in Dragonfly.. From owner-freebsd-fs@FreeBSD.ORG Thu Mar 29 07:32:06 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1DF1216A405 for ; Thu, 29 Mar 2007 07:32:06 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id D565D13C43E for ; Thu, 29 Mar 2007 07:32:05 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 70DA32100; Thu, 29 Mar 2007 09:32:00 +0200 (CEST) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: 0.0/3.0 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on tim.des.no Received: from dwp.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id 98F93207E; Thu, 29 Mar 2007 09:31:59 +0200 (CEST) Received: by dwp.des.no (Postfix, from userid 1001) id 7DB6AA1073; Thu, 29 Mar 2007 09:31:59 +0200 (CEST) From: des@des.no (Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?=) To: Aniruddha Bohra References: <460AA411.3010904@cs.rutgers.edu> Date: Thu, 29 Mar 2007 09:31:59 +0200 In-Reply-To: <460AA411.3010904@cs.rutgers.edu> (Aniruddha Bohra's message of "Wed, 28 Mar 2007 13:21:21 -0400") Message-ID: <861wj8sdxs.fsf@dwp.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@freebsd.org Subject: Re: Pseudofs question 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, 29 Mar 2007 07:32:06 -0000 Aniruddha Bohra writes: > Pseudofs handles the fileno allocation and deallocation using > alloc_unr() and free_unr(). > > The fileno is allocated on demand when vn_readdir is called > (pseudofs_vnops.c). However, > I could not find the deallocation in pseudofs. > > So, when I unload my fs module, I get a crash with the unit busy: > kern/subr_unit.c:321 KASSERT(uh->busy =3D=3D 0, ("unrhdr has %u > allocations", uh->busy)); > > This is a good kassert as the pfs_fileno_free is never called. Damn. Pseudofs used to have its own fileno allocator, which contained the following comment: #if 0 /* we currently don't reclaim filenos */ if (used > 2) printf("WARNING: %d file numbers still in use\n", used); #endif I obviously didn't pay close enough attention when I reviewed the switch to *_unr(). > Actually, the module unload function calls _fsname_uninit() which > calls pfs_uninit() which calls pfs_fileno_uninit(pi) without first > destroying the file system or deallocating any allocated unit > numbers. Again, this was fine when we had our own allocator. It obviously isn't fine now. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-fs@FreeBSD.ORG Thu Mar 29 10:08:22 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9B0F516A402 for ; Thu, 29 Mar 2007 10:08:22 +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 5A32A13C43E for ; Thu, 29 Mar 2007 10:08:21 +0000 (UTC) (envelope-from freebsd-fs@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1HWrY5-0003xo-Or for freebsd-fs@freebsd.org; Thu, 29 Mar 2007 12:08:10 +0200 Received: from 213.202.123.87 ([213.202.123.87]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 29 Mar 2007 12:08:05 +0200 Received: from ivoras by 213.202.123.87 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 29 Mar 2007 12:08:05 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-fs@freebsd.org From: Ivan Voras Date: Thu, 29 Mar 2007 12:08:15 +0200 Lines: 9 Message-ID: References: <6F52125FD798AC9E4A28A778@ganymede.hub.org> <46092E7E.402@fer.hr> <460B0567.40706@elischer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 213.202.123.87 User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) In-Reply-To: <460B0567.40706@elischer.org> X-Enigmail-Version: 0.94.1.0 Sender: news Subject: Re: TDFS ... or other distributed file system technologies for FreeBSD? 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, 29 Mar 2007 10:08:22 -0000 Julian Elischer wrote: > Ivan Voras wrote: >> No, but the idea is to make a nullfs-like thing that exports file OPs >> remotely. Way more complex than TDFS. > > I believe Matt Dillon has taken this to extremes in Dragonfly.. Yes, that was one of the sources for the idea. From owner-freebsd-fs@FreeBSD.ORG Thu Mar 29 19:54:42 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 78B5516A407 for ; Thu, 29 Mar 2007 19:54:42 +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 32A9213C44C for ; Thu, 29 Mar 2007 19:54:41 +0000 (UTC) (envelope-from freebsd-fs@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1HX0ha-00048i-O1 for freebsd-fs@freebsd.org; Thu, 29 Mar 2007 21:54:31 +0200 Received: from 83-131-175-241.adsl.net.t-com.hr ([83.131.175.241]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 29 Mar 2007 21:54:30 +0200 Received: from ivoras by 83-131-175-241.adsl.net.t-com.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 29 Mar 2007 21:54:30 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-fs@freebsd.org From: Ivan Voras Date: Thu, 29 Mar 2007 21:54:23 +0200 Lines: 45 Message-ID: References: <20070328100536.S6916@besplex.bde.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig19E0AD0FFBAE1C71053DAC4D" X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 83-131-175-241.adsl.net.t-com.hr User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) In-Reply-To: <20070328100536.S6916@besplex.bde.org> X-Enigmail-Version: 0.94.1.2 Sender: news Subject: Re: gvirstor & UFS 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, 29 Mar 2007 19:54:42 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig19E0AD0FFBAE1C71053DAC4D Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Bruce Evans wrote: > The following old patch may help. vfs retries too hard after write > errors. Retrying after EIO is bad enough (since most parts of the > kernel still expect the old treatment of not retrying), but retrying > after a non-recoverable error is just a bug. I've tried the patch - it resulted in a panic :( g_vfs_done():virstor/foo[WRITE(offset=3D17353104384, length=3D131072)]err= or =3D 28 /bla: got error 28 while accessing file system panic: softdep_deallocate_dependencies: unrecovered I/O error cpuid=3D0 The file system on the virstor device was created with softupdates enables, as shown... backtrace: panic() ... softdep_deallocate_dependencies() ... brelse() ... bufdone_finish() ... bufdone() ... cluster_callback() ... bufdone() ... g_vfs_done() ... bio_done() ... g_io_schedule_up(), ... --------------enig19E0AD0FFBAE1C71053DAC4D 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.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGDBlvldnAQVacBcgRAqj0AKCweUTU0T2GWIUfxc4NU9q9s86FoQCcCkSE +ZsYk/Rgd75FOStz3vu50nQ= =RcU7 -----END PGP SIGNATURE----- --------------enig19E0AD0FFBAE1C71053DAC4D-- From owner-freebsd-fs@FreeBSD.ORG Thu Mar 29 20:53:33 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D781716A401 for ; Thu, 29 Mar 2007 20:53:33 +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 91E5813C480 for ; Thu, 29 Mar 2007 20:53:33 +0000 (UTC) (envelope-from freebsd-fs@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1HX1cZ-0008IR-QG for freebsd-fs@freebsd.org; Thu, 29 Mar 2007 22:53:23 +0200 Received: from 83-131-175-241.adsl.net.t-com.hr ([83.131.175.241]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 29 Mar 2007 22:53:23 +0200 Received: from ivoras by 83-131-175-241.adsl.net.t-com.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 29 Mar 2007 22:53:23 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-fs@freebsd.org From: Ivan Voras Date: Thu, 29 Mar 2007 22:53:06 +0200 Lines: 36 Message-ID: References: <20070328100536.S6916@besplex.bde.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig49E93BE3886E2BDB8412BCED" X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 83-131-175-241.adsl.net.t-com.hr User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) In-Reply-To: X-Enigmail-Version: 0.94.1.2 Sender: news Subject: Re: gvirstor & UFS 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, 29 Mar 2007 20:53:33 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig49E93BE3886E2BDB8412BCED Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Ivan Voras wrote: > The file system on the virstor device was created with softupdates > enables, as shown... Without softupdates, the I/O requests fail, with the usual spewing of kernel messages from g_vfs_done() in the log, but the application (dd) doesn't receive failure codes. In effect, it looks like the requests are ignored - they fail, but dd continues pumping more requests. Something else occurred to me: what if an UFS metadata update (for example, in cg) fails in this way - that it requires an additional chunk of physical data that's not available, is there a chance that the fs will be corrupted? --------------enig49E93BE3886E2BDB8412BCED 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.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGDCcyldnAQVacBcgRAm+UAKDOWa8HNMiwiQute5gF7fTRvP74gACfYtnW RqF7eiQJtXQcSG4yKwZSTWU= =VbO6 -----END PGP SIGNATURE----- --------------enig49E93BE3886E2BDB8412BCED-- From owner-freebsd-fs@FreeBSD.ORG Thu Mar 29 21:14:02 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 45F9A16A400 for ; Thu, 29 Mar 2007 21:14:02 +0000 (UTC) (envelope-from bde@zeta.org.au) Received: from mailout2.pacific.net.au (mailout2-3.pacific.net.au [61.8.2.226]) by mx1.freebsd.org (Postfix) with ESMTP id DCBA313C46C for ; Thu, 29 Mar 2007 21:14:01 +0000 (UTC) (envelope-from bde@zeta.org.au) Received: from mailproxy2.pacific.net.au (mailproxy2.pacific.net.au [61.8.2.163]) by mailout2.pacific.net.au (Postfix) with ESMTP id A88831099BD; Fri, 30 Mar 2007 07:13:55 +1000 (EST) Received: from besplex.bde.org (katana.zip.com.au [61.8.7.246]) by mailproxy2.pacific.net.au (Postfix) with ESMTP id 6A55027405; Fri, 30 Mar 2007 07:13:59 +1000 (EST) Date: Fri, 30 Mar 2007 07:13:57 +1000 (EST) From: Bruce Evans X-X-Sender: bde@besplex.bde.org To: Ivan Voras In-Reply-To: Message-ID: <20070330062726.I2388@besplex.bde.org> References: <20070328100536.S6916@besplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-fs@freebsd.org Subject: Re: gvirstor & UFS 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, 29 Mar 2007 21:14:02 -0000 On Thu, 29 Mar 2007, Ivan Voras wrote: > Bruce Evans wrote: > >> The following old patch may help. vfs retries too hard after write >> errors. Retrying after EIO is bad enough (since most parts of the >> kernel still expect the old treatment of not retrying), but retrying >> after a non-recoverable error is just a bug. > > I've tried the patch - it resulted in a panic :( > > g_vfs_done():virstor/foo[WRITE(offset=17353104384, length=131072)]error = 28 > /bla: got error 28 while accessing file system > panic: softdep_deallocate_dependencies: unrecovered I/O error > cpuid=0 That is hard to fix. The change to vfs_bio.c to not discard buffer contents after a write error (rev.1.196 of vfs_bio.c) may even have been triggered by this and similar panics in soft updates. However, I think it is a bug for file systems to not be able to deal with i/o errors. Rev.1.196 could have reasonably left the buffer alone instead of discarding it as before or clearing its error indicator and dirty flag as now, so that file system code could deal with the error a little later. Then I think the above panic would still occur, sincs soft updates can't deal with the error. Soft updates is apparently depending on not even seeing the error. But some errors are non-recoverable, so not seeing them is no solution. > The file system on the virstor device was created with softupdates > enables, as shown... > > backtrace: > panic() ... softdep_deallocate_dependencies() ... brelse() ... > bufdone_finish() ... bufdone() ... cluster_callback() ... bufdone() ... > g_vfs_done() ... bio_done() ... g_io_schedule_up(), ... Apparently it get past the media size check in g_io_check() to give ENOSPC instead of EIO because g_io_check() only checks the virtual size. To support virtual overcommitted media, it is necessary for file systems to either do a physical check whenever they allocate a block (just checking that the block number is <= the maximum allocated one like most file systems do is insufficient of the media is overcommitted), or deal with ENOSPC-type errors later when they occur at write time. I once worked on a toy file system that did the former -- allocation was essentially malloc() and done by the file system, and deallocation was essentially free() and also done by the file system. FreeBSD seems to only have support for the free() part of this -- BIO_DELETE. For malloc()ed md disks, BIO_DELETE gives the free(), but allocation is done by just writing to a block. The malloc() for this uses M_WAITOK, so when a malloc()ed md disk is overcommitted and full, ENOSPC is not returned -- the system hangs instead :-(. Bruce From owner-freebsd-fs@FreeBSD.ORG Thu Mar 29 21:41:12 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D674D16A406 for ; Thu, 29 Mar 2007 21:41:12 +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 6485313C455 for ; Thu, 29 Mar 2007 21:41:12 +0000 (UTC) (envelope-from freebsd-fs@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1HX2Mg-0002H1-4S for freebsd-fs@freebsd.org; Thu, 29 Mar 2007 23:41:02 +0200 Received: from 83-131-175-241.adsl.net.t-com.hr ([83.131.175.241]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 29 Mar 2007 23:41:02 +0200 Received: from ivoras by 83-131-175-241.adsl.net.t-com.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 29 Mar 2007 23:41:02 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-fs@freebsd.org From: Ivan Voras Date: Thu, 29 Mar 2007 23:40:49 +0200 Lines: 48 Message-ID: References: <20070328100536.S6916@besplex.bde.org> <20070330062726.I2388@besplex.bde.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig5A351F2053C82BEB6673C1A4" X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 83-131-175-241.adsl.net.t-com.hr User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) In-Reply-To: <20070330062726.I2388@besplex.bde.org> X-Enigmail-Version: 0.94.1.2 Sender: news Subject: Re: gvirstor & UFS 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, 29 Mar 2007 21:41:12 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig5A351F2053C82BEB6673C1A4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Bruce Evans wrote: > That is hard to fix. The change to vfs_bio.c to not discard buffer > contents > after a write error (rev.1.196 of vfs_bio.c) may even have been trigger= ed > by this and similar panics in soft updates. However, I think it is a b= ug > for file systems to not be able to deal with i/o errors. Rev.1.196 cou= ld > have reasonably left the buffer alone instead of discarding it as befor= e > or clearing its error indicator and dirty flag as now, so that file sys= tem > code could deal with the error a little later. Then I think the above > panic would still occur, sincs soft updates can't deal with the error. > Soft updates is apparently depending on not even seeing the error. But= > some errors are non-recoverable, so not seeing them is no solution. Ah. It looks like I've again stumbled on a task that needs non-trivial interaction with the UFS (the last time was gjournal, which Pawel thankfully took over and made it work) :( I can probably try solving this one, but I'll need major hand-holding through it since I'm afraid of the UFS code. Any volunteers? --------------enig5A351F2053C82BEB6673C1A4 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.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGDDJhldnAQVacBcgRAqxlAJ429DbUz2zidKwmetc3FJ1dhbdVOgCgqWSO QQMZ4GUyyDN8XhswMcg23OY= =bpsz -----END PGP SIGNATURE----- --------------enig5A351F2053C82BEB6673C1A4-- From owner-freebsd-fs@FreeBSD.ORG Thu Mar 29 22:10:46 2007 Return-Path: X-Original-To: freebsd-fs@FreeBSD.org Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 024A216A41A for ; Thu, 29 Mar 2007 22:10:46 +0000 (UTC) (envelope-from bde@zeta.org.au) Received: from mailout1.pacific.net.au (mailout1-3.pacific.net.au [61.8.2.210]) by mx1.freebsd.org (Postfix) with ESMTP id 8CE1E13C480 for ; Thu, 29 Mar 2007 22:10:45 +0000 (UTC) (envelope-from bde@zeta.org.au) Received: from mailproxy1.pacific.net.au (mailproxy1.pacific.net.au [61.8.2.162]) by mailout1.pacific.net.au (Postfix) with ESMTP id DE9D75A0DCE; Fri, 30 Mar 2007 08:10:43 +1000 (EST) Received: from katana.zip.com.au (katana.zip.com.au [61.8.7.246]) by mailproxy1.pacific.net.au (Postfix) with ESMTP id DDB958C16; Fri, 30 Mar 2007 08:10:42 +1000 (EST) Date: Fri, 30 Mar 2007 08:10:40 +1000 (EST) From: Bruce Evans X-X-Sender: bde@delplex.bde.org To: Ivan Voras In-Reply-To: Message-ID: <20070330072950.S15433@delplex.bde.org> References: <20070328100536.S6916@besplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-fs@FreeBSD.org Subject: Re: gvirstor & UFS 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, 29 Mar 2007 22:10:46 -0000 On Thu, 29 Mar 2007, Ivan Voras wrote: > Ivan Voras wrote: > >> The file system on the virstor device was created with softupdates >> enables, as shown... > > Without softupdates, the I/O requests fail, with the usual spewing of > kernel messages from g_vfs_done() in the log, but the application (dd) > doesn't receive failure codes. In effect, it looks like the requests are > ignored - they fail, but dd continues pumping more requests. This might be because the writes are only of data, and data writes are async with little error checking in ffs without soft updates. Any error cannot be reported on return from bdwrite() and bawrite() since the write probably hasn't happened then, and there is no mechanism other than kernel messages for reporting errors. I thought that geom was too silent about i/o errors. Actually, it seems to be more verbose than my dscheck() about low level errors (g_vfs_done() always prints something if there is an error) and less verbose about errors that it checks for (g_io_check() never prints anything, and buffers with errors detected by g_io_check() apparently don't get as far as g_vfs_done()). The messages printed by my dscheck() are too verbose but are sometimes useful (especially the details about what caused the error, which g_vfs_done() cannot print because its level is too high). > Something else occurred to me: what if an UFS metadata update (for > example, in cg) fails in this way - that it requires an additional chunk > of physical data that's not available, is there a chance that the fs > will be corrupted? ffs is supposed to detect and handle i/o errors for metadata. It is sloppy for indirect blocks (it uses (void)bwrite() a lot), but hopefully when the write of an indirect block fails the damage is limited to one file. I/o errors in old blocks can easily cause corruption, but for ENOSPC-type errors in new blocks the error handling hopefully aborts writing before any damage is done. This depends on ffs using a safe order of writing and the physical order not being different, which I doubt actually happens, especially for virtual disks -- everything would have to be synchronous or otherwise slow to preserve the order in all lower layers. Bruce From owner-freebsd-fs@FreeBSD.ORG Thu Mar 29 22:21:12 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2D5CF16A405 for ; Thu, 29 Mar 2007 22:21:12 +0000 (UTC) (envelope-from fbsd-fs@mawer.org) Received: from customer-domains.icp-qv1-irony11.iinet.net.au (customer-domains.icp-qv1-irony11.iinet.net.au [203.59.1.151]) by mx1.freebsd.org (Postfix) with ESMTP id A34D613C48C for ; Thu, 29 Mar 2007 22:21:11 +0000 (UTC) (envelope-from fbsd-fs@mawer.org) Received: from 203-206-173-235.perm.iinet.net.au (HELO [10.24.1.1]) ([203.206.173.235]) by iinet-mail.icp-qv1-irony11.iinet.net.au with ESMTP; 30 Mar 2007 05:51:22 +0800 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgAAAKLRC0bLzq3r/2dsb2JhbAAN X-IronPort-AV: i="4.14,348,1170601200"; d="scan'208"; a="37248363:sNHT26221278" Message-ID: <460C34E4.5050506@mawer.org> Date: Fri, 30 Mar 2007 07:51:32 +1000 From: Antony Mawer User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) MIME-Version: 1.0 To: Bruce Evans References: <20070328100536.S6916@besplex.bde.org> <20070330062726.I2388@besplex.bde.org> In-Reply-To: <20070330062726.I2388@besplex.bde.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org, Ivan Voras Subject: Re: gvirstor & UFS 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, 29 Mar 2007 22:21:12 -0000 On 30/03/2007 7:13 AM, Bruce Evans wrote: > On Thu, 29 Mar 2007, Ivan Voras wrote: > >> Bruce Evans wrote: >> >>> The following old patch may help. vfs retries too hard after write >>> errors. Retrying after EIO is bad enough (since most parts of the >>> kernel still expect the old treatment of not retrying), but retrying >>> after a non-recoverable error is just a bug. >> >> I've tried the patch - it resulted in a panic :( >> >> g_vfs_done():virstor/foo[WRITE(offset=17353104384, >> length=131072)]error = 28 >> /bla: got error 28 while accessing file system >> panic: softdep_deallocate_dependencies: unrecovered I/O error >> cpuid=0 > > That is hard to fix. The change to vfs_bio.c to not discard buffer > contents > after a write error (rev.1.196 of vfs_bio.c) may even have been triggered > by this and similar panics in soft updates. However, I think it is a bug > for file systems to not be able to deal with i/o errors. Rev.1.196 could > have reasonably left the buffer alone instead of discarding it as before > or clearing its error indicator and dirty flag as now, so that file system > code could deal with the error a little later. Then I think the above > panic would still occur, sincs soft updates can't deal with the error. > Soft updates is apparently depending on not even seeing the error. But > some errors are non-recoverable, so not seeing them is no solution. Is this at all related to the whole being unable to unmount a filesystem after the device goes awall (eg. removable media disconnected), and forcibly doing so leads to a panic? I haven't looked into this recently, but recall stumbling across the thread as something that interested me some years back. I imagine this would be particularly messy for any sort of embedded system dealing with removable media (eg. USB/Firewire devices), as if an end-user unplugs a device when you don't want them to, the whole system will collapse in a heap... From what I gather, this is probably related, as the device goes walkabout generating IO errors, but the filesystem keeps trying over and over to flush any dirty buffers. Forgive me if any of the above seems incorrect - I'm just going from memory! --Antony From owner-freebsd-fs@FreeBSD.ORG Fri Mar 30 00:48:41 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E291116A403 for ; Fri, 30 Mar 2007 00:48:41 +0000 (UTC) (envelope-from nb_root@videotron.ca) Received: from relais.videotron.ca (relais.videotron.ca [24.201.245.36]) by mx1.freebsd.org (Postfix) with ESMTP id 8A4B013C44B for ; Fri, 30 Mar 2007 00:48:41 +0000 (UTC) (envelope-from nb_root@videotron.ca) Received: from clk01a ([24.202.150.69]) by VL-MO-MR004.ip.videotron.ca (Sun Java System Messaging Server 6.2-2.05 (built Apr 28 2005)) with ESMTP id <0JFO008S4VH4PN00@VL-MO-MR004.ip.videotron.ca> for freebsd-fs@freebsd.org; Thu, 29 Mar 2007 19:48:40 -0400 (EDT) Date: Thu, 29 Mar 2007 19:48:34 -0400 From: Nicolas Blais To: freebsd-fs@freebsd.org Message-id: <200703291948.40100.nb_root@videotron.ca> MIME-version: 1.0 Content-type: multipart/signed; boundary=nextPart4355290.nCFbbvuQQ5; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-transfer-encoding: 7bit User-Agent: KMail/1.9.6 Subject: gjournal questions 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, 30 Mar 2007 00:48:42 -0000 --nextPart4355290.nCFbbvuQQ5 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi, I've posted this here since this is probably the place to get an answer :)= =20 I've been experimenting with gjournal with the hopes of using it in my new= =20 multi-TB server (SuperMicro 5015M-NTB) . I have several questions, hopefull= y=20 someone can help me out (long read though!). 1. I simulated a crash (hard power-off while transfering files). When I=20 rebooted, I got the following on my console: ad0: 78167MB at ata0-master UDMA133 acd0: DVDR at ata1-master UDMA33 ad4: 76319MB at ata2-master SATA150 ad6: 76319MB at ata3-master SATA150 ad10: 76319MB at ata5-master SATA150 GEOM_JOURNAL: Journal 2822006383: ad10s1 contains data. GEOM_JOURNAL: Journal 2822006383: ad10s1 contains journal. GEOM_JOURNAL: Journal ad10s1 clean. acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=3D0x24 ascq=3D0x00 sks=3D0x40 0= x00 0x01 ar0: 76293MB status: READY ar0: disk0 READY (master) using ad4 at ata2-master ar0: disk1 READY (mirror) using ad6 at ata3-master WARNING: /usr was not properly dismounted WARNING: /var was not properly dismounted WARNING: R/W mount of /mnt/journaled denied. =A0Filesystem is not clean - r= un=20 fsck Only /mnt/journaled (ad10s1.journal) is gjournaled. Why doesn't fsck, which= is=20 running in background mode by now, check my /mnt/journaled and tag it clean= ?=20 I have to manually fsck /dev/ad10s1.journal and manually remount it. This i= s=20 a no-go because I want my system to be able to run without the helps of us,= =20 bipeds even in the event of a crash :). /usr and /var where fsck'ed in=20 background as expected. Therefore, is it possible to make a crash recovery with gjournal without th= e=20 need of humains? Can I boot from a crash, with background_fsck=3D"NO" and s= till=20 mount the journaled FS? 2. Since my new server will require a fresh installation, can I set up my=20 gjournal slices from within sysinstall by choosing "Custom NewFS" and putti= ng=20 the -J option in there? Will that load the gjournal module? What is the=20 correct way to implement gjournal (and if possible with gmirror) from a fre= sh=20 start? 3. From gjournal(8) man page: "It is not recommended to use gjournal for sm= all=20 file systems (e.g.: only few gigabytes big)." How much is a "few"? Is it <= =20 10gb? <50gb? I intend to use gjournal on /var (10gb), /usr (100gb), /home=20 (1tb) and some misc mounts. (~25-100gb). 4. I'm thinking of using gmirror instead of my MB's onboard raid. I found f= rom=20 previous posts that I can mount async, disable soft-updates and that for=20 simplicity it would be better to mirror the whole drive instead of slices=20 (which is what I'm intending to do). Anything else I could use/know about=20 using gmirror and gjournal?=20 Thank you VERY MUCH for your help. Nicolas. =2D-=20 =46reeBSD 7.0-CURRENT #18: Sun Mar 25 16:03:50 EDT 2007 =20 nicblais@clk01a:/usr/obj/usr/src/sys/CLK01A=20 PGP? : http://plaintext.clkroot.net/security/nb_root.asc --nextPart4355290.nCFbbvuQQ5 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQBGDFBS4wTBlvcsbJURAlyRAJ9LGemZXaE1TVVUbt5ubDX5RnVOlQCggOiD LpDSTu3/CCy5v7NZH3VRBUU= =In9E -----END PGP SIGNATURE----- --nextPart4355290.nCFbbvuQQ5-- From owner-freebsd-fs@FreeBSD.ORG Fri Mar 30 12:23:20 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 830C216A400 for ; Fri, 30 Mar 2007 12:23:20 +0000 (UTC) (envelope-from dan.cojocar@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.242]) by mx1.freebsd.org (Postfix) with ESMTP id 43E7F13C483 for ; Fri, 30 Mar 2007 12:23:20 +0000 (UTC) (envelope-from dan.cojocar@gmail.com) Received: by an-out-0708.google.com with SMTP id c24so472114ana for ; Fri, 30 Mar 2007 05:23:19 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=K4r2OdnEEvKLlhPCD0dZlNFSbHZ48QqhGZaCCikqNv+fahVs6CkkTZVArMkBq/zSPwef/8CNG3qFgY8ZD+QS5J4YJWNxxSFFzIzgriSp9kDrbmnZUKkH+1sK2h8TLaR0X9CI9oUTauhQfkaOgftOoSxOBaJjfmhsidL8CeWSOvk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=iCVjVoe5yMUHOOPrfR5ZuFsNBgZ+r7XSVwLpV2OOvzXi2vOprsi/bvGPmVkgm3x771Qfd9oGJVWPh3lTgBEm8Nl1AanUEHFYPiy9wlHelXI9ZUzyBaekHDjZNJd9VSM3iT3xncd+8kwSPVUowhTDGO3jCvahvfIUhek4j81x1FE= Received: by 10.100.135.16 with SMTP id i16mr1253503and.1175255668547; Fri, 30 Mar 2007 04:54:28 -0700 (PDT) Received: by 10.100.137.1 with HTTP; Fri, 30 Mar 2007 04:54:28 -0700 (PDT) Message-ID: Date: Fri, 30 Mar 2007 14:54:28 +0300 From: "Dan Cojocar" To: freebsd-fs@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: gjournal error 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, 30 Mar 2007 12:23:20 -0000 Hello all, I noticed this error in my logs: GEOM_JOURNAL: [flush] Error while writting data (error=1) ad1s1d[WRITE(offset=512, length=115200)] fsync: giving up on dirty 0xc435910c: tag devfs, type VCHR usecount 1, writecount 0, refcount 96 mountedhere 0xc41f9900 flags () v_object 0xc1048e10 ref 0 pages 2236 lock type devfs: EXCL (count 1) by thread 0xc3f7d6c0 (pid 27) dev ad1s1e.journal GEOM_JOURNAL: Cannot suspend file system /extra/large (error=35). This is: FreeBSD 7.0-CURRENT #1: Mon Mar 12 17:55:55 EET 2007 Thank you, Dan From owner-freebsd-fs@FreeBSD.ORG Fri Mar 30 18:10:31 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E024916A407 for ; Fri, 30 Mar 2007 18:10:31 +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 7855413C4D0 for ; Fri, 30 Mar 2007 18:10:31 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 15FDD4880A; Fri, 30 Mar 2007 20:10:29 +0200 (CEST) Received: from localhost (154.81.datacomsa.pl [195.34.81.154]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 66FBD487F0; Fri, 30 Mar 2007 20:10:22 +0200 (CEST) Date: Fri, 30 Mar 2007 20:10:15 +0200 From: Pawel Jakub Dawidek To: Dan Cojocar Message-ID: <20070330181015.GB11360@garage.freebsd.pl> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="cvVnyQ+4j833TQvp" Content-Disposition: inline In-Reply-To: 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=-2.6 required=3.0 tests=BAYES_00 autolearn=ham version=3.0.4 Cc: freebsd-fs@freebsd.org Subject: Re: gjournal error 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, 30 Mar 2007 18:10:32 -0000 --cvVnyQ+4j833TQvp Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Mar 30, 2007 at 02:54:28PM +0300, Dan Cojocar wrote: > Hello all, >=20 > I noticed this error in my logs: >=20 > GEOM_JOURNAL: [flush] Error while writting data (error=3D1) > ad1s1d[WRITE(offset=3D512, length=3D115200)] > fsync: giving up on dirty > 0xc435910c: tag devfs, type VCHR > usecount 1, writecount 0, refcount 96 mountedhere 0xc41f9900 > flags () > v_object 0xc1048e10 ref 0 pages 2236 > lock type devfs: EXCL (count 1) by thread 0xc3f7d6c0 (pid 27) > dev ad1s1e.journal > GEOM_JOURNAL: Cannot suspend file system /extra/large (error=3D35). >=20 > This is: FreeBSD 7.0-CURRENT #1: Mon Mar 12 17:55:55 EET 2007 Can you paste output of: # bsdlabel /dev/ad1s1 ? --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --cvVnyQ+4j833TQvp Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFGDVKHForvXbEpPzQRAlw+AJ4mE18WT4/VFip5rJuaP0NHnTV+qgCguvSq fhfnzRnf9kZQixpMh+l0RFk= =Nnks -----END PGP SIGNATURE----- --cvVnyQ+4j833TQvp-- From owner-freebsd-fs@FreeBSD.ORG Sat Mar 31 12:51:28 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4414A16A402 for ; Sat, 31 Mar 2007 12:51:28 +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 1951F13C468 for ; Sat, 31 Mar 2007 12:51:28 +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 8B8A3470EA; Sat, 31 Mar 2007 07:51:27 -0500 (EST) Date: Sat, 31 Mar 2007 07:51:27 -0500 (EST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: =?ISO-8859-1?Q?C=E9dric?= Jonas In-Reply-To: <20070327130208.400a0310@luna> Message-ID: <20070331075039.R75869@fledge.watson.org> References: <20070321175253.54b4b1ed@ganymed> <4601763E.2050309@elischer.org> <20070327130208.400a0310@luna> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1987084258-1175345487=:75869" Cc: freebsd-fs@freebsd.org, Julian Elischer Subject: Re: ACL's doesn't work with SUIDDIR 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: Sat, 31 Mar 2007 12:51:28 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-1987084258-1175345487=:75869 Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE On Tue, 27 Mar 2007, C=E9dric Jonas wrote: > On Wed, 21 Mar 2007 11:15:26 -0700 > Julian Elischer wrote: > >> C=E9dric Jonas wrote: >> >>> thanks to correct me. >>> >>> PS: Please CC me, I'm not on the list. >> >> SUIDDIR is probably mot widely used so it may not have ever been tested= =20 >> with ACL (also not widely used) is is possible that you are the first=20 >> person to have ever tried this combination :-) >> >> I suggest that the ACL guys take a look as they i think have some shared= =20 >> code with other OS's which probably don't have SUIDDIR, which is a FreeB= SD=20 >> only option. > > Typical for me :-( But however, it seems that I'm not the very first one = who=20 > tries this. I found this in the freebsd-stable archive from February 2005= : > > http://lists.freebsd.org/pipermail/freebsd-stable/2005-February/011786.ht= ml=20 > http://lists.freebsd.org/pipermail/freebsd-stable/2005-February/011797.ht= ml > > It it can help... I also filled in a PR: misc/110915 > > Let me know if you need further informations. Thanks for this report -- I will try to investigate this issue sometime thi= s=20 week. Is there a PR files for this currently? Thanks, Robert N M Watson Computer Laboratory University of Cambridge --0-1987084258-1175345487=:75869-- From owner-freebsd-fs@FreeBSD.ORG Sat Mar 31 13:31:10 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 88BBB16A407; Sat, 31 Mar 2007 13:31:10 +0000 (UTC) (envelope-from cedric@decemplex.net) Received: from mail.decemplex.net (mail.decemplex.net [80.237.247.202]) by mx1.freebsd.org (Postfix) with ESMTP id 44B7E13C468; Sat, 31 Mar 2007 13:31:09 +0000 (UTC) (envelope-from cedric@decemplex.net) Received: from localhost (mail.decemplex.net [80.237.247.202]) by mail.decemplex.net (Postfix) with ESMTP id DB7B57D1F65; Sat, 31 Mar 2007 15:31:08 +0200 (CEST) X-Virus-Scanned: amavisd-new at decemplex.net Received: from mail.decemplex.net ([80.237.247.202]) by localhost (mail.decemplex.net [80.237.247.202]) (amavisd-new, port 10024) with LMTP id at9kitdnKzdt; Sat, 31 Mar 2007 15:31:08 +0200 (CEST) Received: from decemplex.loc (46-186-112-217.dyn.adsl.belcenter.be [217.112.186.46]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.decemplex.net (Postfix) with ESMTP id EBCA17D1F57; Sat, 31 Mar 2007 15:31:07 +0200 (CEST) Date: Sat, 31 Mar 2007 15:30:56 +0200 From: =?ISO-8859-1?Q?C=E9dric?= Jonas To: Robert Watson Message-ID: <20070331153056.5a2509ff@ganymed> In-Reply-To: <20070331075039.R75869@fledge.watson.org> References: <20070321175253.54b4b1ed@ganymed> <4601763E.2050309@elischer.org> <20070327130208.400a0310@luna> <20070331075039.R75869@fledge.watson.org> X-Mailer: Claws Mail 2.8.1 (GTK+ 2.10.11; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_5/ERXWythhIH_1D/DT7qLqV"; protocol="application/pgp-signature"; micalg=PGP-SHA1 Cc: freebsd-fs@freebsd.org, Julian Elischer Subject: Re: ACL's doesn't work with SUIDDIR 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: Sat, 31 Mar 2007 13:31:10 -0000 --Sig_5/ERXWythhIH_1D/DT7qLqV Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Sat, 31 Mar 2007 07:51:27 -0500 (EST) Robert Watson wrote: >=20 > On Tue, 27 Mar 2007, C=E9dric Jonas wrote: >=20 > > On Wed, 21 Mar 2007 11:15:26 -0700 > > Julian Elischer wrote: > > > >> C=E9dric Jonas wrote: > >> > >>> thanks to correct me. > >>> > >>> PS: Please CC me, I'm not on the list. > >> > >> SUIDDIR is probably mot widely used so it may not have ever been > >> tested with ACL (also not widely used) is is possible that you are > >> the first person to have ever tried this combination :-) > >> > >> I suggest that the ACL guys take a look as they i think have some > >> shared code with other OS's which probably don't have SUIDDIR, > >> which is a FreeBSD only option. > > > > Typical for me :-( But however, it seems that I'm not the very > > first one who tries this. I found this in the freebsd-stable > > archive from February 2005: > > > > http://lists.freebsd.org/pipermail/freebsd-stable/2005-February/011786.= html=20 > > http://lists.freebsd.org/pipermail/freebsd-stable/2005-February/011797.= html > > > > It it can help... I also filled in a PR: misc/110915 > > > > Let me know if you need further informations. >=20 > Thanks for this report -- I will try to investigate this issue > sometime this week. Is there a PR files for this currently? >=20 > Thanks, >=20 > Robert N M Watson Thank you. Yes, I filled in a PR: kern/110915. --=20 C=E9dric Jonas cedric@decemplex.net GPG ID: 30CCFE8D GPG Key: http://box.decemplex.net/~cedric/cedric.key.asc GPG Fingerprint: CF03 E1FD 9428 1B6B E971 B107 9044 AA99 30CC FE8D Jabber-ID: cedric@decemplex.net --Sig_5/ERXWythhIH_1D/DT7qLqV Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFGDmKQkESqmTDM/o0RAk4mAJwKDVkEPfwvOkEDqbvwl1qYn+75qQCcDPeI pENmHQSZ7hRS1Mw+PGAXo1o= =ukup -----END PGP SIGNATURE----- --Sig_5/ERXWythhIH_1D/DT7qLqV-- From owner-freebsd-fs@FreeBSD.ORG Sat Mar 31 16:30:05 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 01E0716A40D for ; Sat, 31 Mar 2007 16:30:05 +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 8BEA313C4B0 for ; Sat, 31 Mar 2007 16:30:04 +0000 (UTC) (envelope-from freebsd-fs@m.gmane.org) Received: from root by ciao.gmane.org with local (Exim 4.43) id 1HXgSo-0005a4-Ec for freebsd-fs@freebsd.org; Sat, 31 Mar 2007 18:30:02 +0200 Received: from www.creo.hu ([217.113.62.14]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 31 Mar 2007 18:30:02 +0200 Received: from csaba-ml by www.creo.hu with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 31 Mar 2007 18:30:02 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-fs@freebsd.org From: Csaba Henk Date: Thu, 29 Mar 2007 13:49:43 +0000 (UTC) Lines: 33 Message-ID: References: <4746DA006C148BC0FF1241C6@ganymede.hub.org> <45CCECCB7ECB612F504211F3@ganymede.hub.org> X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: www.creo.hu User-Agent: slrn/0.9.8.1 (FreeBSD) Sender: news Subject: Re: TDFS ... or other distributed file system technologies for FreeBSD? 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: Sat, 31 Mar 2007 16:30:05 -0000 On 2007-03-27, Ivan Voras wrote: > Since FUSE is (L)GPL'ed, chances of getting it into base are slim. Then > there's the question of who would be responsible for it, since the > developer of the FUSE BSD module was also a SoC student and I don't know > if he's interested in maintaining it that way - I'll go ask him. Yep, Ivan asked me so its time for me to chime in. (Thanks for waking me up from my sleeping beauty state.) I think fuse4bsd could and should included into FreeBSD. Why is it not yet there? Those FBSD commiters I talked with gave a positive feedback so the reason is not that anyone had opposed such an addition. The reason is the combination of my perfectionalism and business/laziness. I wanted to achieve certain milestones before asking for having it merged in. I didn't achieve them last year. Now it's time to change strategy. While certain features are missing (and will be for a while), the existing code works well and is not yet bitrotten. So while I might whine to myself about those missing features, the average FUSE based filesystem will run happily with it and I think the average FreeBSD user Joe could be happy with what she gets. To add, much more happier with what is availabe as sysutils/fusefs-kmod from the ports tree -- current fuse4bsd is pretty much superior than version 0.3.0 (the one in ports). So, whom to pester about getting fuse4bsd merged?... Csaba From owner-freebsd-fs@FreeBSD.ORG Sat Mar 31 17:10:59 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E8C9F16A402 for ; Sat, 31 Mar 2007 17:10:59 +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 AC38113C44C for ; Sat, 31 Mar 2007 17:10:59 +0000 (UTC) (envelope-from freebsd-fs@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1HXh6J-0002z9-17 for freebsd-fs@freebsd.org; Sat, 31 Mar 2007 19:10:51 +0200 Received: from www.creo.hu ([217.113.62.14]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 31 Mar 2007 19:10:51 +0200 Received: from csaba-ml by www.creo.hu with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 31 Mar 2007 19:10:51 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-fs@freebsd.org From: Csaba Henk Date: Sat, 31 Mar 2007 17:10:37 +0000 (UTC) Lines: 12 Message-ID: References: <4746DA006C148BC0FF1241C6@ganymede.hub.org> <45CCECCB7ECB612F504211F3@ganymede.hub.org> X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: www.creo.hu User-Agent: slrn/0.9.8.1 (FreeBSD) Sender: news Subject: Re: TDFS ... or other distributed file system technologies for FreeBSD? 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: Sat, 31 Mar 2007 17:11:00 -0000 On 2007-03-27, Ivan Voras wrote: > Since FUSE is (L)GPL'ed, chances of getting it into base are slim. Then Regarding the license issue: the userspace component is LGPL'd but the kernel component is under a BSD style license (this was made possible by re-licensing the header file which defines the kernel/userland protocol under BSDL by FUSE author Miklos Szeredi upon my request). I don't think that adding such components should be a concern to FreeBSD, but YMMV... Csaba