Date: Mon, 21 Aug 2006 14:09:20 +0000 (UTC) From: Tor Egge <Tor.Egge@cvsup.no.freebsd.org> To: anderson@centtech.com Cc: freebsd-fs@freebsd.org, tegge@freebsd.org Subject: Re: Deadlock between nfsd and snapshots. Message-ID: <20060821.140920.85376544.Tor.Egge@cvsup.no.freebsd.org> In-Reply-To: <44E9B722.2040407@centtech.com> References: <20060818.202001.74745664.Tor.Egge@cvsup.no.freebsd.org> <20060821.132151.41668008.Tor.Egge@cvsup.no.freebsd.org> <44E9B722.2040407@centtech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Does this mean that setting the noatime flag on mount would dodge this? It might solve the deadlock issue when creating snapshots. Note that snapshots might fail to make copies of the original content when file system metadata changes on some systems (cf. PR kern/100365). Setting the noatime flag does not prevent ufs_itimes() from changing the inode flags without proper locking. IN_CHANGE might be set on the inode after a chmod() system call, a following fstat() system call can then trigger a call to ufs_itimes(). - Tor Egge
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060821.140920.85376544.Tor.Egge>