From: Martin Steigerwald <martin@lichtvoll.de>
To: "Alan C. Assis" <acassis@gmail.com>, Theodore Ts'o <tytso@mit.edu>
Cc: "Bjørn Forsman" <bjorn.forsman@gmail.com>,
dm-devel@redhat.com,
"Ext4 Developers List" <linux-ext4@vger.kernel.org>,
linux-embedded@vger.kernel.org, "Kai Tomerius" <kai@tomerius.de>
Subject: Re: [dm-devel] File system robustness
Date: Wed, 19 Jul 2023 08:22:43 +0200 [thread overview]
Message-ID: <4835096.GXAFRqVoOG@lichtvoll.de> (raw)
In-Reply-To: <20230718213212.GE3842864@mit.edu>
Theodore Ts'o - 18.07.23, 23:32:12 CEST:
> If you get it all right, you'll be fine. On the other hand, if you
> have crappy hardware (such as might be found for cheap in the checkout
> counter of the local Micro Center, or in a back alley vendor in
> Shenzhen, China), or if you do something like misconfigure the file
> system such as using the "nobarrier" mount option "to speed things
> up", or if you have applications that update files in an unsafe
> manner, then you will have problems.
Is "nobarrier" mount option still a thing? I thought those mount options
have been deprecated or even removed with the introduction of cache flush
handling in kernel 2.6.37?
Hmm, the mount option has been removed from XFS in in kernel 4.19
according to manpage, however no mention of any deprecation or removal
in ext4 manpage. It also does not seem to be removed in BTRFS at least
according to manpage btrfs(5).
--
Martin
--
dm-devel mailing list
dm-devel@redhat.com
https://listman.redhat.com/mailman/listinfo/dm-devel
WARNING: multiple messages have this Message-ID (diff)
From: Martin Steigerwald <martin@lichtvoll.de>
To: "Alan C. Assis" <acassis@gmail.com>, Theodore Ts'o <tytso@mit.edu>
Cc: "Bjørn Forsman" <bjorn.forsman@gmail.com>,
"Kai Tomerius" <kai@tomerius.de>,
linux-embedded@vger.kernel.org,
"Ext4 Developers List" <linux-ext4@vger.kernel.org>,
dm-devel@redhat.com
Subject: Re: File system robustness
Date: Wed, 19 Jul 2023 08:22:43 +0200 [thread overview]
Message-ID: <4835096.GXAFRqVoOG@lichtvoll.de> (raw)
In-Reply-To: <20230718213212.GE3842864@mit.edu>
Theodore Ts'o - 18.07.23, 23:32:12 CEST:
> If you get it all right, you'll be fine. On the other hand, if you
> have crappy hardware (such as might be found for cheap in the checkout
> counter of the local Micro Center, or in a back alley vendor in
> Shenzhen, China), or if you do something like misconfigure the file
> system such as using the "nobarrier" mount option "to speed things
> up", or if you have applications that update files in an unsafe
> manner, then you will have problems.
Is "nobarrier" mount option still a thing? I thought those mount options
have been deprecated or even removed with the introduction of cache flush
handling in kernel 2.6.37?
Hmm, the mount option has been removed from XFS in in kernel 4.19
according to manpage, however no mention of any deprecation or removal
in ext4 manpage. It also does not seem to be removed in BTRFS at least
according to manpage btrfs(5).
--
Martin
next prev parent reply other threads:[~2023-07-19 7:03 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230717075035.GA9549@tomerius.de>
2023-07-17 9:08 ` [dm-devel] File system robustness Geert Uytterhoeven
2023-07-17 9:08 ` Geert Uytterhoeven
2023-07-17 9:08 ` Geert Uytterhoeven
[not found] ` <CAG4Y6eTU=WsTaSowjkKT-snuvZwqWqnH3cdgGoCkToH02qEkgg@mail.gmail.com>
[not found] ` <20230718053017.GB6042@tomerius.de>
2023-07-18 12:56 ` [dm-devel] " Alan C. Assis
2023-07-18 12:56 ` Alan C. Assis
[not found] ` <CAEYzJUGC8Yj1dQGsLADT+pB-mkac0TAC-typAORtX7SQ1kVt+g@mail.gmail.com>
2023-07-18 13:04 ` [dm-devel] " Alan C. Assis
2023-07-18 13:04 ` Alan C. Assis
2023-07-18 14:47 ` [dm-devel] " Chris
2023-07-18 14:47 ` Chris
2023-07-18 21:32 ` [dm-devel] " Theodore Ts'o
2023-07-18 21:32 ` Theodore Ts'o
2023-07-19 6:22 ` Martin Steigerwald [this message]
2023-07-19 6:22 ` Martin Steigerwald
2023-07-20 4:20 ` [dm-devel] " Theodore Ts'o
2023-07-20 4:20 ` Theodore Ts'o
2023-07-20 7:55 ` [dm-devel] Nobarrier mount option (was: Re: File system robustness) Martin Steigerwald
2023-07-20 7:55 ` Martin Steigerwald
2023-07-21 13:35 ` [dm-devel] " Theodore Ts'o
2023-07-21 13:35 ` Theodore Ts'o
2023-07-21 14:51 ` [dm-devel] " Martin Steigerwald
2023-07-21 14:51 ` Martin Steigerwald
2023-07-19 10:51 ` [dm-devel] File system robustness Kai Tomerius
2023-07-19 10:51 ` Kai Tomerius
2023-07-20 4:41 ` [dm-devel] " Theodore Ts'o
2023-07-20 4:41 ` Theodore Ts'o
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4835096.GXAFRqVoOG@lichtvoll.de \
--to=martin@lichtvoll.de \
--cc=acassis@gmail.com \
--cc=bjorn.forsman@gmail.com \
--cc=dm-devel@redhat.com \
--cc=kai@tomerius.de \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.