<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
    <channel>
        <title>devops - Tag - Sergey Chulanov&#39;s site</title>
        <link>https://dodcaf.ru/tags/devops/</link>
        <description>devops - Tag - Sergey Chulanov&#39;s site</description>
        <generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>tty8747@gmail.com (Sergey Chualnov)</managingEditor>
            <webMaster>tty8747@gmail.com (Sergey Chualnov)</webMaster><lastBuildDate>Tue, 02 Jun 2026 09:27:51 &#43;0300</lastBuildDate><atom:link href="https://dodcaf.ru/tags/devops/" rel="self" type="application/rss+xml" /><item>
    <title>Forcing an ext4 filesystem check on the next reboot</title>
    <link>https://dodcaf.ru/forcing-an-ext4-filesystem-check-on-the-next-reboot/</link>
    <pubDate>Tue, 02 Jun 2026 09:27:51 &#43;0300</pubDate>
    <author>Sergey Chulanov</author>
    <guid>https://dodcaf.ru/forcing-an-ext4-filesystem-check-on-the-next-reboot/</guid>
    <description><![CDATA[Forcing an ext4 Filesystem Check on the Next Reboot with tune2fs Sometimes you need to verify an ext4 filesystem, but the filesystem is mounted and cannot safely be repaired online. This is especially common when the filesystem is the root filesystem, such as /dev/md0 mounted as /.
Running fsck directly on a mounted filesystem is not a safe way to repair it:
1 sudo fsck -n -f /dev/md0 The -n option makes it read-only, so it will not fix anything.]]></description>
</item>
</channel>
</rss>
