From: Dave Jones <davej@codemonkey.org.uk>
To: Jens Axboe <axboe@kernel.dk>
Cc: Mike Snitzer <snitzer@redhat.com>,
Greg KH <gregkh@linuxfoundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-block@vger.kernel.org, dm-devel@redhat.com
Subject: Re: Linux 5.10
Date: Mon, 14 Dec 2020 12:29:55 -0500 [thread overview]
Message-ID: <20201214172955.GA9066@codemonkey.org.uk> (raw)
In-Reply-To: <6522caad-bfe8-2554-2ba9-dff5856233d1@kernel.dk>
On Mon, Dec 14, 2020 at 10:21:59AM -0700, Jens Axboe wrote:
> >>>> [ 87.290698] attempt to access beyond end of device
> >>>> md0: rw=4096, want=13996467328, limit=6261202944
> >>>> [ 87.293371] attempt to access beyond end of device
> >>>> md0: rw=4096, want=13998564480, limit=6261202944
> >>>> [ 87.296045] BTRFS warning (device md0): couldn't read tree root
> >>>> [ 87.300056] BTRFS error (device md0): open_ctree failed
> >>>>
> >>>> Reverting it goes back to the -rc7 behaviour where it mounts fine.
> >>>
> >>> If the developer/maintainer(s) agree, I can revert this and push out a
> >>> 5.10.1, just let me know.
> >>
> >> Yes, these should be reverted from 5.10 via 5.10.1:
> >>
> >> e0910c8e4f87 dm raid: fix discard limits for raid1 and raid10
> >> f075cfb1dc59 md: change mddev 'chunk_sectors' from int to unsigned
> >
> > Sorry, f075cfb1dc59 was my local commit id, the corresponding upstream
> > commit as staged by Jens is:
> >
> > 6ffeb1c3f82 md: change mddev 'chunk_sectors' from int to unsigned
> >
> > So please revert:
> > 6ffeb1c3f822 md: change mddev 'chunk_sectors' from int to unsigned
> > and then revert:
> > e0910c8e4f87 dm raid: fix discard limits for raid1 and raid10
>
> Working with Song on understanding the failure case here. raid6 was
> tested prior to this being shipped. We'll be back with more soon...
FYI, mixup in my original mail, it was raid5 (I forgot I converted it from
raid6->raid5 a few months back). But I wouldn't be surprised if they
were both equally affected given what that header touched.
Dave
next prev parent reply other threads:[~2020-12-14 17:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-13 23:03 Linux 5.10 Linus Torvalds
2020-12-14 5:31 ` Dave Jones
2020-12-14 5:40 ` Dave Jones
2020-12-14 5:52 ` Greg KH
2020-12-14 16:02 ` Mike Snitzer
2020-12-14 16:26 ` Mike Snitzer
2020-12-14 17:21 ` Jens Axboe
2020-12-14 17:29 ` Dave Jones [this message]
2020-12-14 16:44 ` Greg KH
2020-12-14 17:06 ` Mike Snitzer
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=20201214172955.GA9066@codemonkey.org.uk \
--to=davej@codemonkey.org.uk \
--cc=axboe@kernel.dk \
--cc=dm-devel@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=snitzer@redhat.com \
--cc=torvalds@linux-foundation.org \
/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).