[Kernel-packages] [Bug 1190295] Re: 2.6.32-47 kernel update on 10.04 breaks software RAID (+ LVM)

2019-10-03 Thread Po-Hsu Lin
Closing this bug with Won't fix as this kernel / release is no longer supported. Please feel free to open a new bug report if you're still experiencing this on a newer release (Bionic 18.04.3 / Disco 19.04) Thanks! ** Changed in: linux (Ubuntu) Status: Incomplete => Won't Fix -- You

[Kernel-packages] [Bug 1190295] Re: 2.6.32-47 kernel update on 10.04 breaks software RAID (+ LVM)

2013-08-07 Thread A1an
@penalvch New bug filed as requested: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1209423 PS: I did not realize the kernel versions (using a dot for the last digits) are different from the ubuntu ones (using a -). I'll also answer latest questions by sconklin on the new bugreport. --

[Kernel-packages] [Bug 1190295] Re: 2.6.32-47 kernel update on 10.04 breaks software RAID (+ LVM)

2013-08-06 Thread Steve Conklin
** Changed in: linux (Ubuntu) Assignee: (unassigned) = Steve Conklin (sconklin) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1190295 Title: 2.6.32-47 kernel update on 10.04

[Kernel-packages] [Bug 1190295] Re: 2.6.32-47 kernel update on 10.04 breaks software RAID (+ LVM)

2013-08-06 Thread Steve Conklin
It's possible that the patches which were linked are not related. They're not in the delta between the two versions which are listed. Here are some questions to try to narrow down the field of potential issues. 1. You mention that this occurs on various upgrades, could you confirm that these

[Kernel-packages] [Bug 1190295] Re: 2.6.32-47 kernel update on 10.04 breaks software RAID (+ LVM)

2013-08-01 Thread A1an
I see and I'll try to flie the new report as soon as possible, even though I think it is the same cause as this one. I've had a look at the kernel log and see that only two patches affected the md component between 2.6.32-46 (working kernel) and 2.6.32-47 (broken kernel, reported in this bug):