In gmane.comp.file-systems.ext4 Pavel Machek wrote:
> [-- text/plain, кодировка quoted-printable, кодировка: us-ascii, 32 строк --]
> Hi!
> > > >> OK, - and now we are looking forward to *your* ideas how to solve this.
> > > >
> > > > After four days playing games around git bisect - real winner
Hi!
> > >> OK, - and now we are looking forward to *your* ideas how to solve this.
> > >
> > > After four days playing games around git bisect - real winner is
> > > debian gcc-8.2.0-9. Upgrade it to 8.2.0-10 or use 7.3.0-30 version for
> > > same kernel + config - does not exhibit ext4 corruption
пн, 3 дек. 2018 г. в 01:11, Rainer Fiebig :
>
> Am 02.12.18 um 21:19 schrieb Andrey Melnikov:
> > чт, 29 нояб. 2018 г. в 01:08, Rainer Fiebig :
> >>
> >> Am 28.11.18 um 22:13 schrieb Andrey Melnikov:
> >>> ср, 28 нояб. 2018 г. в 18:55, Rainer Fiebig :
>
> Am Mittwoch, 28. November 2018, 1
After upgrading my kernel to 4.19 I got a corruption on nearly every
reboot or resume from suspend on my Acer s7-391 [UEFI boot].
Going to my UEFI setup and changing IDE mode from IDE to ATA seems to
have resolved the issue for me.
Don't know, though, if that is a valid data point or if it was a
I'm suffering from ext4 corruption too.
(Ubuntu 18.10, 4.19.6-041906-generic, 64 bit)
22:00:01 kernel: EXT4-fs error (device sda4): ext4_iget:4831: inode
#42484759: comm rm: bad extra_isize 58853 (inode size 256)
22:00:01 kernel: EXT4-fs error (device sda4): ext4_iget:4831: inode
#42484759: comm r
Am 02.12.18 um 21:19 schrieb Andrey Melnikov:
> чт, 29 нояб. 2018 г. в 01:08, Rainer Fiebig :
>>
>> Am 28.11.18 um 22:13 schrieb Andrey Melnikov:
>>> ср, 28 нояб. 2018 г. в 18:55, Rainer Fiebig :
Am Mittwoch, 28. November 2018, 13:02:56 schrieb Andrey Jr. Melnikov:
> In gmane.comp.fil
чт, 29 нояб. 2018 г. в 01:08, Rainer Fiebig :
>
> Am 28.11.18 um 22:13 schrieb Andrey Melnikov:
> > ср, 28 нояб. 2018 г. в 18:55, Rainer Fiebig :
> >>
> >> Am Mittwoch, 28. November 2018, 13:02:56 schrieb Andrey Jr. Melnikov:
> >>> In gmane.comp.file-systems.ext4 Theodore Y. Ts'o wrote:
> On
On Tue, 27 Nov 2018 23:15:55 -0500, Theodore Y. Ts'o wrote:
> I'm trying to figure out common factors from those people who are
> reporting problems.
Hello, I experienced the ext4-randomly-switching-to-read-only issue
with Linux kernel 4.19.5 (from
http://kernel.ubuntu.com/~kernel-ppa/mainline/ ;
Am 28.11.18 um 22:13 schrieb Andrey Melnikov:
> ср, 28 нояб. 2018 г. в 18:55, Rainer Fiebig :
>>
>> Am Mittwoch, 28. November 2018, 13:02:56 schrieb Andrey Jr. Melnikov:
>>> In gmane.comp.file-systems.ext4 Theodore Y. Ts'o wrote:
On Wed, Nov 28, 2018 at 03:16:33AM +0300, Andrey Jr. Melnikov w
ср, 28 нояб. 2018 г. в 18:55, Rainer Fiebig :
>
> Am Mittwoch, 28. November 2018, 13:02:56 schrieb Andrey Jr. Melnikov:
> > In gmane.comp.file-systems.ext4 Theodore Y. Ts'o wrote:
> > > On Wed, Nov 28, 2018 at 03:16:33AM +0300, Andrey Jr. Melnikov wrote:
> > > > Corrupted inodes - always directory
Am 28.11.18 um 17:10 schrieb Theodore Y. Ts'o:
> On Wed, Nov 28, 2018 at 04:56:51PM +0100, Rainer Fiebig wrote:
>>
>> If you still see the errors, at least the Ubuntu-kernel could be ruled out.
>
> My impression is that some of the people reporting problems have been
> using stock upstream kernels
On 28/11/2018 17:10, Theodore Y. Ts'o wrote:
> On Wed, Nov 28, 2018 at 04:56:51PM +0100, Rainer Fiebig wrote:
>>
>> If you still see the errors, at least the Ubuntu-kernel could be ruled out.
>
> My impression is that some of the people reporting problems have been
> using stock upstream kernels,
On Wed, Nov 28, 2018 at 04:56:51PM +0100, Rainer Fiebig wrote:
>
> If you still see the errors, at least the Ubuntu-kernel could be ruled out.
My impression is that some of the people reporting problems have been
using stock upstream kernels, so I wasn't really worried about the
Ubuntu kernel (al
Am Mittwoch, 28. November 2018, 13:02:56 schrieb Andrey Jr. Melnikov:
> In gmane.comp.file-systems.ext4 Theodore Y. Ts'o wrote:
> > On Wed, Nov 28, 2018 at 03:16:33AM +0300, Andrey Jr. Melnikov wrote:
> > > Corrupted inodes - always directory, not touched at least year or
> > > more for writing. S
ср, 28 нояб. 2018 г. в 07:15, Theodore Y. Ts'o :
>
> On Wed, Nov 28, 2018 at 03:16:33AM +0300, Andrey Jr. Melnikov wrote:
> > Corrupted inodes - always directory, not touched at least year or
> > more for writing. Something wrong when updating atime?
>
> We're not sure. The frustrating thing is th
In gmane.comp.file-systems.ext4 Theodore Y. Ts'o wrote:
> On Wed, Nov 28, 2018 at 03:16:33AM +0300, Andrey Jr. Melnikov wrote:
> > Corrupted inodes - always directory, not touched at least year or
> > more for writing. Something wrong when updating atime?
> We're not sure. The frustrating thing
Am 27.11.18 um 22:22 schrieb Guenter Roeck:
> On Tue, Nov 27, 2018 at 07:55:01PM +0100, Rainer Fiebig wrote:
>> Am Dienstag, 27. November 2018, 15:48:19 schrieb Marek Habersack:
>>> On 27/11/2018 15:32, Guenter Roeck wrote:
>>> Hi,
>>>
>>> You might try to see if you have CONFIG_SCSI_MQ_DEFAULT=yes
On 28/11/2018 05:15, Theodore Y. Ts'o wrote:
> On Wed, Nov 28, 2018 at 03:16:33AM +0300, Andrey Jr. Melnikov wrote:
>> Corrupted inodes - always directory, not touched at least year or
>> more for writing. Something wrong when updating atime?
I've just seen the errors come back despite having MQ of
On Wed, Nov 28, 2018 at 03:16:33AM +0300, Andrey Jr. Melnikov wrote:
> Corrupted inodes - always directory, not touched at least year or
> more for writing. Something wrong when updating atime?
We're not sure. The frustrating thing is that it's not reproducing
for me. I run extensive regression
On Tue, Nov 27, 2018 at 01:22:55PM -0800, Guenter Roeck wrote:
> On Tue, Nov 27, 2018 at 07:55:01PM +0100, Rainer Fiebig wrote:
> > Am Dienstag, 27. November 2018, 15:48:19 schrieb Marek Habersack:
> > > On 27/11/2018 15:32, Guenter Roeck wrote:
> > > Hi,
> > >
> > > You might try to see if you ha
In gmane.comp.file-systems.ext4 Guenter Roeck wrote:
> [trying again, this time with correct kernel.org address]
> Hi,
> I have seen the following and similar problems several times,
> with both v4.19.3 and v4.19.4:
> Nov 23 04:32:25 mars kernel: [112668.673671] EXT4-fs error (device sdb1):
>
On Tue, Nov 27, 2018 at 07:55:01PM +0100, Rainer Fiebig wrote:
> Am Dienstag, 27. November 2018, 15:48:19 schrieb Marek Habersack:
> > On 27/11/2018 15:32, Guenter Roeck wrote:
> > Hi,
> >
> > You might try to see if you have CONFIG_SCSI_MQ_DEFAULT=yes in your kernel
> > config. Starting with 4.19
Am Dienstag, 27. November 2018, 15:48:19 schrieb Marek Habersack:
> On 27/11/2018 15:32, Guenter Roeck wrote:
> Hi,
>
> You might try to see if you have CONFIG_SCSI_MQ_DEFAULT=yes in your kernel
> config. Starting with 4.19.1 it somehow interferes with ext4 and causes
> problems similar to the one
On Tue, Nov 27, 2018 at 03:48:19PM +0100, Marek Habersack wrote:
> On 27/11/2018 15:32, Guenter Roeck wrote:
> Hi,
>
> You might try to see if you have CONFIG_SCSI_MQ_DEFAULT=yes in your kernel
> config. Starting with 4.19.1 it somehow
Yes, it is enabled in my configuration.
> interferes with e
Am Dienstag, 27. November 2018, 06:32:08 schrieb Guenter Roeck:
> [trying again, this time with correct kernel.org address]
>
> Hi,
>
> I have seen the following and similar problems several times,
> with both v4.19.3 and v4.19.4:
>
> Nov 23 04:32:25 mars kernel: [112668.673671] EXT4-fs error (d
On 27/11/2018 15:32, Guenter Roeck wrote:
Hi,
You might try to see if you have CONFIG_SCSI_MQ_DEFAULT=yes in your kernel
config. Starting with 4.19.1 it somehow
interferes with ext4 and causes problems similar to the ones you list below.
Ever since I disabled MQ (either recompile
your kernel or
[trying again, this time with correct kernel.org address]
Hi,
I have seen the following and similar problems several times,
with both v4.19.3 and v4.19.4:
Nov 23 04:32:25 mars kernel: [112668.673671] EXT4-fs error (device sdb1):
ext4_iget:4831: inode #12602889: comm git: bad extra_isize 33661
27 matches
Mail list logo
