From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: Russell Coker <russell@coker.com.au>,
Chris Murphy <lists@colorremedies.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Btrfs and integration with GNU ++
Date: Tue, 19 May 2015 07:56:38 -0400 [thread overview]
Message-ID: <555B24F6.4050607@gmail.com> (raw)
In-Reply-To: <6079A80F-4A26-4D34-AF20-C3161E895FB0@coker.com.au>
[-- Attachment #1: Type: text/plain, Size: 480 bytes --]
On 2015-05-19 03:24, Russell Coker wrote:
> Do you have a reference for fsck on a ro mounted ext4 filesystem being dangerous? The standard behavior of Linux systems has been to fsck a ro mounted ext* root filesystem since long before an initrd was invented.
>
It's only dangerous if fsck changed anything and you then try to use the
filesystem without umounting it and dropping caches or rebooting. I
have had issues in the past with metadata corruption in such cases.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 2967 bytes --]
next prev parent reply other threads:[~2015-05-19 11:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-17 19:33 Btrfs and integration with GNU ++ Roy Sigurd Karlsbakk
2015-05-18 1:32 ` Qu Wenruo
2015-05-18 6:41 ` Duncan
2015-05-18 8:57 ` Duncan
2015-05-18 9:22 ` Roy Sigurd Karlsbakk
2015-05-18 11:58 ` Austin S Hemmelgarn
2015-05-18 14:31 ` Chris Murphy
2015-05-19 17:09 ` Roy Sigurd Karlsbakk
2015-05-19 18:05 ` Chris Murphy
2015-05-19 18:09 ` Chris Murphy
2015-05-19 19:41 ` Eric Sandeen
2015-05-19 20:04 ` Chris Murphy
2015-05-20 6:45 ` Duncan
2015-05-18 14:24 ` Chris Murphy
2015-05-19 7:24 ` Russell Coker
2015-05-19 11:56 ` Austin S Hemmelgarn [this message]
2015-05-19 18:02 ` Chris Murphy
2015-05-20 18:04 ` Zygo Blaxell
2015-05-20 18:02 ` David Sterba
2015-05-18 15:14 ` Eric Sandeen
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=555B24F6.4050607@gmail.com \
--to=ahferroin7@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=russell@coker.com.au \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).