{"action":"opened","issue":{"url":"https://api.github.com/repos/lizardfs/lizardfs/issues/364","labels_url":"https://api.github.com/repos/lizardfs/lizardfs/issues/364/labels{/name}","comments_url":"https://api.github.com/repos/lizardfs/lizardfs/issues/364/comments","events_url":"https://api.github.com/repos/lizardfs/lizardfs/issues/364/events","html_url":"https://github.com/lizardfs/lizardfs/issues/364","id":123184516,"number":364,"title":"Optimise HDD removal; unable to remove HDD","user":{"login":"onlyjob","id":1061236,"avatar_url":"https://avatars.githubusercontent.com/u/1061236?v=3","gravatar_id":"","url":"https://api.github.com/users/onlyjob","html_url":"https://github.com/onlyjob","followers_url":"https://api.github.com/users/onlyjob/followers","following_url":"https://api.github.com/users/onlyjob/following{/other_user}","gists_url":"https://api.github.com/users/onlyjob/gists{/gist_id}","starred_url":"https://api.github.com/users/onlyjob/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/onlyjob/subscriptions","organizations_url":"https://api.github.com/users/onlyjob/orgs","repos_url":"https://api.github.com/users/onlyjob/repos","events_url":"https://api.github.com/users/onlyjob/events{/privacy}","received_events_url":"https://api.github.com/users/onlyjob/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-12-20T21:31:52Z","updated_at":"2015-12-20T21:31:52Z","closed_at":null,"body":"Marking HDD (i.e. mount point) for removal in `mfshdd.cfg` does nothing if chunkserver is the only one with a certain label.\r\nIn my case there is only one chunkserver labelled `poolA` - it has 10+ HDDs but nothing happens when I mark HDD for removal. I expect data from the HDD marked for removal to be distributed among local HDDs when there are no other chunkservers to send data to.\r\nOn chunkservers with many HDDs sending at least some data from HDD marked for removal to other local HDDs will be more effective than sending all data to other chunkservers.\r\n\r\nUsing local HDDs may prevent data from being moved twice -- first time when it is sent away from chunkserver and second time when data is sent back after triggering rebalancing threshold.\r\n\r\nThis bug is related to #280.\r\n"}}