Date: Tue, 10 Apr 2007 11:42:48 +0200 From: Ivan Voras <ivoras@fer.hr> To: freebsd-fs@freebsd.org Subject: Re: gvirstor & UFS Message-ID: <evfm6p$751$1@sea.gmane.org> In-Reply-To: <20070330062726.I2388@besplex.bde.org> References: <euca4b$6l8$1@sea.gmane.org> <20070328100536.S6916@besplex.bde.org> <euh5hh$iis$1@sea.gmane.org> <20070330062726.I2388@besplex.bde.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig75FCAF2FA895EF3969DECB66 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Bruce Evans wrote: > Apparently it get past the media size check in g_io_check() to give > ENOSPC instead of EIO because g_io_check() only checks the virtual > size. To support virtual overcommitted media, it is necessary for > file systems to either do a physical check whenever they allocate a Ok, what about this: What would happen if I "stall" the IO ops? When I=20 get into the ENOSPC situation (which can happen only during BIO_WRITE),=20 I can add the request in an internal queue, and process it only when I=20 reliably determine that a new physical provider is added (which I can)? Would it interact badly with soft-updates timeouts? --------------enig75FCAF2FA895EF3969DECB66 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFGG1wYldnAQVacBcgRAsZPAKDgzKZH9BzOuL3T6+fhK0aEMKn5fQCfThE9 IjgdqdzICFyNJg53NcMWGlw= =E+o3 -----END PGP SIGNATURE----- --------------enig75FCAF2FA895EF3969DECB66--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?evfm6p$751$1>