[Kernel-packages] [Bug 992424] Re: ext4 filesystem errors on SSD disk
Good ** Changed in: linux (Ubuntu) Assignee: (unassigned) => denace (denace03) -- 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/992424 Title: ext4 filesystem errors on SSD disk Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: After Upgrading from 11.10 to 12.04 I quickly got EXT4 Filesystem errors on my root-fs, which will result in / being remounted as readonly. How to reproduce: 1. Boot 12.04 with latest 12.04 kernel (3.2.0.24.26) 2. Start some io-heavy (probably write-intensive) task, like syncing your mailboxes with offlineimap 3. Bumm -> / is mounted as readonly (there are 2 partitions /boot and / ) Dmesg then Usually shows these 4 lines, but nothing more: [11742.577091] EXT4-fs error (device dm-1): ext4_mb_generate_buddy:739: group 908, 32254 clusters in bitmap, 32258 in gd [11742.577100] Aborting journal on device dm-1-8. [11742.577337] EXT4-fs (dm-1): Remounting filesystem read-only [11742.577357] EXT4-fs (dm-1): ext4_da_writepages: jbd2_start: 9223372036854775807 pages, ino 14876673; err -30 You can then reboot your system, let fsck find a few errors it can fix, reboot again (as /-fs changed) and repeat the steps above. I can boot my 12.04 with the kernel of 11.10 (2.6.38-12.51) and everything works fine (except the wireless card, but that's probably an unrelated bug). So I assume it must be a regression in the EXT4-code of the latest 12.04 Kernel. Also I had no problems with 11.10 and all its previous versions. This happens only on my laptop that uses an INTEL SSDSA2CW160G3. On another machine, which I upgraded at the same time and I use as frequently as my laptop, but with a normal SATA disk it didn't happen so far. Both machines, have 2 partitions, while the LVM for the root filesystem and swap is on the second - an encrypted partition: /dev/sda1 /boot /dev/sda2 -> cryptsetup -> lvm -> root -> swap As both systems are setup the same way, but only the desktop behaves badly on the latest kernel, I assume it could have todo something with the SSD disk, therefor SSD in the title of that bug report. My fstab looks like this: $ cat /etc/fstab # /etc/fstab: static file system information. # # proc/proc procdefaults0 0 # /dev/mapper/foo-root UUID=5eb462f7-485f-48f0-a50b-f07de47c8d01 / ext4 defaults,errors=remount-ro,relatime 0 1 # /dev/sda1 UUID=c69c5d4d-179f-43c7-a793-bc10254f2b1c /boot ext3 defaults,relatime0 2 # /dev/mapper/foo-swap_1 UUID=e8c2dc03-1b7a-4bb9-a983-cdf40d77d50f noneswapsw 0 0 Attached is also a dmesg-output with the 12.04 Kernel and a lspci-vnn output. After submitting that bug I will boot into the newer kernel and also attach uname and version_signature output. If you need any additional information, please let me know. $ lsb_release -rd Description: Ubuntu 12.04 LTS Release: 12.04 $ apt-cache policy linux-image linux-image: Installed: 3.2.0.24.26 Candidate: 3.2.0.24.26 Version table: *** 3.2.0.24.26 0 500 http://archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.2.0.23.25 0 500 http://archive.ubuntu.com/ubuntu/ precise/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/992424/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 992424] Re: ext4 filesystem errors on SSD disk
@THCTLO and all, is there a type of SSD that works better for you?? For me, kernels 3.13, 3.19, and 4.2 (all variants of linux mint 17.x) create this issue with intel SSD drive 460GB. Extremely annoying because windoze 7 worked like a beast on this drive for over a year and I just migrated the disk to run linux in another pc... I guess I should avoid having an SSD mounting / for the forseeable future ... ?? -- 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/992424 Title: ext4 filesystem errors on SSD disk Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: After Upgrading from 11.10 to 12.04 I quickly got EXT4 Filesystem errors on my root-fs, which will result in / being remounted as readonly. How to reproduce: 1. Boot 12.04 with latest 12.04 kernel (3.2.0.24.26) 2. Start some io-heavy (probably write-intensive) task, like syncing your mailboxes with offlineimap 3. Bumm -> / is mounted as readonly (there are 2 partitions /boot and / ) Dmesg then Usually shows these 4 lines, but nothing more: [11742.577091] EXT4-fs error (device dm-1): ext4_mb_generate_buddy:739: group 908, 32254 clusters in bitmap, 32258 in gd [11742.577100] Aborting journal on device dm-1-8. [11742.577337] EXT4-fs (dm-1): Remounting filesystem read-only [11742.577357] EXT4-fs (dm-1): ext4_da_writepages: jbd2_start: 9223372036854775807 pages, ino 14876673; err -30 You can then reboot your system, let fsck find a few errors it can fix, reboot again (as /-fs changed) and repeat the steps above. I can boot my 12.04 with the kernel of 11.10 (2.6.38-12.51) and everything works fine (except the wireless card, but that's probably an unrelated bug). So I assume it must be a regression in the EXT4-code of the latest 12.04 Kernel. Also I had no problems with 11.10 and all its previous versions. This happens only on my laptop that uses an INTEL SSDSA2CW160G3. On another machine, which I upgraded at the same time and I use as frequently as my laptop, but with a normal SATA disk it didn't happen so far. Both machines, have 2 partitions, while the LVM for the root filesystem and swap is on the second - an encrypted partition: /dev/sda1 /boot /dev/sda2 -> cryptsetup -> lvm -> root -> swap As both systems are setup the same way, but only the desktop behaves badly on the latest kernel, I assume it could have todo something with the SSD disk, therefor SSD in the title of that bug report. My fstab looks like this: $ cat /etc/fstab # /etc/fstab: static file system information. # # proc/proc procdefaults0 0 # /dev/mapper/foo-root UUID=5eb462f7-485f-48f0-a50b-f07de47c8d01 / ext4 defaults,errors=remount-ro,relatime 0 1 # /dev/sda1 UUID=c69c5d4d-179f-43c7-a793-bc10254f2b1c /boot ext3 defaults,relatime0 2 # /dev/mapper/foo-swap_1 UUID=e8c2dc03-1b7a-4bb9-a983-cdf40d77d50f noneswapsw 0 0 Attached is also a dmesg-output with the 12.04 Kernel and a lspci-vnn output. After submitting that bug I will boot into the newer kernel and also attach uname and version_signature output. If you need any additional information, please let me know. $ lsb_release -rd Description: Ubuntu 12.04 LTS Release: 12.04 $ apt-cache policy linux-image linux-image: Installed: 3.2.0.24.26 Candidate: 3.2.0.24.26 Version table: *** 3.2.0.24.26 0 500 http://archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.2.0.23.25 0 500 http://archive.ubuntu.com/ubuntu/ precise/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/992424/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 992424] Re: ext4 filesystem errors on SSD disk
Additional info: note that the drive has been absolutely beaten down mercilessly in that year with building 20GB+ MSVC solution projects in numerous directories, recursive changes to permissions on many files, weekly unpacking and writing many TB's of zip files. Is the io error symptoms possibly more of an issue once the drive has gotten a lot of heavy use? -- 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/992424 Title: ext4 filesystem errors on SSD disk Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: After Upgrading from 11.10 to 12.04 I quickly got EXT4 Filesystem errors on my root-fs, which will result in / being remounted as readonly. How to reproduce: 1. Boot 12.04 with latest 12.04 kernel (3.2.0.24.26) 2. Start some io-heavy (probably write-intensive) task, like syncing your mailboxes with offlineimap 3. Bumm -> / is mounted as readonly (there are 2 partitions /boot and / ) Dmesg then Usually shows these 4 lines, but nothing more: [11742.577091] EXT4-fs error (device dm-1): ext4_mb_generate_buddy:739: group 908, 32254 clusters in bitmap, 32258 in gd [11742.577100] Aborting journal on device dm-1-8. [11742.577337] EXT4-fs (dm-1): Remounting filesystem read-only [11742.577357] EXT4-fs (dm-1): ext4_da_writepages: jbd2_start: 9223372036854775807 pages, ino 14876673; err -30 You can then reboot your system, let fsck find a few errors it can fix, reboot again (as /-fs changed) and repeat the steps above. I can boot my 12.04 with the kernel of 11.10 (2.6.38-12.51) and everything works fine (except the wireless card, but that's probably an unrelated bug). So I assume it must be a regression in the EXT4-code of the latest 12.04 Kernel. Also I had no problems with 11.10 and all its previous versions. This happens only on my laptop that uses an INTEL SSDSA2CW160G3. On another machine, which I upgraded at the same time and I use as frequently as my laptop, but with a normal SATA disk it didn't happen so far. Both machines, have 2 partitions, while the LVM for the root filesystem and swap is on the second - an encrypted partition: /dev/sda1 /boot /dev/sda2 -> cryptsetup -> lvm -> root -> swap As both systems are setup the same way, but only the desktop behaves badly on the latest kernel, I assume it could have todo something with the SSD disk, therefor SSD in the title of that bug report. My fstab looks like this: $ cat /etc/fstab # /etc/fstab: static file system information. # # proc/proc procdefaults0 0 # /dev/mapper/foo-root UUID=5eb462f7-485f-48f0-a50b-f07de47c8d01 / ext4 defaults,errors=remount-ro,relatime 0 1 # /dev/sda1 UUID=c69c5d4d-179f-43c7-a793-bc10254f2b1c /boot ext3 defaults,relatime0 2 # /dev/mapper/foo-swap_1 UUID=e8c2dc03-1b7a-4bb9-a983-cdf40d77d50f noneswapsw 0 0 Attached is also a dmesg-output with the 12.04 Kernel and a lspci-vnn output. After submitting that bug I will boot into the newer kernel and also attach uname and version_signature output. If you need any additional information, please let me know. $ lsb_release -rd Description: Ubuntu 12.04 LTS Release: 12.04 $ apt-cache policy linux-image linux-image: Installed: 3.2.0.24.26 Candidate: 3.2.0.24.26 Version table: *** 3.2.0.24.26 0 500 http://archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.2.0.23.25 0 500 http://archive.ubuntu.com/ubuntu/ precise/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/992424/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 992424] Re: ext4 filesystem errors on SSD disk
and for the users : 99Sono (nuno-godinhomatos) wrote on 2013-03-03: missing the option discard in fstab this is what you should have. /dev/sda1 /noatime,discard,errors=remount-ro 0 1 and yes, you can optimze a lot more but it's not needed, try this like above, reboot and test TRIM. -- 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/992424 Title: ext4 filesystem errors on SSD disk Status in The Linux Kernel: Fix Released Status in “linux” package in Ubuntu: Fix Released Bug description: After Upgrading from 11.10 to 12.04 I quickly got EXT4 Filesystem errors on my root-fs, which will result in / being remounted as readonly. How to reproduce: 1. Boot 12.04 with latest 12.04 kernel (3.2.0.24.26) 2. Start some io-heavy (probably write-intensive) task, like syncing your mailboxes with offlineimap 3. Bumm - / is mounted as readonly (there are 2 partitions /boot and / ) Dmesg then Usually shows these 4 lines, but nothing more: [11742.577091] EXT4-fs error (device dm-1): ext4_mb_generate_buddy:739: group 908, 32254 clusters in bitmap, 32258 in gd [11742.577100] Aborting journal on device dm-1-8. [11742.577337] EXT4-fs (dm-1): Remounting filesystem read-only [11742.577357] EXT4-fs (dm-1): ext4_da_writepages: jbd2_start: 9223372036854775807 pages, ino 14876673; err -30 You can then reboot your system, let fsck find a few errors it can fix, reboot again (as /-fs changed) and repeat the steps above. I can boot my 12.04 with the kernel of 11.10 (2.6.38-12.51) and everything works fine (except the wireless card, but that's probably an unrelated bug). So I assume it must be a regression in the EXT4-code of the latest 12.04 Kernel. Also I had no problems with 11.10 and all its previous versions. This happens only on my laptop that uses an INTEL SSDSA2CW160G3. On another machine, which I upgraded at the same time and I use as frequently as my laptop, but with a normal SATA disk it didn't happen so far. Both machines, have 2 partitions, while the LVM for the root filesystem and swap is on the second - an encrypted partition: /dev/sda1 /boot /dev/sda2 - cryptsetup - lvm - root - swap As both systems are setup the same way, but only the desktop behaves badly on the latest kernel, I assume it could have todo something with the SSD disk, therefor SSD in the title of that bug report. My fstab looks like this: $ cat /etc/fstab # /etc/fstab: static file system information. # # file system mount point type options dump pass proc/proc procdefaults0 0 # /dev/mapper/foo-root UUID=5eb462f7-485f-48f0-a50b-f07de47c8d01 / ext4 defaults,errors=remount-ro,relatime 0 1 # /dev/sda1 UUID=c69c5d4d-179f-43c7-a793-bc10254f2b1c /boot ext3 defaults,relatime0 2 # /dev/mapper/foo-swap_1 UUID=e8c2dc03-1b7a-4bb9-a983-cdf40d77d50f noneswapsw 0 0 Attached is also a dmesg-output with the 12.04 Kernel and a lspci-vnn output. After submitting that bug I will boot into the newer kernel and also attach uname and version_signature output. If you need any additional information, please let me know. $ lsb_release -rd Description: Ubuntu 12.04 LTS Release: 12.04 $ apt-cache policy linux-image linux-image: Installed: 3.2.0.24.26 Candidate: 3.2.0.24.26 Version table: *** 3.2.0.24.26 0 500 http://archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.2.0.23.25 0 500 http://archive.ubuntu.com/ubuntu/ precise/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/992424/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
