{"action":"created","issue":{"url":"https://api.github.com/repos/lizardfs/lizardfs/issues/443","repository_url":"https://api.github.com/repos/lizardfs/lizardfs","labels_url":"https://api.github.com/repos/lizardfs/lizardfs/issues/443/labels{/name}","comments_url":"https://api.github.com/repos/lizardfs/lizardfs/issues/443/comments","events_url":"https://api.github.com/repos/lizardfs/lizardfs/issues/443/events","html_url":"https://github.com/lizardfs/lizardfs/issues/443","id":170598652,"number":443,"title":"cgiserv view hard disks timed out","user":{"login":"biocyberman","id":447942,"avatar_url":"https://avatars.githubusercontent.com/u/447942?v=3","gravatar_id":"","url":"https://api.github.com/users/biocyberman","html_url":"https://github.com/biocyberman","followers_url":"https://api.github.com/users/biocyberman/followers","following_url":"https://api.github.com/users/biocyberman/following{/other_user}","gists_url":"https://api.github.com/users/biocyberman/gists{/gist_id}","starred_url":"https://api.github.com/users/biocyberman/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/biocyberman/subscriptions","organizations_url":"https://api.github.com/users/biocyberman/orgs","repos_url":"https://api.github.com/users/biocyberman/repos","events_url":"https://api.github.com/users/biocyberman/events{/privacy}","received_events_url":"https://api.github.com/users/biocyberman/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":7,"created_at":"2016-08-11T08:57:02Z","updated_at":"2016-08-13T16:03:36Z","closed_at":null,"body":"OS: Ubuntu 16.04\r\nLizardfs: 3.10\r\n\r\nIt has been working fine since some days ago when I first installed the system. Now I don't know what happened but I can't view disks:\r\n\r\nhttp://myhost:9425/mfs.cgi?sections=HD\r\n\r\n```\r\nTraceback (most recent call last):\r\n  File \"/usr/share/mfscgi/mfs.cgi\", line 1423, in \r\n    s.connect((hostip,port))\r\n  File \"/usr/lib/python2.7/socket.py\", line 228, in meth\r\n    return getattr(self._sock,name)(*args)\r\nerror: [Errno 110] Connection timed out\r\n\r\n```\r\nI restarted the cgiserv service, it did not help. \r\nI will do something more later but not now because the server is busy."},"comment":{"url":"https://api.github.com/repos/lizardfs/lizardfs/issues/comments/239628129","html_url":"https://github.com/lizardfs/lizardfs/issues/443#issuecomment-239628129","issue_url":"https://api.github.com/repos/lizardfs/lizardfs/issues/443","id":239628129,"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},"created_at":"2016-08-13T16:03:36Z","updated_at":"2016-08-13T16:03:36Z","body":"> I removed some non-LFS data from /mnt/mydisk and free space is now about 50%. The problem still remains. \r\n\r\nWhich probably means that the storage is not causing the problem...\r\n\r\n> how to prepare hard drive and filesystem for LFS\r\n\r\nJust format the file system (_ext4_, _xfs_, etc.), create _fstab_ record and add corresponding entry to _mfshdd.cfg_ for each disk.\r\n\r\n> How harmful is RAID5?\r\n\r\nQuite harmful. It gives illusion of protection as degraded RAID-5 is much more vulnerable than single non-redundant disk. RAID-5 is not maintainable because removing HDD for replacement exposes data to unacceptable risks. RAID-5 exposes HDDs to symmetric load and considering that usually HDDs are not diversified among vendors and models it is likely that catastrophic failure of second HDD in RAID-5 happens during recovery after failure. IMHO RAID-5 is unreliable and it should never be used.\r\n\r\n> in case file goal is 1\r\n\r\nReplicated file system probably should never use goal=1 unless data is not valuable in which case is shouldn't matter if it is on non-redundant disks.\r\n\r\n> should I use LFS directly to dozens of disks on a server?\r\n\r\nBy all means. Yes. Unlike RAID-5, failure of standalone HDD will have only little effect on performance.\r\nBesides load is distributed among standalone HDDs when RAID-5 reads from all disks (minus one) therefore your I/O would be N times better on standalone disks than on RAID-5 (where N is number of HDDs)."}}
{"actor":{"display_login":"onlyjob"}}