From owner-freebsd-current Sat Jan 16 04:43:50 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA10632 for freebsd-current-outgoing; Sat, 16 Jan 1999 04:43:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA10626; Sat, 16 Jan 1999 04:43:47 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id NAA10832; Sat, 16 Jan 1999 13:43:24 +0100 (CET) To: asami@FreeBSD.ORG (Satoshi Asami) cc: current@FreeBSD.ORG Subject: Re: mounting double-ended SCSI disks In-reply-to: Your message of "Sat, 16 Jan 1999 02:46:30 PST." <199901161046.CAA47630@silvia.hip.berkeley.edu> Date: Sat, 16 Jan 1999 13:43:24 +0100 Message-ID: <10830.916490604@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199901161046.CAA47630@silvia.hip.berkeley.edu>, Satoshi Asami write s: > * >However, if I try to mount it from B read-only while A is mounting it > * >read-write, it succeeds. This looks dangerous, as A writing data onto > * >the disk could cause B's cache to go stale without B knowing it. Is > * >it a good idea to allow read-only mounts of a dirty filesystem anyway? > * >(The filesystem could be corrupted, right?) > * > * UFS/FFS doesn't expect anybody else to muck about on the device > * while they have it open, and violating that is a bad idea, I cannot > >I know that, but that's not the point here. If the filesystem is >marked dirty, it could very well be corrupted. Why am I allowed to >mount it (even read-only)? how else would you fsck / if it was dirty ? -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message