Date: Fri, 13 Apr 2007 00:40:52 +0200 From: Ivan Voras <ivoras@fer.hr> To: freebsd-geom@freebsd.org Subject: Re: volume management Message-ID: <evmcho$s54$2@sea.gmane.org> In-Reply-To: <461BCC85.2080900@freebsd.org> References: <20070409152401.GG76673@garage.freebsd.pl> <20070409153203.GA88082@harmless.hu> <461A5EC6.8010000@freebsd.org> <20070409154407.GA88621@harmless.hu> <evfqtt$n23$1@sea.gmane.org> <20070410111957.GA85578@garage.freebsd.pl> <461B75B2.40201@fer.hr> <20070410114115.GB85578@garage.freebsd.pl> <20070410161445.GA18858@keira.kiwi-computer.com> <20070410162129.GI85578@garage.freebsd.pl> <20070410172604.GA21036@keira.kiwi-computer.com> <461BCC85.2080900@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig717EBA8E6710E7A1A144E517 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Eric Anderson wrote: > I think the issue is that UFS doesn't expect to see ENOSPC from the > storage, since it believes it's on a provider that should be big enough= =2E > Is the right thing to teach UFS to recognize ENOSPC, and pass that on > to the userland? It's not just ENOSPC. Any error codes GEOM returns in code sections I've hit on (mostly softdep) will panic or confuse the kernel beyond repair. --------------enig717EBA8E6710E7A1A144E517 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.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGHrV0ldnAQVacBcgRAha1AKDSO9WYpCNOWxceqmcc6myUEW3YwQCgiRmI 3iVB7VovlKZnaa0sWimz3KY= =VUyc -----END PGP SIGNATURE----- --------------enig717EBA8E6710E7A1A144E517--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?evmcho$s54$2>