Date: Thu, 22 Oct 1998 15:54:18 -0700 From: Kirk McKusick <mckusick@McKusick.COM> To: Don Lewis <Don.Lewis@tsc.tdk.com> Cc: dag-erli@ifi.uio.no, hackers@FreeBSD.ORG Subject: Re: softupdates and sync Message-ID: <199810222254.PAA19166@flamingo.McKusick.COM> In-Reply-To: Your message of "Thu, 22 Oct 1998 15:37:38 PDT." <199810222237.PAA17114@salsa.gv.tsc.tdk.com>
next in thread | previous in thread | raw e-mail | index | archive | help
From: Don Lewis <Don.Lewis@tsc.tdk.com> Date: Thu, 22 Oct 1998 15:37:38 -0700 In-Reply-To: Kirk McKusick <mckusick@McKusick.COM> "Re: softupdates and sync" (Oct 19, 8:42pm) To: Kirk McKusick <mckusick@McKusick.COM>, dag-erli@ifi.uio.no Subject: Re: softupdates and sync Cc: hackers@FreeBSD.ORG I wonder if this is related to: On Oct 14, 5:06pm, Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?= wrote: } Subject: SoftUpdates anomaly: what happens when you 'mount -u -o ro /usr'? ... Down-grading to read-only goes through the same process as unmounting. In particular it calls softdep_flushfiles which sync's the filesystem and flushes all the related background jobs from the work queue. If the deleted files had been on the work queue, they would have been flushed. That implies to me that they had not gotten to the work queue. Something very fishy is going on here, because this behavior does not show up in any of the other soft updates ports. My guess is that if you remove a bunch of files, then downgrade the filesystem, and finally run fsck -f (or whatever your option is to force it to run in the face of the clean flag being set), that you will have lost files. You will likely get the same effect if you do an unmount rather than a downgrade. Kirk McKusick 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?199810222254.PAA19166>