Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 20 Aug 2011 23:12:21 -0400 (EDT)
From:      Benjamin Kaduk <kaduk@MIT.EDU>
To:        Rick Macklem <rmacklem@uoguelph.ca>
Cc:        pjd@freebsd.org, current@freebsd.org
Subject:   Re: fsid change of ZFS?
Message-ID:  <alpine.GSO.1.10.1108202308530.7526@multics.mit.edu>
In-Reply-To: <1522286016.115315.1313878060040.JavaMail.root@erie.cs.uoguelph.ca>
References:  <1522286016.115315.1313878060040.JavaMail.root@erie.cs.uoguelph.ca>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 20 Aug 2011, Rick Macklem wrote:

>> Yes, using vfs_getnewfsid() does not solve the issue.
>>
>> I noticed that Solaris looked up a fixed array vfssw[] exactly for
>> the purpose. I think a table like it is a good solution for fixing
>> fsid for each file system.
>>
>> -- Hiroki
> If anyone thinks using a fixed table to assign vfc_typenum for known
> file system types is a bad idea, please let us know.

Fixed table sounds like a good plan.
Is there a reason for/against using a hash table for types that are not in 
the fixed table?  The advantage would be that out-of-tree filesystems get 
a consistent typenum (modulo hash collisions), but there would be more 
overhead in maintaining the table.

-Ben Kaduk



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.GSO.1.10.1108202308530.7526>