From mboxrd@z Thu Jan 1 00:00:00 1970 From: "H. Peter Anvin" Subject: Re: [Fwd: [Bug 136] New: FSID returned from statvfs always 0] Date: Wed, 18 Dec 2002 12:18:59 -0800 Sender: linux-fsdevel-owner@vger.kernel.org Message-ID: <3E00D833.7070700@zytor.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: Andrew Morton , Andries Brouwer , linux-fsdevel@vger.kernel.org Return-path: To: Bryan Henderson In-Reply-To: List-Id: linux-fsdevel.vger.kernel.org Bryan Henderson wrote: > > To have _any_ value would be an overstatement. Today's FSID (always zero) > has no value. An FSID that works only in machines where the disks never > move would have more value than that. > > But as long as we're talking about designs that solve the entire problem, > don't forget this aspect too: A perfect FSID must be stable as the > filesystem is moved from one disk to another while the disks stay put. > And, more importantly, must change when you replace the contents of a disk > with a new or different filesystem. > I.e. it's the UUID of the filesystem (if one exists.) -hpa