Ubuntu和Debian内核因SSD而腐败的问题。

HACCR
徽章 +5
  • HACCR
  • 旅行者
  • 2个答复
我们有一个NX-3050，由于其Ext4文件系统损坏并仅读取了读取，我们经常不得不重建Linux VM。我们的研究指出了Linux内核与SSD有问题的文章。有没有其他人经历过这种情况，如果是这样，您如何解决？


编辑：我们创建了一个绕过SSD的容器，但我们尚未看到那里的问题，但是我们很想在服务器上重新接触SSD。Linux版本/发行版是Ubuntu 12.04.3 Lts。

我们发现与此有关的文章之一是：http://askubuntu.com/questions/262717/ubuntu-12-04-ssd-root-frequent-random-read-read-only-file-system

我希望如果你们中的任何一个经历了这个问题，这会有所帮助。
    \n
    \n
    \nEdit: We created a container that bypassed the SSD's and we have not yet see the issue there, but we would love to re-engage the SSD's on our servers. The linux version\/distro is Ubuntu 12.04.3 LTS.
    \n
    \nOne of the articles we found relating to this is: http:\/\/askubuntu.com\/questions\/262717\/ubuntu-12-04-ssd-root-frequent-random-read-only-file-system<\/a>
    \n
    \nI hope this helps if any of you have experienced this issue.","quoteUsername":"haccr","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    该主题已关闭以供评论

    8个答复

    j
    秩
    徽章 +7
    您是否看到Windows或Centos的类似问题？从访客操作系统的角度来看，这是一个硬盘驱动器，不应将其视为SSD驱动器，因此该内核腐败错误无关紧要。

    如果绕过容器中的SSD解决此问题，那将是令人惊讶的。
    \n
    \nIt would be surprising, if bypassing SSD in container fixes this issue.","quoteUsername":"jerome","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    k
    徽章 +4
    我注意到类似的问题。在我们的情况下，我们的模板VM被关闭，并根据可用VM的要求克隆它们。运行Ubuntu 12.04 LTS时，我们开始遇到常规磁盘IO错误，从而导致VM暂停，并且在不良情况下，该驱动器仅按照OP的报道而变得读取。

    我们只需要在CentOS 6上运行的单个应用程序的Ubuntu。在相同情况下，我们还没有看到CentOS的这个问题。
    \n
    \nWe only needed Ubuntu for a single application which now runs on CentOS 6. We have not seen this issue with CentOS under identical circumstances.","quoteUsername":"kiboro","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    HACCR
    徽章 +5
    @Jerome

    这个问题也使我们感到困惑，因为我同意来宾操作系统不应具有SSD，但是我们在日志中发现的错误与上面提到的错误保持一致。Windows尚未出现问题，我们还没有尝试过CentOS，因为我们发现的一个博客是使用SSD的CentOS上的一个类似问题（如果不是相同的话）。我们仅创建了 *应该 *忽略几周前SSD的容器，但到目前为止还没有任何问题。如果所有其他方法都失败了，我们将通过NFS向VSphere展示NAS，并使用新容器和更新的内核，将其放置在Linux盒中，情况看起来不错。

    @kiboro

    我很高兴我不是唯一的一个，我很高兴听到有关Centos的消息，我们可能必须切换。我仍然是Linux的新手（大约1年），从一开始就一直在Ubuntu和Debian上。您是否完全向Nutanix报告了这个问题，当我第一次与他们讨论时，他们没有听说过。
    @jerome<\/a>
    \n
    \nThe issue confused us also as I agree that the guest os should have no ides they are SSDs, but the errors we found in the logs were consistant with the bug referred to above. Windows as yet to have a problem, and we haven't tried Centos yet as one of the blogs we found was a similar issue (if not the same) on CentOS with SSDs. We only created the container that *should* ignore the SSD's a few weeks ago but so far there haven't been any issues. If all else fails, we have a NAS presented to vSphere via NFS that we could put our linux boxes on, with the new container and the updated kernel, things are looking good.
    \n
    \n@kiboro<\/u>
    \n
    \nI am glad I'm not the only one and I am very happy to hear about CentOS, we may have to switch. I am still fairly new to linux (about 1 year exp.) and have been on Ubuntu and Debian from the start. Have you reported the issue to Nutanix at all, when I first talked to them about it, they hadn't heard of it.","quoteUsername":"haccr","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    斯瓦特金斯
    秩
    徽章 +4
    你们都有日志的副本或故障的屏幕截图，即/var/log/log/sagess或/var/log/dmesg

    由于管理程序显示磁盘，因此应该对VM透明，尤其是考虑到群集中分散的文件系统的工作方式。

    这是KVM，VSPHERE还是HYPERV？
    \n
    \nSince the hypervisor presents a disk, it should be transparent to the VM, espically given how the distrubuted file system in a cluster works.
    \n
    \nIs this KVM, vSphere, or HyperV?","quoteUsername":"swatkins","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    k
    徽章 +4
    就我而言，它是Ubuntu，有一次在KVM下的Windows。VMS停了下来，唯一的证据是在/var/log/libvirt/qemu中报告磁盘io错误，这就是为什么VM暂停的原因。VMS重新启动了OK withouth腐败。

    从未见过Centos的这个问题，也从未与非关闭驱动器见过。

    如果删除SSD层可以阻止它（不是我尝试过），那么我怀疑某种延迟问题。我想知道克隆磁盘上的复印件是否会导致SSD高速缓存层短暂地绊倒，而Spinny磁盘的运行足够慢，以至于不发生这种情况。到那时，它可能按照内核参数调整的数量级，这可能解释了为什么CentOS不表现出相同的行为。
    \n
    \nNever seen this issue with CentOS and never with non-cloned drives.
    \n
    \nIf removing the SSD tier stops it (not that I've tried) then I'm suspecting some sort of latency issue. I wonder if copy-on-write on a cloned disk causes the SSD cache layer to trip up briefly where running of spinny disk is slow enough for this not to happen. At that point it might be in the order of magnitude of kernel parameter tweaks which might explain why CentOS doesn't exhibit the same behaviour.","quoteUsername":"kiboro","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    斯瓦特金斯
    秩
    徽章 +4
    所有有效的思考过程。当问题出现，是否发生任何特定事件，高磁盘IO或VM上的某些proccess时，检查日志会很有帮助吗？

    当暂停VM时，有可能接触支持是一件好事，因此案件支持可能能够找到根本原因。
    \n
    \nIt would be a good thing to potentially contact support when there is a paused VM so wost case support may be able to find the root cause.","quoteUsername":"swatkins","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    k
    徽章 +4
    现在已经有一段时间了。我们需要将Ubuntu用于特定应用程序，该应用程序现在已移植到我们的默认发行版CentOS上。我确实提出了一张票，任何日志中没有任何音符。Nutanix的支持也花了很多时间来研究它。即使在Ubuntu和Ubuntu进行的意识形态设置下，问题也从未在CentOS下发生。
    HACCR
    徽章 +5
    我将不得不看看我是否可以吓noc。我现在将所有内容都切换到CentOS，但我可能仍然有几个VM存档。如果我能找到它们，我会将它们添加到此线程中。

    这是在Vsphere 5.1上，Ubuntu为12.04.3 Lts。

    @kiboro有趣的是，您提到克隆的驱动器，我没有克隆我们的Centos盒子的驱动器，但是我与Ubuntu一起做了，我想知道这是否是一个因素。

    删除SSD层没有工作，即使在“ NOSSD”容器中，我们也有一些故障。
    @swatkins我们从来没有I/O认为Nutanix会认为很高，我认为我们看到的最高是大约2000 IOP（在尖峰期间）。

    我确实联系了Nutanix，并在审查了他们建议使用VMware打开案例的所有内容之后，但是自从我们改用CentOS以来，我们就没有解决这个问题（无论如何是时候更新了）。

    我首先认为这是转换机器的副作用（nutanix，我们在Hyper-V 2上）

    无论如何，我将尝试找到日志，但是我们认为这是由于Centos为我们工作而解决的。

    感谢大家！！
    \n
    \nThis is on vSphere 5.1 and the Ubuntu was 12.04.3 LTS.
    \n
    \n@kiboro<\/a> Interesting you mention cloned drives, I haven't been cloning the drives of our CentOS boxes, but I did with Ubuntu, I wonder if that is a factor.
    \n
    \nRemoving the SSD layer did not work, we had some fail even in the \"noSSD\" container.
    \n @swatkins<\/b> We have not ever had I\/O that the nutanix would consider high, I think the highest we have seen is about 2000 iops (during a spike).
    \n
    \nI did contact Nutanix and after reviewing everything they recommended opening a case with VMware, but we haven't gotten around to that since we switched to CentOS (it was time to update anyways).
    \n
    \nI had first thought it was a side effect of converting the machines (pre-nutanix, we were on hyper-v 2)
    \n
    \nAnyways, I will try to find the logs, but we consider this resolved since CentOS is working for us.
    \n
    \nThanks everyone!!","quoteUsername":"haccr","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    条款和条件
    Learn more about our cookies.<\/a>","cookiepolicy.button":"Accept cookies","cookiepolicy.button.deny":"Deny all","cookiepolicy.link":"Cookie settings","cookiepolicy.modal.title":"Cookie settings","cookiepolicy.modal.content":"We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.<\/a>","cookiepolicy.modal.level1":"Basic
    Functional","cookiepolicy.modal.level2":"Normal
    Functional + analytics","cookiepolicy.modal.level3":"Complete
    Functional + analytics + social media + embedded videos"}}}">
    Baidu