From: james harvey <jamespharvey20@gmail.com>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: Roman Mamedov <rm@romanrm.net>,
Nikolay Borisov <nborisov@suse.com>, Qu Wenruo <wqu@suse.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] btrfs: inode: Don't compress if NODATASUM or NODATACOW set
Date: Mon, 14 May 2018 18:24:21 -0400 [thread overview]
Message-ID: <CA+X5Wn47NrKLvB8qRKQFq8Kd7oeB2R08TPTM7WZqy2SAtM1xTw@mail.gmail.com> (raw)
In-Reply-To: <f6da1d59-c68a-9adb-464f-629b94067538@gmx.com>
On Mon, May 14, 2018 at 6:35 AM, Qu Wenruo <quwenruo.btrfs@gmx.com> wrote:
> And if possible, please don't just remove those offending files (yet).
> Your binary dump would help a lot locating the root case.
Absolutely. This is on a 50G LVM root volume, so I've been able to
leave the original one unmodified and always mounted ro. Copied it
and changed the UUID. So, I can leave it around for a while without a
problem.
next prev parent reply other threads:[~2018-05-14 22:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-14 7:02 [PATCH] btrfs: inode: Don't compress if NODATASUM or NODATACOW set Qu Wenruo
2018-05-14 8:10 ` Nikolay Borisov
2018-05-14 8:20 ` Roman Mamedov
2018-05-14 8:36 ` Nikolay Borisov
2018-05-14 9:31 ` james harvey
2018-05-14 9:39 ` Roman Mamedov
2018-05-14 9:46 ` Nikolay Borisov
2018-05-14 16:49 ` David Sterba
2018-05-14 9:30 ` james harvey
2018-05-14 10:35 ` Qu Wenruo
2018-05-14 22:24 ` james harvey [this message]
2018-05-15 0:15 ` james harvey
2018-05-14 8:24 ` Qu Wenruo
2018-05-14 16:52 ` David Sterba
2018-05-14 20:46 ` Timofey Titovets
2018-05-15 18:18 ` David Sterba
2018-05-14 22:29 ` james harvey
2018-05-15 1:35 ` Qu Wenruo
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=CA+X5Wn47NrKLvB8qRKQFq8Kd7oeB2R08TPTM7WZqy2SAtM1xTw@mail.gmail.com \
--to=jamespharvey20@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=nborisov@suse.com \
--cc=quwenruo.btrfs@gmx.com \
--cc=rm@romanrm.net \
--cc=wqu@suse.com \
/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).