Date: Mon, 18 Oct 1999 11:44:59 -0700 (PDT) From: Julian Elischer <julian@whistle.com> To: Poul-Henning Kamp <phk@FreeBSD.org> Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Was: Re: cvs commit: src/sys/miscfs/specfs spec_vnops.c Message-ID: <Pine.BSF.4.10.9910181138440.24435-100000@current1.whistle.com> In-Reply-To: <199910181659.JAA86963@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
I think everyone should first try run their systems with block device IO totally disabled, as just changing vfs.bdev_buffered to 0 might lead to un-noticed corruption rather than failure. Note we have still not had an announcement from core, (PHK on his own does not count) that it is official policy that block devices a re going away. I will personally fight such a move until such an announcement is made. If you can get BDE and all the others to agree to this than I see no problems. I believe that even Matt will agree to let the matter rest if it is seen to have gone through te propper channels. julian On Mon, 18 Oct 1999, Poul-Henning Kamp wrote: > phk 1999/10/18 09:59:51 PDT > > Modified files: > sys/miscfs/specfs spec_vnops.c > Log: > Change the default for the vfs.bdev_buffered sysctl to zero. > > This means that access to block devices nodes will act the > same as char device nodes for disk-like devices. > > If you encounter problems after this, where programs accessing > disks directly fail to operate, please use the following command > to revert to previous behaviour: > > sysctl -w vfs.bdev_buffered=1 > > And verify that this was indeed the cause of your trouble. > > See the mail-archives of the arch@FreeBSD.org list for background. > > Revision Changes Path > 1.120 +2 -2 src/sys/miscfs/specfs/spec_vnops.c > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" 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.9910181138440.24435-100000>