From owner-freebsd-fs@freebsd.org Thu Feb 2 14:52:53 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 43A56CCD5F0 for ; Thu, 2 Feb 2017 14:52:53 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0658095C for ; Thu, 2 Feb 2017 14:52:53 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1cZIkl-000MP6-2t; Thu, 02 Feb 2017 17:52:51 +0300 Date: Thu, 2 Feb 2017 17:52:51 +0300 From: Slawa Olhovchenkov To: Steven Hartland Cc: freebsd-fs@freebsd.org Subject: Re: ZFS: mkdir: File too large Message-ID: <20170202145251.GC26493@zxy.spb.ru> References: <20170202115304.GA26493@zxy.spb.ru> <20170202142455.GB26493@zxy.spb.ru> <397541e0-2327-0591-e05c-bdf09cb2d923@multiplay.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <397541e0-2327-0591-e05c-bdf09cb2d923@multiplay.co.uk> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Feb 2017 14:52:53 -0000 On Thu, Feb 02, 2017 at 02:50:01PM +0000, Steven Hartland wrote: > On 02/02/2017 14:24, Slawa Olhovchenkov wrote: > >> Try tracing SET_ERROR for EFBIG with dtrace to determine underlying > >> cause. > > 0 37281 none:set-error set-error 27 > > zfs.ko`zfs_freebsd_mkdir+0x3a3 > > kernel`VOP_MKDIR_APV+0x8a > > kernel`kern_mkdirat+0x1e1 > > kernel`amd64_syscall+0x50e > > kernel`0xffffffff8079499b > > > > (kgdb) x zfs_freebsd_mkdir+0x3a3 > > 0xffffffff81171813 : 0xb4b78b45 > > Current language: auto; currently minimal > > (kgdb) info line *0xffffffff81171813 > > Line 2145 of "/usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c" starts at address 0xffffffff81171813 and ends at 0xffffffff8117181a . > > > > 2138 /* > > 2139 * Add a new entry to the directory. > > 2140 */ > > 2141 getnewvnode_reserve(1); > > 2142 tx = dmu_tx_create(zfsvfs->z_os); > > 2143 dmu_tx_hold_zap(tx, dzp->z_id, TRUE, dirname); > > 2144 dmu_tx_hold_zap(tx, DMU_NEW_OBJECT, FALSE, NULL); > > 2145 fuid_dirtied = zfsvfs->z_fuid_dirty; > > 2146 if (fuid_dirtied) > > 2147 zfs_fuid_txhold(zfsvfs, tx); > > 2148 if (!zfsvfs->z_use_sa && acl_ids.z_aclp->z_acl_bytes > ZFS_ACE_SPACE) { > > 2149 dmu_tx_hold_write(tx, DMU_NEW_OBJECT, 0, > > 2150 acl_ids.z_aclp->z_acl_bytes); > > 2151 } > > > > PS: Please, CC me > What OS ver as those offsets seem odd? I am try trace every call in zfs_freebsd_mkdir. This is dmu_tx_assign: 3 29599 dmu_tx_assign:return ret 27 2153 dmu_tx_hold_sa_create(tx, acl_ids.z_aclp->z_acl_bytes + 2154 ZFS_SA_BASE_ATTR_SIZE); 2155 2156 error = dmu_tx_assign(tx, TXG_WAIT); 2157 if (error) { 2158 zfs_acl_ids_free(&acl_ids); 2159 dmu_tx_abort(tx); 2160 getnewvnode_drop_reserve(); 2161 ZFS_EXIT(zfsvfs); 2162 return (error); 2163 }