From: Goffredo Baroncelli <kreijack@inwind.it>
To: Liu Bo <obuil.liubo@gmail.com>,
waxhead@dirtcellar.net, David Sterba <dsterba@suse.cz>
Cc: Mike Stevens <michael.stevens@bayer.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Crashes running btrfs scrub
Date: Tue, 20 Mar 2018 21:04:23 +0100 [thread overview]
Message-ID: <ae7fb47a-c05e-ed23-58cf-e4c05a5334ef@inwind.it> (raw)
In-Reply-To: <CANQeFDDK7uU+USWzzDvWBG1SCpQJyZgrTnYoZ0qp99txSp7cEg@mail.gmail.com>
On 03/19/2018 07:06 PM, Liu Bo wrote:
[...]
>
> So Mike's case is, that both metadata and data are configured as
> raid6, and the operations, balance and scrub, that he tried, need to
> set the existing block group as readonly (in order to avoid any
> further changes being applied during operations are running), then we
> got into the place where another system chunk is needed.
>
> However, I think it'd be better to have some warnings about this when
> doing a) mkfs.btrfs -mraid6, b) btrfs device add.
What about in the kernel dmesg during the mount
>
> David, any idea?
>
> thanks,
> liubo
>
--
gpg @keyserver.linux.it: Goffredo Baroncelli <kreijackATinwind.it>
Key fingerprint BBF5 1610 0B64 DAC6 5F7D 17B2 0EDA 9B37 8B82 E0B5
next prev parent reply other threads:[~2018-03-20 20:04 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-15 18:58 Crashes running btrfs scrub Mike Stevens
2018-03-15 20:32 ` waxhead
2018-03-15 21:07 ` Mike Stevens
2018-03-15 21:22 ` Chris Murphy
[not found] ` <6b4f2b33edb44f1ea8cef47ae68960af@MOXDE7.na.bayer.cnb>
2018-03-16 16:00 ` Chris Murphy
2018-03-16 16:17 ` Mike Stevens
2018-03-16 16:44 ` Chris Murphy
2018-03-16 18:53 ` Mike Stevens
2018-03-18 2:23 ` Qu Wenruo
2018-03-16 21:39 ` Liu Bo
2018-03-16 21:46 ` Mike Stevens
2018-03-18 0:26 ` Liu Bo
2018-03-18 6:41 ` Liu Bo
2018-03-18 7:57 ` Goffredo Baroncelli
2018-03-18 14:46 ` Goffredo Baroncelli
2018-03-18 22:52 ` waxhead
2018-03-19 1:51 ` Qu Wenruo
2018-03-19 18:06 ` Liu Bo
2018-03-20 17:44 ` Mike Stevens
2018-03-21 2:01 ` Qu Wenruo
2018-03-21 17:13 ` Liu Bo
2018-03-22 0:08 ` Qu Wenruo
2018-03-20 20:04 ` Goffredo Baroncelli [this message]
2018-03-15 21:15 ` Chris Murphy
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=ae7fb47a-c05e-ed23-58cf-e4c05a5334ef@inwind.it \
--to=kreijack@inwind.it \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=michael.stevens@bayer.com \
--cc=obuil.liubo@gmail.com \
--cc=waxhead@dirtcellar.net \
/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).