Date: Mon, 18 Oct 1999 13:44:34 -0700 (PDT) From: Julian Elischer <julian@whistle.com> To: Terry Lambert <tlambert@primenet.com> Cc: Poul-Henning Kamp <phk@critter.freebsd.dk>, freebsd-arch@freebsd.org Subject: Re: The eventual fate of BLOCK devices. Message-ID: <Pine.BSF.4.10.9910181308270.24435-100000@current1.whistle.com> In-Reply-To: <199910181726.KAA03157@usr07.primenet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Here's something that needs to be solved before Block devices can go away: Fsck on / in single user mode is presently done of the block device so that if fsck changes any blocks that are presently cached by the filesystem, they get updated for the filesystem. This ensures that should the filesystem then decide to read further data from the disk, that his data is consistent with that it has in memory. Changing this to be a simple char device will just not work correctly in the cases where there is minor cleanup required in the directories already loaded into memory. Until this is solved, block devices cannot be removed and certainly they cannot be replaced by char device. note: you need to corrupt the inodes in ways that they still appear valid to test this. (i.e. clri won't work) julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" 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.4.10.9910181308270.24435-100000>