From owner-freebsd-fs@FreeBSD.ORG Sat Jun 10 16:35:42 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3236616A7FE; Sat, 10 Jun 2006 16:35:42 +0000 (UTC) (envelope-from hiroo@oikumene.gcd.org) Received: from smtp2.inetd.co.jp (smtp2.inetd.co.jp [211.13.220.139]) by mx1.FreeBSD.org (Postfix) with ESMTP id 50FE74525D; Sat, 10 Jun 2006 09:31:22 +0000 (GMT) (envelope-from hiroo@oikumene.gcd.org) Received: from chrysanthe.oikumene.gcd.org (206.162.192.61.tokyo.global.alpha-net.ne.jp [61.192.162.206]) by smtp2.inetd.co.jp (Postfix) with ESMTP id 2748EC4EB3; Sat, 10 Jun 2006 18:31:21 +0900 (JST) Received: from chrysanthe.oikumene.gcd.org (mail.oikumene.gcd.org [192.168.0.2]) (authenticated bits=0) by chrysanthe.oikumene.gcd.org (8.13.6/8.13.6) with ESMTP id k5A9VAmS000694; Sat, 10 Jun 2006 18:31:16 +0900 (JST) (envelope-from hiroo@oikumene.gcd.org) Date: Sat, 10 Jun 2006 18:31:10 +0900 Message-ID: <86ver9qrvl.wl%hiroo@oikumene.gcd.org> From: Hiroo Ono To: Alexander Leidinger In-Reply-To: <20060531133814.acykloyqhkcccg80@netchild.homeip.net> References: <43E5D052.3020207@freebsd.org> <43E656C7.8040302@freesbie.org> <43E6D5C8.4050405@freebsd.org> <43E71485.5040901@freesbie.org> <43E73330.8070101@freebsd.org> <43EB4C00.2030101@freebsd.org> <4417DD8D.3050201@freebsd.org> <4433CA53.5050000@freebsd.org> <444E13BA.8050902@freebsd.org> <4475C119.1020305@freebsd.org> <447C919B.20303@freebsd.org> <86bqteikj4.fsf@xps.des.no> <20060531133814.acykloyqhkcccg80@netchild.homeip.net> User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (=?ISO-8859-4?Q?Shij=F2?=) APEL/10.6 Emacs/21.3 (i386--freebsd) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-Mailman-Approved-At: Sun, 11 Jun 2006 00:01:54 +0000 Cc: ozawa@ongs.co.jp, dkirhlarov@oilspace.com, freebsd-hackers@freebsd.org, Daichi GOTO , meianoite@gmail.com, freebsd-fs@freebsd.org, freebsd-current@freebsd.org, kris@obsecurity.org, Dag-Erling =?ISO-8859-1?Q?Sm=F8rgrav?= Subject: Re: [ANN] unionfs patchset-13 release 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, 10 Jun 2006 16:35:42 -0000 At Wed, 31 May 2006 13:38:14 +0200, Alexander Leidinger wrote: > He's not a src-committer and he prefers to let a src-committer do it. > I offered to commit it, but so far either the man-page was missing > (what's the status of this?) or a bug showed up. Daichi and ozawa do not have enough time to write the manual page. I talked with daichi that I will write the manpage update to mount_unionfs.8. My english is not so good, so I think the patch to the manual page I am going to make should be intensively reviewed. I will send it to -fs and -current for review in a few days. From owner-freebsd-fs@FreeBSD.ORG Sun Jun 11 20:01:53 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7D79416A473; Sun, 11 Jun 2006 20:01:53 +0000 (UTC) (envelope-from anderson@centtech.com) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 211AF43D46; Sun, 11 Jun 2006 20:01:50 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [192.168.42.22] (andersonbox2.centtech.com [192.168.42.22]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id k5BK1nrl092952; Sun, 11 Jun 2006 15:01:50 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <448C76B6.9050200@centtech.com> Date: Sun, 11 Jun 2006 15:01:58 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5.0.2 (X11/20060506) MIME-Version: 1.0 To: Robin Elfrink References: <44852CF1.5070300@introweb.nl> <62208.10.20.200.100.1149598242.squirrel@10.20.200.100> <44857BA4.90405@introweb.nl> <56782.10.20.200.100.1149599550.squirrel@10.20.200.100> <4486C4DA.6080905@introweb.nl> <4486D193.3000801@centtech.com> <4486E0F2.8080809@introweb.nl> In-Reply-To: <4486E0F2.8080809@introweb.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1525/Sun Jun 11 10:56:09 2006 on mh2.centtech.com X-Virus-Status: Clean Cc: freebsd-fs@freebsd.org Subject: Re: Recovery from disk+fs crash X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Jun 2006 20:01:53 -0000 Robin Elfrink wrote: > Eric Anderson wrote: > >> Can you run dumpfs on it, and put the output somewhere accessible on the >> web? > > Yes, here it is: > > http://eddy.introweb.nl/~robin/dump/ > > File da0s1f.dump is the output from 'dumpfs /dev/da0s1f', dumpfs.core is > the result of dumpfs dumping core. > > > > Robin Robin, I looked at it, and it looks like the reading of cylindar group 185 is the culprit. Without fsdb usable, it's hard to attempt fixing. I think the routine that attempts to alloc memory needs to be tweaked to recognize ridiculous numbers, but I'm not sure the best way to do it - I suppose for this case, one could just truncate at some ceiling to get past it, but that would definitely be the wrong thing to do, and dangerous too most likely. I've cc'ed the -fs list, and bcc'ed the -isp list, since this is a filesystem issue, and more people with fs-foo will be able to chime in. Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-fs@FreeBSD.ORG Fri Jun 16 07:53:33 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 98D7D16A47A; Fri, 16 Jun 2006 07:53:33 +0000 (UTC) (envelope-from daichi@freebsd.org) Received: from natial.ongs.co.jp (natial.ongs.co.jp [202.216.232.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2D14243D48; Fri, 16 Jun 2006 07:53:30 +0000 (GMT) (envelope-from daichi@freebsd.org) Received: from [192.168.1.101] (dullmdaler.ongs.co.jp [202.216.232.62]) by natial.ongs.co.jp (Postfix) with ESMTP id E68B1244C3A; Fri, 16 Jun 2006 16:53:29 +0900 (JST) Message-ID: <44926377.5000005@freebsd.org> Date: Fri, 16 Jun 2006 16:53:27 +0900 From: Daichi GOTO User-Agent: Thunderbird 1.5.0.4 (X11/20060612) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org, freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Fri, 16 Jun 2006 11:41:06 +0000 Cc: ozawa@ongs.co.jp, dkirhlarov@oilspace.com, daichi@freebsd.org, freebsd-listen@fabiankeil.de, meianoite@gmail.com, kris@obsecurity.org, Alexander@Leidinger.net Subject: [ANN] unionfs patchset-14 release 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, 16 Jun 2006 07:53:33 -0000 Hi Guys! It is my pleasure and honor to announce the availability of the unionfs patchset-14. Patchset-14: For 7-current http://people.freebsd.org/~daichi/unionfs/unionfs-p14.diff For 6.x http://people.freebsd.org/~daichi/unionfs/unionfs6-p14.diff Changes in unionfs-p14.diff - Added a patch of mount_unionfs.8. It means that this patchset is ready to be merged to FreeBSD base system. (hrs contributed it, thanks) - Fixed a problem that sets EXTATTR(ACL, MAC) information to lower layer files and directories. - Removed the third terms of the BSD License to get more easy to handle for FreeBSD. The documents of those unionfs patches: http://people.freebsd.org/~daichi/unionfs/ (English) http://people.freebsd.org/~daichi/unionfs/index-ja.html (Japanese) We think that patchset-14 is ready to be merged to FreeBSD base system with the production level high quality :) Thanks -- Daichi GOTO, http://people.freebsd.org/~daichi From owner-freebsd-fs@FreeBSD.ORG Fri Jun 16 12:15:08 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1510916A479 for ; Fri, 16 Jun 2006 12:15:08 +0000 (UTC) (envelope-from pabmara@fiv.upv.es) Received: from smtp.upv.es (84-123-2-197.onocable.ono.com [84.123.2.197]) by mx1.FreeBSD.org (Postfix) with SMTP id F3A9B43D46 for ; Fri, 16 Jun 2006 12:15:06 +0000 (GMT) (envelope-from pabmara@fiv.upv.es) Received: (qmail 28944 invoked by uid 1000); 16 Jun 2006 12:15:35 -0000 Date: Fri, 16 Jun 2006 14:15:35 +0200 From: Pablo =?iso-8859-1?Q?Mar=EDn_Ram=F3n?= To: freebsd-fs@freebsd.org Message-ID: <20060616121535.GA28485@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: FFS data integrity 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, 16 Jun 2006 12:15:08 -0000 (I didn't know this mailing list and I sent this message to freebsd-questions@ about 2 hours ago. It's more on-topic here, so I crosspost it. Sorry for the inconveniences.) Here goes a newbie question about classical FFS (without softupdates). As metadata is updated synchronously, can an i-node, at some point, end pointing to not written yet data blocks? Is this a security risk, i.e., can those pointed to data blocks pertain to another user's deleted on memory but not deleted on disk data, or that deleted data will be marked in metadata as not initialized and after a crash fsck will fix all i-nodes pointing to it? AFAIK, softupdates and ext3 in the default mode (data=ordered) don't have this problem, but journalling filesystems that journal only metadata do. Is this correct? Thanks in advance. From owner-freebsd-fs@FreeBSD.ORG Fri Jun 16 16:51:36 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 24F5A16A508; Fri, 16 Jun 2006 16:51:36 +0000 (UTC) (envelope-from jhein@timing.com) Received: from Daffy.timing.com (w.timing.com [206.168.13.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id A5E6943D46; Fri, 16 Jun 2006 16:51:35 +0000 (GMT) (envelope-from jhein@timing.com) Received: from gromit.timing.com (gromit.timing.com [206.168.13.209]) by Daffy.timing.com (8.13.1/8.13.1) with ESMTP id k5GGpYRD028652; Fri, 16 Jun 2006 10:51:34 -0600 (MDT) (envelope-from jhein@timing.com) Received: from gromit.timing.com (localhost [127.0.0.1]) by gromit.timing.com (8.13.6/8.13.4) with ESMTP id k5GGpWgX076669; Fri, 16 Jun 2006 10:51:32 -0600 (MDT) (envelope-from jhein@gromit.timing.com) Received: (from jhein@localhost) by gromit.timing.com (8.13.6/8.13.6/Submit) id k5GGpW3g076666; Fri, 16 Jun 2006 10:51:32 -0600 (MDT) (envelope-from jhein) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17554.57748.372948.664580@gromit.timing.com> Date: Fri, 16 Jun 2006 10:51:32 -0600 From: John Hein To: Daichi GOTO In-Reply-To: <44926377.5000005@freebsd.org> References: <44926377.5000005@freebsd.org> X-Mailer: VM 7.19 under Emacs 21.3.1 X-Virus-Scanned: ClamAV version 0.87.1, clamav-milter version 0.87 on Daffy.timing.com X-Virus-Status: Clean Cc: freebsd-fs@freebsd.org Subject: Re: [ANN] unionfs patchset-14 release 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, 16 Jun 2006 16:51:36 -0000 At first I looked at fixing the wording for the deprecation of -r like so: --- mount_unionfs.c.patchset-14 Fri Jun 16 10:27:35 2006 +++ mount_unionfs.c Fri Jun 16 10:23:00 2006 @@ -95,8 +95,8 @@ switch (ch) { case 'r': errno = EOPNOTSUPP; - perror("option '-r' cannot already be used." - "you should use nullfs instead."); + perror("Option '-r' is no longer available. " + "You should use nullfs instead"); break; case 'b': iov[iovcnt].iov_base = "below"; But then I thought that it would be even better to just drop it altogether (and perhaps add a note to UPDATING) like so: --- mount_unionfs.c.patchset-14 Fri Jun 16 10:27:35 2006 +++ mount_unionfs.c Fri Jun 16 10:30:41 2006 @@ -91,13 +91,8 @@ iovcnt = 6; mntflags = 0; - while ((ch = getopt(argc, argv, "brc:o:m:M:u:g:")) != -1) { + while ((ch = getopt(argc, argv, "bc:o:m:M:u:g:")) != -1) { switch (ch) { - case 'r': - errno = EOPNOTSUPP; - perror("option '-r' cannot already be used." - "you should use nullfs instead."); - break; case 'b': iov[iovcnt].iov_base = "below"; iov[iovcnt].iov_len = strlen(iov[iovcnt].iov_base) + 1; Then reword the text in the man page about the deprecation. It's wrong anyway since it says -r is available for "backward compatibility". To reflect the patchset-14 version accurately, it should really say that it is ignored. I would just remove -r from mount_unionfs.c. Then, in the man page, perhaps move the discussion about its removal to the HISTORY section (in addition to some brief words about this rewrite as an evolutionary milestone). Thanks for the good work.