67fbd34d83
Currently we save device metadata and have a helper function saveMetadata() which converts data in json format as well as saves it to file. For converting data in json format, one needs to know what is being saved. Break this function down in two functions. One function only has file write capability and takes in argument about byte array of json data. Now this function does not have to know what data is being saved. It only knows about a stream of json data is being saved to a file. This allows me to reuse this function to save a different type of metadata. In this case I am planning to save NextDeviceId so that docker can use this device Id upon next restart. Otherwise docker starts from 0 which is suboptimal. Signed-off-by: Vivek Goyal <vgoyal@redhat.com> |
||
|---|---|---|
| .. | ||
| aufs | ||
| btrfs | ||
| devmapper | ||
| graphtest | ||
| vfs | ||
| driver.go | ||
| fsdiff.go | ||