From owner-freebsd-current Fri Feb 19 19:52:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (Postfix) with ESMTP id ED7AD10E7A for ; Fri, 19 Feb 1999 19:52:35 -0800 (PST) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id UAA11078; Fri, 19 Feb 1999 20:52:29 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp02.primenet.com, id smtpd011066; Fri Feb 19 20:52:26 1999 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id UAA27646; Fri, 19 Feb 1999 20:52:24 -0700 (MST) From: Terry Lambert Message-Id: <199902200352.UAA27646@usr02.primenet.com> Subject: Re: softupdate panic, anyone seen this? (fwd) To: julian@whistle.com (Julian Elischer) Date: Sat, 20 Feb 1999 03:52:09 +0000 (GMT) Cc: mckusick@McKusick.COM, jake@checker.org, Don.Lewis@tsc.tdk.com, current@FreeBSD.ORG In-Reply-To: from "Julian Elischer" at Feb 18, 99 01:26:16 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > [Expanded audience] > > This is a generic problem with the present VFS system and also with some > specific parts of FreeBSD. There is "bleed-over" of all sorts of > parameters from filesystems and devices that they are mounted on and > devices that are sourced from them. (e.g. blocksizes etc.) > luckily at the moment it doesn't usually break things. > > I've come across quite a few examples of it though through the > system at various times. > > Has anyone any plans for cleaning up this sort of thing? > I've been tempted several times. I remember that Terry had some VFS patches a while back that did part of this. And Julian had some SLICE code a while back that could be aboused to do another part of this. And I think that if everything was labelled as "vinum" under the volume management, a lot of this would be abstracted. > > Bmsafemap structures hang only from buffers associated with > > filesystem block devices. In looking at the code I can imagine > > that these could show up if you were running soft updates on > > the filesystem that contains the block devices (e.g., the root > > filesystem). On that filesystem, the block device will be > > encountered during the walk of the files and potentially before > > the rest of the files associated with its filesystem have been > > sync'ed to disk. Can you verify that you are running with soft > > updates on your root filesystem. If so, does turning them off > > on that filesystem make the panic go away? > > > > Kirk McKusick Alternately, I think Julian had some devfs code that would move the devices off the root FS, and thus avoid the problem. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message