Date: Thu, 18 Feb 1999 11:42:10 -0800 (PST) From: Julian Elischer <julian@whistle.com> To: Don Lewis <Don.Lewis@tsc.tdk.com> Cc: Jake <jake@checker.org>, hackers@FreeBSD.ORG Subject: Re: softupdate panic, anyone seen this? Message-ID: <Pine.BSF.3.95.990218112555.13983V-100000@current1.whistle.com> In-Reply-To: <199902180912.BAA18642@salsa.gv.tsc.tdk.com>
next in thread | previous in thread | raw e-mail | index | archive | help
remember that mfs is still a UFS and as such still calls the stub entrypoints for softupdates and is still subject to the 'syncer' daemon. On Thu, 18 Feb 1999, Don Lewis wrote: > 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? > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" 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.990218112555.13983V-100000>