From owner-freebsd-fs Sun Feb 24 14:44:32 2002 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 1191F37B404; Sun, 24 Feb 2002 14:44:24 -0800 (PST) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.5) with SMTP id g1OMiED95247; Sun, 24 Feb 2002 17:44:15 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Sun, 24 Feb 2002 17:44:14 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Dag-Erling Smorgrav Cc: freebsd-fs@freebsd.org, doc@freebsd.org Subject: Re: maximum filesystem size In-Reply-To: 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 I've taken David out of the CC list. This FAQ entry probably needs updating: it talks about 2.2.7-STABLE and 3.0-CURRENT. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services On 22 Feb 2002, Dag-Erling Smorgrav wrote: > David Dougall writes: > > What is the largest filesystem that the freebsd kernel can support? > > I am not on the list. Please reply directly. > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/install.html#FFS-LIMITS > > Do a minimum amount of research yourself next time. > > DES > -- > Dag-Erling Smorgrav - des@ofug.org > > 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 Sun Feb 24 17:28:49 2002 Delivered-To: freebsd-fs@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id 2B54937B400; Sun, 24 Feb 2002 17:28:44 -0800 (PST) Received: (from mwlucas@localhost) by blackhelicopters.org (8.11.6/8.11.6) id g1P1Shb47346; Sun, 24 Feb 2002 20:28:43 -0500 (EST) (envelope-from mwlucas) Date: Sun, 24 Feb 2002 20:28:43 -0500 From: Michael Lucas To: Robert Watson Cc: Dag-Erling Smorgrav , freebsd-fs@FreeBSD.ORG, doc@FreeBSD.ORG Subject: Re: maximum filesystem size Message-ID: <20020224202843.A47334@blackhelicopters.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from rwatson@FreeBSD.ORG on Sun, Feb 24, 2002 at 05:44:14PM -0500 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 That would be good... is the info correct, except the version number? On Sun, Feb 24, 2002 at 05:44:14PM -0500, Robert Watson wrote: > > I've taken David out of the CC list. This FAQ entry probably needs > updating: it talks about 2.2.7-STABLE and 3.0-CURRENT. > > > Robert N M Watson FreeBSD Core Team, TrustedBSD Project > robert@fledge.watson.org NAI Labs, Safeport Network Services > > On 22 Feb 2002, Dag-Erling Smorgrav wrote: > > > David Dougall writes: > > > What is the largest filesystem that the freebsd kernel can support? > > > I am not on the list. Please reply directly. > > > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/install.html#FFS-LIMITS > > > > Do a minimum amount of research yourself next time. > > > > DES > > -- > > Dag-Erling Smorgrav - des@ofug.org > > > > 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 -- Michael Lucas mwlucas@FreeBSD.org, mwlucas@BlackHelicopters.org my FreeBSD column: http://www.oreillynet.com/pub/q/Big_Scary_Daemons http://www.blackhelicopters.org/~mwlucas/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Mon Feb 25 1:40:35 2002 Delivered-To: freebsd-fs@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-169-107-10.dsl.lsan03.pacbell.net [64.169.107.10]) by hub.freebsd.org (Postfix) with ESMTP id 2BF0137B404; Mon, 25 Feb 2002 01:40:29 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 986EE66C76; Mon, 25 Feb 2002 01:40:28 -0800 (PST) Date: Mon, 25 Feb 2002 01:40:28 -0800 From: Kris Kennaway To: mckusick@mckusick.com, fs@FreeBSD.org, dillon@FreeBSD.org Subject: UFS panic on -stable Message-ID: <20020225014028.A53147@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="FCuugMFkClbJLl1L" Content-Disposition: inline User-Agent: Mutt/1.2.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 --FCuugMFkClbJLl1L Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Since upgrading the ports cluster to 4.5 I've been seeing a lot of UFS panics (about one a day, over the 8 client machines). I upgraded the kernels yesterday to try and fix this, but one of them panicked again today. I managed to capture one of the panics, and I have the core. Is there anything else I can provide? Kris panicstr: from debugger panic messages: --- panic: ffs_vfree: freeing free inode panic: from debugger Uptime: 11h44m29s dumping to dev #ad/1, offset 1575424 dump ata0: resetting devices .. done 254 253 252 251 250 249 248 247 246 245 244 243 242 241 240 239 238 237 236 235 234 233 232 231 230 229 228 227 226 225 224 223 222 221 220 219 218 217 216 215 214 213 212 211 210 209 208 207 206 205 204 203 202 201 200 199 198 197 196 195 194 193 192 191 190 189 188 187 186 185 184 183 182 181 180 179 178 177 176 175 174 173 172 171 170 169 168 167 166 165 164 163 162 161 160 159 158 157 156 155 154 153 152 151 150 149 148 147 146 145 144 143 142 141 140 139 138 137 136 135 134 133 132 131 130 129 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 58 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 --- #0 dumpsys () at ../../kern/kern_shutdown.c:487 487 if (dumping++) { (kgdb) bt #0 dumpsys () at ../../kern/kern_shutdown.c:487 #1 0xc01b1554 in boot (howto=260) at ../../kern/kern_shutdown.c:316 #2 0xc01b19a1 in panic (fmt=0xc03510e4 "from debugger") at ../../kern/kern_shutdown.c:595 #3 0xc013d1b1 in db_panic (addr=-1070477807, have_addr=0, count=-1, modif=0xcdf30bd4 "") at ../../ddb/db_command.c:435 #4 0xc013d14f in db_command (last_cmdp=0xc03a8f64, cmd_table=0xc03a8da4, aux_cmd_tablep=0xc03d9618) at ../../ddb/db_command.c:333 #5 0xc013d216 in db_command_loop () at ../../ddb/db_command.c:457 #6 0xc013f3c7 in db_trap (type=3, code=0) at ../../ddb/db_trap.c:71 #7 0xc031cbb0 in kdb_trap (type=3, code=0, regs=0xcdf30cdc) at ../../i386/i386/db_interface.c:158 #8 0xc032bee0 in trap (frame={tf_fs = -1070333936, tf_es = -1050935280, tf_ds = -839712752, tf_edi = 400, tf_esi = 256, tf_ebp = -839709404, tf_isp = -839709432, tf_ebx = -1070053391, tf_edx = -1069968593, tf_ecx = 1021, tf_eax = 18, tf_trapno = 3, tf_err = 0, tf_eip = -1070477807, tf_cs = 8, tf_eflags = 582, tf_esp = -1069968609, tf_ss = -1070158597}) at ../../i386/i386/trap.c:584 #9 0xc031ce11 in Debugger (msg=0xc036acfb "panic") at machine/cpufunc.h:67 #10 0xc01b1998 in panic (fmt=0xc03847f1 "ffs_vfree: freeing free inode") at ../../kern/kern_shutdown.c:593 #11 0xc02ad7ce in ffs_freefile (pvp=0xce24d180, ino=400, mode=438) at ../../ufs/ffs/ffs_alloc.c:1611 #12 0xc02ad652 in ffs_vfree (pvp=0xce24d180, ino=400, mode=438) at ../../ufs/ffs/ffs_alloc.c:1566 #13 0xc02b9d98 in ufs_inactive (ap=0xcdf30de4) at ../../ufs/ufs/ufs_inode.c:94 #14 0xc02bf1bd in ufs_vnoperate (ap=0xcdf30de4) at ../../ufs/ufs/ufs_vnops.c:2422 #15 0xc01df9f3 in vrele (vp=0xce24d180) at vnode_if.h:815 #16 0xc01e64b7 in vn_close (vp=0xce24d180, flags=3, cred=0xc1f0c080, p=0xcc2fba00) at ../../kern/vfs_vnops.c:235 #17 0xc01e6e2a in vn_closefile (fp=0xc1d658c0, p=0xcc2fba00) at ../../kern/vfs_vnops.c:693 #18 0xc01a71d4 in fdrop (fp=0xc1d658c0, p=0xcc2fba00) at ../../sys/file.h:217 #19 0xc01a711b in closef (fp=0xc1d658c0, p=0xcc2fba00) at ../../kern/kern_descrip.c:1218 #20 0xc01a6e71 in fdfree (p=0xcc2fba00) at ../../kern/kern_descrip.c:1057 #21 0xc01a9a5e in exit1 (p=0xcc2fba00, rv=11) at ../../kern/kern_exit.c:189 #22 0xc01b350b in sigexit (p=0xcc2fba00, sig=11) at ../../kern/kern_sig.c:1501 #23 0xc01b327c in postsig (sig=11) at ../../kern/kern_sig.c:1404 #24 0xc032bfff in trap (frame={tf_fs = 983087, tf_es = 47, tf_ds = -1078001617, tf_edi = 673763328, tf_esi = 135036927, tf_ebp = -1077939412, tf_isp = -839708716, tf_ebx = 673757860, tf_edx = 673763336, tf_ecx = 16384, tf_eax = 673763336, tf_trapno = 12, tf_err = 1213911044, tf_eip = 673711863, tf_cs = 31, tf_eflags = 66070, tf_esp = -1077939436, tf_ss = 47}) at ../../i386/i386/trap.c:174 #25 0x282806f7 in ?? () #26 0x806ef3d in ?? () #27 0x806ed91 in ?? () #28 0x804fce4 in ?? () #29 0x80560db in ?? () #30 0x8055e51 in ?? () #31 0x8053ec1 in ?? () #32 0x804e252 in ?? () #33 0x804c70d in ?? () (kgdb) --FCuugMFkClbJLl1L 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 iD8DBQE8egaLWry0BWjoQKURAsaXAJ44po1NysTFCCs6mnJQNIhp0ukGQACg6L+z 4rO2FtPPRE00Pm113WTxO/o= =a6Ig -----END PGP SIGNATURE----- --FCuugMFkClbJLl1L-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Mon Feb 25 8:12:15 2002 Delivered-To: freebsd-fs@freebsd.org Received: from smtpout.mac.com (smtpout.mac.com [204.179.120.85]) by hub.freebsd.org (Postfix) with ESMTP id 80DDA37B404 for ; Mon, 25 Feb 2002 08:12:13 -0800 (PST) Received: from smtp-relay02.mac.com (server-source-si02 [10.13.10.6]) by smtpout.mac.com (8.12.1/8.10.2/1.0) with ESMTP id g1PGCDFD003540 for ; Mon, 25 Feb 2002 08:12:13 -0800 (PST) Received: from asmtp02.mac.com ([10.13.10.66]) by smtp-relay02.mac.com (Netscape Messaging Server 4.15 relay02 Jun 21 2001 23:53:48) with ESMTP id GS3JOC00.8KG for ; Mon, 25 Feb 2002 08:12:12 -0800 Received: from [194.59.183.223] ([194.59.183.223]) by asmtp02.mac.com (Netscape Messaging Server 4.15 asmtp02 Jun 21 2001 23:53:48) with ESMTP id GS3JOC00.F34 for ; Mon, 25 Feb 2002 08:12:12 -0800 User-Agent: Microsoft-Entourage/9.0.2509 Date: Mon, 25 Feb 2002 17:10:52 +0100 Subject: get/setattrlist functions From: Luca Severini To: Message-ID: Mime-version: 1.0 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 Hi everybody, I'm porting a volume mirroring software, I developed years ago for A/UX and AIX, to MacOSX/Darwin. Unfortunately the way to store the resource fork and the Finder's attributes in MacOSX/Darwin is completely different than what A/UX and AIX used (files and folders). "More unfortunately" there is no official documentation about the two functions you must use to achieve that from a Mach-O software; I know I could use the Carbon API but I don't want to develop a real mac Application for now, I want only to port the old one. Does anybody of you know where/how is possible to obtain an exaustive explanation for those calls? (is anybody working at Apple listening?). Those are very import calls for whoever has to work with filesystems. Do anybody of you knows which of the values listed in I have to use with get/setattrlist() to get/set the "Appleshare" folder attribute that prevents the user to move, rename or delete such folder (from the MacOS9 Finder "Get Info" command) ? Thanks a lot in advance and sorry for my english. Best regards, Luca Severini email: lucaseverini@mac.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Mon Feb 25 10:22:19 2002 Delivered-To: freebsd-fs@freebsd.org Received: from hand.dotat.at (host217-35-46-127.in-addr.btopenworld.com [217.35.46.127]) by hub.freebsd.org (Postfix) with ESMTP id 8505037B404; Mon, 25 Feb 2002 10:22:10 -0800 (PST) Received: from fanf by hand.dotat.at with local (Exim 3.35 #1) id 16fPkz-0001DW-00; Mon, 25 Feb 2002 18:21:49 +0000 From: Tony Finch To: Kris Kennaway , mckusick@mckusick.com, fs@FreeBSD.org, dillon@FreeBSD.org Cc: fanf@chiark.greenend.org.uk Subject: Re: UFS panic on -stable In-Reply-To: <20020225014028.A53147@xor.obsecurity.org> Message-Id: Date: Mon, 25 Feb 2002 18:21:49 +0000 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 also saw a UFS panic recently, although rather different from Kris's. This was on -STABLE as of 2002-02-20, the panic being "ffs_valloc: dup alloc". http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/35248 I still have the core file if that would help. Tony. -- f.a.n.finch BAILEY: NORTHEAST GALE 8 TO STORM 10, PERHAPS VIOLENT STORM 11 LATER, BECOMING CYCLONIC 7 IN SOUTH. RAIN. MODERATE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Mon Feb 25 10:40:12 2002 Delivered-To: freebsd-fs@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 11D4437B402; Mon, 25 Feb 2002 10:40:08 -0800 (PST) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 25 Feb 2002 18:40:07 +0000 (GMT) To: Kris Kennaway Cc: mckusick@mckusick.com, fs@FreeBSD.org, dillon@FreeBSD.org, fanf@chiark.greenend.org.uk Subject: Re: UFS panic on -stable In-Reply-To: Your message of "Mon, 25 Feb 2002 01:40:28 PST." <20020225014028.A53147@xor.obsecurity.org> Date: Mon, 25 Feb 2002 18:40:07 +0000 From: Ian Dowse Message-ID: <200202251840.aa88376@salmon.maths.tcd.ie> 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 In message <20020225014028.A53147@xor.obsecurity.org>, Kris Kennaway writes: >Is there anything else I can provide? I don't have any real idea where to start, but the following information from frame 11 (ffs_freefile) would be useful. The alternatives are in case gdb is confused by register variables. *pvp [or *(struct vnode *)0xce24d180] *pip [or *(struct inode *)pvp->v_data] *fs [or *pip->i_fs] *bp *cgp [or *(struct cg *)bp->b_data] inosused[400/8] [or *((char *)cgp + cgp->cg_iusedoff + 50)] inosused[0]@200 From frame 18 (fdrop), "*p" and "*fp" might help to give some context too. Actually, one thing that does stand out (I think) is the value of `mode' in the ffs_freefile and ffs_vfree arguments. This is 0666 in octal, but should it not include some IFMT bits too? I would have expected it to be 0100666 (33206) instead. Maybe something is managing to change the mode of an inode after it has been already freed, causing the (ip->i_mode == 0) check in ufs_inactive to draw the wrong conclusion? #11 0xc02ad7ce in ffs_freefile (pvp=0xce24d180, ino=400, mode=438) at ../../ufs/ffs/ffs_alloc.c:1611 #12 0xc02ad652 in ffs_vfree (pvp=0xce24d180, ino=400, mode=438) at ../../ufs/ffs/ffs_alloc.c:1566 Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Mon Feb 25 11: 0:58 2002 Delivered-To: freebsd-fs@freebsd.org Received: from rwcrmhc54.attbi.com (rwcrmhc54.attbi.com [216.148.227.87]) by hub.freebsd.org (Postfix) with ESMTP id E9A9637B41B; Mon, 25 Feb 2002 11:00:25 -0800 (PST) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc54.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020225190025.BTHG1214.rwcrmhc54.attbi.com@InterJet.elischer.org>; Mon, 25 Feb 2002 19:00:25 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id KAA89238; Mon, 25 Feb 2002 10:53:50 -0800 (PST) Date: Mon, 25 Feb 2002 10:53:50 -0800 (PST) From: Julian Elischer To: Tony Finch Cc: Kris Kennaway , mckusick@mckusick.com, fs@FreeBSD.org, dillon@FreeBSD.org, fanf@chiark.greenend.org.uk Subject: Re: UFS panic on -stable In-Reply-To: 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 I have a strange crash in 4.4 where the inode hash seems to have been corrupted leading to various wierd behaviours. If I see more like it I'll examine it further... (this is with a 500 GB filesystem) On Mon, 25 Feb 2002, Tony Finch wrote: > > I also saw a UFS panic recently, although rather different from > Kris's. This was on -STABLE as of 2002-02-20, the panic being > "ffs_valloc: dup alloc". > > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/35248 > > I still have the core file if that would help. > > Tony. > -- > f.a.n.finch > BAILEY: NORTHEAST GALE 8 TO STORM 10, PERHAPS VIOLENT STORM 11 LATER, BECOMING > CYCLONIC 7 IN SOUTH. RAIN. MODERATE. > > 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 Feb 25 13:11:13 2002 Delivered-To: freebsd-fs@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-169-107-10.dsl.lsan03.pacbell.net [64.169.107.10]) by hub.freebsd.org (Postfix) with ESMTP id 7654437B400; Mon, 25 Feb 2002 13:11:07 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id C746466C32; Mon, 25 Feb 2002 13:11:06 -0800 (PST) Date: Mon, 25 Feb 2002 13:11:06 -0800 From: Kris Kennaway To: Tony Finch Cc: Kris Kennaway , mckusick@mckusick.com, fs@FreeBSD.org, dillon@FreeBSD.org, fanf@chiark.greenend.org.uk Subject: Re: UFS panic on -stable Message-ID: <20020225131106.A59373@xor.obsecurity.org> References: <20020225014028.A53147@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="MGYHOYXEY6WxJCY8" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from dot@dotat.at on Mon, Feb 25, 2002 at 06:21:49PM +0000 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 --MGYHOYXEY6WxJCY8 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Feb 25, 2002 at 06:21:49PM +0000, Tony Finch wrote: >=20 > I also saw a UFS panic recently, although rather different from > Kris's. This was on -STABLE as of 2002-02-20, the panic being > "ffs_valloc: dup alloc". >=20 > http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dkern/35248 >=20 > I still have the core file if that would help. Yes, I've also been getting "dup alloc" panics on the cluster. Kris --MGYHOYXEY6WxJCY8 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 iD8DBQE8eqhpWry0BWjoQKURAgFQAKDN4jR7BjNRxMh3Gyfka8P5nxVaxwCg0MP+ rY4fYHfFNQFAAon0xCsBCNs= =998d -----END PGP SIGNATURE----- --MGYHOYXEY6WxJCY8-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Mon Feb 25 13:17:28 2002 Delivered-To: freebsd-fs@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-169-107-10.dsl.lsan03.pacbell.net [64.169.107.10]) by hub.freebsd.org (Postfix) with ESMTP id 81FFF37B402; Mon, 25 Feb 2002 13:17:15 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 10B3F66C32; Mon, 25 Feb 2002 13:17:14 -0800 (PST) Date: Mon, 25 Feb 2002 13:17:14 -0800 From: Kris Kennaway To: Ian Dowse Cc: Kris Kennaway , mckusick@mckusick.com, fs@FreeBSD.org, dillon@FreeBSD.org, fanf@chiark.greenend.org.uk Subject: Re: UFS panic on -stable Message-ID: <20020225131714.B59373@xor.obsecurity.org> References: <20020225014028.A53147@xor.obsecurity.org> <200202251840.aa88376@salmon.maths.tcd.ie> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="hHWLQfXTYDoKhP50" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <200202251840.aa88376@salmon.maths.tcd.ie>; from iedowse@maths.tcd.ie on Mon, Feb 25, 2002 at 06:40:07PM +0000 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 --hHWLQfXTYDoKhP50 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Feb 25, 2002 at 06:40:07PM +0000, Ian Dowse wrote: > In message <20020225014028.A53147@xor.obsecurity.org>, Kris Kennaway writ= es: >=20 > >Is there anything else I can provide? >=20 > I don't have any real idea where to start, but the following information > from frame 11 (ffs_freefile) would be useful. The alternatives are in > case gdb is confused by register variables. >=20 > *pvp [or *(struct vnode *)0xce24d180] > *pip [or *(struct inode *)pvp->v_data] > *fs [or *pip->i_fs] > *bp > *cgp [or *(struct cg *)bp->b_data] > inosused[400/8] [or *((char *)cgp + cgp->cg_iusedoff + 50)] > inosused[0]@200 >=20 > >From frame 18 (fdrop), "*p" and "*fp" might help to give some context > too. Here you go, hope I got everything: (kgdb) frame 11 #11 0xc02ad7ce in ffs_freefile (pvp=3D0xce24d180, ino=3D400, mode=3D438) at= ../../ufs/ffs/ffs_alloc.c:1611 1611 panic("ffs_vfree: freeing free inode"); (kgdb) print *pip $1 =3D {i_lock =3D {lk_interlock =3D {lock_data =3D 0}, lk_flags =3D 1088, = lk_sharecount =3D 0, lk_waitcount =3D 0, lk_exclusivecount =3D 1, lk_prio =3D 8, lk_wmesg =3D 0xc0386582 "inode"= , lk_timo =3D 6, lk_lockholder =3D 2216}, i_hash =3D {le_next =3D 0x0, le_prev =3D 0xc16= 3f64c}, i_vnode =3D 0xce24d180, i_devvp =3D 0xcde3c780, i_flag =3D 134, i_dev =3D 0xc171d100, i_number = =3D 400, i_effnlink =3D 0, inode_u =3D { fs =3D 0xc16f6000, e2fs =3D 0xc16f6000}, i_dquot =3D {0x0, 0x0}, i_modr= ev =3D 181199503653679, i_lockf =3D 0x0, i_count =3D 0, i_endoff =3D 0, i_diroff =3D 0, i_offset = =3D 0, i_ino =3D 0, i_reclen =3D 0, i_spare =3D {0, 0, 0}, i_dirhash =3D 0x0, i_din =3D {di_mode =3D 0, di_nl= ink =3D 0, di_u =3D {oldids =3D {0, 0}, inumber =3D 0}, di_size =3D 0, di_atime =3D 0, di_atimensec =3D 0, di= _mtime =3D 1014629101, di_mtimensec =3D 0, di_ctime =3D 1014629101, di_ctimensec =3D 0, di_db = =3D {0 }, di_ib =3D {0, 0, 0}, di_flags =3D 0, di_blocks =3D 0, di_gen =3D 812712= 882, di_uid =3D 0, di_gid =3D 0, di_spare =3D {0, 0}}} (kgdb) print *(struct inode *)pvp->v_data Cannot access memory at address 0x78. (kgdb) print *pvp Cannot access memory at address 0x0. (kgdb) print *(struct vnode *)0xce24d180 $2 =3D {v_flag =3D 0, v_usecount =3D 0, v_writecount =3D 0, v_holdcnt =3D 0= , v_id =3D 6943683, v_mount =3D 0xc1692000, v_op =3D 0xc1604e00, v_freelist =3D {tqe_next =3D= 0xce6a6fc0, tqe_prev =3D 0xc03e8efc}, v_nmntvnodes =3D {tqe_next =3D 0x0, tqe_prev = =3D 0xcdfeae64}, v_cleanblkhd =3D { tqh_first =3D 0x0, tqh_last =3D 0xce24d1ac}, v_dirtyblkhd =3D {tqh_firs= t =3D 0x0, tqh_last =3D 0xce24d1b4}, v_synclist =3D {le_next =3D 0x0, le_prev =3D 0xce5728fc}, v_numoutput =3D= 0, v_type =3D VNON, v_un =3D { vu_mountedhere =3D 0x0, vu_socket =3D 0x0, vu_spec =3D {vu_specinfo =3D= 0x0, vu_specnext =3D { sle_next =3D 0x0}}, vu_fifoinfo =3D 0x0}, v_lease =3D 0x0, v_lastw = =3D 0, v_cstart =3D 0, v_lasta =3D 0, v_clen =3D 0, v_object =3D 0x0, v_interlock =3D {lock_data =3D 0}, v_vnlo= ck =3D 0xc188f900, v_tag =3D VT_UFS, v_data =3D 0xc188f900, v_cache_src =3D {lh_first =3D 0x0}, v_cache_dst = =3D {tqh_first =3D 0xc1d17680, tqh_last =3D 0xc1d17690}, v_dd =3D 0xce24d180, v_ddid =3D 0, v_pollinfo= =3D {vpi_lock =3D {lock_data =3D 0}, vpi_selinfo =3D {si_pid =3D 0, si_note =3D {slh_first =3D 0x0}, si_flag= s =3D 0}, vpi_events =3D 0, vpi_revents =3D 0}, v_vxproc =3D 0x0} (kgdb) print *fs $3 =3D {fs_firstfield =3D 0, fs_unused_1 =3D 0, fs_sblkno =3D 8, fs_cblkno = =3D 16, fs_iblkno =3D 24, fs_dblkno =3D 280, fs_cgoffset =3D 1024, fs_cgmask =3D -1, fs_time =3D 10= 14587292, fs_size =3D 1024, fs_dsize =3D 743, fs_ncg =3D 1, fs_bsize =3D 16384, fs_fsize =3D 2048, fs= _frag =3D 8, fs_minfree =3D 8, fs_rotdelay =3D 0, fs_rps =3D 60, fs_bmask =3D -16384, fs_fmask =3D -2048= , fs_bshift =3D 14, fs_fshift =3D 11, fs_maxcontig =3D 7, fs_maxbpg =3D 4096, fs_fragshift =3D 3, fs_fsbtodb = =3D 2, fs_sbsize =3D 2048, fs_csmask =3D -1024, fs_csshift =3D 10, fs_nindir =3D 4096, fs_inopb =3D = 128, fs_nspf =3D 4, fs_optim =3D 0, fs_npsect =3D 4096, fs_interleave =3D 1, fs_trackskew =3D 0, fs_id =3D {1= 014586946, 723435801}, fs_csaddr =3D 280, fs_cssize =3D 2048, fs_cgsize =3D 16384, fs_ntrak =3D = 1, fs_nsect =3D 4096, fs_spc =3D 4096, fs_ncyl =3D 1, fs_cpg =3D 104, fs_ipg =3D 4096, fs_fpg =3D 106496, fs_cst= otal =3D {cs_ndir =3D 2, cs_nbfree =3D 88, cs_nifree =3D 3362, cs_nffree =3D 5}, fs_fmod =3D 1 '= \001', fs_clean =3D 0 '\000', fs_ronly =3D 0 '\000', fs_flags =3D 0 '\000', fs_fsmnt =3D "/dev", '\000'= , fs_cgrotor =3D 0, fs_ocsp =3D {0x0 }, fs_contigdirs =3D= 0xc16f7804 "", fs_csp =3D 0xc16f7000, fs_maxcluster =3D 0xc16f7800, fs_cpc =3D 0, fs_opo= stbl =3D {{0, 0, 0, 0, 0, 0, 0, 0} }, fs_snapinum =3D {0 }, fs_av= gfilesize =3D 16384, fs_avgfpdir =3D 64, fs_sparecon =3D {0 }, fs_pendingblo= cks =3D 0, fs_pendinginodes =3D 0, fs_contigsumsize =3D 7, fs_maxsymlinklen =3D 60, fs_inodefmt =3D 2, fs_ma= xfilesize =3D 17592186044415, fs_qbmask =3D 16383, fs_qfmask =3D 2047, fs_state =3D 0, fs_postblformat = =3D 1, fs_nrpos =3D 1, fs_postbloff =3D 0, fs_rotbloff =3D 0, fs_magic =3D 72020, fs_space =3D "= "} (kgdb) print *bp $4 =3D {b_hash =3D {le_next =3D 0xc6891dc0, le_prev =3D 0xc68d3fac}, b_vnbu= fs =3D {tqe_next =3D 0xc68c6f34, tqe_prev =3D 0xcde3c7b4}, b_freelist =3D {tqe_next =3D 0xc68350d4, tqe_= prev =3D 0xc6898ea4}, b_act =3D { tqe_next =3D 0x0, tqe_prev =3D 0xc171e190}, b_flags =3D 160, b_qindex = =3D 0, b_xflags =3D 5 '\005', b_lock =3D {lk_interlock =3D {lock_data =3D 0}, lk_flags =3D 1024, lk_sha= recount =3D 0, lk_waitcount =3D 0, lk_exclusivecount =3D 1, lk_prio =3D 20, lk_wmesg =3D 0xc036db70 "bufwa= it", lk_timo =3D 0, lk_lockholder =3D 2216}, b_error =3D 0, b_bufsize =3D 16384, b_runningb= ufspace =3D 0, b_bcount =3D 16384, b_resid =3D 0, b_dev =3D 0xc171d100, b_data =3D 0xc8169000 "", b_kvabase = =3D 0xc8169000 "", b_kvasize =3D 16384, b_lblkno =3D 64, b_blkno =3D 64, b_offset =3D 32768,= b_iodone =3D 0, b_iodone_chain =3D 0x0, b_vp =3D 0xcde3c780, b_dirtyoff =3D 0, b_dirtyend= =3D 0, b_rcred =3D 0x0, b_wcred =3D 0x0, b_pblkno =3D 47230112, b_saveaddr =3D 0x0, b_driver1 =3D= 0x0, b_driver2 =3D 0x0, b_caller1 =3D 0x0, b_caller2 =3D 0x0, b_pager =3D {pg_spc =3D 0x0, pg_req= page =3D 0}, b_cluster =3D { cluster_head =3D {tqh_first =3D 0xc689ce20, tqh_last =3D 0xc6818ba0}, c= luster_entry =3D { tqe_next =3D 0xc689ce20, tqe_prev =3D 0xc6818ba0}}, b_pages =3D {0xc0= c2b61c, 0xc0bef658, 0xc09ce414, 0xc098d1d0, 0x0 }, b_npages =3D 4, b_dep =3D {lh_firs= t =3D 0x0}, b_chain =3D { parent =3D 0x0, count =3D 0}} (kgdb) print *cgp $5 =3D {cg_firstfield =3D 0, cg_magic =3D 590421, cg_time =3D 1014629101, c= g_cgx =3D 0, cg_ncyl =3D 1, cg_niblk =3D 4096, cg_ndblk =3D 1024, cg_cs =3D {cs_ndir =3D 2, cs_nbfree= =3D 88, cs_nifree =3D 3362, cs_nffree =3D 5}, cg_rotor =3D 312, cg_frotor =3D 312, cg_irotor =3D 81= , cg_frsum =3D {0, 0, 0, 0, 0, 1, 0, 0}, cg_btotoff =3D 168, cg_boff =3D 584, cg_iusedoff =3D 792, cg_freeof= f =3D 1304, cg_nextfreeoff =3D 16308, cg_clustersumoff =3D 14612, cg_clusteroff =3D 1= 4644, cg_nclusterblks =3D 128, cg_sparecon =3D {0 }, cg_space =3D "X"} (kgdb) print inosused[400/8] $6 =3D 254 '=FE' (kgdb) print inosused[0]@200 $7 =3D "=FF=FF=FF=FF=FF=FF=FF=FF=FF=FF=FD", '=FF' , "=FE"= , '=FF' , "?=FE", '=FF' , "=F7\017", '\= 000' (kgdb) print *((char *)cgp + cgp->cg_iusedoff + 50) $8 =3D -2 '=FE' (kgdb) frame 18 #18 0xc01a71d4 in fdrop (fp=3D0xc1d658c0, p=3D0xcc2fba00) at ../../sys/file= .h:217 217 return ((*fp->f_ops->fo_close)(fp, p)); (kgdb) print *p Cannot access memory at address 0x0. (kgdb) print *fp $9 =3D {f_list =3D {le_next =3D 0xc17c1d00, le_prev =3D 0xc1755740}, f_FILL= ER3 =3D 0, f_type =3D 1, f_flag =3D 3, f_cred =3D 0xc1f0c080, f_ops =3D 0xc03b2028, f_seqcount =3D 1, f_nextoff = =3D 0, f_offset =3D 0, f_data =3D 0xce24d180 "", f_count =3D 0, f_msgcount =3D 0} (kgdb) Kris --hHWLQfXTYDoKhP50 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 iD8DBQE8eqnaWry0BWjoQKURAqJcAKDVnVrpW/T7XaQ8QJouoJF5GUJ3egCfTvrM xjCN/BmfZenfyAQ3Opot62w= =jVxw -----END PGP SIGNATURE----- --hHWLQfXTYDoKhP50-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Mon Feb 25 14:30:18 2002 Delivered-To: freebsd-fs@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 9406637B402; Mon, 25 Feb 2002 14:30:12 -0800 (PST) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 25 Feb 2002 22:30:11 +0000 (GMT) To: Kris Kennaway Cc: mckusick@mckusick.com, fs@FreeBSD.org, dillon@FreeBSD.org, fanf@chiark.greenend.org.uk Subject: Re: UFS panic on -stable In-Reply-To: Your message of "Mon, 25 Feb 2002 13:17:14 PST." <20020225131714.B59373@xor.obsecurity.org> Date: Mon, 25 Feb 2002 22:30:11 +0000 From: Ian Dowse Message-ID: <200202252230.aa23166@salmon.maths.tcd.ie> 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 In message <20020225131714.B59373@xor.obsecurity.org>, Kris Kennaway writes: >Here you go, hope I got everything: Mostly :-) Could you print out "*(struct proc *)0xcc2fba00", as the `p' pointer in frame 18 got lost. I just want to see what process was exiting to see if it offers any further hints. The superblock claims that this is a 2MB "/dev" filesystem - is that a real disk filesystem, or mounted from a vnconfig disk or something? In the vnode we have v_type set to VNON, v_mount is non-NULL, v_data is non-NULL, i_mode was 0666. Candidates I could see for leaving vnodes like this are getnewvnode() and the weird code in ufs_mknod(). I guess ufs_mknod is the main suspect since the filesystem is /dev. I wonder is the new vlrureclaim() code somehow reclaiming vnodes at a bad time. Maybe try setting kern.maxvnodes to some really large value to see if it stops the crashes, or set it very small and see if they occur more frequently. Matt, can you see any way that the weird/broken ufs_mknod() code could interact badly with vlrureclaim()? Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Mon Feb 25 14:38:49 2002 Delivered-To: freebsd-fs@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-169-107-10.dsl.lsan03.pacbell.net [64.169.107.10]) by hub.freebsd.org (Postfix) with ESMTP id 149AA37B400; Mon, 25 Feb 2002 14:38:41 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 9869066C32; Mon, 25 Feb 2002 14:38:40 -0800 (PST) Date: Mon, 25 Feb 2002 14:38:40 -0800 From: Kris Kennaway To: Ian Dowse Cc: Kris Kennaway , mckusick@mckusick.com, fs@FreeBSD.org, dillon@FreeBSD.org, fanf@chiark.greenend.org.uk Subject: Re: UFS panic on -stable Message-ID: <20020225143840.A60688@xor.obsecurity.org> References: <20020225131714.B59373@xor.obsecurity.org> <200202252230.aa23166@salmon.maths.tcd.ie> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="GvXjxJ+pjyke8COw" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <200202252230.aa23166@salmon.maths.tcd.ie>; from iedowse@maths.tcd.ie on Mon, Feb 25, 2002 at 10:30:11PM +0000 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 --GvXjxJ+pjyke8COw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Feb 25, 2002 at 10:30:11PM +0000, Ian Dowse wrote: > In message <20020225131714.B59373@xor.obsecurity.org>, Kris Kennaway writ= es: > >Here you go, hope I got everything: >=20 > Mostly :-) Could you print out "*(struct proc *)0xcc2fba00", as the > `p' pointer in frame 18 got lost. I just want to see what process > was exiting to see if it offers any further hints. (kgdb) print *(struct proc *)0xcc2fba00 $1 =3D {p_procq =3D {tqe_next =3D 0xcc2fdf60, tqe_prev =3D 0xc0402560}, p_l= ist =3D {le_next =3D 0xce7809c0, le_prev =3D 0xce295a48}, p_cred =3D 0xc1f8b720, p_fd =3D 0xc1ed9b00, p_= stats =3D 0xcdf2ecd0, p_limit =3D 0xc166d200, p_upages_obj =3D 0xcdf438a0, p_procsig =3D 0xc1ac= 5640, p_flag =3D 8452, p_stat =3D 2 '\002', p_pad1 =3D "\000\000", p_pid =3D 2216, p_hash =3D {l= e_next =3D 0x0, le_prev =3D 0xc15b52a0}, p_pglist =3D {le_next =3D 0xce476700, le_prev = =3D 0xcc2fcc1c}, p_pptr =3D 0xcc2fcbe0, p_sibling =3D {le_next =3D 0xce476700, le_prev =3D= 0xcc2fcc30}, p_children =3D { lh_first =3D 0x0}, p_ithandle =3D {callout =3D 0xc67f64e0}, p_oppid =3D= 0, p_dupfd =3D 0, p_vmspace =3D 0xce3022c0, p_estcpu =3D 295, p_cpticks =3D 106, p_pctcpu = =3D 7355, p_wchan =3D 0x0, p_wmesg =3D 0xc036dbc9 "biord", p_swtime =3D 5, p_slptime =3D 0, p_realti= mer =3D {it_interval =3D { tv_sec =3D 0, tv_usec =3D 0}, it_value =3D {tv_sec =3D 42188, tv_usec= =3D 597238}}, p_runtime =3D 32182, p_uu =3D 0, p_su =3D 0, p_iu =3D 0, p_uticks =3D 2, p_sticks =3D 10278, p= _iticks =3D 0, p_traceflag =3D 0, p_tracep =3D 0x0, p_siglist =3D {__bits =3D {0, 0, 0, 0}}, p_textvp =3D 0= xcde86480, p_lock =3D 0 '\000', p_oncpu =3D 0 '\000', p_lastcpu =3D 0 '\000', p_rqindex =3D 12 '\f', p_lo= cks =3D -7, p_simple_locks =3D 0, p_stops =3D 0, p_stype =3D 0, p_step =3D 0 '\000', p_pfsflags =3D 0 '\000= ', p_pad3 =3D "\000", p_retval =3D {0, 0}, p_sigiolst =3D {slh_first =3D 0x0}, p_sigparent =3D 20, p_oldsigmas= k =3D {__bits =3D {0, 0, 0, 0}}, p_sig =3D 11, p_code =3D 12, p_klist =3D {slh_first =3D 0x0}, p_sigmask = =3D {__bits =3D {0, 0, 0, 0}}, p_sigstk =3D {ss_sp =3D 0x0, ss_size =3D 0, ss_flags =3D 4}, p_priority = =3D 86 'V', p_usrpri =3D 86 'V', p_nice =3D 0 '\000', p_comm =3D "sshd\000er\000\000\000\000\000\000\000\0= 00\000", p_pgrp =3D 0xc15db000, p_sysent =3D 0xc03b0140, p_rtprio =3D {type =3D 1, prio =3D 0}, p_prison = =3D 0x0, p_args =3D 0xc1faa260, p_addr =3D 0xcdf2e000, p_md =3D {md_regs =3D 0xcdf30fa8}, p_xstat =3D 0, = p_acflag =3D 19, p_ru =3D 0xc1fba080, p_nthreads =3D 0, p_aioinfo =3D 0x0, p_wakeup =3D 0, p_peers =3D 0x0, p_l= eader =3D 0xcc2fba00, p_asleep =3D { as_priority =3D 0, as_timo =3D 0}, p_emuldata =3D 0x0} > The superblock claims that this is a 2MB "/dev" filesystem - is > that a real disk filesystem, or mounted from a vnconfig disk or > something? I should have provided more information about the clients in the initial email: they boot "diskless" via NFS, but also have local disk. Here's the df output: Filesystem 1K-blocks Used Avail Capacity Mou= nted on 216.136.204.23:/a/nfsroots/4.dir4 176873964 99865811 62858236 61% / mfs:13 3935 1055 2566 29% /etc mfs:21 32206 856 28774 3% /var mfs:28 10030 188 9040 2% /tmp mfs:33 1486 68 1300 5% /dev /dev/ad0e 2032839 108878 1761334 6% /a /dev/ad0f 26046238 7158650 16803889 30% /x > In the vnode we have v_type set to VNON, v_mount is non-NULL, v_data > is non-NULL, i_mode was 0666. Candidates I could see for leaving > vnodes like this are getnewvnode() and the weird code in ufs_mknod(). > I guess ufs_mknod is the main suspect since the filesystem is /dev. >=20 > I wonder is the new vlrureclaim() code somehow reclaiming vnodes > at a bad time. Maybe try setting kern.maxvnodes to some really large > value to see if it stops the crashes, or set it very small and see > if they occur more frequently. Okay, I'll try this. Kris --GvXjxJ+pjyke8COw 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 iD8DBQE8erzvWry0BWjoQKURAn6QAKCURXVGSHiZ8ob5sOZjQoQKrP9fEACdGIsF vCH4Nzq9LkN9+xShLlRJihM= =FRnw -----END PGP SIGNATURE----- --GvXjxJ+pjyke8COw-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Mon Feb 25 15:42:12 2002 Delivered-To: freebsd-fs@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 9493737B402 for ; Mon, 25 Feb 2002 15:42:08 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id g1PNfmA53877; Mon, 25 Feb 2002 15:41:48 -0800 (PST) (envelope-from dillon) Date: Mon, 25 Feb 2002 15:41:48 -0800 (PST) From: Matthew Dillon Message-Id: <200202252341.g1PNfmA53877@apollo.backplane.com> To: Kris Kennaway Cc: Tony Finch , Kris Kennaway , mckusick@mckusick.com, fs@FreeBSD.ORG, fanf@chiark.greenend.org.uk Subject: Re: UFS panic on -stable References: <20020225014028.A53147@xor.obsecurity.org> <20020225131106.A59373@xor.obsecurity.org> 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 also saw a UFS panic recently, although rather different from :> Kris's. This was on -STABLE as of 2002-02-20, the panic being :> "ffs_valloc: dup alloc". :>=20 :> http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dkern/35248 :>=20 :> I still have the core file if that would help. : :Yes, I've also been getting "dup alloc" panics on the cluster. : :Kris Have you gotten any dup alloc panics after upgrading to the latest -stable? -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Mon Feb 25 15:48:59 2002 Delivered-To: freebsd-fs@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id E7D0637B402 for ; Mon, 25 Feb 2002 15:48:57 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id g1PNmmI53958; Mon, 25 Feb 2002 15:48:48 -0800 (PST) (envelope-from dillon) Date: Mon, 25 Feb 2002 15:48:48 -0800 (PST) From: Matthew Dillon Message-Id: <200202252348.g1PNmmI53958@apollo.backplane.com> To: Ian Dowse Cc: Kris Kennaway , mckusick@mckusick.com, fs@FreeBSD.ORG, fanf@chiark.greenend.org.uk Subject: Re: UFS panic on -stable References: <200202252230.aa23166@salmon.maths.tcd.ie> 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 wonder is the new vlrureclaim() code somehow reclaiming vnodes :at a bad time. Maybe try setting kern.maxvnodes to some really large :value to see if it stops the crashes, or set it very small and see :if they occur more frequently. : :Matt, can you see any way that the weird/broken ufs_mknod() code :could interact badly with vlrureclaim()? : :Ian Not that I know of, but it is worth raising kern.maxvnodes to find out. Kris, is softupdates turned on on those MFS filesystems? -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Mon Feb 25 17:30:50 2002 Delivered-To: freebsd-fs@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-169-107-10.dsl.lsan03.pacbell.net [64.169.107.10]) by hub.freebsd.org (Postfix) with ESMTP id D62D837B400 for ; Mon, 25 Feb 2002 17:30:45 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 8788F66C32; Mon, 25 Feb 2002 17:30:42 -0800 (PST) Date: Mon, 25 Feb 2002 17:30:42 -0800 From: Kris Kennaway To: Matthew Dillon Cc: Kris Kennaway , Tony Finch , mckusick@mckusick.com, fs@FreeBSD.ORG, fanf@chiark.greenend.org.uk Subject: Re: UFS panic on -stable Message-ID: <20020225173042.A62821@xor.obsecurity.org> References: <20020225014028.A53147@xor.obsecurity.org> <20020225131106.A59373@xor.obsecurity.org> <200202252341.g1PNfmA53877@apollo.backplane.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="gKMricLos+KVdGMg" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <200202252341.g1PNfmA53877@apollo.backplane.com>; from dillon@apollo.backplane.com on Mon, Feb 25, 2002 at 03:41:48PM -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 --gKMricLos+KVdGMg Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Feb 25, 2002 at 03:41:48PM -0800, Matthew Dillon wrote: > :> I also saw a UFS panic recently, although rather different from > :> Kris's. This was on -STABLE as of 2002-02-20, the panic being > :> "ffs_valloc: dup alloc". > :>=3D20 > :> http://www.freebsd.org/cgi/query-pr.cgi?pr=3D3Dkern/35248 > :>=3D20 > :> I still have the core file if that would help. > : > :Yes, I've also been getting "dup alloc" panics on the cluster. > : > :Kris >=20 > Have you gotten any dup alloc panics after upgrading to the latest > -stable? Not yet (fingers crossed), but I only upgraded (from 4.5-STABLE of a few weeks prior) yesterday. Kris --gKMricLos+KVdGMg 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 iD8DBQE8euVBWry0BWjoQKURAoceAJ9GuA4IPPy82y8B3xrnQ6ewHiyy4gCeOmg/ o6S8p3J+2/zBQm3p/bWpUXU= =+vw0 -----END PGP SIGNATURE----- --gKMricLos+KVdGMg-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Mon Feb 25 17:41:25 2002 Delivered-To: freebsd-fs@freebsd.org Received: from beastie.mckusick.com (beastie.mckusick.com [209.31.233.184]) by hub.freebsd.org (Postfix) with ESMTP id 34C5437B404 for ; Mon, 25 Feb 2002 17:41:20 -0800 (PST) Received: from beastie.mckusick.com (localhost [127.0.0.1]) by beastie.mckusick.com (8.11.4/8.9.3) with ESMTP id g1Q1f8i28365; Mon, 25 Feb 2002 17:41:08 -0800 (PST) (envelope-from mckusick@beastie.mckusick.com) Message-Id: <200202260141.g1Q1f8i28365@beastie.mckusick.com> To: Matthew Dillon , Ian Dowse Subject: Re: UFS panic on -stable Cc: Kris Kennaway , Tony Finch , fs@FreeBSD.ORG, fanf@chiark.greenend.org.uk In-Reply-To: Your message of "Mon, 25 Feb 2002 17:30:42 PST." <20020225173042.A62821@xor.obsecurity.org> Date: Mon, 25 Feb 2002 17:41:08 -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 The fact that this is happening on mfs which (presumably) is running async and without soft updates plus the fact that it is not doing any disk I/O should be a big help in tracking down this bug. It does point a big finger at the buffer cache code since that would be about the only place that data corruption could be happening here. Perhaps we can find a reliable way to generate a crash. Maybe a series of mknod/rm commands. If we can find a way to reliably get this panic, finding the bug should be possible. And if this is the elusive bitmap corruption panic we have been hunting for the last two years, that would really make my day! Kris, can you send the result of a `mount -v' command on your system so we can confirm that the mfs filesystems are running async without soft updates. Kirk McKusick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Mon Feb 25 17:47:11 2002 Delivered-To: freebsd-fs@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-169-107-10.dsl.lsan03.pacbell.net [64.169.107.10]) by hub.freebsd.org (Postfix) with ESMTP id 2E98A37B400 for ; Mon, 25 Feb 2002 17:47:06 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 78A2A66D73; Mon, 25 Feb 2002 17:47:05 -0800 (PST) Date: Mon, 25 Feb 2002 17:47:05 -0800 From: Kris Kennaway To: Kirk McKusick Cc: Matthew Dillon , Ian Dowse , Kris Kennaway , Tony Finch , fs@FreeBSD.ORG, fanf@chiark.greenend.org.uk Subject: Re: UFS panic on -stable Message-ID: <20020225174705.A63111@xor.obsecurity.org> References: <20020225173042.A62821@xor.obsecurity.org> <200202260141.g1Q1f8i28365@beastie.mckusick.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="OXfL5xGRrasGEqWY" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <200202260141.g1Q1f8i28365@beastie.mckusick.com>; from mckusick@mckusick.com on Mon, Feb 25, 2002 at 05:41:08PM -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 --OXfL5xGRrasGEqWY Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Mon, Feb 25, 2002 at 05:41:08PM -0800, Kirk McKusick wrote: > Kris, can you send the result of a `mount -v' command on your > system so we can confirm that the mfs filesystems are running > async without soft updates. That's correct. The NFS mounts shown below are used transiently by the package building process, but that's probably not relevant to this situation. 216.136.204.23:/a/nfsroots/4.dir4 on / (nfs, read-only) mfs:13 on /etc (mfs, asynchronous, local) mfs:21 on /var (mfs, asynchronous, local) mfs:28 on /tmp (mfs, asynchronous, local) mfs:33 on /dev (mfs, asynchronous, local) /dev/ad0e on /a (ufs, local, soft-updates, writes: sync 3 async 3790, reads: sync 770 async 6740) /dev/ad0f on /x (ufs, local, soft-updates, writes: sync 75409 async 5164118, reads: sync 1178673 async 152182) bento:/var/portbuild/4/ports on /x/tmp/4/chroot/32318/a/ports (nfs, read-only) bento:/var/portbuild/4/src on /x/tmp/4/chroot/32318/usr/src (nfs, read-only) bento:/var/portbuild/usr/opt/doc on /x/tmp/4/chroot/32318/usr/opt/doc (nfs, read-only) bento:/var/portbuild/4/ports on /x/tmp/4/chroot/35504/a/ports (nfs, read-only) bento:/var/portbuild/4/src on /x/tmp/4/chroot/35504/usr/src (nfs, read-only) bento:/var/portbuild/usr/opt/doc on /x/tmp/4/chroot/35504/usr/opt/doc (nfs, read-only) bento:/var/portbuild/4/ports on /x/tmp/4/chroot/56757/a/ports (nfs, read-only) bento:/var/portbuild/4/src on /x/tmp/4/chroot/56757/usr/src (nfs, read-only) bento:/var/portbuild/usr/opt/doc on /x/tmp/4/chroot/56757/usr/opt/doc (nfs, read-only) bento:/var/portbuild/4/src on /x/tmp/4/chroot/6141/usr/src (nfs, read-only) bento:/var/portbuild/usr/opt/doc on /x/tmp/4/chroot/6141/usr/opt/doc (nfs, read-only) Kris --OXfL5xGRrasGEqWY 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 iD8DBQE8eukYWry0BWjoQKURAvCOAKDyizOOWPrCsNmhZEH01pM4g6XxGQCgqtb1 d+Vjlc5nPhCfPsLyIOLPJNE= =j/6x -----END PGP SIGNATURE----- --OXfL5xGRrasGEqWY-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Mon Feb 25 17:56:35 2002 Delivered-To: freebsd-fs@freebsd.org Received: from beastie.mckusick.com (beastie.mckusick.com [209.31.233.184]) by hub.freebsd.org (Postfix) with ESMTP id CA8B137B404 for ; Mon, 25 Feb 2002 17:56:31 -0800 (PST) Received: from beastie.mckusick.com (localhost [127.0.0.1]) by beastie.mckusick.com (8.11.4/8.9.3) with ESMTP id g1Q1uLi28550; Mon, 25 Feb 2002 17:56:21 -0800 (PST) (envelope-from mckusick@beastie.mckusick.com) Message-Id: <200202260156.g1Q1uLi28550@beastie.mckusick.com> To: Kris Kennaway Subject: Re: UFS panic on -stable Cc: Matthew Dillon , Ian Dowse , Tony Finch , fs@FreeBSD.ORG, fanf@chiark.greenend.org.uk In-Reply-To: Your message of "Mon, 25 Feb 2002 17:47:05 PST." <20020225174705.A63111@xor.obsecurity.org> Date: Mon, 25 Feb 2002 17:56:21 -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 Thanks for the quick reply Kris. Do you have any idea what you are doing on /dev to cause the panic? If so, can you go through the /dev operations that you do and see if you can come up with a script that triggers the panic? If you cannot easily get the set of operations, it would be pretty trivial to hack up the mfs code to trace all the operations done on it. Kirk McKusick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Mon Feb 25 18:20:36 2002 Delivered-To: freebsd-fs@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-169-107-10.dsl.lsan03.pacbell.net [64.169.107.10]) by hub.freebsd.org (Postfix) with ESMTP id 1608537B402 for ; Mon, 25 Feb 2002 18:20:32 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 6FA4266C32; Mon, 25 Feb 2002 18:20:31 -0800 (PST) Date: Mon, 25 Feb 2002 18:20:31 -0800 From: Kris Kennaway To: Kirk McKusick Cc: Kris Kennaway , Matthew Dillon , Ian Dowse , Tony Finch , fs@FreeBSD.ORG, fanf@chiark.greenend.org.uk Subject: Re: UFS panic on -stable Message-ID: <20020225182031.A63513@xor.obsecurity.org> References: <20020225174705.A63111@xor.obsecurity.org> <200202260156.g1Q1uLi28550@beastie.mckusick.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="wRRV7LY7NUeQGEoC" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <200202260156.g1Q1uLi28550@beastie.mckusick.com>; from mckusick@mckusick.com on Mon, Feb 25, 2002 at 05:56:21PM -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 --wRRV7LY7NUeQGEoC Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Mon, Feb 25, 2002 at 05:56:21PM -0800, Kirk McKusick wrote: > Thanks for the quick reply Kris. Do you have any idea what you > are doing on /dev to cause the panic? If so, can you go through > the /dev operations that you do and see if you can come up with > a script that triggers the panic? If you cannot easily get the > set of operations, it would be pretty trivial to hack up the mfs > code to trace all the operations done on it. As far as I can tell the only use of /dev by the build scripts themselves is to write to /dev/null. The scripts are copied around and invoked via ssh, so there are pty devices being accessed too. I can't immediately think of anything else. The actual package builds (which may do other /dev operations) are done in a chroot, which has its own copy of /dev and is on a UFS filesystem on disk (/x), so that's apparently ruled out as being a factor here. Kris --wRRV7LY7NUeQGEoC 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 iD8DBQE8evDuWry0BWjoQKURAkWsAJ9SmdLS9x2xItdX7cUOTh/By6K8NACeJ3CE J3F16qRTlX+P6f4FyUgRi6E= =AAp1 -----END PGP SIGNATURE----- --wRRV7LY7NUeQGEoC-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Mon Feb 25 18:38:12 2002 Delivered-To: freebsd-fs@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 9F7E737B421 for ; Mon, 25 Feb 2002 18:37:49 -0800 (PST) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 26 Feb 2002 02:37:48 +0000 (GMT) To: Kirk McKusick Cc: Matthew Dillon , Kris Kennaway , Tony Finch , fs@FreeBSD.ORG, fanf@chiark.greenend.org.uk Subject: Re: UFS panic on -stable In-Reply-To: Your message of "Mon, 25 Feb 2002 17:41:08 PST." <200202260141.g1Q1f8i28365@beastie.mckusick.com> Date: Tue, 26 Feb 2002 02:37:47 +0000 From: Ian Dowse Message-ID: <200202260237.aa51774@salmon.maths.tcd.ie> 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 In message <200202260141.g1Q1f8i28365@beastie.mckusick.com>, Kirk McKusick writ es: >this bug. It does point a big finger at the buffer cache code >since that would be about the only place that data corruption >could be happening here. My feeling was that this particular crash may be caused by something at the vnode level since it appeared that the inode had been fully freed while the vnode was still referenced. The process was sshd, so I was looking for something that could have changed the mode on the inode after it had been inadvertantly freed. The best I've found so far is in the ssh source there is the code: /* Releases the tty. Its ownership is returned to root, and permissions to 0666. */ void pty_release(const char *ttyname) { if (chown(ttyname, (uid_t) 0, (gid_t) 0) < 0) ... if (chmod(ttyname, (mode_t) 0666) < 0) ... The inode looked as if a VOP_SETATTR to gid root, uid root, mode 666 had succeeded even though the inode was already free. That explains the lack of IFMT bits in the mode argument to ffs_freefile(). Kris, if it's not too awkward to make changes to the cluster kernels, could you try applying the following extra sanity check to ufs_chmod? This should attempt to catch the bug a little bit earlier by detecting an attempt to VOP_SETATTR a free inode. Ian Index: ufs_vnops.c =================================================================== RCS file: /dump/FreeBSD-CVS/src/sys/ufs/ufs/ufs_vnops.c,v retrieving revision 1.131.2.7 diff -u -r1.131.2.7 ufs_vnops.c --- ufs_vnops.c 5 Feb 2002 18:35:04 -0000 1.131.2.7 +++ ufs_vnops.c 26 Feb 2002 02:28:02 -0000 @@ -570,6 +570,8 @@ if (!groupmember(ip->i_gid, cred) && (mode & ISGID)) return (EPERM); } + if (ip->i_mode == 0) + panic("ufs_chmod: free inode"); ip->i_mode &= ~ALLPERMS; ip->i_mode |= (mode & ALLPERMS); ip->i_flag |= IN_CHANGE; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Mon Feb 25 21:55:28 2002 Delivered-To: freebsd-fs@freebsd.org Received: from dns.pacang.com (adsl-63-193-245-242.dsl.snfc21.pacbell.net [63.193.245.242]) by hub.freebsd.org (Postfix) with ESMTP id A438B37B404 for ; Mon, 25 Feb 2002 21:55:26 -0800 (PST) Received: (from bservies@localhost) by dns.pacang.com (8.9.3/8.9.2) id VAA14854 for freebsd-fs@freebsd.org; Mon, 25 Feb 2002 21:55:26 -0800 Date: Mon, 25 Feb 2002 21:55:26 -0800 From: Byron Servies To: freebsd-fs@freebsd.org Subject: Retrieving a list of ACLs for a file Message-ID: <20020225215526.J13918@pacang.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i 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 there! I am working on adding ACL support to the freebsd port of Legato NetWorker. Everything appears to be straight forward, with the exception of retrieving a complete list of the ACLs on a file. From the acl_get manual page, it appears that there is no way to retrieve a complete list, but that each ACL type must be retrieved individually. My concern is that if new ACL types are added, the backup will still succeed though the new ACLs would not actually be backed up. Does anyone have any suggestions on a good way to retrieve a complete list, or do I just have to hard code it? Thanks, Byron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Mon Feb 25 22: 5:40 2002 Delivered-To: freebsd-fs@freebsd.org Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by hub.freebsd.org (Postfix) with ESMTP id 332F237B420 for ; Mon, 25 Feb 2002 22:05:25 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1192) id B4120AE27F; Mon, 25 Feb 2002 22:05:25 -0800 (PST) Date: Mon, 25 Feb 2002 22:05:25 -0800 From: Alfred Perlstein To: Byron Servies Cc: freebsd-fs@freebsd.org Subject: Re: Retrieving a list of ACLs for a file Message-ID: <20020226060525.GF80761@elvis.mu.org> References: <20020225215526.J13918@pacang.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020225215526.J13918@pacang.com> User-Agent: Mutt/1.3.27i 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 * Byron Servies [020225 21:55] wrote: > Hi there! > > I am working on adding ACL support to the freebsd port of Legato > NetWorker. Everything appears to be straight forward, with the > exception of retrieving a complete list of the ACLs on a file. > > >From the acl_get manual page, it appears that there is no way > to retrieve a complete list, but that each ACL type must be > retrieved individually. My concern is that if new ACL types > are added, the backup will still succeed though the new ACLs > would not actually be backed up. > > Does anyone have any suggestions on a good way to retrieve > a complete list, or do I just have to hard code it? acl_gen_entry(3) specifically: If the value of entry_id is ACL_FIRST_ENTRY, then the function will return in entry_p a descriptor for the first ACL entry within acl. If a call is made to acl_get_entry() with entry_id set to ACL_NEXT_ENTRY when there has not been either an initial successful call to acl_get_entry(), or a previous successfull call to acl_create_entry(), acl_delete_entry(), acl_dup(), acl_from_text(), acl_get_fd(), acl_get_file(), acl_set_fd(), acl_set_file(), or acl_valid(), then the result is unspecified. Hopefully this helps. -- -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.' Tax deductible donations for FreeBSD: http://www.freebsdfoundation.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Mon Feb 25 22:14:49 2002 Delivered-To: freebsd-fs@freebsd.org Received: from dns.pacang.com (adsl-63-193-245-242.dsl.snfc21.pacbell.net [63.193.245.242]) by hub.freebsd.org (Postfix) with ESMTP id C4C5337B402 for ; Mon, 25 Feb 2002 22:14:45 -0800 (PST) Received: (from bservies@localhost) by dns.pacang.com (8.9.3/8.9.2) id WAA15040; Mon, 25 Feb 2002 22:14:43 -0800 Date: Mon, 25 Feb 2002 22:14:43 -0800 From: Byron Servies To: Alfred Perlstein Cc: freebsd-fs@freebsd.org Subject: Re: Retrieving a list of ACLs for a file Message-ID: <20020225221443.K13918@pacang.com> References: <20020225215526.J13918@pacang.com> <20020226060525.GF80761@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020226060525.GF80761@elvis.mu.org>; from bright@mu.org on Mon, Feb 25, 2002 at 10:05:25PM -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 February 25, 2002 at 22:05, Alfred Perlstein wrote: > * Byron Servies [020225 21:55] wrote: > > Hi there! > > > > I am working on adding ACL support to the freebsd port of Legato > > NetWorker. Everything appears to be straight forward, with the > > exception of retrieving a complete list of the ACLs on a file. > > > > >From the acl_get manual page, it appears that there is no way > > to retrieve a complete list, but that each ACL type must be > > retrieved individually. My concern is that if new ACL types > > are added, the backup will still succeed though the new ACLs > > would not actually be backed up. > > > > Does anyone have any suggestions on a good way to retrieve > > a complete list, or do I just have to hard code it? > > acl_get_entry(3) > > specifically: > > If the value of entry_id is ACL_FIRST_ENTRY, then the function will > return in entry_p a descriptor for the first ACL entry within acl. If a > call is made to acl_get_entry() with entry_id set to ACL_NEXT_ENTRY when > there has not been either an initial successful call to acl_get_entry(), > or a previous successfull call to acl_create_entry(), acl_delete_entry(), > acl_dup(), acl_from_text(), acl_get_fd(), acl_get_file(), acl_set_fd(), > acl_set_file(), or acl_valid(), then the result is unspecified. This will allow you to itterate over the entries in an acl after it has been retrieved from a file (e.g with acl_get_file). But each file may have multiple acls, apparently requiring multiple acl_get_file calls with specific acl type specifiers. Thanks, though. Byron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Tue Feb 26 18:43:45 2002 Delivered-To: freebsd-fs@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-169-107-10.dsl.lsan03.pacbell.net [64.169.107.10]) by hub.freebsd.org (Postfix) with ESMTP id 880BC37B405 for ; Tue, 26 Feb 2002 18:43:41 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id E1E2066C32; Tue, 26 Feb 2002 18:43:40 -0800 (PST) Date: Tue, 26 Feb 2002 18:43:40 -0800 From: Kris Kennaway To: Ian Dowse Cc: Kirk McKusick , Matthew Dillon , Kris Kennaway , Tony Finch , fs@FreeBSD.ORG, fanf@chiark.greenend.org.uk Subject: Re: UFS panic on -stable Message-ID: <20020226184340.A78562@xor.obsecurity.org> References: <200202260141.g1Q1f8i28365@beastie.mckusick.com> <200202260237.aa51774@salmon.maths.tcd.ie> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="BXVAT5kNtrzKuDFl" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <200202260237.aa51774@salmon.maths.tcd.ie>; from iedowse@maths.tcd.ie on Tue, Feb 26, 2002 at 02:37:47AM +0000 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 --BXVAT5kNtrzKuDFl Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Feb 26, 2002 at 02:37:47AM +0000, Ian Dowse wrote: > Kris, if it's not too awkward to make changes to the cluster kernels, > could you try applying the following extra sanity check to ufs_chmod? > This should attempt to catch the bug a little bit earlier by detecting > an attempt to VOP_SETATTR a free inode. No problem, I'll let you know how it goes. Kris --BXVAT5kNtrzKuDFl 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 iD8DBQE8fEfcWry0BWjoQKURAkO4AKDB3/XOExbYbjJI7tcWim/u3ns+zgCgiXMs 1fTvsnozYRZLgDTMvuXICeI= =5vCb -----END PGP SIGNATURE----- --BXVAT5kNtrzKuDFl-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Wed Feb 27 3:23:47 2002 Delivered-To: freebsd-fs@freebsd.org Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by hub.freebsd.org (Postfix) with ESMTP id 9AB4737B400 for ; Wed, 27 Feb 2002 03:23:41 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1192) id 7C178AE27E; Wed, 27 Feb 2002 03:23:41 -0800 (PST) Date: Wed, 27 Feb 2002 03:23:41 -0800 From: Alfred Perlstein To: Bruce Evans Cc: fs@FreeBSD.ORG Subject: Re: mkdir / == odd Message-ID: <20020227112341.GI80761@elvis.mu.org> References: <20020218132751.GX12136@elvis.mu.org> <20020219162133.D858-100000@gamplex.bde.org> <20020219054710.GD12136@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020219054710.GD12136@elvis.mu.org> User-Agent: Mutt/1.3.27i 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 * Alfred Perlstein [020218 21:47] wrote: > * Bruce Evans [020218 21:33] wrote: > > On Mon, 18 Feb 2002, Alfred Perlstein wrote: > > > > > # mkdir / > > > mkdir: /: Is a directory > > > > > > shouldn't mkdir get a EEXIST error back? > > > > Looks like I didn't fix this special case when I fixed trailing slash > > handling in rev.1.8 of vfs_lookup.c. > > > > I was looking at something like this: (untested) > > Index: vfs_lookup.c > =================================================================== > RCS file: /home/ncvs/src/sys/kern/vfs_lookup.c,v > retrieving revision 1.49 > diff -u -r1.49 vfs_lookup.c > --- vfs_lookup.c 13 Jan 2002 21:37:48 -0000 1.49 > +++ vfs_lookup.c 18 Feb 2002 20:59:59 -0000 > @@ -386,7 +386,11 @@ > goto bad; > } > if (cnp->cn_nameiop != LOOKUP) { > - error = EISDIR; > + if (cnp->cn_nameiop == CREATE && > + (ndp->ni_cnd.cn_flags & WILLBEDIR) != 0) > + error = EEXIST; > + else > + error = EISDIR; > goto bad; > } > if (wantparent) { Any comments/objections? Do I need the test for WILLBEDIR? -- -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.' Tax deductible donations for FreeBSD: http://www.freebsdfoundation.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Wed Feb 27 20:11: 8 2002 Delivered-To: freebsd-fs@freebsd.org Received: from hotmail.com (oe30.law14.hotmail.com [64.4.20.87]) by hub.freebsd.org (Postfix) with ESMTP id 3CFB737B400 for ; Wed, 27 Feb 2002 20:11:05 -0800 (PST) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed, 27 Feb 2002 20:11:05 -0800 X-Originating-IP: [202.9.133.182] From: "Rohan Bakshi" To: Subject: Date: Thu, 28 Feb 2002 09:30:54 +0530 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 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Message-ID: X-OriginalArrivalTime: 28 Feb 2002 04:11:05.0009 (UTC) FILETIME=[F0CBF210:01C1C00D] 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 subscribe freebsd-fs To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Wed Feb 27 23:20:56 2002 Delivered-To: freebsd-fs@freebsd.org Received: from web14604.mail.yahoo.com (web14604.mail.yahoo.com [216.136.224.84]) by hub.freebsd.org (Postfix) with SMTP id 2364537B427 for ; Wed, 27 Feb 2002 23:20:51 -0800 (PST) Message-ID: <20020228072050.15227.qmail@web14604.mail.yahoo.com> Received: from [61.11.22.169] by web14604.mail.yahoo.com via HTTP; Wed, 27 Feb 2002 23:20:50 PST Date: Wed, 27 Feb 2002 23:20:50 -0800 (PST) From: Balaji Subject: Help on NFS Metadata!! To: rick@snowhite.uoguelph.ca, rick@snowhite.cis.uoguelph.ca, root@snowhite.cis.uoguelph.ca 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 Respected Sir, My name is Balaji Raghavan. My two friends and I are implementing high availability for NFS in FreeBSD 4.3, according to Dr. Anupam Bhide's Usenix paper. We would like to know what all metadata are to be stored to build the state of the failed server on the alive one in BSD. This is very urgent. I am sorry for any kind of inconvenience caused. Thanking you in Anticipation. Yours Sincerely, Balaji. __________________________________________________ Do You Yahoo!? Yahoo! Greetings - Send FREE e-cards for every occasion! http://greetings.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Wed Feb 27 23:21:39 2002 Delivered-To: freebsd-fs@freebsd.org Received: from web14601.mail.yahoo.com (web14601.mail.yahoo.com [216.136.224.79]) by hub.freebsd.org (Postfix) with SMTP id F24F537B426 for ; Wed, 27 Feb 2002 23:20:59 -0800 (PST) Message-ID: <20020228072058.12024.qmail@web14601.mail.yahoo.com> Received: from [61.11.22.169] by web14601.mail.yahoo.com via HTTP; Wed, 27 Feb 2002 23:20:58 PST Date: Wed, 27 Feb 2002 23:20:58 -0800 (PST) From: Balaji Subject: Help on NFS Metadata!! To: rick@snowhite.uoguelph.ca, rick@snowhite.cis.uoguelph.ca, root@snowhite.cis.uoguelph.ca 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 Respected Sir, My name is Balaji Raghavan. My two friends and I are implementing high availability for NFS in FreeBSD 4.3, according to Dr. Anupam Bhide's Usenix paper. We would like to know what all metadata are to be stored to build the state of the failed server on the alive one. This is very urgent. I am sorry for any kind of inconvenience caused. Thanking you in Anticipation. Yours Sincerely, Balaji. __________________________________________________ Do You Yahoo!? Yahoo! Greetings - Send FREE e-cards for every occasion! http://greetings.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Thu Feb 28 13:53: 7 2002 Delivered-To: freebsd-fs@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-169-107-10.dsl.lsan03.pacbell.net [64.169.107.10]) by hub.freebsd.org (Postfix) with ESMTP id 6532B37B43A for ; Thu, 28 Feb 2002 13:52:34 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id B72C466C32; Thu, 28 Feb 2002 13:52:33 -0800 (PST) Date: Thu, 28 Feb 2002 13:52:33 -0800 From: Kris Kennaway To: Kris Kennaway Cc: Ian Dowse , Kirk McKusick , Matthew Dillon , Tony Finch , fs@FreeBSD.ORG, fanf@chiark.greenend.org.uk Subject: Re: UFS panic on -stable Message-ID: <20020228135233.B5586@xor.obsecurity.org> References: <200202260141.g1Q1f8i28365@beastie.mckusick.com> <200202260237.aa51774@salmon.maths.tcd.ie> <20020226184340.A78562@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="s/l3CgOIzMHHjg/5" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20020226184340.A78562@xor.obsecurity.org>; from kris@obsecurity.org on Tue, Feb 26, 2002 at 06:43:40PM -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 --s/l3CgOIzMHHjg/5 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Feb 26, 2002 at 06:43:40PM -0800, Kris Kennaway wrote: > On Tue, Feb 26, 2002 at 02:37:47AM +0000, Ian Dowse wrote: >=20 > > Kris, if it's not too awkward to make changes to the cluster kernels, > > could you try applying the following extra sanity check to ufs_chmod? > > This should attempt to catch the bug a little bit earlier by detecting > > an attempt to VOP_SETATTR a free inode. >=20 > No problem, I'll let you know how it goes. Well, I got a different panic last night on one of them (I don't think there's much hope of debugging this one). The only thing I'd change was to increase kern.maxvnodes from 33952 to 100000 (they weren't running a kernel with your patch yet, one of them is now ;-). Kris IdlePTD at phsyical address 0x004a2000 initial pcb at physical address 0x003e84a0 panicstr: from debugger panic messages: --- panic: double fault panic: from debugger Uptime: 7h21m38s dumping to dev #ad/1, offset 1051136 dump ata0: resetting devices .. done 510 509 508 507 506 505 504 503 502 501 500 499 498 497 496 495 494 493 492= 491 490 489 488 487 486 485 484 483 482 481 480 479 478 477 476 475 474 47= 3 472 471 470 469 468 467 466 465 464 463 462 461 460 459 458 457 456 455 4= 54 453 452 451 450 449 448 447 446 445 444 443 442 441 440 439 438 437 436 = 435 434 433 432 431 430 429 428 427 426 425 424 423 422 421 420 419 418 417= 416 415 414 413 412 411 410 409 408 407 406 405 404 403 402 401 400 399 39= 8 397 396 395 394 393 392 391 390 389 388 387 386 385 384 383 382 381 380 3= 79 378 377 376 375 374 373 372 371 370 369 368 367 366 365 364 363 362 361 = 360 359 358 357 356 355 354 353 352 351 350 349 348 347 346 345 344 343 342= 341 340 339 338 337 336 335 334 333 332 331 330 329 328 327 326 325 324 32= 3 322 321 320 319 318 317 316 315 314 313 312 311 310 309 308 307 306 305 3= 04 303 302 301 300 299 298 297 296 295 294 293 292 291 290 289 288 287 286 = 285 284 283 282 281 280 279 278 277 276 275 274 273 272 271 270 269 268 267= 266 265 264 263 262 261 260 259 258 257 256 255 254 253 252 251 250 249 24= 8 247 246 245 244 243 242 241 240 239 238 237 236 235 234 233 232 231 230 2= 29 228 227 226 225 224 223 222 221 220 219 218 217 216 215 214 213 212 211 = 210 209 208 207 206 205 204 203 202 201 200 199 198 197 196 195 194 193 192= 191 190 189 188 187 186 185 184 183 182 181 180 179 178 177 176 175 174 17= 3 172 171 170 169 168 167 166 165 164 163 162 161 160 159 158 157 156 155 1= 54 153 152 151 150 149 148 147 146 145 144 143 142 141 140 139 138 137 136 = 135 134 133 132 131 130 129 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 58 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 --- #0 dumpsys () at ../../kern/kern_shutdown.c:487 487 if (dumping++) { (kgdb) bt #0 dumpsys () at ../../kern/kern_shutdown.c:487 #1 0xc01b1554 in boot (howto=3D260) at ../../kern/kern_shutdown.c:316 #2 0xc01b19a1 in panic (fmt=3D0xc03510e4 "from debugger") at ../../kern/ke= rn_shutdown.c:595 #3 0xc013d1b1 in db_panic (addr=3D-1070477807, have_addr=3D0, count=3D-1, = modif=3D0xc040074c "") at ../../ddb/db_command.c:435 #4 0xc013d14f in db_command (last_cmdp=3D0xc03a8f64, cmd_table=3D0xc03a8da= 4, aux_cmd_tablep=3D0xc03d9618) at ../../ddb/db_command.c:333 #5 0xc013d216 in db_command_loop () at ../../ddb/db_command.c:457 #6 0xc013f3c7 in db_trap (type=3D3, code=3D0) at ../../ddb/db_trap.c:71 #7 0xc031cbb0 in kdb_trap (type=3D3, code=3D0, regs=3D0xc0400854) at ../..= /i386/i386/db_interface.c:158 #8 0xc032bee0 in trap (frame=3D{tf_fs =3D 912654360, tf_es =3D 808648720, = tf_ds =3D 16, tf_edi =3D 0, tf_esi =3D 256, tf_ebp =3D -1069545316, tf_isp = =3D -1069545344, tf_ebx =3D -1069958749, tf_edx =3D -1069968593, tf_ecx =3D 1021, tf_eax =3D 18, tf_trapno =3D= 3, tf_err =3D 0, tf_eip =3D -1070477807, tf_cs =3D 8, tf_eflags =3D 16454,= tf_esp =3D -1069968609, tf_ss =3D -1070158597}) at ../../i386/i386/trap.c:584 #9 0xc031ce11 in Debugger (msg=3D0xc036acfb "panic") at machine/cpufunc.h:= 67 #10 0xc01b1998 in panic (fmt=3D0xc039b9a3 "double fault") at ../../kern/ker= n_shutdown.c:593 #11 0xc032c5eb in dblfault_handler () at ../../i386/i386/trap.c:996 (kgdb) --s/l3CgOIzMHHjg/5 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 iD8DBQE8fqahWry0BWjoQKURAvlCAJ9zBie1fJ8lrv4ENxxJbDYSJjQncwCg6e3m iAJtWpgnUY+pARW6BUoKNBM= =qK5f -----END PGP SIGNATURE----- --s/l3CgOIzMHHjg/5-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Thu Feb 28 23: 4:51 2002 Delivered-To: freebsd-fs@freebsd.org Received: from web14607.mail.yahoo.com (web14607.mail.yahoo.com [216.136.224.87]) by hub.freebsd.org (Postfix) with SMTP id DAB2937B417 for ; Thu, 28 Feb 2002 23:04:45 -0800 (PST) Message-ID: <20020301070445.87381.qmail@web14607.mail.yahoo.com> Received: from [61.11.21.103] by web14607.mail.yahoo.com via HTTP; Thu, 28 Feb 2002 23:04:45 PST Date: Thu, 28 Feb 2002 23:04:45 -0800 (PST) From: Balaji To: rick@snowhite.cis.uoguelph.ca, brent.callaghan@sun.com 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 Respected Sir, I have two NFS servers acting as backups for each other. We are working in FreeBSD. Now when a server fails, the other server takes over the IP address of the failed server on a different Network Interface. But, now the clients of the failed server are not able to mount from the backup server inspite of the fact that the mountpoint permissions are satisfied in /etc/exports. The NFS mountpoints are shared by both servers. I cannot afford to kill and restart the nfsds. I run a "kill -s HUP 'cat /var/run/mountd.pid'" after combining the exports files of both the servers. But still this does not work. How can I bind the nfsds to the new IP address without restarting them? If I try to run more nfsds by binding them to the new IP address, it gives me a "can't bind udp adress: address already in use" error. And still the nfs clients cannot mount the NFS exported partitions. Plz help. Awaiting your reply. Yours Sincerely, Balaji. __________________________________________________ Do You Yahoo!? Yahoo! Greetings - Send FREE e-cards for every occasion! http://greetings.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Fri Mar 1 13:50:16 2002 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 9363D37B405 for ; Fri, 1 Mar 2002 13:50:12 -0800 (PST) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.5) with SMTP id g21LnxD95578; Fri, 1 Mar 2002 16:49:59 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Fri, 1 Mar 2002 16:49:59 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Luca Severini Cc: freebsd-fs@freebsd.org Subject: Re: get/setattrlist functions In-Reply-To: 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 You probably want to send this e-mail to the Darwin Development mailing list, darwin-development@lists.apple.com, since this is more strictly a Darwin question than a FreeBSD question. The get/setattrlist() vnode operations (and system calls) are not present on the FreeBSD side. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services On Mon, 25 Feb 2002, Luca Severini wrote: > Hi everybody, > > I'm porting a volume mirroring software, I developed years ago for A/UX and > AIX, to MacOSX/Darwin. > Unfortunately the way to store the resource fork and the Finder's attributes > in MacOSX/Darwin is completely different than what A/UX and AIX used (files > and folders). > "More unfortunately" there is no official documentation about the two > functions you must use to achieve that from a Mach-O software; I know I > could use the Carbon API but I don't want to develop a real mac Application > for now, I want only to port the old one. > Does anybody of you know where/how is possible to obtain an exaustive > explanation for those calls? (is anybody working at Apple listening?). Those > are very import calls for whoever has to work with filesystems. > Do anybody of you knows which of the values listed in I have to > use with get/setattrlist() to get/set the "Appleshare" folder attribute that > prevents the user to move, rename or delete such folder (from the MacOS9 > Finder "Get Info" command) ? > Thanks a lot in advance and sorry for my english. > > Best regards, > > Luca Severini > email: lucaseverini@mac.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 Fri Mar 1 13:52:38 2002 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 3E4A137B41D for ; Fri, 1 Mar 2002 13:52:34 -0800 (PST) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.5) with SMTP id g21LqGD95599; Fri, 1 Mar 2002 16:52:20 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Fri, 1 Mar 2002 16:52:16 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Byron Servies Cc: freebsd-fs@freebsd.org Subject: Re: Retrieving a list of ACLs for a file In-Reply-To: <20020225215526.J13918@pacang.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 Unfortunately, the POSIX.1e API doesn't define a way to get a list of valid ACL types for a particular filesystem object (or even a filesystem). For the time being, it's probably sufficient to assume that there will only be ACL_TYPE_ACCESS and ACL_TYPE_DEFAULT ACLs present on filesystems. Other ACL constants have been tentatively assigned, but are not used. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services On Mon, 25 Feb 2002, Byron Servies wrote: > Hi there! > > I am working on adding ACL support to the freebsd port of Legato > NetWorker. Everything appears to be straight forward, with the > exception of retrieving a complete list of the ACLs on a file. > > From the acl_get manual page, it appears that there is no way > to retrieve a complete list, but that each ACL type must be > retrieved individually. My concern is that if new ACL types > are added, the backup will still succeed though the new ACLs > would not actually be backed up. > > Does anyone have any suggestions on a good way to retrieve > a complete list, or do I just have to hard code it? > > Thanks, > > Byron > > > 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 Fri Mar 1 14:13:54 2002 Delivered-To: freebsd-fs@freebsd.org Received: from deathsgate.demon.co.uk (deathsgate.demon.co.uk [193.237.157.5]) by hub.freebsd.org (Postfix) with ESMTP id 8147F37B402 for ; Fri, 1 Mar 2002 14:13:51 -0800 (PST) Received: (from bradley@localhost) by deathsgate.demon.co.uk (8.11.6/8.11.6) id g21MER212450; Fri, 1 Mar 2002 22:14:27 GMT (envelope-from bradley) Date: Fri, 1 Mar 2002 22:13:06 +0000 From: Bradley Kite To: reiserfs-list@namesys.com, freebsd-fs@freebsd.org Subject: Reiserfs on Freebsd Message-ID: <20020301221306.A12425@deathsgate.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.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 Hi there. I currently have too much time on my hands and am looking into the possibilities (and feasibility) of implementing ReiserFS on FreeBSD. Does any body know if someone is currently doing this? I dont want to duplicate the effort involved, and would much rather join an existing project that is trying to achieve the same thing. Also, (correct me if I am wrong), I believe that the main ReiserFS code can remain pritty much the same, and only the parts where it interfaces with the VFS, and low-level device drivers would need to be changed in order to port it over to FreeBSD. This is just a guess tho, as I havent really had a propper look at the reiserFS code yet. Any guidance/advice will be much appreciated. -- Bradley Kite. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Fri Mar 1 14:31: 9 2002 Delivered-To: freebsd-fs@freebsd.org Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by hub.freebsd.org (Postfix) with ESMTP id 6E17137B402 for ; Fri, 1 Mar 2002 14:31:06 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1192) id 3C738AE2DA; Fri, 1 Mar 2002 14:31:06 -0800 (PST) Date: Fri, 1 Mar 2002 14:31:06 -0800 From: Alfred Perlstein To: Bradley Kite Cc: reiserfs-list@namesys.com, freebsd-fs@freebsd.org Subject: Re: Reiserfs on Freebsd Message-ID: <20020301223106.GN77980@elvis.mu.org> References: <20020301221306.A12425@deathsgate.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020301221306.A12425@deathsgate.demon.co.uk> User-Agent: Mutt/1.3.27i 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 * Bradley Kite [020301 14:14] wrote: > Hi there. > > I currently have too much time on my hands and am looking > into the possibilities (and feasibility) of implementing ReiserFS > on FreeBSD. Why? Softupdates does a better job than logging does. :) > Does any body know if someone is currently doing this? I dont want to > duplicate the effort involved, and would much rather join an > existing project that is trying to achieve the same thing. No one that I've heard of. > Also, (correct me if I am wrong), I believe that the main ReiserFS > code can remain pritty much the same, and only the parts where it > interfaces with the VFS, and low-level device drivers would need > to be changed in order to port it over to FreeBSD. This is just a guess > tho, as I havent really had a propper look at the reiserFS code yet. Your assumptions are correct however your belief that it's a simple task may be a mistake. :) -- -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.' Tax deductible donations for FreeBSD: http://www.freebsdfoundation.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Fri Mar 1 14:47: 7 2002 Delivered-To: freebsd-fs@freebsd.org Received: from deathsgate.demon.co.uk (deathsgate.demon.co.uk [193.237.157.5]) by hub.freebsd.org (Postfix) with ESMTP id 91D3437B405 for ; Fri, 1 Mar 2002 14:47:04 -0800 (PST) Received: (from bradley@localhost) by deathsgate.demon.co.uk (8.11.6/8.11.6) id g21Mlbv12660; Fri, 1 Mar 2002 22:47:37 GMT (envelope-from bradley) Date: Fri, 1 Mar 2002 22:46:16 +0000 From: Bradley Kite To: Alfred Perlstein Cc: reiserfs-list@namesys.com, freebsd-fs@freebsd.org Subject: Re: [reiserfs-list] Re: Reiserfs on Freebsd Message-ID: <20020301224616.A12630@deathsgate.demon.co.uk> References: <20020301221306.A12425@deathsgate.demon.co.uk> <20020301223106.GN77980@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20020301223106.GN77980@elvis.mu.org>; from bright@mu.org on Fri, Mar 01, 2002 at 02:31:06PM -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 The reason is convenience (dont want to have to reboot every time I need that 2k file in Linux) - you may well ask why FreeBSD supports NTFS + FAT > Why? Softupdates does a better job than logging does. :) [snip] > Your assumptions are correct however your belief that it's a simple > task may be a mistake. :) And also it will teach me a lot about both Linux + FreeBSD kernel internals -- Brad To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Fri Mar 1 17:37:48 2002 Delivered-To: freebsd-fs@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-169-107-10.dsl.lsan03.pacbell.net [64.169.107.10]) by hub.freebsd.org (Postfix) with ESMTP id E786C37B405 for ; Fri, 1 Mar 2002 17:37:41 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 31E4D66C32; Fri, 1 Mar 2002 17:37:41 -0800 (PST) Date: Fri, 1 Mar 2002 17:37:41 -0800 From: Kris Kennaway To: Kris Kennaway Cc: Ian Dowse , Kirk McKusick , Matthew Dillon , Tony Finch , fs@FreeBSD.ORG, fanf@chiark.greenend.org.uk Subject: Re: UFS panic on -stable Message-ID: <20020301173740.A21179@xor.obsecurity.org> References: <200202260141.g1Q1f8i28365@beastie.mckusick.com> <200202260237.aa51774@salmon.maths.tcd.ie> <20020226184340.A78562@xor.obsecurity.org> <20020228135233.B5586@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="u3/rZRmxL6MmkK24" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20020228135233.B5586@xor.obsecurity.org>; from kris@obsecurity.org on Thu, Feb 28, 2002 at 01:52:33PM -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 --u3/rZRmxL6MmkK24 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline One of the other machines panicked today; it wasn't even under load at the time (last reported load average was 0.00). A different panic this time (I've seen it before, but I couldn't get a crashdump that time). A common thread in all of these panics is that they all seem to involve operations on MFS filesystems. Even though the two UFS disk filesystems on the clients have the most read/write load, I don't think I've seen a panic involving them. /var: bad dir ino 24 at offset 0: mangled entry panic: ufs_dirbad: bad dir Debugger("panic") Stopped at Debugger+0x35: movb $0,in_Debugger.426 db> Here's the backtrace. #10 0xc01b1998 in panic (fmt=0xc03868e7 "ufs_dirbad: bad dir") at ../../kern/kern_shutdown.c:593 #11 0xc02ba91e in ufs_dirbad (ip=0xc1d6bb00, offset=0, how=0xc0386890 "mangled entry") at ../../ufs/ufs/ufs_lookup.c:641 #12 0xc02ba11b in ufs_lookup (ap=0xd6853d24) at ../../ufs/ufs/ufs_lookup.c:291 #13 0xc02bf1bd in ufs_vnoperate (ap=0xd6853d24) at ../../ufs/ufs/ufs_vnops.c:2422 #14 0xc01dab16 in vfs_cache_lookup (ap=0xd6853d7c) at vnode_if.h:77 #15 0xc02bf1bd in ufs_vnoperate (ap=0xd6853d7c) at ../../ufs/ufs/ufs_vnops.c:2422 #16 0xc01ddaf5 in lookup (ndp=0xd6853ed4) at vnode_if.h:52 #17 0xc01dd5e0 in namei (ndp=0xd6853ed4) at ../../kern/vfs_lookup.c:153 #18 0xc01e61b5 in vn_open (ndp=0xd6853ed4, fmode=1, cmode=420) at ../../kern/vfs_vnops.c:138 #19 0xc01e21c8 in open (p=0xd6796a00, uap=0xd6853f80) at ../../kern/vfs_syscalls.c:1006 #20 0xc032c7fd in syscall2 (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 4, tf_esi = 672135776, tf_ebp = -1077945320, tf_isp = -695910444, tf_ebx = 672062116, tf_edx = 672135776, tf_ecx = 16, tf_eax = 5, tf_trapno = 7, tf_err = 2, tf_eip = 671971036, tf_cs = 31, tf_eflags = 647, tf_esp = -1077945364, tf_ss = 47}) at ../../i386/i386/trap.c:1167 #21 0xc031dab5 in Xint0x80_syscall () #22 0x804a987 in ?? () #23 0x804a4b5 in ?? () #24 0x8049432 in ?? () #25 0x80491c9 in ?? () #26 0x80490bd in ?? () (kgdb) Kris --u3/rZRmxL6MmkK24 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 iD8DBQE8gCzkWry0BWjoQKURAu55AJ9itvIYKYzoJRmcU4yLvrzpzortMwCdGTWo 5DI5b2Xqb31Ft2rSq2VoRPg= =v+Qi -----END PGP SIGNATURE----- --u3/rZRmxL6MmkK24-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Fri Mar 1 17:44: 3 2002 Delivered-To: freebsd-fs@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-169-107-10.dsl.lsan03.pacbell.net [64.169.107.10]) by hub.freebsd.org (Postfix) with ESMTP id 7335A37B417 for ; Fri, 1 Mar 2002 17:43:58 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id D471666C32; Fri, 1 Mar 2002 17:43:57 -0800 (PST) Date: Fri, 1 Mar 2002 17:43:57 -0800 From: Kris Kennaway To: Kris Kennaway Cc: Ian Dowse , Kirk McKusick , Matthew Dillon , Tony Finch , fs@FreeBSD.ORG, fanf@chiark.greenend.org.uk Subject: Re: UFS panic on -stable Message-ID: <20020301174357.A21371@xor.obsecurity.org> References: <200202260141.g1Q1f8i28365@beastie.mckusick.com> <200202260237.aa51774@salmon.maths.tcd.ie> <20020226184340.A78562@xor.obsecurity.org> <20020228135233.B5586@xor.obsecurity.org> <20020301173740.A21179@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="M9NhX3UHpAaciwkO" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20020301173740.A21179@xor.obsecurity.org>; from kris@obsecurity.org on Fri, Mar 01, 2002 at 05:37:41PM -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 --M9NhX3UHpAaciwkO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Mar 01, 2002 at 05:37:41PM -0800, Kris Kennaway wrote: > Here's the backtrace. I forgot to mention that this was a kernel without Ian's sanity check patch. I'm rebooting all of the machines now so they're running with that kernel. Kris --M9NhX3UHpAaciwkO 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 iD8DBQE8gC5dWry0BWjoQKURAjAYAJ9/maH9BVgkP6EXuQTmtrLJubTz9wCeIpQg hDbmTVFeDLP6YoWS0Vzbrbw= =v2ux -----END PGP SIGNATURE----- --M9NhX3UHpAaciwkO-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Fri Mar 1 17:50:40 2002 Delivered-To: freebsd-fs@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 28DD337B400 for ; Fri, 1 Mar 2002 17:50:36 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id g221oWS48392; Fri, 1 Mar 2002 17:50:32 -0800 (PST) (envelope-from dillon) Date: Fri, 1 Mar 2002 17:50:32 -0800 (PST) From: Matthew Dillon Message-Id: <200203020150.g221oWS48392@apollo.backplane.com> To: Kris Kennaway , Ian Dowse , Kirk McKusick , Finch , fs@FreeBSD.ORG, fanf@chiark.greenend.org.uk Subject: Re: UFS panic on -stable References: <200202260141.g1Q1f8i28365@beastie.mckusick.com> <200202260237.aa51774@salmon.maths.tcd.ie> <20020226184340.A78562@xor.obsecurity.org> <20020228135233.B5586@xor.obsecurity.org> <20020301173740.A21179@xor.obsecurity.org> 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 :One of the other machines panicked today; it wasn't even under load at :the time (last reported load average was 0.00). A different panic :this time (I've seen it before, but I couldn't get a crashdump that :time). : :A common thread in all of these panics is that they all seem to :involve operations on MFS filesystems. Even though the two UFS disk :filesystems on the clients have the most read/write load, I don't :think I've seen a panic involving them. : :/var: bad dir ino 24 at offset 0: mangled entry :panic: ufs_dirbad: bad dir :Debugger("panic") :Stopped at Debugger+0x35: movb $0,in_Debugger.426 :db> : :Here's the backtrace. I wonder if this has anything to do with MFS's VM pages getting paged in and out. Could you try hacking mount_mfs to mlock() the MFS memory? As shown below. I'm not entirely sure this will actually do anything, but it's worth a shot (assuming you have enough memory to cover all your MFS mounted filesystems). If this does the trick I'll take a look at the way MFS accesses the process's VM space. If it doesn't at least we will know it isn't related to MFS's paging. -Matt Index: mkfs.c =================================================================== RCS file: /home/ncvs/src/sbin/newfs/mkfs.c,v retrieving revision 1.29.2.6 diff -u -r1.29.2.6 mkfs.c --- mkfs.c 21 Sep 2001 19:15:21 -0000 1.29.2.6 +++ mkfs.c 2 Mar 2002 01:49:33 -0000 @@ -236,6 +236,8 @@ 0); if(membase == MAP_FAILED) err(12, "mmap"); + mlock(membase, fssize * sectorsize); + bzero(membase, fssize * sectorsize); close(fd); } else { #ifndef STANDALONE To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Fri Mar 1 17:56:40 2002 Delivered-To: freebsd-fs@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-169-107-10.dsl.lsan03.pacbell.net [64.169.107.10]) by hub.freebsd.org (Postfix) with ESMTP id 75D5A37B402 for ; Fri, 1 Mar 2002 17:56:36 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 8CBA166C32; Fri, 1 Mar 2002 17:56:32 -0800 (PST) Date: Fri, 1 Mar 2002 17:56:32 -0800 From: Kris Kennaway To: Matthew Dillon Cc: Kris Kennaway , Ian Dowse , Kirk McKusick , Finch , fs@FreeBSD.ORG, fanf@chiark.greenend.org.uk Subject: Re: UFS panic on -stable Message-ID: <20020301175632.A21599@xor.obsecurity.org> References: <200202260141.g1Q1f8i28365@beastie.mckusick.com> <200202260237.aa51774@salmon.maths.tcd.ie> <20020226184340.A78562@xor.obsecurity.org> <20020228135233.B5586@xor.obsecurity.org> <20020301173740.A21179@xor.obsecurity.org> <200203020150.g221oWS48392@apollo.backplane.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="82I3+IH0IqGh5yIs" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <200203020150.g221oWS48392@apollo.backplane.com>; from dillon@apollo.backplane.com on Fri, Mar 01, 2002 at 05:50:32PM -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 --82I3+IH0IqGh5yIs Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Mar 01, 2002 at 05:50:32PM -0800, Matthew Dillon wrote: > I wonder if this has anything to do with MFS's VM pages getting > paged in and out. >=20 > Could you try hacking mount_mfs to mlock() the MFS memory? As > shown below. I'm not entirely sure this will actually do anything, > but it's worth a shot (assuming you have enough memory to cover all > your MFS mounted filesystems). >=20 > If this does the trick I'll take a look at the way MFS accesses > the process's VM space. If it doesn't at least we will know it > isn't related to MFS's paging. Will try! I've also given up on trying to get packages built for now, and am just running some MFS stress tests to try and trigger panics. Kris --82I3+IH0IqGh5yIs 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 iD8DBQE8gDFPWry0BWjoQKURAiWMAKCWlh+5o7fPzz1ZC+6v9tgVE2egGACggJPI ZAy7hkFU+JXogoWP1X+8YU8= =t1Ud -----END PGP SIGNATURE----- --82I3+IH0IqGh5yIs-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Fri Mar 1 18:40:53 2002 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 2D44537B402 for ; Fri, 1 Mar 2002 18:40:49 -0800 (PST) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.5) with SMTP id g222c4D00111; Fri, 1 Mar 2002 21:38:04 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Fri, 1 Mar 2002 21:38:04 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Bradley Kite Cc: Alfred Perlstein , reiserfs-list@namesys.com, freebsd-fs@freebsd.org Subject: Re: [reiserfs-list] Re: Reiserfs on Freebsd In-Reply-To: <20020301224616.A12630@deathsgate.demon.co.uk> 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 On Fri, 1 Mar 2002, Bradley Kite wrote: > The reason is convenience (dont want to have to reboot every time I need > that 2k file in Linux) - you may well ask why FreeBSD supports NTFS + FAT > > > Why? Softupdates does a better job than logging does. :) > [snip] > > Your assumptions are correct however your belief that it's a simple > > task may be a mistake. :) > > And also it will teach me a lot about both Linux + FreeBSD kernel > internals Unfortunately, it's probably one of those tasks where you want to go in knowing those things, too :-). Suffice to say that, despite Alfred's skepticism, there probably is interest in this in the FreeBSD community, although perhaps not for the reasons you cite. I personally would be interested in seeing the full data journalling for reliability in some environments. I won't discourage you from giving it a spin, of course :-) Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Fri Mar 1 23: 4:21 2002 Delivered-To: freebsd-fs@freebsd.org Received: from deathsgate.demon.co.uk (deathsgate.demon.co.uk [193.237.157.5]) by hub.freebsd.org (Postfix) with ESMTP id D9E1F37B400; Fri, 1 Mar 2002 23:03:58 -0800 (PST) Received: (from bradley@localhost) by deathsgate.demon.co.uk (8.11.6/8.11.6) id g2274RQ16009; Sat, 2 Mar 2002 07:04:27 GMT (envelope-from bradley) Date: Sat, 2 Mar 2002 07:03:05 +0000 From: Bradley Kite To: Robert Watson Cc: Alfred Perlstein , reiserfs-list@namesys.com, freebsd-fs@freebsd.org Subject: Re: [reiserfs-list] Re: Reiserfs on Freebsd Message-ID: <20020302070305.A15982@deathsgate.demon.co.uk> References: <20020301224616.A12630@deathsgate.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from rwatson@freebsd.org on Fri, Mar 01, 2002 at 09:38:04PM -0500 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 Fri, Mar 01, 2002 at 09:38:04PM -0500, Robert Watson wrote: > Unfortunately, it's probably one of those tasks where you want to go in > knowing those things, too :-). > > Suffice to say that, despite Alfred's skepticism, there probably is > interest in this in the FreeBSD community, although perhaps not for the > reasons you cite. I personally would be interested in seeing the full > data journalling for reliability in some environments. > > I won't discourage you from giving it a spin, of course :-) Ack, I probably am approaching the problem with a little naivety, but this is one way of learning, and your feedback is much appreciated!! On the other hand, some of the best peices of software in use today stemmed from the need of the developer to scratch a personal itch without quite realising the full value of their code :-) -- Bradley To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Sat Mar 2 10: 0:56 2002 Delivered-To: freebsd-fs@freebsd.org Received: from dns.pacang.com (adsl-63-193-245-242.dsl.snfc21.pacbell.net [63.193.245.242]) by hub.freebsd.org (Postfix) with ESMTP id AD88D37B405; Sat, 2 Mar 2002 10:00:51 -0800 (PST) Received: (from bservies@localhost) by dns.pacang.com (8.9.3/8.9.2) id KAA15722; Sat, 2 Mar 2002 10:00:50 -0800 Date: Sat, 2 Mar 2002 10:00:50 -0800 From: Byron Servies To: Robert Watson Cc: freebsd-fs@freebsd.org Subject: Re: Retrieving a list of ACLs for a file Message-ID: <20020302100050.A15624@pacang.com> References: <20020225215526.J13918@pacang.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from rwatson@freebsd.org on Fri, Mar 01, 2002 at 04:52:16PM -0500 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 March 01, 2002 at 16:52, Robert Watson wrote: > > Unfortunately, the POSIX.1e API doesn't define a way to get a list of > valid ACL types for a particular filesystem object (or even a filesystem). > For the time being, it's probably sufficient to assume that there will > only be ACL_TYPE_ACCESS and ACL_TYPE_DEFAULT ACLs present on filesystems. > Other ACL constants have been tentatively assigned, but are not used. > Hi, I was looking around some more last week and noticed that the posix acl support is built upon a more generic extattr facility. Instead of backing up the posix acl's directly, should I instead be using this facility to backup any possible additional attributes on a file? Since this is a freebsd api, I could add the function necessary to collect a complete list, if one does not exist yet. Preferences? Thanks for the advice, Byron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Sat Mar 2 10:10: 8 2002 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 3F51F37B41A for ; Sat, 2 Mar 2002 10:09:56 -0800 (PST) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.5) with SMTP id g22I9iD15108; Sat, 2 Mar 2002 13:09:44 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Sat, 2 Mar 2002 13:09:43 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Byron Servies Cc: freebsd-fs@freebsd.org Subject: Re: Retrieving a list of ACLs for a file In-Reply-To: <20020302100050.A15624@pacang.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 On Sat, 2 Mar 2002, Byron Servies wrote: > On March 01, 2002 at 16:52, Robert Watson wrote: > > > > Unfortunately, the POSIX.1e API doesn't define a way to get a list of > > valid ACL types for a particular filesystem object (or even a filesystem). > > For the time being, it's probably sufficient to assume that there will > > only be ACL_TYPE_ACCESS and ACL_TYPE_DEFAULT ACLs present on filesystems. > > Other ACL constants have been tentatively assigned, but are not used. > > I was looking around some more last week and noticed that the posix acl > support is built upon a more generic extattr facility. Instead of > backing up the posix acl's directly, should I instead be using this > facility to backup any possible additional attributes on a file? > > Since this is a freebsd api, I could add the function necessary to > collect a complete list, if one does not exist yet. > > Preferences? > > Thanks for the advice, Byron, Yes, indeed, the ACL mechanism for UFS is based on a general purpose extended attribute service. However, that may not be the case for all filesystems. Extended attributes currently exist in two namespaces: system, and user. My suggestion would be to use the following strategy: - Back up all available user extended attributes for a file system node. Currently, I don't know of anyone deploying/using user namespace attributes. Right now, our API supports listing the attributes on a node, but it's not implemented. I think Brian Feldman has that on his TODO list, but I should check. - Don't back up system namespace extended attributes, instead, back up the higher level primitive (such as ACL) using the defined higher level API. Generally speaking, backing up the higher level primitive will result in a portable representation, whereas backing up the lower level primitive may (and probably will) not. The various implementations I've looked at so far tend to actually store the ACL using the results of acl_to_text(), so that the results can be restored on another POSIX.1e-supporting system that might use a different on-disk representation (perhaps due to size differences in uid_t, gid_t, mode_t, etc). I think that we also don't have an implementation of the pathconf() call for POSIX.1e ACLs, but that should be easy to fix as the new mount API becomes available. In that case, when backing up the file system, you should be able to query the availability of EA and ACL services, then if the filesystem supports them, pull out the user EAs, and the POSIX.1e ACLs (default and access for directories, otherwise generally access). With the UFS2 implementation, this should all get a lot faster. I'll prod Brian to make sure we get the ability to list EAs in the next week or so. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Sat Mar 2 11:32:48 2002 Delivered-To: freebsd-fs@freebsd.org Received: from hotmail.com (oe55.law11.hotmail.com [64.4.16.63]) by hub.freebsd.org (Postfix) with ESMTP id CB86E37B405; Sat, 2 Mar 2002 11:32:42 -0800 (PST) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sat, 2 Mar 2002 11:32:42 -0800 X-Originating-IP: [210.214.70.31] From: "Rohan Bakshi" To: "FreeBSD File Systems" Cc: "FreeBSD" Subject: Help: Filesystems Date: Sun, 3 Mar 2002 00:48:16 +0530 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_01B5_01C1C24D.1AC430A0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Message-ID: X-OriginalArrivalTime: 02 Mar 2002 19:32:42.0656 (UTC) FILETIME=[0596C200:01C1C221] 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 This is a multi-part message in MIME format. ------=_NextPart_000_01B5_01C1C24D.1AC430A0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi Sir, Ma'am I am working on project which can be described as below (problem definition) - The project is a utility/ small operating system which will fit on some floppys and the condition is that it should be = able to access any (some of popular like fat, ntfs, ext2,ext3 etc. ) file = systems ie it should be able to read and write and display contents in gui mode I am starting this from scratch. If you have any knowledge, reference or guidence concerning above please mail me. Bye Waiting for your mail ------=_NextPart_000_01B5_01C1C24D.1AC430A0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi Sir,=20 Ma'am

