Date: Thu, 18 Feb 1999 13:26:16 -0800 (PST) From: Julian Elischer <julian@whistle.com> To: Kirk McKusick <mckusick@McKusick.COM> Cc: Jake <jake@checker.org>, Don Lewis <Don.Lewis@tsc.tdk.com>, current@freebsd.org Subject: Re: softupdate panic, anyone seen this? (fwd) Message-ID: <Pine.BSF.3.95.990218132053.16922A-100000@current1.whistle.com> In-Reply-To: <199902182036.MAA26682@flamingo.McKusick.COM>
next in thread | previous in thread | raw e-mail | index | archive | help
[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. julian On Thu, 18 Feb 1999, Kirk McKusick wrote: > Date: Thu, 18 Feb 1999 01:12:50 -0800 > From: Don Lewis <Don.Lewis@tsc.tdk.com> > To: Jake <jake@checker.org>, hackers@FreeBSD.ORG > Subject: Re: softupdate panic, anyone seen this? > > On Feb 17, 7:30pm, Jake wrote: > } Subject: Re: softupdate panic, anyone seen this? > } > > * mfs process aborts with signal 11. > } > > * Hang after "syncing disks ... done" message. > } > > } > occasionaly I see the "panic: softdep_sync_metadata: > } > Unknown type bmsafemap" > > After reading the source for softdep_sync_metadata(), I > might believe this could happen if the system tried to sync > the block device for a softdep filesystem before had synced > all the files. > > } I was seeing all of this and other wierdness when I had mfs's > } mounted on /tmp and /var/tmp. > > I don't know why MFS would have an effect on this. The > only two things I can think of are either swapping to a > file on a softdep filesystem, or somehow the softupdates > stuff thinks it should be active on the MFS filesystems. > What does /sbin/mount say about the mount flags on these > filesystems? > > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95.990218132053.16922A-100000>