Date: Mon, 21 Apr 2008 14:01:05 +0300 From: Kostik Belousov <kostikbel@gmail.com> To: "Mikhail T." <mi@aldan.algebra.com> Cc: stable@freebsd.org, fs@freebsd.org Subject: Re: panic: ffs_truncate: readonly filesystem Message-ID: <20080421110105.GH18958@deviant.kiev.zoral.com.ua> In-Reply-To: <200804202310.m3KNAi9b001090@aldan.algebra.com> References: <200804202310.m3KNAi9b001090@aldan.algebra.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--xEruU51OOzV9VdJQ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Apr 20, 2008 at 07:10:44PM -0400, Mikhail T. wrote: > Hello! >=20 > I tried, accidentally, to save a video-file (via firewire) to a > read-only location. >=20 > The entire system paniced with the message in subject. Why did it > happen? Because the kernel has a bug ? As is, the report is useless. Please, do not hesitate to provide at least the backtrace. The ufs_setattr() seems to properly check for ro mounts, as well as the direct callers of the UFS_TRUNCATE() function. Besides the possible logic error, the other possibility is the concurrent remount. Could it be that you actually remounted the fs readonly during the write ? --xEruU51OOzV9VdJQ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (FreeBSD) iEYEARECAAYFAkgMc/AACgkQC3+MBN1Mb4hahwCeLY+yLzxcTiaVnLtLvxXzK/OZ mJUAn2yDu+FLm1gjHEap89vW2meb1PeC =/GD2 -----END PGP SIGNATURE----- --xEruU51OOzV9VdJQ--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080421110105.GH18958>