I am working on project which can be described as=20 below

(problem definition) - The project is a utility/ small = operating=20 system
which will fit on some floppys and the condition is that it = should be=20 able
to access any (some of popular like fat, ntfs, ext2,ext3 etc. ) = file=20 systems
ie it should be able to read and write and display contents = in gui=20 mode

I am starting this from scratch. If you have any knowledge,=20 reference or
guidence concerning above please mail me.

Bye = Waiting for=20 your mail
------=_NextPart_000_01B5_01C1C24D.1AC430A0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Sat Mar 2 14: 0:18 2002 Delivered-To: freebsd-fs@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-169-107-10.dsl.lsan03.pacbell.net [64.169.107.10]) by hub.freebsd.org (Postfix) with ESMTP id 129A937B4EF for ; Sat, 2 Mar 2002 13:59:46 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 3EA9966C80; Sat, 2 Mar 2002 13:59:14 -0800 (PST) Date: Sat, 2 Mar 2002 13:59:14 -0800 From: Kris Kennaway To: Kris Kennaway Cc: Matthew Dillon , Ian Dowse , Kirk McKusick , Finch , fs@FreeBSD.ORG, fanf@chiark.greenend.org.uk Subject: Re: UFS panic on -stable Message-ID: <20020302135914.A33051@xor.obsecurity.org> References: <200202260141.g1Q1f8i28365@beastie.mckusick.com> <200202260237.aa51774@salmon.maths.tcd.ie> <20020226184340.A78562@xor.obsecurity.org> <20020228135233.B5586@xor.obsecurity.org> <20020301173740.A21179@xor.obsecurity.org> <200203020150.g221oWS48392@apollo.backplane.com> <20020301175632.A21599@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="FCuugMFkClbJLl1L" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20020301175632.A21599@xor.obsecurity.org>; from kris@obsecurity.org on Fri, Mar 01, 2002 at 05:56:32PM -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 --FCuugMFkClbJLl1L Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Mar 01, 2002 at 05:56:32PM -0800, Kris Kennaway wrote: > On Fri, Mar 01, 2002 at 05:50:32PM -0800, Matthew Dillon wrote: >=20 > > I wonder if this has anything to do with MFS's VM pages getting > > paged in and out. > >=20 > > Could you try hacking mount_mfs to mlock() the MFS memory? As > > shown below. I'm not entirely sure this will actually do anything, > > but it's worth a shot (assuming you have enough memory to cover all > > your MFS mounted filesystems). > >=20 > > If this does the trick I'll take a look at the way MFS accesses > > the process's VM space. If it doesn't at least we will know it > > isn't related to MFS's paging. >=20 > Will try! >=20 > I've also given up on trying to get packages built for now, and am > just running some MFS stress tests to try and trigger panics. So much for the MFS theory: /x: bad dir ino 1006899 at offset 0: mangled entry panic: ufs_dirbad: bad dir Debugger("panic") Stopped at Debugger+0x35: movb $0,in_Debugger.426 db> /x is a local UFS filesystem. Kris --FCuugMFkClbJLl1L 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 iD8DBQE8gUsxWry0BWjoQKURArvuAKCF1xy0feM+34O+QYFcHr+E9pO/FgCg0CeM M42TrAykJhOeQyq/xK9PF8I= =qCkL -----END PGP SIGNATURE----- --FCuugMFkClbJLl1L-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Sat Mar 2 14:10:16 2002 Delivered-To: freebsd-fs@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 69CC137B402 for ; Sat, 2 Mar 2002 14:10:13 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id g22MA8B56666; Sat, 2 Mar 2002 14:10:08 -0800 (PST) (envelope-from dillon) Date: Sat, 2 Mar 2002 14:10:08 -0800 (PST) From: Matthew Dillon Message-Id: <200203022210.g22MA8B56666@apollo.backplane.com> To: Kris Kennaway , Ian Dowse , Kirk McKusick , Finch , fs@FreeBSD.ORG, fanf@chiark.greenend.org.uk Subject: Re: UFS panic on -stable References: <200202260141.g1Q1f8i28365@beastie.mckusick.com> <200202260237.aa51774@salmon.maths.tcd.ie> <20020226184340.A78562@xor.obsecurity.org> <20020228135233.B5586@xor.obsecurity.org> <20020301173740.A21179@xor.obsecurity.org> <200203020150.g221oWS48392@apollo.backplane.com> <20020301175632.A21599@xor.obsecurity.org> <20020302135914.A33051@xor.obsecurity.org> 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 :> Will try! :>=20 :> I've also given up on trying to get packages built for now, and am :> just running some MFS stress tests to try and trigger panics. : :So much for the MFS theory: : :/x: bad dir ino 1006899 at offset 0: mangled entry :panic: ufs_dirbad: bad dir :Debugger("panic") :Stopped at Debugger+0x35: movb $0,in_Debugger.426 :db> : :/x is a local UFS filesystem. : :Kris Do a 'mount -v'. Have you managed to get it to panic in a repeatable fashion yet? -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Sat Mar 2 14:28:17 2002 Delivered-To: freebsd-fs@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-169-107-10.dsl.lsan03.pacbell.net [64.169.107.10]) by hub.freebsd.org (Postfix) with ESMTP id A6B3837B419 for ; Sat, 2 Mar 2002 14:28:08 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 20EC266C32; Sat, 2 Mar 2002 14:28:08 -0800 (PST) Date: Sat, 2 Mar 2002 14:28:07 -0800 From: Kris Kennaway To: Matthew Dillon Cc: Kris Kennaway , Ian Dowse , Kirk McKusick , Finch , fs@FreeBSD.ORG, fanf@chiark.greenend.org.uk Subject: Re: UFS panic on -stable Message-ID: <20020302142807.B33223@xor.obsecurity.org> References: <200202260141.g1Q1f8i28365@beastie.mckusick.com> <200202260237.aa51774@salmon.maths.tcd.ie> <20020226184340.A78562@xor.obsecurity.org> <20020228135233.B5586@xor.obsecurity.org> <20020301173740.A21179@xor.obsecurity.org> <200203020150.g221oWS48392@apollo.backplane.com> <20020301175632.A21599@xor.obsecurity.org> <20020302135914.A33051@xor.obsecurity.org> <200203022210.g22MA8B56666@apollo.backplane.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="IS0zKkzwUGydFO0o" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <200203022210.g22MA8B56666@apollo.backplane.com>; from dillon@apollo.backplane.com on Sat, Mar 02, 2002 at 02:10:08PM -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 --IS0zKkzwUGydFO0o Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Mar 02, 2002 at 02:10:08PM -0800, Matthew Dillon wrote: >=20 > :> Will try! > :>=3D20 > :> I've also given up on trying to get packages built for now, and am > :> just running some MFS stress tests to try and trigger panics. > : > :So much for the MFS theory: > : > :/x: bad dir ino 1006899 at offset 0: mangled entry > :panic: ufs_dirbad: bad dir > :Debugger("panic") > :Stopped at Debugger+0x35: movb $0,in_Debugger.426 > :db> > : > :/x is a local UFS filesystem. > : > :Kris >=20 > Do a 'mount -v'. I posted one earlier in the thread, but here it is again: 216.136.204.23:/a/nfsroots/4.dir4 on / (nfs, read-only) mfs:13 on /etc (mfs, asynchronous, local) mfs:21 on /var (mfs, asynchronous, local) mfs:28 on /tmp (mfs, asynchronous, local) mfs:33 on /dev (mfs, asynchronous, local) /dev/ad0e on /a (ufs, local, soft-updates, writes: sync 2 async 1038, reads= : sync 255 async 1482) /dev/ad0f on /x (ufs, local, soft-updates, writes: sync 718 async 155758, r= eads: sync 21022 async 232) bento:/var/portbuild/4/ports on /x/tmp/4/chroot/26132/a/ports (nfs, read-on= ly) bento:/var/portbuild/4/src on /x/tmp/4/chroot/26132/usr/src (nfs, read-only) bento:/var/portbuild/usr/opt/doc on /x/tmp/4/chroot/26132/usr/opt/doc (nfs,= read-only) > Have you managed to get it to panic in a repeatable > fashion yet? Unfortunately not, except by starting up a package build and waiting a bit :-) However I just realised that I have another datapoint as to when the problem was introduced, because the alpha cluster has been perfectly stable and is running a 4.x kernel dated around Jan 26 (probably a few days earlier, because peter had problems getting the machines to netboot). The most obvious commit after that time period was this one: dillon 2002/01/31 10:51:48 PST Modified files: (Branch: RELENG_4) sys/kern vfs_subr.c Log: MFC new vlrureclaim trigger-point code. [...] I'm going to try backing that out now to see if it fixes things. Kris --IS0zKkzwUGydFO0o 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 iD8DBQE8gVH3Wry0BWjoQKURAoCxAKDsY7zivtMyonXQNGfhJc9wYWNzkgCeOZ0v 2okqmHr4jX59oxsLtlJ63Fw= =x0t1 -----END PGP SIGNATURE----- --IS0zKkzwUGydFO0o-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Sat Mar 2 14:33:19 2002 Delivered-To: freebsd-fs@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 4A79337B405 for ; Sat, 2 Mar 2002 14:33:15 -0800 (PST) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 2 Mar 2002 22:33:14 +0000 (GMT) To: Kris Kennaway Cc: Matthew Dillon , Kirk McKusick , Finch , fs@FreeBSD.ORG, fanf@chiark.greenend.org.uk Subject: Re: UFS panic on -stable In-Reply-To: Your message of "Sat, 02 Mar 2002 13:59:14 PST." <20020302135914.A33051@xor.obsecurity.org> Date: Sat, 02 Mar 2002 22:33:14 +0000 From: Ian Dowse Message-ID: <200203022233.aa08277@salmon.maths.tcd.ie> 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 In message <20020302135914.A33051@xor.obsecurity.org>, Kris Kennaway writes: >So much for the MFS theory: > >/x: bad dir ino 1006899 at offset 0: mangled entry >panic: ufs_dirbad: bad dir >Debugger("panic") >Stopped at Debugger+0x35: movb $0,in_Debugger.426 >db> > >/x is a local UFS filesystem. Hmm. You said originally that the problem first appeared when the cluster was upgraded to 4.5. Was that 4.5-RELEASE or -STABLE? If it was -STABLE, the approximate date would help as we can ignore commits since then. One change that I am slightly suspicious of is the moving of the VOP_INACTIVE call in vput and vrele. That was MFC'd on Feb 2nd (vfs_subr.c revision 1.249.2.25), so I'd be interested to know if the crashes occurred before this change. The reason I'm concerned about this one is that the NFS client does not use vnode locking (vn_lock always succeeds), and nfs_inactive can block, so calling VOP_INACTIVE while the vnode is not marked VFREE may cause subtle changes in behaviour elsewhere. Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Sat Mar 2 14:41:21 2002 Delivered-To: freebsd-fs@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 99E2D37B41B for ; Sat, 2 Mar 2002 14:40:51 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id g22MelU56868; Sat, 2 Mar 2002 14:40:47 -0800 (PST) (envelope-from dillon) Date: Sat, 2 Mar 2002 14:40:47 -0800 (PST) From: Matthew Dillon Message-Id: <200203022240.g22MelU56868@apollo.backplane.com> To: Kris Kennaway Cc: Ian Dowse , Kirk McKusick , Finch , fs@FreeBSD.ORG, fanf@chiark.greenend.org.uk Subject: Re: UFS panic on -stable References: <200202260141.g1Q1f8i28365@beastie.mckusick.com> <200202260237.aa51774@salmon.maths.tcd.ie> <20020226184340.A78562@xor.obsecurity.org> <20020228135233.B5586@xor.obsecurity.org> <20020301173740.A21179@xor.obsecurity.org> <200203020150.g221oWS48392@apollo.backplane.com> <20020301175632.A21599@xor.obsecurity.org> <20020302135914.A33051@xor.obsecurity.org> <200203022210.g22MA8B56666@apollo.backplane.com> <20020302142807.B33223@xor.obsecurity.org> 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 :Unfortunately not, except by starting up a package build and waiting a :bit :-) However I just realised that I have another datapoint as to :when the problem was introduced, because the alpha cluster has been :perfectly stable and is running a 4.x kernel dated around Jan 26 :(probably a few days earlier, because peter had problems getting the :machines to netboot). The most obvious commit after that time period :was this one: : :dillon 2002/01/31 10:51:48 PST : Modified files: (Branch: RELENG_4) : sys/kern vfs_subr.c : Log: : MFC new vlrureclaim trigger-point code. [...] : :I'm going to try backing that out now to see if it fixes things. : :Kris It's worth trying but if kern.maxvnodes isn't getting hit this code will not get hit either. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Sat Mar 2 14:42: 4 2002 Delivered-To: freebsd-fs@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 1AD8237B400 for ; Sat, 2 Mar 2002 14:42:01 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id g22MftL56881; Sat, 2 Mar 2002 14:41:55 -0800 (PST) (envelope-from dillon) Date: Sat, 2 Mar 2002 14:41:55 -0800 (PST) From: Matthew Dillon Message-Id: <200203022241.g22MftL56881@apollo.backplane.com> To: Ian Dowse Cc: Kris Kennaway , Kirk McKusick , Finch , fs@FreeBSD.ORG, fanf@chiark.greenend.org.uk Subject: Re: UFS panic on -stable References: <200203022233.aa08277@salmon.maths.tcd.ie> 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 :In message <20020302135914.A33051@xor.obsecurity.org>, Kris Kennaway writes: :>So much for the MFS theory: :> :>/x: bad dir ino 1006899 at offset 0: mangled entry :>panic: ufs_dirbad: bad dir :>Debugger("panic") :>Stopped at Debugger+0x35: movb $0,in_Debugger.426 :>db> :> :>/x is a local UFS filesystem. : :Hmm. You said originally that the problem first appeared when the :cluster was upgraded to 4.5. Was that 4.5-RELEASE or -STABLE? If :it was -STABLE, the approximate date would help as we can ignore :commits since then. : :One change that I am slightly suspicious of is the moving of the :VOP_INACTIVE call in vput and vrele. That was MFC'd on Feb 2nd :(vfs_subr.c revision 1.249.2.25), so I'd be interested to know if :the crashes occurred before this change. The reason I'm concerned :about this one is that the NFS client does not use vnode locking :(vn_lock always succeeds), and nfs_inactive can block, so calling :VOP_INACTIVE while the vnode is not marked VFREE may cause subtle :changes in behaviour elsewhere. : :Ian This is definitely worth trying. If it comes down to it, the only way to track the problem down may be to cvs update -D, build, install, test and close in on the date it broke. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Sat Mar 2 14:45:37 2002 Delivered-To: freebsd-fs@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-169-107-10.dsl.lsan03.pacbell.net [64.169.107.10]) by hub.freebsd.org (Postfix) with ESMTP id EA95337B416 for ; Sat, 2 Mar 2002 14:45:32 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 47DE866C32; Sat, 2 Mar 2002 14:45:32 -0800 (PST) Date: Sat, 2 Mar 2002 14:45:32 -0800 From: Kris Kennaway To: Ian Dowse Cc: Kris Kennaway , Matthew Dillon , Kirk McKusick , Finch , fs@FreeBSD.ORG, fanf@chiark.greenend.org.uk Subject: Re: UFS panic on -stable Message-ID: <20020302144532.A33433@xor.obsecurity.org> References: <20020302135914.A33051@xor.obsecurity.org> <200203022233.aa08277@salmon.maths.tcd.ie> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="lrZ03NoBR/3+SXJZ" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <200203022233.aa08277@salmon.maths.tcd.ie>; from iedowse@maths.tcd.ie on Sat, Mar 02, 2002 at 10:33:14PM +0000 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 --lrZ03NoBR/3+SXJZ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Mar 02, 2002 at 10:33:14PM +0000, Ian Dowse wrote: > In message <20020302135914.A33051@xor.obsecurity.org>, Kris Kennaway writ= es: > >So much for the MFS theory: > > > >/x: bad dir ino 1006899 at offset 0: mangled entry > >panic: ufs_dirbad: bad dir > >Debugger("panic") > >Stopped at Debugger+0x35: movb $0,in_Debugger.426 > >db> > > > >/x is a local UFS filesystem. >=20 > Hmm. You said originally that the problem first appeared when the > cluster was upgraded to 4.5. Was that 4.5-RELEASE or -STABLE? If > it was -STABLE, the approximate date would help as we can ignore > commits since then. I believe it was 4.5-STABLE around Feb 10 - I sent the following message on that date: -- I restarted the bento build with the 4.x package set, after upgrading the gohans to 4.5-STABLE (one of them had panicked with ffs_alloc: dup alloc). I also set up the gohans to scrub their disks at boot time. -- Prior to this, I think they were running 4.4-STABLE as of about Nov 25, which was the last time I upgraded them. I don't think I've seen a recurrence of the dup alloc panic lately, so this might have been fixed between November and January. Combined with the alpha kernels running from around Jan 26 this seems to narrow the range a fair bit. Kris --lrZ03NoBR/3+SXJZ 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 iD8DBQE8gVYLWry0BWjoQKURAmBtAJ4oNbVltUZSUGFtHtRqNKLR5yeL1QCg8S1w PFk9Lb+Rw9wbcc4jW2ORO+U= =HhvC -----END PGP SIGNATURE----- --lrZ03NoBR/3+SXJZ-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Sat Mar 2 21:29: 5 2002 Delivered-To: freebsd-fs@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 9495B37B400 for ; Sat, 2 Mar 2002 21:29:01 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id g235Stc59042; Sat, 2 Mar 2002 21:28:55 -0800 (PST) (envelope-from dillon) Date: Sat, 2 Mar 2002 21:28:55 -0800 (PST) From: Matthew Dillon Message-Id: <200203030528.g235Stc59042@apollo.backplane.com> To: Kris Kennaway Cc: Ian Dowse , Kris Kennaway , Kirk McKusick , Finch , fs@FreeBSD.ORG, fanf@chiark.greenend.org.uk Subject: Re: UFS panic on -stable References: <20020302135914.A33051@xor.obsecurity.org> <200203022233.aa08277@salmon.maths.tcd.ie> <20020302144532.A33433@xor.obsecurity.org> 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 restarted the bento build with the 4.x package set, after upgrading :the gohans to 4.5-STABLE (one of them had panicked with ffs_alloc: dup :alloc). I also set up the gohans to scrub their disks at boot time. :-- : :Prior to this, I think they were running 4.4-STABLE as of about Nov :25, which was the last time I upgraded them. I don't think I've seen :a recurrence of the dup alloc panic lately, so this might have been :fixed between November and January. : :Combined with the alpha kernels running from around Jan 26 this seems :to narrow the range a fair bit. : :Kris The date range needs to be narrowed down on a single machine if possible. A lot of changes were made between January 26th and February 10th: cd /usr/src/sys cvs diff -j RELENG_4:20020125 -j RELENG_4:20020211 * device polling was added to a couple of ethernet drivers * changes to usb were made * changes to vinum * i386 cr0 boot-time initialization changed * changes to the floppy driver * changes to the timecounter * maxusers auto-sizing calculation changed * changes to aio * changes to kern.maxvnodes handling * VOP_INACTIVE MFC * WRITECLOSE flushing - now also flushes out unlinked but still open files. * route socket interface announcements were added * ip_input / ip_output changes * bootp changes. * minor nfs changes * FFS mount downgrade to read-only fix MFC * various softupdates fixes Also, when you get it narrowed down, see if the kern.maxvnodes setting has an effect (e.g. normal verses something large like 9999999). -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Sat Mar 2 22:14:40 2002 Delivered-To: freebsd-fs@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-169-107-10.dsl.lsan03.pacbell.net [64.169.107.10]) by hub.freebsd.org (Postfix) with ESMTP id 8495637B400 for ; Sat, 2 Mar 2002 22:14:35 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id D253066C32; Sat, 2 Mar 2002 22:14:34 -0800 (PST) Date: Sat, 2 Mar 2002 22:14:34 -0800 From: Kris Kennaway To: Matthew Dillon Cc: Kris Kennaway , Ian Dowse , Kirk McKusick , Finch , fs@FreeBSD.ORG, fanf@chiark.greenend.org.uk Subject: Re: UFS panic on -stable Message-ID: <20020302221434.A37529@xor.obsecurity.org> References: <20020302135914.A33051@xor.obsecurity.org> <200203022233.aa08277@salmon.maths.tcd.ie> <20020302144532.A33433@xor.obsecurity.org> <200203030528.g235Stc59042@apollo.backplane.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="2fHTh5uZTiUOsy+g" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <200203030528.g235Stc59042@apollo.backplane.com>; from dillon@apollo.backplane.com on Sat, Mar 02, 2002 at 09:28:55PM -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 --2fHTh5uZTiUOsy+g Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Sat, Mar 02, 2002 at 09:28:55PM -0800, Matthew Dillon wrote: > The date range needs to be narrowed down on a single machine if possible. > A lot of changes were made between January 26th and February 10th: Yes, I'm currently running with vfs_subr.c:1.249.2.24 to determine whether it could be that revision or 1.249.2.25 as Ian suggested it could be. So far no panics, although one of the alphas just panicked with the Jan 26 kernel an hour after I rebooted it, when it was doing nothing. panic: ffs_clusteralloc: map mismatch Unfortunately, I don't have the debug kernel any more. I haven't seen this one on the i386es yet. Kris --2fHTh5uZTiUOsy+g 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 iD8DBQE8gb9KWry0BWjoQKURAnJVAJwOD3gxXDVyQqzq6EtTcoTNJQFFigCeJBGQ yV6AihJNozHVj2aI1xJC/hU= =7qqN -----END PGP SIGNATURE----- --2fHTh5uZTiUOsy+g-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Sat Mar 2 22:30:12 2002 Delivered-To: freebsd-fs@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-169-107-10.dsl.lsan03.pacbell.net [64.169.107.10]) by hub.freebsd.org (Postfix) with ESMTP id 68CA037B400 for ; Sat, 2 Mar 2002 22:30:03 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id CB09D66C32; Sat, 2 Mar 2002 22:30:02 -0800 (PST) Date: Sat, 2 Mar 2002 22:30:02 -0800 From: Kris Kennaway To: Kris Kennaway Cc: Matthew Dillon , Ian Dowse , Kirk McKusick , Finch , fs@FreeBSD.ORG, fanf@chiark.greenend.org.uk Subject: Re: UFS panic on -stable Message-ID: <20020302223002.A37826@xor.obsecurity.org> References: <20020302135914.A33051@xor.obsecurity.org> <200203022233.aa08277@salmon.maths.tcd.ie> <20020302144532.A33433@xor.obsecurity.org> <200203030528.g235Stc59042@apollo.backplane.com> <20020302221434.A37529@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="liOOAslEiF7prFVr" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20020302221434.A37529@xor.obsecurity.org>; from kris@obsecurity.org on Sat, Mar 02, 2002 at 10:14:34PM -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 --liOOAslEiF7prFVr Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Mar 02, 2002 at 10:14:34PM -0800, Kris Kennaway wrote: > On Sat, Mar 02, 2002 at 09:28:55PM -0800, Matthew Dillon wrote: >=20 > > The date range needs to be narrowed down on a single machine if pos= sible. > > A lot of changes were made between January 26th and February 10th: >=20 > Yes, I'm currently running with vfs_subr.c:1.249.2.24 to determine > whether it could be that revision or 1.249.2.25 as Ian suggested it > could be. So far no panics, although one of the alphas just panicked > with the Jan 26 kernel an hour after I rebooted it, when it was doing > nothing. Still problems with 1.249.2.24. Two of the i386'es just panicked too: Fatal double fault: eip =3D 0xc032a070 esp =3D 0xd627beb0 ebp =3D 0xd627becc panic: double fault Debugger("panic") Stopped at Debugger+0x35: movb $0,in_Debugger.426 db> trace Debugger(c0368c9b) at Debugger+0x35 panic(c039a563,c039ab53,d627becc,c039ab47,d627beb0) at panic+0x70 dblfault_handler(0,0,0,0,0) at dblfault_handler+0x47 db> /dev: bad dir ino 2 at offset 16384: mangled entry panic: ufs_dirbad: bad dir Debugger("panic") Stopped at Debugger+0x35: movb $0,in_Debugger.426 db> Next stop is backing out 1.249.2.24 also. Kris --liOOAslEiF7prFVr 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 iD8DBQE8gcLqWry0BWjoQKURAsC0AJ9KmiQ9OOvh6bHFS2woRKkp6aFa4QCgkmul DEp+Q9o8dqhfmH/kba40SpU= =uWQc -----END PGP SIGNATURE----- --liOOAslEiF7prFVr-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Sat Mar 2 23:57:36 2002 Delivered-To: freebsd-fs@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-169-107-10.dsl.lsan03.pacbell.net [64.169.107.10]) by hub.freebsd.org (Postfix) with ESMTP id CFCB237B417 for ; Sat, 2 Mar 2002 23:57:33 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 40EC466C32; Sat, 2 Mar 2002 23:57:33 -0800 (PST) Date: Sat, 2 Mar 2002 23:57:33 -0800 From: Kris Kennaway To: Kris Kennaway Cc: Matthew Dillon , Ian Dowse , Kirk McKusick , Finch , fs@FreeBSD.ORG, fanf@chiark.greenend.org.uk Subject: Re: UFS panic on -stable Message-ID: <20020302235733.A38947@xor.obsecurity.org> References: <20020302135914.A33051@xor.obsecurity.org> <200203022233.aa08277@salmon.maths.tcd.ie> <20020302144532.A33433@xor.obsecurity.org> <200203030528.g235Stc59042@apollo.backplane.com> <20020302221434.A37529@xor.obsecurity.org> <20020302223002.A37826@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="HcAYCG3uE/tztfnV" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20020302223002.A37826@xor.obsecurity.org>; from kris@obsecurity.org on Sat, Mar 02, 2002 at 10:30:02PM -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 --HcAYCG3uE/tztfnV Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Sigh, now bento page faulted: Fatal trap 12: page fault while in kernel mode mp_lock = 01000005; cpuid = 1; lapic.id = 00000000 fault virtual address = 0x6620545f fault code = supervisor read, page not present instruction pointer = 0x8:0xc017af61 stack pointer = 0x10:0xdf0b4888 frame pointer = 0x10:0xdf0b4894 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 = 93482 (sshd) interrupt mask = net <- SMP: XXX trap number = 12 panic: page fault mp_lock = 01000005; cpuid = 1; lapic.id = 00000000 boot() called on cpu#1 Uptime: 14d9h38m11s Kris --HcAYCG3uE/tztfnV 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 iD8DBQE8gddsWry0BWjoQKURAiYlAKC2tiXWcot7WZ/mt0lRHpLFFlZ9bQCfSXsl ilpspye9V3a9Bg/nSOXwxeM= =z0OV -----END PGP SIGNATURE----- --HcAYCG3uE/tztfnV-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message