On Wed, 2014-05-14 at 14:25 +0200, Brendan Hide wrote: > On 14/05/14 09:31, Wang Shilong wrote: > > On 05/14/2014 09:18 AM, Eric Sandeen wrote: > >> Allow the specification of the filesystem UUID at mkfs time. > >> > >> (Implemented only for mkfs.btrfs, not btrfs-convert). > > Just out of curiosity, this option is used for what kind of use case? > > I notice Ext4 also has this option.:-) > Personally I can't think of any "average" or "normal" use case. The > simplest case however is in using predictable/predetermined UUIDs. > > Certain things, such as testing or perhaps even large-scale automation, > are likely simpler to implement with a predictable UUID. > Exactly this! My use case is actually for storage automation. By using an internally generated UUID, it's one easy way to "track" which filesystem your automation code made.
Example: https://github.com/purpleidea/puppet-gluster/blob/master/manifests/brick.pp#L469 HTH, James
signature.asc
Description: This is a digitally signed message part
