search for: unshard

Displaying 4 results from an estimated 4 matches for "unshard".

Did you mean: unshared
2018 Apr 27
0
Reconstructing files from shards
...pying is complete. And until then no IO can happen into this file. (I haven't found the time to work on this, as there exists a workaround and I've been busy with other tasks. If anyone wants to volunteer to get this done, I'll be happy to help). But anway, why is copying data into new unsharded volume disruptive for you? -Krutika On Sat, Apr 21, 2018 at 1:14 AM, Jamie Lawrence <jlawrence at squaretrade.com> wrote: > Hello, > > So I have a volume on a gluster install (3.12.5) on which sharding was > enabled at some point recently. (Don't know how it happened, it...
2018 Apr 23
1
Reconstructing files from shards
2018-04-23 9:34 GMT+02:00 Alessandro Briosi <ab1 at metalit.com>: > Is it that really so? yes, i've opened a bug asking developers to block removal of sharding when volume has data on it or to write a huge warning message saying that data loss will happen > I thought that sharding was a extended attribute on the files created when > sharding is enabled. > > Turning off
2018 Apr 20
7
Reconstructing files from shards
Hello, So I have a volume on a gluster install (3.12.5) on which sharding was enabled at some point recently. (Don't know how it happened, it may have been an accidental run of an old script.) So it has been happily sharding behind our backs and it shouldn't have. I'd like to turn sharding off and reverse the files back to normal. Some of these are sparse files, so I need to account
2018 Apr 13
0
Is the size of bricks limiting the size of files I can store?
...anks a lot for that definitive answer. Is there a way to manage this? >>> Can you shard just those files, making them replicated in the process? >>> >> Is your question about whether you can shard just that big file that caused space to run out and keep the rest of the files unsharded? This is a bit tricky. From the time you enable sharding on your volume, all newly created shards will get sharded once their size exceeds features.shard-block-size value (which is configurable) because it's a volume-wide option. As for volumes which have pre-existing data even before shard...