Date: Tue, 2 Feb 2016 00:17:10 +0200 From: Konstantin Belousov <kostikbel@gmail.com> To: Rick Macklem <rmacklem@uoguelph.ca> Cc: FreeBSD Filesystems <freebsd-fs@freebsd.org>, Kirk McKusick <mckusick@mckusick.com> Subject: Re: panic ffs_truncate3 (maybe fuse being evil) Message-ID: <20160201221710.GR91220@kib.kiev.ua> In-Reply-To: <855760730.165482737.1453177516248.JavaMail.zimbra@uoguelph.ca> References: <1696608910.154845456.1452438117036.JavaMail.zimbra@uoguelph.ca> <20160114092934.GL72455@kib.kiev.ua> <964333498.161527381.1452827658163.JavaMail.zimbra@uoguelph.ca> <20160115095749.GC3942@kib.kiev.ua> <1817287612.162823118.1452909605928.JavaMail.zimbra@uoguelph.ca> <20160116191116.GI3942@kib.kiev.ua> <853868666.163292727.1452986431921.JavaMail.zimbra@uoguelph.ca> <20160117035858.GO3942@kib.kiev.ua> <855760730.165482737.1453177516248.JavaMail.zimbra@uoguelph.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jan 18, 2016 at 11:25:16PM -0500, Rick Macklem wrote: > Kostik wrote: > > On Sat, Jan 16, 2016 at 06:20:31PM -0500, Rick Macklem wrote: > > > Kostik wrote: > > > > Was IO_EXT flag passed to the ffs_truncate() invocation where the > > > > assert ffs_truncate3 fired ? > > > > > > > Yes. The only call to UFS_TRUNCATE() in ufs_inactive() specified both > > > IO_EXT | IO_NORMAL. > > > > Please try this. > > > Still happens. I put the old panic test in, but with a printf() instead > of panic() and the printf() happens with this patch. > Btw, whenever I've looked, the entry is on the clean list. > No other panics happen and the file system fsck's fine after the test run. I thought that you posted a stand-alone program which triggered the issue on non-SU mounts, but I cannot find it. Does such program exist, or this is just me misremembering ?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160201221710.GR91220>