[Kernel-packages] [Bug 1298972] Re: stacktrace in ext4: /build/buildd/linux-3.13.0/fs/ext4/ext4_jbd2.c:259 __ext4_handle_dirty_metadata+0x1a2/0x1c0()

2015-04-02 Thread Russell Smith
Hi, I've been running the following kernel for a while and have reproduced the error in this bug with the following kernel. Linux mirror 3.15.0-031500rc2-generic #201404201435 SMP Sun Apr 20 18:36:18 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Regards Russell -- You received this bug notification

[Kernel-packages] [Bug 1298972] Re: stacktrace in ext4: /build/buildd/linux-3.13.0/fs/ext4/ext4_jbd2.c:259 __ext4_handle_dirty_metadata+0x1a2/0x1c0()

2015-04-02 Thread Russell Smith
The filesystem details are as follows. This may be related to an historic bug in the filesystem that is now causing ongoing corruption as the file system was created in 2010. mr-russ@mirror:~$ sudo tune2fs -l /dev/vda1 tune2fs 1.42.9 (4-Feb-2014) Filesystem volume name: Last mounted on:

[Kernel-packages] [Bug 1298972] Re: stacktrace in ext4: /build/buildd/linux-3.13.0/fs/ext4/ext4_jbd2.c:259 __ext4_handle_dirty_metadata+0x1a2/0x1c0()

2014-12-07 Thread Russell Smith
I just upgraded my hypervisor to Ubuntu 14.04 in an attempt to resolve this issue as Simon experienced. However under heavy I/O of 'aptitude upgrade', I've had 3 more occurences of this with hours of upgrading the host to 14.04. So it appears not to be related to the hypervisor. This leads me do

[Kernel-packages] [Bug 1298972] Re: stacktrace in ext4: /build/buildd/linux-3.13.0/fs/ext4/ext4_jbd2.c:259 __ext4_handle_dirty_metadata+0x1a2/0x1c0()

2014-10-02 Thread Russell Smith
** Attachment added: "tune2fs output from mirror server." https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1298972/+attachment/443/+files/mirror.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.

[Kernel-packages] [Bug 1298972] Re: stacktrace in ext4: /build/buildd/linux-3.13.0/fs/ext4/ext4_jbd2.c:259 __ext4_handle_dirty_metadata+0x1a2/0x1c0()

2014-10-02 Thread Russell Smith
Also the two servers are running; Linux mirror 3.13.0-36-generic #63-Ubuntu SMP Wed Sep 3 21:30:07 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux If there is any other information you want me to attach, please ask. Thanks Russell. -- You received this bug notification because you are a member of Ker

[Kernel-packages] [Bug 1298972] Re: stacktrace in ext4: /build/buildd/linux-3.13.0/fs/ext4/ext4_jbd2.c:259 __ext4_handle_dirty_metadata+0x1a2/0x1c0()

2014-10-02 Thread Russell Smith
Hi, I behaved lazily... and have been trying to collect more data before posting back. Sorry for the delay. 1. I can only reproduce the bug about once a week on 3.13 kernel that is running on ubuntu 14.04. 2. I was lazy and after reading patches and kernel stuff, I marked it as fixed upstream

[Kernel-packages] [Bug 1298972] Re: stacktrace in ext4: /build/buildd/linux-3.13.0/fs/ext4/ext4_jbd2.c:259 __ext4_handle_dirty_metadata+0x1a2/0x1c0()

2014-09-27 Thread Russell Smith
https://www.kernel.org/pub/linux/kernel/v3.0/ChangeLog-3.14.2 contains ext4 patches related to the code in this stack dump; ad6599ab3ac98a4474544086e048ce86ec15a4d1 specifically references incorrect freeing of the function. I'm not able to reliably reproduce the stack dump and am not clear on wh

[Kernel-packages] [Bug 1298972] Re: stacktrace in ext4: /build/buildd/linux-3.13.0/fs/ext4/ext4_jbd2.c:259 __ext4_handle_dirty_metadata+0x1a2/0x1c0()

2014-09-27 Thread Russell Smith
I see this with relative consistency on a number of 14.04 VM's. I will attempt to upgrade to 3.14 and see what happens. -- 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/1298972 Title: st