Was a volume with existing data got converted to sharding volume?
On Wed, Jan 27, 2021 at 5:06 AM Erik Jacobson wrote:
> Shortly after the sharded volume is made, there are some fuse mount
> messages. I'm not 100% sure if this was just before or during the
> big qemu-img command to make the 5T
Shortly after the sharded volume is made, there are some fuse mount
messages. I'm not 100% sure if this was just before or during the
big qemu-img command to make the 5T image
(qemu-img create -f raw -o preallocation=falloc
/adminvm/images/adminvm.img 5T)
(from /var/log/glusterfs/adminvm.log)
Dear Schlick,
It's indeed dropped, I think it's in favor of more native options. The go
to replacement is lvm-cache (
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/logical_volume_manager_administration/lvm_cache_volume_creation
).
This places just an amount of SSD
Dear List,
could anyone enlighten me what happened to the tiered storage feature?
When finding references to it online, it seemed to be the perfect solution for
my problem, but further digging shows it was removed in gluster 6.
What digging did not show is why it was removed and if there are
Thank you so much for responding! More below.
> Anything in the logs of the fuse mount? can you stat the file from the mount?
> also, the report of an image is only 64M makes me think about Sharding as the
> default value of Shard size is 64M.
> Do you have any clues on when this issue start to
