Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #63939 > unrolled thread
| Started by | Harald Dunkel <harri@afaics.de> |
|---|---|
| First post | 2019-04-27 13:40 +0200 |
| Last post | 2019-04-27 14:50 +0200 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.debian.kernel
RAID 1 problem with 4.19.16 bpo kernel Harald Dunkel <harri@afaics.de> - 2019-04-27 13:40 +0200
Re: RAID 1 problem with 4.19.16 bpo kernel Ben Hutchings <ben@decadent.org.uk> - 2019-04-27 14:50 +0200
| From | Harald Dunkel <harri@afaics.de> |
|---|---|
| Date | 2019-04-27 13:40 +0200 |
| Subject | RAID 1 problem with 4.19.16 bpo kernel |
| Message-ID | <xRtQt-7EY-5@gated-at.bofh.it> |
[Multipart message — attachments visible in raw view] — view raw
Hi folks, Using kernel 4.19.0-0.bpo.2-amd64 on Stretch I had 2 incidents in the past 3 weeks: The PC got stuck, apparently related to md and RAID1 (see the attached logfiles). I have installed 4.19.0-0.bpo.4-amd64 this morning. According to the changelog there were a few changes wrt md and raid since 4.19.16: - md: fix raid10 hang issue caused by barrier - md/raid1: don't clear bitmap bits on interrupted recovery - md/raid5: fix 'out of memory' during raid cache recovery Are these fixes related? Should I create a new bug report? Every helpful comment is highly appreciated. Regards Harri
[toc] | [next] | [standalone]
| From | Ben Hutchings <ben@decadent.org.uk> |
|---|---|
| Date | 2019-04-27 14:50 +0200 |
| Message-ID | <xRuWd-8gq-1@gated-at.bofh.it> |
| In reply to | #63939 |
[Multipart message — attachments visible in raw view] — view raw
On Sat, 2019-04-27 at 13:28 +0200, Harald Dunkel wrote: > Hi folks, > > Using kernel 4.19.0-0.bpo.2-amd64 on Stretch I had 2 incidents > in the past 3 weeks: The PC got stuck, apparently related to md and > RAID1 (see the attached logfiles). > > I have installed 4.19.0-0.bpo.4-amd64 this morning. According > to the changelog there were a few changes wrt md and raid since > 4.19.16: > > - md: fix raid10 hang issue caused by barrier > - md/raid1: don't clear bitmap bits on interrupted recovery > - md/raid5: fix 'out of memory' during raid cache recovery > > Are these fixes related? Should I create a new bug report? > > Every helpful comment is highly appreciated. I don't know if they're related, but please only open a bug report if you can reproduce the issues with the new version. Ben. -- Ben Hutchings Teamwork is essential - it allows you to blame someone else.
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.kernel
csiph-web