From owner-freebsd-fs Mon Aug 27 2:34:55 2001 Delivered-To: freebsd-fs@freebsd.org Received: from synology.com (dns1.synology.com [202.173.37.131]) by hub.freebsd.org (Postfix) with ESMTP id 0806037B410 for ; Mon, 27 Aug 2001 02:34:45 -0700 (PDT) (envelope-from rexluo@synology.com) Received: from synology.com (IDENT:nobody@localhost [127.0.0.1]) by synology.com (8.9.3/8.9.3) with SMTP id RAA13906 for freebsd-fs@FreeBSD.ORG; Mon, 27 Aug 2001 17:36:29 +0800 Date: Mon, 27 Aug 2001 17:36:29 +0800 Message-Id: <200108270936.RAA13906@synology.com> To: freebsd-fs@FreeBSD.ORG Subject: quick question: softupdate - metadata logging & data logging? From: Rex Luo X-Mailer: TWIG 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 Dear, Sorry to not survey thoroughly, and maybe someone can give me some information quickly. Since Filesystem logging can be 3 common forms:(Solaris interinals Core Kernel Architecture Jim Mauro. Richard McDougall) 1. Metadata logging -- logs only file system structure changes 2. File and metadata loggging -- Logs all changes to the filesystem 3. Log-structured file system -- The entire file system is implemented as a log I remember I have seem on mailinglist that FFS with softupdate has similar function as journal filesystem. What kind of journal filesystem it can be? or I am totally wrong. Thanks -- -- Rex Luo Tel : 886-2-25521814 Ext. 824 Fax : 886-2-25521824 e-mail : rexluo@synology.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Mon Aug 27 6:36:37 2001 Delivered-To: freebsd-fs@freebsd.org Received: from torb.pix.net (torb.pix.net [192.135.81.20]) by hub.freebsd.org (Postfix) with ESMTP id 496DF37B430 for ; Mon, 27 Aug 2001 06:36:22 -0700 (PDT) (envelope-from stripes@iamsofired.com) Received: (from stripes@localhost) by torb.pix.net (8.11.4/8.11.4) id f7RDaCN18476; Mon, 27 Aug 2001 09:36:12 -0400 (EDT) (envelope-from stripes@iamsofired.com) X-Authentication-Warning: torb.pix.net: stripes set sender to stripes@iamsofired.com using -f Date: Mon, 27 Aug 2001 09:36:12 -0400 From: Josh M Osborne To: Rex Luo Cc: freebsd-fs@FreeBSD.ORG Subject: Re: quick question: softupdate - metadata logging & data logging? Message-ID: <20010827093612.A18455@torb.pix.net> References: <200108270936.RAA13906@synology.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200108270936.RAA13906@synology.com>; from rexluo@synology.com on Mon, Aug 27, 2001 at 05:36:29PM +0800 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 On Mon, Aug 27, 2001 at 05:36:29PM +0800, Rex Luo wrote: [...] > 1. Metadata logging -- logs only file system structure changes > 2. File and metadata loggging -- Logs all changes to the filesystem > 3. Log-structured file system -- The entire file system is implemented as a log > > I remember I have seem on mailinglist that FFS with softupdate has similar > function as journal filesystem. What kind of journal filesystem it can be? > or I am totally wrong. [...] None of the above, it doesn't log. It carefully orders the writes into the normal filesystem. Actually it does a little more, the data it writes out is sometimes different from the current in-memory state (but consistent with a historical state that the other on disk data represents -- or maybe a non-historical state, I'm not 100% clear on that). I believe it has consistency traits similar to #1 above, but not a bounded recovery time. In FreeBSD 5 checkpoints are being added which give a bounded system restart time, and the recovery can be done in the background. For some definitions of "logging" that might be thought of as #3 or #2 above, but only when a checkpoint is active. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Mon Aug 27 8:28:48 2001 Delivered-To: freebsd-fs@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 4A5DB37B406 for ; Mon, 27 Aug 2001 08:28:45 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.5/8.11.5) with SMTP id f7RFSZP42061; Mon, 27 Aug 2001 11:28:35 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Mon, 27 Aug 2001 11:28:35 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Rex Luo Cc: freebsd-fs@FreeBSD.ORG Subject: Re: quick question: softupdate - metadata logging & data logging? In-Reply-To: <200108270936.RAA13906@synology.com> 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 Take a look at: http://www.usenix.org/publications/library/proceedings/usenix2000/general/seltzer.html This paper by Seltzer, et al, compares the semantics and performance of journalling and soft updates, and was presented at USENIX in 2000. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services On Mon, 27 Aug 2001, Rex Luo wrote: > Dear, > > Sorry to not survey thoroughly, and maybe someone can give me some information > quickly. > > Since Filesystem logging can be 3 common forms:(Solaris interinals Core Kernel > Architecture Jim Mauro. Richard McDougall) > > 1. Metadata logging -- logs only file system structure changes > 2. File and metadata loggging -- Logs all changes to the filesystem > 3. Log-structured file system -- The entire file system is implemented as a log > > I remember I have seem on mailinglist that FFS with softupdate has similar > function as journal filesystem. What kind of journal filesystem it can be? > or I am totally wrong. > > Thanks > > -- > > -- Rex Luo > > Tel : 886-2-25521814 Ext. 824 > Fax : 886-2-25521824 > e-mail : rexluo@synology.com > > > > 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 From owner-freebsd-fs Mon Aug 27 18:50:24 2001 Delivered-To: freebsd-fs@freebsd.org Received: from mail.nipsi.de (dsl-213-023-032-019.arcor-ip.net [213.23.32.19]) by hub.freebsd.org (Postfix) with SMTP id 4F29437B407 for ; Mon, 27 Aug 2001 18:50:19 -0700 (PDT) (envelope-from HypnotiZer@gmx.net) Received: (qmail 50577 invoked from network); 21 Aug 2001 09:21:58 -0000 Received: from nachpolierer.home.net (HELO nachpolierer) (172.16.1.101) by 172.16.1.1 with SMTP; 21 Aug 2001 09:21:58 -0000 Message-ID: <000701c12a22$c4a84020$650110ac@nachpolierer> From: "Dennis Berger" To: Subject: Fw: [gfs-users] current state of GFS for FreeBSD ? Date: Tue, 21 Aug 2001 11:22:15 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 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 ----- Original Message ----- From: "Andrew Barry" To: "Dennis Berger" Cc: Sent: Monday, August 20, 2001 8:26 PM Subject: Re: [gfs-users] current state of GFS for FreeBSD ? > This port is still on hold as there are currently other items of higher > priority to face. If we discover that there is great demand for GFS on BSD > it will be bumped up to higher priority. Thanks for your interest. > > Andrew Barry > barry@sistina.com > > On Mon, 20 Aug 2001, Dennis Berger wrote: > > > Hi I saw the latest info a while ago from 15 june, where this port was on > > hold. > > What is the current state ? > > > > _______________________________________________ > > gfs-users mailing list > > gfs-users@sistina.com > > http://lists.sistina.com/mailman/listinfo/gfs-users > > Read the GFS Howto: http://www.sistina.com/gfs/Pages/howto.html > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Wed Aug 29 13:36:10 2001 Delivered-To: freebsd-fs@freebsd.org Received: from obsecurity.dyndns.org (adsl-63-207-60-54.dsl.lsan03.pacbell.net [63.207.60.54]) by hub.freebsd.org (Postfix) with ESMTP id 9664437B403; Wed, 29 Aug 2001 13:36:03 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 30CCE66E42; Wed, 29 Aug 2001 13:36:03 -0700 (PDT) Date: Wed, 29 Aug 2001 13:36:03 -0700 From: Kris Kennaway To: Chris Pockele Cc: Kris Kennaway , freebsd-gnats-submit@FreeBSD.org, fs@FreeBSD.org Subject: Re: misc/30168: 4-stable, crash when writing to msdos fs Message-ID: <20010829133603.C75228@xor.obsecurity.org> References: <3B8CBCAB.97D88562@belgacom.net> <20010829031921.A69280@xor.obsecurity.org> <3B8CD565.A4A52CC6@belgacom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3B8CD565.A4A52CC6@belgacom.net>; from chrisp@belgacom.net on Wed, Aug 29, 2001 at 01:43:33PM +0200 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 On Wed, Aug 29, 2001 at 01:43:33PM +0200, Chris Pockele wrote: > > That's still not a traceback..please try and obtain that. > > > Here is the output of > > gdb -k /sys/compile/DEBUG/kernel.debug /var/crash/vmcore.1 Thanks, that was what's needed. Now to find an msdosfs guru to debug this :) Kris > > (kgdb) where > > ---- > Script started on Wed Aug 29 13:34:24 2001 > freedaemon# gdb -k /sys/compile/DEBUG/kernel.debug > /var/crash/vmESC[Kcore.1^M > GNU gdb 4.18 > Copyright 1998 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you > are > welcome to change it and/or distribute copies of it under certain > conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for > details. > This GDB was configured as "i386-unknown-freebsd"... > IdlePTD 4874240 > initial pcb at 3ee7e0 > panicstr: page fault > panic messages: > --- > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0xe0f6effc > fault code = supervisor read, page not present > instruction pointer = 0x8:0xc01f8dd3 > stack pointer = 0x10:0xc8565d14 > frame pointer = 0x10:0xc8565d24 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 273 (cp) > interrupt mask = none > trap number = 12 > panic: page fault > > syncing disks... 46 2 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 > 1: dev:#ad/0x60002, flags:00100020, blkno:8344, lblkno:8344 > giving up on 1 buffers > Uptime: 37s > > dumping to dev #ad/0x30001, offset 269872 > dump ata0: resetting devices .. done > 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 > 110 109 > 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 > 87 86 85 > 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 > 60 59 5 > 8 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 > 34 33 32 > 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 > 6 5 4 3 > 2 1 > --- > #0 dumpsys () at ../../kern/kern_shutdown.c:473 > 473 if (dumping++) { > (kgdb) where > #0 dumpsys () at ../../kern/kern_shutdown.c:473 > #1 0xc01bda74 in boot (howto=256) at ../../kern/kern_shutdown.c:313 > #2 0xc01bde54 in poweroff_wait (junk=0xc03a07ea, howto=-1069939985) > at ../../kern/kern_shutdown.c:581 > #3 0xc03339c3 in trap_fatal (frame=0xc8565cd4, eva=3774279676) > at ../../i386/i386/trap.c:956 > #4 0xc033367d in trap_pfault (frame=0xc8565cd4, usermode=0, > eva=3774279676) > at ../../i386/i386/trap.c:849 > #5 0xc03331e7 in trap (frame={tf_fs = -933887984, tf_es = -1071775728, > tf_ds = -933625840, tf_edi = 8344, tf_esi = -1057558528, > tf_ebp = -933864156, tf_isp = -933864192, tf_ebx = -1057562624, > tf_edx = 134217727, tf_ecx = 31, tf_eax = -2147483648, tf_trapno = > 12, > tf_err = 0, tf_eip = -1071673901, tf_cs = 8, tf_eflags = 66182, > tf_esp = 268435455, tf_ss = 268435455}) at > ../../i386/i386/trap.c:448 > #6 0xc01f8dd3 in updatefats (pmp=0xc0f6e000, bp=0xc3703284, fatbn=8344) > at ../../msdosfs/msdosfs_fat.c:353 > #7 0xc01f947e in fatchain (pmp=0xc0f6e000, start=1064363, count=0, > fillwith=4294967295) at ../../msdosfs/msdosfs_fat.c:674 > #8 0xc01f959a in chainalloc (pmp=0xc0f6e000, start=1064363, count=1, > fillwith=4294967295, retcluster=0xc8565df0, got=0xc8565dec) > at ../../msdosfs/msdosfs_fat.c:748 > #9 0xc01f979a in clusteralloc (pmp=0xc0f6e000, start=0, count=1, > fillwith=4294967295, retcluster=0xc8565df0, got=0xc8565dec) > at ../../msdosfs/msdosfs_fat.c:842 > ---Type to continue, or q to quit--- > #10 0xc01f9c2a in extendfile (dep=0xc0f5c400, count=1, bpp=0x0, ncp=0x0, > flags=0) at ../../msdosfs/msdosfs_fat.c:1034 > #11 0xc01fcf0e in msdosfs_write (ap=0xc8565e78) > at ../../msdosfs/msdosfs_vnops.c:725 > #12 0xc01f28a2 in vn_write (fp=0xc0f69bc0, uio=0xc8565ee4, > cred=0xc0f64600, > flags=0, p=0xc7b665e0) at vnode_if.h:363 > #13 0xc01cc93a in dofilewrite (p=0xc7b665e0, fp=0xc0f69bc0, fd=4, > buf=0x28058000, nbyte=187, offset=-1, flags=0) at > ../../sys/file.h:162 > #14 0xc01cc7eb in write (p=0xc7b665e0, uap=0xc8565f80) > at ../../kern/sys_generic.c:329 > #15 0xc0333c39 in syscall2 (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, > tf_edi = 671449088, tf_esi = 671449088, tf_ebp = -1077937572, > tf_isp = -933863468, tf_ebx = 187, tf_edx = 4, tf_ecx = 1, tf_eax > = 4, > tf_trapno = 12, tf_err = 2, tf_eip = 134561808, tf_cs = 31, > tf_eflags = 663, tf_esp = -1077937632, tf_ss = 47}) > at ../../i386/i386/trap.c:1155 > #16 0xc0324d75 in Xint0x80_syscall () > #17 0x8048989 in ?? () > #18 0x804851a in ?? () > #19 0x8048135 in ?? () > (kgdb) exit > Undefined command: "exit". Try "help". > (kgdb) quit > freedaemon# exit > > Script done on Wed Aug 29 13:35:00 2001 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Thu Aug 30 4:44:28 2001 Delivered-To: freebsd-fs@freebsd.org Received: from tao.org.uk (genesis.tao.org.uk [212.135.162.62]) by hub.freebsd.org (Postfix) with ESMTP id A832F37B40A; Thu, 30 Aug 2001 04:44:20 -0700 (PDT) (envelope-from joe@tao.org.uk) Received: by tao.org.uk (Postfix, from userid 100) id 1F7A554A; Thu, 30 Aug 2001 12:44:19 +0100 (BST) Date: Thu, 30 Aug 2001 12:44:19 +0100 From: Josef Karthauser To: Robert Watson Cc: freebsd-fs@FreeBSD.ORG Subject: Re: parsing problem with /proc/N/status Message-ID: <20010830124419.C5602@tao.org.uk> References: <20010817102549.A712@tao.org.uk> <20010822083921.A1147@tao.org.uk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="xo44VMWPx7vlQ2+2" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010822083921.A1147@tao.org.uk>; from joe@tao.org.uk on Wed, Aug 22, 2001 at 08:39:21AM +0100 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 --xo44VMWPx7vlQ2+2 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Aug 22, 2001 at 08:39:21AM +0100, Josef Karthauser wrote: > On Sun, Aug 19, 2001 at 11:09:35PM -0400, Robert Watson wrote: > >=20 > > I guess my feeling is that fundamentally, this type of process data is > > "typed" as a nul-terminated string. procfs fails to export all types > > safely (i.e., unambiguously), including nul-terminated strings. I supp= ose > > really, the kernel should export in ASN.1... (run away)=20 > >=20 > > Actually, the right answer is probably simply to use sysctl to get this > > type of process information, since the results actually do have types > > respected by the medium.=20 >=20 > Accepted, but we do support procfs/status as a method too otherwise we > wouldn't implement it. >=20 > The procfs manual page says: >=20 > status The process status. This file is read-only and returns a si= ngle > line containing multiple space-separated fields as follows: > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [cut] > This suggests that whatever we do in addition the minimum is to ensure > that 'command name' doesn't contain spaces. If we're not going to > replace them with underscores, for example, what are we going to replace > them with? Does anyone have a strong opinion on this? If not I'm going to make this functional change. Joe --xo44VMWPx7vlQ2+2 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjuOJxIACgkQXVIcjOaxUBZoGQCeNrXyyTP4N6SYhlMsO88JqYOl niMAoKKdo7gODchMKEuF3YeKdbnXF8as =Vby1 -----END PGP SIGNATURE----- --xo44VMWPx7vlQ2+2-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Thu Aug 30 7:29:31 2001 Delivered-To: freebsd-fs@freebsd.org Received: from bigglesworth.mail.be.easynet.net (bigglesworth.mail.be.easynet.net [212.100.160.67]) by hub.freebsd.org (Postfix) with ESMTP id 7A86C37B407; Thu, 30 Aug 2001 07:29:20 -0700 (PDT) (envelope-from chrisp@belgacom.net) Received: from 212-100-182-44.adsl.easynet.be ([212.100.182.44] helo=belgacom.net) by bigglesworth.mail.be.easynet.net with esmtp (Exim 3.16 #1) id 15cSpw-0004tY-00; Thu, 30 Aug 2001 16:30:28 +0200 Message-ID: <3B8E4CA0.2688C566@belgacom.net> Date: Thu, 30 Aug 2001 16:24:32 +0200 From: Chris Pockele X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Kris Kennaway Cc: freebsd-gnats-submit@FreeBSD.org, fs@FreeBSD.org Subject: Re: misc/30168: 4-stable, crash when writing to msdos fs References: <3B8CBCAB.97D88562@belgacom.net> <20010829031921.A69280@xor.obsecurity.org> <3B8CD565.A4A52CC6@belgacom.net> <20010829133603.C75228@xor.obsecurity.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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 Kris Kennaway wrote: > > On Wed, Aug 29, 2001 at 01:43:33PM +0200, Chris Pockele wrote: > > > That's still not a traceback..please try and obtain that. > > > some "phenomenon" i observed today: I compiled a kernel without MSDOSFS support included, so msdos.ko is now loaded when mounting the partition. Now it does NOT crash when trying to write a file. Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message