Also display the internal cacheset uuid for each dev, stored in
the superblock.
As well as the dev uuid stored in the struct member_info.
Signed-off-by: Jacob Malevich <jam@daterainc.com>
Issue DAT-1913
Change-Id: Ib9815a023b0791c54ffde573fda1e9911d757c34
This shows the superblock set_uuid, given the user_uuid.
Signed-off-by: Jacob Malevich <jam@daterainc.com>
Issue DAT-1913
Change-Id: If5f81427ac02bceeb609ae119f044de3fb5a0d77
it might not exists when a cache disk device is removed and
further cache device might be active.
Also handle the case where cache set might not be registered
and the status should just believe what the super block
says and not mark the disk as missing.
This part of code needs optimization but that is a separate
change.
Issue DAT-1859
Issue DAT-1860
Change-Id: I7eb8e8ff517eae240fde30c70b3ac90aa9a50ed6
information in both set-uuid and user-uuid until support is added
in the CLI to display user-uuid as part of query-devs and in
format command to accept set_uuid and user_uuid.
Issue DAT-
Change-Id: I6f2306d858211933cb783f0efe8fe0ade64dd312
add-devs, rm-devs, and set-failed no longer need the
cacheset uuid. The cacheset already comes with the bcache_extent0
chardev.
Change-Id: I32572e865361d3c6ce759cf53f19d3f0e4cf04ce
Signed-off-by: Jacob Malevich <jam@daterainc.com>
Don't say that the device is missing unless it is still showing
"active" state.
Change-Id: I708d7719c6f6804cd06e75cbadf7bea36ac4b62d
Signed-off-by: Jacob Malevich <jam@daterainc.com>
Given a cacheset uuid and a device uuid, set that devices
member_info to CACHE_FAILED.
Change-Id: Ideb2034b1deb5fd11efda67f85b82d8a49fe71e4
Signed-off-by: Jacob Malevich <jam@daterainc.com>
Cross reference the superblock with the highest sequence number
to sysfs. If there is a device shown still active in the superblock,
mark it as 'missing'.
Fixes DAT-1758
Change-Id: I13098bbde6bd4b0b402c74ed648160576605311c
Signed-off-by: Jacob Malevich <jam@daterainc.com>
If the user added n caches but <n bucket_sizes, print a message
saying that cache# will be using the default bucket_size
Change-Id: I025474ca672bf79d1c88813e6f030ba7590e820d
Signed-off-by: Jacob Malevich <jam@daterainc.com>
buckets over 512k were causing deadlocks when the btree node
size was smaller than the bucket size.
Change-Id: Icb278d75c241e9643ab1355620e3d656df52c4ee
Signed-off-by: Jacob Malevich <jam@daterainc.com>
