From owner-freebsd-fs Mon Nov 18 11: 0:32 2002 Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 97CE637B409 for ; Mon, 18 Nov 2002 11:00:31 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 65B4743EFA for ; Mon, 18 Nov 2002 11:00:18 -0800 (PST) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.6/8.12.6) with ESMTP id gAIJ0Ix3076811 for ; Mon, 18 Nov 2002 11:00:18 -0800 (PST) (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.12.6/8.12.6/Submit) id gAIJ0IGD076809 for fs@freebsd.org; Mon, 18 Nov 2002 11:00:18 -0800 (PST) Date: Mon, 18 Nov 2002 11:00:18 -0800 (PST) Message-Id: <200211181900.gAIJ0IGD076809@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: fs@FreeBSD.org Subject: Current problem reports assigned to you Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Mon Nov 18 11: 7:49 2002 Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1060E37B404 for ; Mon, 18 Nov 2002 11:07:49 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id ACFC443E42 for ; Mon, 18 Nov 2002 11:07:48 -0800 (PST) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.6/8.12.6) with ESMTP id gAIJ7mx3085762 for ; Mon, 18 Nov 2002 11:07:48 -0800 (PST) (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.12.6/8.12.6/Submit) id gAIJ7l37085751 for fs@freebsd.org; Mon, 18 Nov 2002 11:07:47 -0800 (PST) Date: Mon, 18 Nov 2002 11:07:47 -0800 (PST) Message-Id: <200211181907.gAIJ7l37085751@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: fs@FreeBSD.org Subject: Current problem reports assigned to you Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Current FreeBSD problem reports Critical problems Serious problems Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- a [2000/10/06] kern/21807 fs [patches] Make System attribute correspon 1 problem total. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Wed Nov 20 7:32:20 2002 Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9A51337B401 for ; Wed, 20 Nov 2002 07:32:19 -0800 (PST) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B36843E42 for ; Wed, 20 Nov 2002 07:32:18 -0800 (PST) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.12.6/8.12.5) with SMTP id gAKFWFBF043624 for ; Wed, 20 Nov 2002 10:32:16 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Wed, 20 Nov 2002 10:32:15 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: freebsd-fs@FreeBSD.org Subject: FREENIX 2003 official deadline extension (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Since we've gotten a lot of good FreeBSD-based file system papers for FREENIX and USENIX ATC in the past, I figured I'd forward this over to freebsd-fs and see if anyone was interested. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories ---------- Forwarded message ---------- Date: Tue, 19 Nov 2002 20:09:57 +0100 From: Guido van Rooij To: freebsd-announce@freebsd.org Subject: FREENIX 2003 official deadline extension Hi, this is to notify you that we have officially extended the submission deadline for FREENIX 2003 by seven more days. The new deadline is Monday, 11/25/2002, 11:59pm EST. FreeNIX is a very nice opportunity to inform the world about cool developments going on in the FreeBSD world! You do not have to have a full paper ready by this time: an extended abstract is enough. Please look at http://www.usenix.org/events/usenix03/cfp/freenix-2003-ea.html for what a good extended abstract should contain. See http://www.usenix.org/events/usenix03/cfp/freenix.html for more information on the FreeNIX refereed track. -Guido This is the moderated mailing list freebsd-announce. The list contains announcements of new FreeBSD capabilities, important events and project milestones. See also the FreeBSD Web pages at http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-announce" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Wed Nov 20 21:25:24 2002 Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1DE8E37B401 for ; Wed, 20 Nov 2002 21:25:23 -0800 (PST) Received: from beastie.mckusick.com (beastie.mckusick.com [209.31.233.184]) by mx1.FreeBSD.org (Postfix) with ESMTP id CEC2643E42 for ; Wed, 20 Nov 2002 21:25:21 -0800 (PST) (envelope-from mckusick@beastie.mckusick.com) Received: from beastie.mckusick.com (localhost [127.0.0.1]) by beastie.mckusick.com (8.12.3/8.12.3) with ESMTP id gAL5PG59058300; Wed, 20 Nov 2002 21:25:16 -0800 (PST) (envelope-from mckusick@beastie.mckusick.com) Message-Id: <200211210525.gAL5PG59058300@beastie.mckusick.com> To: Alfred Perlstein Subject: Re: snapshots+dump/restore Cc: fs@freebsd.org, Poul-Henning Kamp In-Reply-To: Your message of "Mon, 04 Nov 2002 00:34:53 PST." <20021104083453.GR24139@elvis.mu.org> Date: Wed, 20 Nov 2002 21:25:16 -0800 From: Kirk McKusick Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Date: Mon, 4 Nov 2002 00:34:53 -0800 From: Alfred Perlstein To: fs@freebsd.org Cc: Kirk McKusick , Poul-Henning Kamp Subject: snapshots+dump/restore I'm cc'ing the those most involved with the current code. When taking a dump(8) on a ufs filesystem with a snapshot node the dump grabs the snapshot file and trys to dump it, shouldn't some flag or something be set on the file that tells dump(8) to skip over it? If the semantics can be agreed on I can take a shot at implementing a fix/workaround/whatever. I particularly think that dump should _never_ try to grab a .fsck_snapshot file. Comments/suggestions? -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' You are correct. Dump should never try to dump a snapshot. Rather it should just put the inode on the tape as a zero length regular file (much as snapshots do if you try to look at other snapshots contained within them). You cannot just skip the inode entirely because that would require you to find all the directory entries that point at that inode and delete them which would be a lot more work). I have added the skipping over of snapshot inodes in dump to my TODO list. Kirk McKusick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Thu Nov 21 8:56: 5 2002 Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0E7E737B401 for ; Thu, 21 Nov 2002 08:56:04 -0800 (PST) Received: from digitas.harvard.edu (digitas.eecs.harvard.edu [140.247.60.248]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6AFF743E6E for ; Thu, 21 Nov 2002 08:56:03 -0800 (PST) (envelope-from jecarrol@digitas.harvard.edu) Received: from digitas.harvard.edu (localhost [127.0.0.1]) by digitas.harvard.edu (8.12.6/8.12.6) with ESMTP id gALGtspp011359 for ; Thu, 21 Nov 2002 11:55:54 -0500 (EST) (envelope-from jecarrol@digitas.harvard.edu) Received: from localhost (jecarrol@localhost) by digitas.harvard.edu (8.12.6/8.12.6/Submit) with ESMTP id gALGtsXC011356 for ; Thu, 21 Nov 2002 11:55:54 -0500 (EST) (envelope-from jecarrol@digitas.harvard.edu) Date: Thu, 21 Nov 2002 11:55:54 -0500 (EST) From: Jason Carroll To: freebsd-fs@freebsd.org Subject: Maximum filesystem size Message-ID: <20021121110057.U11066-100000@digitas.harvard.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi everyone-- Paul Anderson posed this question on the list several months ago, but I didn't see an answer to it. I'm interested in creating a filesystem larger than the 1 terabyte "soft limit" indicated in the FreeBSD FAQ (question 3.29). The FAQ claims: "For ffs filesystems, the maximum theoretical limit is 8 terabytes (2G blocks), or 16TB for the default block size of 8K. In practice, there is a soft limit of 1 terabyte, but with modifications filesystems with 4 terabytes are possible (and exist)." Anyone have any experience with this or know what modifications this might entail? I'd also like to hear anyone's thoughts on what kind of problems (performance or more serious) might be created with such a large filesystem. In more detail, I'm trying to create a 2TB filesystem on an external SCSI disk array. I believe SCSI has a 2TB limit which I'm trying to get as close as possible to. Thanks, Jason Carroll To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Thu Nov 21 14:18:10 2002 Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4938D37B401 for ; Thu, 21 Nov 2002 14:18:09 -0800 (PST) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id B72A743E42 for ; Thu, 21 Nov 2002 14:18:08 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.12.6/8.12.6) id gALMI3YB086559 for freebsd-fs@freebsd.org; Thu, 21 Nov 2002 16:18:03 -0600 (CST) (envelope-from dan) Date: Thu, 21 Nov 2002 16:18:03 -0600 From: Dan Nelson To: freebsd-fs@freebsd.org Subject: Should mkdir() inherit setgid? Message-ID: <20021121221802.GE86807@dan.emsphone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-OS: FreeBSD 5.0-CURRENT X-message-flag: Outlook Error User-Agent: Mutt/1.5.1i Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I've got a bunch of systems NFS mounting some FreeBSD servers, and to manage write access to directories, I chgrp the directory and set the setgid bit to ensure that files created from Solaris, Tru64, and Linux boxes get the correct group ownership. This works great, except when the users create subdirectories. The directory itself gets the right group id, but does not inherit the setgid bit so any files created in the subdir have the wrong group permissions. Should we make newly-created directories inherit the setgid bit from their parent? Since FreeBSD doesn't use setgid on directories anyway, it shouldn't cause any harm. -- Dan Nelson dnelson@allantgroup.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Fri Nov 22 16:50:14 2002 Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D15D637B401 for ; Fri, 22 Nov 2002 16:50:13 -0800 (PST) Received: from sccrmhc02.attbi.com (sccrmhc02.attbi.com [204.127.202.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id 469CF43EAF for ; Fri, 22 Nov 2002 16:50:13 -0800 (PST) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org (12-232-168-4.client.attbi.com[12.232.168.4]) by sccrmhc02.attbi.com (sccrmhc02) with ESMTP id <2002112300500100200t4vqqe>; Sat, 23 Nov 2002 00:50:02 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id QAA17009; Fri, 22 Nov 2002 16:48:04 -0800 (PST) Date: Fri, 22 Nov 2002 16:48:03 -0800 (PST) From: Julian Elischer To: fs@freebsd.org Cc: mckusick@mckusick.com Subject: ufs types Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org We had a system on site today that fell over every time re tried to boot it. Causing delays in probably many millions of dollars of transfers. The reason was a currupt word in the cylinder group summary information. a word had been trashed becoming -ve, and fsck didn't check against -ve numbers in that (a rotor value). Noticing that most fields are not checked against being -ve in fsck we started looking at fixing it.. until we realised that the far quicker answer was to define them to be unsigned in ufs.h and just fix the compile errors.. The values are usually checked for reasonable +ve values. Does anyone have a reason why we should not do this in FreeBSD? (fix the superblock and cg summary blocks to have mostly unsigned values..) julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Fri Nov 22 17:14:22 2002 Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7286237B401 for ; Fri, 22 Nov 2002 17:14:21 -0800 (PST) Received: from smtp.goamerica.net (ny-mx-01.goamerica.net [208.200.67.108]) by mx1.FreeBSD.org (Postfix) with ESMTP id A770B43E4A for ; Fri, 22 Nov 2002 17:14:20 -0800 (PST) (envelope-from eaja@erols.com) Received: from vzw-166-141-30-165.airbridge.net (vzw-166-141-30-165.airbridge.net [166.141.30.165] (may be forged)) by smtp.goamerica.net (8.12.4/8.12.4) with ESMTP id gAN1DDBj029844; Fri, 22 Nov 2002 20:13:19 -0500 (EST) Message-Id: <200211230113.gAN1DDBj029844@smtp.goamerica.net> Date: Fri, 22 Nov 2002 20:13:08 -0500 From: Eric Jacobs To: Julian Elischer , fs@freebsd.org Subject: Re: ufs types Reply-To: eaja@erols.com In-Reply-To: References: X-Mailer: Spruce 0.7.6 for X11 w/smtpio 0.9.0 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I put this bug in on July 17. It's still open. Problem Report bin/40697 fsck[_ffs](8) doesn't ensure that (signed) cylinder group rotor values are non-negative I considered it a bug in fsck and included a patch. Eric On Fri, 22 Nov 2002, Julian Elischer wrote: > Date: Fri, 22 Nov 2002 16:48:03 -0800 (PST) > To: fs@freebsd.org > From: Julian Elischer > CC: mckusick@mckusick.com > Sender: owner-freebsd-fs@freebsd.org > Subject: ufs types > > > > We had a system on site today that fell over every time re tried to boot > it. Causing delays in probably many millions of dollars of transfers. > The reason was a currupt word in the cylinder group summary information. > a word had been trashed becoming -ve, and fsck didn't check against > -ve numbers in that (a rotor value). Noticing that most fields are not > checked against being -ve in fsck we started looking at fixing it.. > until we realised that the far quicker answer was to define them to be > unsigned in ufs.h and just fix the compile errors.. The values are > usually checked for reasonable +ve values. > > > Does anyone have a reason why we should not do this in FreeBSD? > > > (fix the superblock and cg summary blocks to have mostly unsigned > values..) > > > julian > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-fs" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message