Re: ext4 file system corruption -> https://bugzilla.kernel.org/show_bug.cgi?id=201685
Am 05.12.18 um 00:23 schrieb Laura Abbott: > On 12/3/18 8:46 AM, Reindl Harald wrote: >> >> Am 03.12.18 um 17:42 schrieb Laura Abbott: >>> On 12/2/18 6:20 AM, Reindl Harald wrote: how does Fedora think to handle https://bugzilla.kernel.org/show_bug.cgi?id=201685 4.18.20 is the last 4.18.x and happily at least 4.18.20 from F27 runs fine on F28 systems but given that bug upgrade to 4.19.x seems to be just a lottery with your data - on some or even many systems all seems to be fine BUT when you are affected and nobody until now knows the root cause honestly the rebase to 4.19 was too fast to start with! WHY did that rebase happen at all? kernel-4.19.2-200.fc28 jcline 2018-11-15 01:34:18 bug reported: 2018-11-13 19:42:20 UTC and yes i had that bugreport in my inbox just because i have subscribed to filesystem / raid related mailing lists and the word "crazy" appeared in my mind when i saw the rebase two days later because i expect that downstream maintainers at least have the same lists subscribed ordinary users have >>> >>> We're working with the upstream maintainers to narrow down the problem. >>> At least on Fedora we haven't seen any reports of corruption reported >>> on our bugzilla which is a useful data point for the upstream >>> maintainers. >>> We'll keep you updated if we find anything. >> >> here you have the first Fedora user upstream >> https://bugzilla.kernel.org/show_bug.cgi?id=201685#c198 > > There's now a fix proposed upstream > https://bugzilla.kernel.org/show_bug.cgi?id=201685#c255 sounds so but i still call it a mistake doing the rebase two days after the problem was reported instead update F28 with 4.18.20 as well as upstream should have removed the "EOL" from 4.18.20 and continue security updates until a confirmed 4.19.x is out ___ kernel mailing list -- kernel@lists.fedoraproject.org To unsubscribe send an email to kernel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Re: ext4 file system corruption -> https://bugzilla.kernel.org/show_bug.cgi?id=201685
On 12/3/18 8:46 AM, Reindl Harald wrote: Am 03.12.18 um 17:42 schrieb Laura Abbott: On 12/2/18 6:20 AM, Reindl Harald wrote: how does Fedora think to handle https://bugzilla.kernel.org/show_bug.cgi?id=201685 4.18.20 is the last 4.18.x and happily at least 4.18.20 from F27 runs fine on F28 systems but given that bug upgrade to 4.19.x seems to be just a lottery with your data - on some or even many systems all seems to be fine BUT when you are affected and nobody until now knows the root cause honestly the rebase to 4.19 was too fast to start with! WHY did that rebase happen at all? kernel-4.19.2-200.fc28 jcline 2018-11-15 01:34:18 bug reported: 2018-11-13 19:42:20 UTC and yes i had that bugreport in my inbox just because i have subscribed to filesystem / raid related mailing lists and the word "crazy" appeared in my mind when i saw the rebase two days later because i expect that downstream maintainers at least have the same lists subscribed ordinary users have We're working with the upstream maintainers to narrow down the problem. At least on Fedora we haven't seen any reports of corruption reported on our bugzilla which is a useful data point for the upstream maintainers. We'll keep you updated if we find anything. here you have the first Fedora user upstream https://bugzilla.kernel.org/show_bug.cgi?id=201685#c198 There's now a fix proposed upstream https://bugzilla.kernel.org/show_bug.cgi?id=201685#c255 ___ kernel mailing list -- kernel@lists.fedoraproject.org To unsubscribe send an email to kernel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Re: ext4 file system corruption -> https://bugzilla.kernel.org/show_bug.cgi?id=201685
On Mon, 3 Dec 2018 08:42:15 -0800 Laura Abbott wrote: > On 12/2/18 6:20 AM, Reindl Harald wrote: > > how does Fedora think to handle > > https://bugzilla.kernel.org/show_bug.cgi?id=201685 > > > > 4.18.20 is the last 4.18.x and happily at least 4.18.20 from F27 > > runs fine on F28 systems but given that bug upgrade to 4.19.x seems > > to be just a lottery with your data - on some or even many systems > > all seems to be fine BUT when you are affected and nobody until now > > knows the root cause > > > > honestly the rebase to 4.19 was too fast to start with! > > WHY did that rebase happen at all? > > > > kernel-4.19.2-200.fc28 jcline 2018-11-15 01:34:18 > > bug reported: 2018-11-13 19:42:20 UTC > > > > and yes i had that bugreport in my inbox just because i have > > subscribed to filesystem / raid related mailing lists and the word > > "crazy" appeared in my mind when i saw the rebase two days later > > because i expect that downstream maintainers at least have the same > > lists subscribed ordinary users have > > We're working with the upstream maintainers to narrow down the > problem. At least on Fedora we haven't seen any reports of corruption > reported on our bugzilla which is a useful data point for the > upstream maintainers. We'll keep you updated if we find anything. I've been running the 4.19 test kernels, and now the release kernels, without any problem on F28. I do compile them locally, and skip anything that doesn't apply to my system, so that could be why. All ext4. That ticket has reports from all over the spectrum. Hard to narrow down a cause, or maybe causes if the error is affecting several kernel subsystems. ___ kernel mailing list -- kernel@lists.fedoraproject.org To unsubscribe send an email to kernel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Re: ext4 file system corruption -> https://bugzilla.kernel.org/show_bug.cgi?id=201685
Am 03.12.18 um 17:42 schrieb Laura Abbott: > On 12/2/18 6:20 AM, Reindl Harald wrote: >> how does Fedora think to handle >> https://bugzilla.kernel.org/show_bug.cgi?id=201685 >> >> 4.18.20 is the last 4.18.x and happily at least 4.18.20 from F27 runs >> fine on F28 systems but given that bug upgrade to 4.19.x seems to be >> just a lottery with your data - on some or even many systems all seems >> to be fine BUT when you are affected and nobody until now knows the root >> cause >> >> honestly the rebase to 4.19 was too fast to start with! >> WHY did that rebase happen at all? >> >> kernel-4.19.2-200.fc28 jcline 2018-11-15 01:34:18 >> bug reported: 2018-11-13 19:42:20 UTC >> >> and yes i had that bugreport in my inbox just because i have subscribed >> to filesystem / raid related mailing lists and the word "crazy" appeared >> in my mind when i saw the rebase two days later because i expect that >> downstream maintainers at least have the same lists subscribed ordinary >> users have > > We're working with the upstream maintainers to narrow down the problem. > At least on Fedora we haven't seen any reports of corruption reported > on our bugzilla which is a useful data point for the upstream maintainers. > We'll keep you updated if we find anything. here you have the first Fedora user upstream https://bugzilla.kernel.org/show_bug.cgi?id=201685#c198 ___ kernel mailing list -- kernel@lists.fedoraproject.org To unsubscribe send an email to kernel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Re: ext4 file system corruption -> https://bugzilla.kernel.org/show_bug.cgi?id=201685
On 12/2/18 6:20 AM, Reindl Harald wrote: how does Fedora think to handle https://bugzilla.kernel.org/show_bug.cgi?id=201685 4.18.20 is the last 4.18.x and happily at least 4.18.20 from F27 runs fine on F28 systems but given that bug upgrade to 4.19.x seems to be just a lottery with your data - on some or even many systems all seems to be fine BUT when you are affected and nobody until now knows the root cause honestly the rebase to 4.19 was too fast to start with! WHY did that rebase happen at all? kernel-4.19.2-200.fc28 jcline 2018-11-15 01:34:18 bug reported: 2018-11-13 19:42:20 UTC and yes i had that bugreport in my inbox just because i have subscribed to filesystem / raid related mailing lists and the word "crazy" appeared in my mind when i saw the rebase two days later because i expect that downstream maintainers at least have the same lists subscribed ordinary users have We're working with the upstream maintainers to narrow down the problem. At least on Fedora we haven't seen any reports of corruption reported on our bugzilla which is a useful data point for the upstream maintainers. We'll keep you updated if we find anything. Thanks, Laura ___ kernel mailing list -- kernel@lists.fedoraproject.org To unsubscribe send an email to kernel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Re: ext4 file system corruption -> https://bugzilla.kernel.org/show_bug.cgi?id=201685
Am 03.12.18 um 08:56 schrieb Peter Robinson: > On Sun, Dec 2, 2018 at 5:04 PM Sérgio Basto wrote: >> >> yeah yestarday my computer don't boot with kernel-4.18.20 , back to >> kernel-core-4.18.19-100.fc27.x86_64. >> >> Thanks for the tip >> >> It might be related with [1] ? >> "I see that a 4.18.20-100.fc27 is already in koji, and unfortunately 4.18.xx >> is now EOL. >> May I suggest that f27 to get a new 4.18.20 build with the STIBP backport >> reverted >> please? (Current 4.19.3-rc reverts that already.)" > > Fedora 27 is end of life, the fix to this problem is to upgrade to a > newer release, or alternatively until you can upgrade you could run a > newer Fedora 28 kernel on Fedora 27. you didn't get the problem! https://bugzilla.kernel.org/show_bug.cgi?id=201685 currently one is running F27 kernels on F28 to avoid 4.19.x until it's clear what is going on and your supposed "run a newwer F28 kernel on F27" is the exactly opposite ___ kernel mailing list -- kernel@lists.fedoraproject.org To unsubscribe send an email to kernel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Re: ext4 file system corruption -> https://bugzilla.kernel.org/show_bug.cgi?id=201685
On Sun, Dec 2, 2018 at 5:04 PM Sérgio Basto wrote: > > yeah yestarday my computer don't boot with kernel-4.18.20 , back to > kernel-core-4.18.19-100.fc27.x86_64. > > Thanks for the tip > > It might be related with [1] ? > "I see that a 4.18.20-100.fc27 is already in koji, and unfortunately 4.18.xx > is now EOL. > May I suggest that f27 to get a new 4.18.20 build with the STIBP backport > reverted > please? (Current 4.19.3-rc reverts that already.)" Fedora 27 is end of life, the fix to this problem is to upgrade to a newer release, or alternatively until you can upgrade you could run a newer Fedora 28 kernel on Fedora 27. Peter ___ kernel mailing list -- kernel@lists.fedoraproject.org To unsubscribe send an email to kernel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Re: ext4 file system corruption -> https://bugzilla.kernel.org/show_bug.cgi?id=201685
yeah yestarday my computer don't boot with kernel-4.18.20 , after back to kernel-core-4.18.19-100.fc27.x86_64, it resume to work perfectly . Thanks for the tip . It might be related with [1] ? "I see that a 4.18.20-100.fc27 is already in koji, and unfortunately 4.18.xx is now EOL. May I suggest that f27 to get a new 4.18.20 build with the STIBP backport reverted please? (Current 4.19.3-rc reverts that already.)" [1] https://bodhi.fedoraproject.org/updates/FEDORA-2018-b68776e5b0#comment-865736 On Sun, 2018-12-02 at 15:20 +0100, Reindl Harald wrote: > how does Fedora think to handle > https://bugzilla.kernel.org/show_bug.cgi?id=201685 > > 4.18.20 is the last 4.18.x and happily at least 4.18.20 from F27 runs > fine on F28 systems but given that bug upgrade to 4.19.x seems to be > just a lottery with your data - on some or even many systems all > seems > to be fine BUT when you are affected and nobody until now knows the > root > cause > > honestly the rebase to 4.19 was too fast to start with! > WHY did that rebase happen at all? > > kernel-4.19.2-200.fc28jcline 2018-11-15 01:34:18 > bug reported: 2018-11-13 19:42:20 UTC > > and yes i had that bugreport in my inbox just because i have > subscribed > to filesystem / raid related mailing lists and the word "crazy" > appeared > in my mind when i saw the rebase two days later because i expect that > downstream maintainers at least have the same lists subscribed > ordinary > users have > ___ > kernel mailing list -- kernel@lists.fedoraproject.org > To unsubscribe send an email to kernel-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelin > es > List Archives: https://lists.fedoraproject.org/archives/list/kernel@l > ists.fedoraproject.org -- Sérgio M. B. ___ kernel mailing list -- kernel@lists.fedoraproject.org To unsubscribe send an email to kernel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Re: ext4 file system corruption -> https://bugzilla.kernel.org/show_bug.cgi?id=201685
yeah yestarday my computer don't boot with kernel-4.18.20 , back to kernel-core-4.18.19-100.fc27.x86_64. Thanks for the tip It might be related with [1] ? "I see that a 4.18.20-100.fc27 is already in koji, and unfortunately 4.18.xx is now EOL. May I suggest that f27 to get a new 4.18.20 build with the STIBP backport reverted please? (Current 4.19.3-rc reverts that already.)" [1] https://bodhi.fedoraproject.org/updates/FEDORA-2018-b68776e5b0#comment-865736 On Sun, 2018-12-02 at 15:20 +0100, Reindl Harald wrote: > how does Fedora think to handle > https://bugzilla.kernel.org/show_bug.cgi?id=201685 > > 4.18.20 is the last 4.18.x and happily at least 4.18.20 from F27 runs > fine on F28 systems but given that bug upgrade to 4.19.x seems to be > just a lottery with your data - on some or even many systems all > seems > to be fine BUT when you are affected and nobody until now knows the > root > cause > > honestly the rebase to 4.19 was too fast to start with! > WHY did that rebase happen at all? > > kernel-4.19.2-200.fc28jcline 2018-11-15 01:34:18 > bug reported: 2018-11-13 19:42:20 UTC > > and yes i had that bugreport in my inbox just because i have > subscribed > to filesystem / raid related mailing lists and the word "crazy" > appeared > in my mind when i saw the rebase two days later because i expect that > downstream maintainers at least have the same lists subscribed > ordinary > users have > ___ > kernel mailing list -- kernel@lists.fedoraproject.org > To unsubscribe send an email to kernel-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelin > es > List Archives: https://lists.fedoraproject.org/archives/list/kernel@l > ists.fedoraproject.org -- Sérgio M. B. ___ kernel mailing list -- kernel@lists.fedoraproject.org To unsubscribe send an email to kernel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
ext4 file system corruption -> https://bugzilla.kernel.org/show_bug.cgi?id=201685
how does Fedora think to handle https://bugzilla.kernel.org/show_bug.cgi?id=201685 4.18.20 is the last 4.18.x and happily at least 4.18.20 from F27 runs fine on F28 systems but given that bug upgrade to 4.19.x seems to be just a lottery with your data - on some or even many systems all seems to be fine BUT when you are affected and nobody until now knows the root cause honestly the rebase to 4.19 was too fast to start with! WHY did that rebase happen at all? kernel-4.19.2-200.fc28 jcline 2018-11-15 01:34:18 bug reported: 2018-11-13 19:42:20 UTC and yes i had that bugreport in my inbox just because i have subscribed to filesystem / raid related mailing lists and the word "crazy" appeared in my mind when i saw the rebase two days later because i expect that downstream maintainers at least have the same lists subscribed ordinary users have ___ kernel mailing list -- kernel@lists.fedoraproject.org To unsubscribe send an email to kernel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
