From mboxrd@z Thu Jan 1 00:00:00 1970 From: "J. R. Okajima" Subject: Re: Stable inode numbers Date: Tue, 26 Jul 2016 10:51:36 +0900 Message-ID: <22701.1469497896@jrobl> References: <20160722121503.GC20504@veci.piliscsaba.szeredi.hu> <20160725113400.GF20504@veci.piliscsaba.szeredi.hu> Return-path: Received: from mfb02-md.ns.itscom.net ([175.177.155.110]:56805 "EHLO mfb02-md.ns.itscom.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754932AbcGZCBb (ORCPT ); Mon, 25 Jul 2016 22:01:31 -0400 Received: from mail03-md.ns.itscom.net (mail03-md.ns.itscom.net [175.177.155.113]) by mfb02-md.ns.itscom.net (Postfix) with ESMTP id CD33C170EBDA for ; Tue, 26 Jul 2016 10:51:40 +0900 (JST) In-Reply-To: Sender: linux-unionfs-owner@vger.kernel.org List-Id: linux-unionfs@vger.kernel.org To: Vito Caputo Cc: Miklos Szeredi , linux-unionfs@vger.kernel.org Vito Caputo: > ... That is the lens I view > overlayfs problems like these through, hence I'd prefer a more general > solution with stable inode numbers making overlayfs behavior more > consistent with the filesystems backing it. You may want to try aufs instead of overlayfs since aufs has a such feature called XINO (external inode number). It is working well for over a decade, but some users set 'noxino' mount option which makes aufs not to use XINO. Because XINO consumes some disk space, and if XINO file is placed on tmpfs, then it means consuming memory. J. R. Okajima