Fixed:Mint13-14 Latest Kernel Version Causing EXT4-fs Errors

Questions about applications and software
Forum rules
Before you post please read this

Fixed:Mint13-14 Latest Kernel Version Causing EXT4-fs Errors

Postby karlchen on Mon Jan 21, 2013 6:13 am

Hello, folks.

Symptoms:

Lately I started finding such error messages in the file /var/log/syslog and /var/log/syslog.1, but never in older already gzipped syslog files, which confirms that this is a new problem:
Code: Select all
syslog:Jan 21 09:29:28 mint13cn kernel: [    3.416571] EXT4-fs (loop0): orphan cleanup on readonly fs
syslog:Jan 21 09:29:28 mint13cn kernel: [    3.463448] EXT4-fs (loop0): ext4_orphan_cleanup: deleting unreferenced inode 805363
syslog:Jan 21 09:29:28 mint13cn kernel: [    3.486513] EXT4-fs (loop0): ext4_orphan_cleanup: deleting unreferenced inode 805362
syslog:Jan 21 09:29:28 mint13cn kernel: [    3.486521] EXT4-fs (loop0): ext4_orphan_cleanup: deleting unreferenced inode 805361
syslog:Jan 21 09:29:28 mint13cn kernel: [    3.486535] EXT4-fs (loop0): ext4_orphan_cleanup: deleting unreferenced inode 805360
syslog:Jan 21 09:29:28 mint13cn kernel: [    3.486542] EXT4-fs (loop0): ext4_orphan_cleanup: deleting unreferenced inode 805359
syslog:Jan 21 09:29:28 mint13cn kernel: [    3.542965] EXT4-fs (loop0): ext4_orphan_cleanup: deleting unreferenced inode 1573846
syslog:Jan 21 09:29:28 mint13cn kernel: [    3.584281] EXT4-fs (loop0): ext4_orphan_cleanup: deleting unreferenced inode 1569852
syslog:Jan 21 09:29:28 mint13cn kernel: [    3.632202] EXT4-fs (loop0): ext4_orphan_cleanup: deleting unreferenced inode 1319573
syslog:Jan 21 09:29:28 mint13cn kernel: [    3.636104] EXT4-fs (loop0): 8 orphan inodes deleted
syslog:Jan 21 09:29:28 mint13cn kernel: [    3.636108] EXT4-fs (loop0): recovery complete
syslog:Jan 21 09:29:28 mint13cn kernel: [    3.708849] EXT4-fs (loop0): mounted filesystem with ordered data mode. Opts: (null)
syslog:Jan 21 09:29:28 mint13cn kernel: [   21.044818] EXT4-fs (loop0): re-mounted. Opts: errors=remount-ro


Note:
Absolutely no need telling me that this is from a Mint4win installation. I know. The problem is not caused by any alledged, but never proven instability of Mint4win installations.
Moreover I have found the same problem on a genuine Mint14 installation which lives on a dedicated partition on /dev/sda6, hence no Mint4win involved.
I will post the corresponding syslog entries as soon as a I will have access to that machine again, sometime tonight.



Scope:

So far I have detected the problem on 1 genuine Linux Mint 14 installation and on 1 Linux Mint 13 installation. Both 32-bit.
(I will check whether my 64-bit Ubuntu / Mint systems exhibit the same problem.)


Common Factors:

  • None of the two systems, where the problem has been detected, had ever exhibited this problem before.
  • On both systems, the latest Ubuntu kernels, 3.5.0-22 (Mint 14), 3.2.0-36 (Mint 13), had been installed right before the problem started.


Workaround:

On the Linux Mint 13 system returning to the previous kernel, i.e. 3.2.0-35, made the symptoms go away.

Note:

As the orphaned inodes are created during the shutdown procedure - root filesystem not being umounted cleanly or not at all - who knows - you will have to reboot twice using the old kernel in order to confirm the problem has gone away: The first session using an older kernel will repair the damage done and not create it on shutdown. The next session(s) using the old kernel will prove the problem does not re-appear.


Next Steps:

As soon as possible I will go through the Ubuntu / Mint systems in order to determine
  • whether only 32-bit systems are aftected or 64-bit systems as well
  • whether returning to the previous kernel versions 3.2.0-35 (Mint13, Ubuntu 12.04) or 3.5.0-21 (Mint 14) respectively will fix the problem on all affected systems
  • post further syslog entries to support my report
  • Once the facts have been established I guess it will the right time to file a Launchpad bug report.

Can anybody confirm the symptoms and the relation in terms of time to installing the latest Ubuntu kernel editions?

Kind regards,
Karl
Last edited by karlchen on Sat Oct 26, 2013 6:08 pm, edited 1 time in total.
User avatar
karlchen
Level 10
Level 10
 
Posts: 3405
Joined: Sat Dec 31, 2011 7:21 am

Linux Mint is funded by ads and donations.
 

Re: Mint13-14 Latest Kernel Version Causing EXT4-fs Errors

Postby viking777 on Mon Jan 21, 2013 6:44 am

I run Ubuntu 12.10 and Mint 14 both with kernel 3.5.0-22 64 bit with the ext4 file system. I searched in syslog and syslog.1 on both systems using the search terms 'orphan' and 'unreferenced' (separately not together) on all 8 searches no results were returned.
Fujitsu Lifebook AH532. Intel i5 processor, 6Gb ram, Intel HD3000 graphics, Intel Audio/wifi. Realtek RTL8111/8168B Ethernet.Lubuntu 13.10,Ubuntu12.10 (Unity), Mint16 (Cinnamon), Manjaro (Xfce).
Image
User avatar
viking777
Level 14
Level 14
 
Posts: 5153
Joined: Mon Dec 01, 2008 11:21 am

Re: Mint13-14 Latest Kernel Version Causing EXT4-fs Errors

Postby karlchen on Mon Jan 21, 2013 7:05 am

Hello, viking777.

Thanks for taking the time to check your syslog files.

I am really curious as to what the results will be on my 2 64-bit Linux systems:
+ 1x Ubuntu 12.04.1 x64 - K3.2.0-36 (updated Sunday)
+ 1x 1x Linux Mint 13 x64 - K3.2.0-36 (updated Sunday)
None of the two systems had any EXT4-fs error messages at all in the past.

So far I have seen and verified the issue as being persistent on two 32-bit systems only:
+ 1x Linux Mint 14 x86 - K3.5.0-22 (updated a few days ago)
+ 1x Linux Mint 13 x86 - K3.2.0-36 (updated Friday)
The Mint 13 machine received no other updates on Friday except the K3.2.0-36 and this is when the problem started.
Reverting to K3.2.0-35 made the problem disappear again.
No EXT4-fs error messages have been seen since Mint 13 was installed on this machine Oct 25th, 2012.

I am pretty sure hardware problems can be ruled out: it would be really more than amazing if the same hardware failure occurred on 4 different machines (in case they should all exhibit the problem) right after kernel updates had been applied. :wink:

Kind regards,
Karl
--
P.S.: Specifications of machine #1 (the second machine where EXT4-fs complained about orphaned inodes after each shutdown/reboot) - note: using the previous kernel 3.2.0-35 again
Code: Select all
inxi -Fx
System:    Host: mint13cn Kernel: 3.2.0-35-generic i686 (32 bit, gcc: 4.6.3) Desktop: Gnome Distro: Linux Mint 13 Maya
Machine:   System: Dell (portable) product: Latitude E6400
           Mobo: Dell model: 0W620R Bios: Dell version: A20 date: 12/21/2009
CPU:       Dual core Intel Core2 Duo CPU P8700 (-MCP-) cache: 3072 KB flags: (lm nx sse sse2 sse3 sse4_1 ssse3 vmx) bmips: 10109
           Clock Speeds: 1: 800.00 MHz 2: 800.00 MHz
Graphics:  Card: Intel Mobile 4 Series Chipset Integrated Graphics Controller bus-ID: 00:02.0
           X.Org: 1.11.3 drivers: intel (unloaded: fbdev,vesa) Resolution: 1680x1050@59.9hz
           GLX Renderer: Mesa DRI Mobile Intel® GM45 Express Chipset x86/MMX/SSE2 GLX Version: 2.1 Mesa 8.0.4 Direct Rendering: Yes
Audio:     Card: Intel 82801I (ICH9 Family) HD Audio Controller driver: snd_hda_intel bus-ID: 00:1b.0 Sound: ALSA ver: 1.0.24
Network:   Card-1: Intel WiFi Link 5100 driver: iwlwifi ver: in-tree: bus-ID: 0c:00.0
           IF: wlan0 state: down mac: 00:24:d6:9b:36:22
           Card-2: Intel 82567LM Gigabit Network Connection driver: e1000e ver: 1.5.1-k port: efe0 bus-ID: 00:19.0
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: 00:26:b9:c1:39:c2
Drives:    HDD Total Size: 250.1GB (24.8% used) 1: /dev/sda WDC_WD2500BJKT 250.1GB
Partition: ID: / size: 29G used: 5.4G (20%) fs: ext4
Sensors:   System Temperatures: cpu: 48.5C mobo: N/A
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 170 Uptime: 2:18 Memory: 555.0/3484.3MB Runlevel: 2 Gcc sys: 4.6.3 Client: Shell inxi: 1.7.33
User avatar
karlchen
Level 10
Level 10
 
Posts: 3405
Joined: Sat Dec 31, 2011 7:21 am

Re: Mint13-14 Latest Kernel Version Causing EXT4-fs Errors

Postby AlbertP on Mon Jan 21, 2013 7:44 am

Just to rule out hardware problems, could you go into Disk Utility (gnome-disk-utility in the repository) on these computers, click the disk controller above the harddisk containing the ext4 partition, and post the driver that it uses? (I suppose #1 is using the ahci driver on Intel 82801I/ICH9 SATA controller?)
Registered Linux User #528502
Image
Feel free to correct me if I'm trying to write in Spanish, French or German.
AlbertP
Level 16
Level 16
 
Posts: 6515
Joined: Sun Jan 30, 2011 12:38 pm
Location: The Netherlands

Re: Mint13-14 Latest Kernel Version Causing EXT4-fs Errors

Postby karlchen on Mon Jan 21, 2013 9:11 am

Hello, AlbertP.

Here is the palimpsest (disk utility) screenshot for the same machine for which the "inxi -Fx" output was posted.

Image
(palimpsest (disk utility) screenshot)

Interesting. The controller seems to be in RAID mode. I have never noticed it might be. I have never bothered to change any settings, because it is a company machine. And it has worked without any "EXT4-fs" error messages for the past 2.5 years, running Lucid Lynx in the past and Mint 13 for the past few months.

Kind regards,
Karl
Last edited by karlchen on Wed Jul 30, 2014 10:44 am, edited 1 time in total.
Reason: replaced local screenshot by screenshot uploaded to imgur.com
User avatar
karlchen
Level 10
Level 10
 
Posts: 3405
Joined: Sat Dec 31, 2011 7:21 am

Re: Mint13-14 Latest Kernel Version Causing EXT4-fs Errors

Postby AlbertP on Mon Jan 21, 2013 9:55 am

I don't think the RAID mode really matters (for Windows, it may require installing a driver for working correctly, but on Linux it should just be supported). Anyway you can try setting it to AHCI mode in the BIOS. I don't think that really makes a difference since it's already using the ahci driver. You could also try setting it to IDE mode to rule out driver issues completely. If both IDE and AHCI mode report the same ext4 errors, then it must be an ext4 problem.
Registered Linux User #528502
Image
Feel free to correct me if I'm trying to write in Spanish, French or German.
AlbertP
Level 16
Level 16
 
Posts: 6515
Joined: Sun Jan 30, 2011 12:38 pm
Location: The Netherlands

Re: Mint13-14 Latest Kernel Version Causing EXT4-fs Errors

Postby karlchen on Mon Jan 21, 2013 3:54 pm

Hello, folks.

Victim #2 has been identified: Linux Mint 13 x64 Cinnamon desktop :cry:

Ran on kernel 3.2.0-35 happily without producing any EXT4-fs errors.
On Jan 20th, 2013, 22:39 upgraded to kernel 3.2.0-36 which was used until shutdown. - Remember: the error is caused in the shutdown procedure somewhere.
Rebooted today: EXT4-fs errors.
Went back to kernel 3.2.0-35 rebooted twice: no more EXT4-fs errors.

Conclusion:
Kernel 3.2.0-36 does break something on Mint 13 x64 as well as on Mint 13 x86.

Pieces of evidence:
  • inxi -Fx report => see below
  • disk utility report (palimpest) => see attached file medionpc_palimpsest.png
  • Synaptic report on K3.2.0-36 installation and other updates => see below
  • EXT4-fs messages gathered from syslog, syslog.1 and syslog?.gz => see below
    Pay attention to the timestamps:
    Before K3.2.0-36 no EXT-fs errors. Back on K3.2.0-35 no more EXT-fs errors (Jan 21st, 2013, 20:09)

Next step:
Going to check genuine Ubuntu 12.04.1 x64 Unity desktop running K3.2.0.36 as well since Sunday evening ...

Kind regards,
Karl

Code: Select all
 $ inix -Fx
System:    Host: voyager Kernel: 3.2.0-36-generic x86_64 (64 bit, gcc: 4.6.3) Desktop: Gnome Distro: Linux Mint 13 Maya
Machine:   System: MEDIONPC product: MS-7358
           Mobo: MICRO-STAR model: MS-7358 version: Fab D Bios: Phoenix version: 6.00 PG date: 07/24/2007
CPU:       Quad core Intel Core2 Quad CPU (-MCP-) cache: 4096 KB flags: (lm nx sse sse2 sse3 ssse3 vmx) bmips: 19139.6
           Clock Speeds: 1: 1600.00 MHz 2: 1600.00 MHz 3: 1600.00 MHz 4: 1600.00 MHz
Graphics:  Card: NVIDIA G86 [GeForce 8500 GT] bus-ID: 01:00.0
           X.Org: 1.11.3 drivers: nvidia (unloaded: nouveau,vesa,fbdev) Resolution: 1280x1024@51.0hz
           GLX Renderer: GeForce 8500 GT/PCIe/SSE2 GLX Version: 3.3.0 NVIDIA 295.40 Direct Rendering: Yes
Audio:     Card: Intel 82801I (ICH9 Family) HD Audio Controller driver: snd_hda_intel bus-ID: 00:1b.0 Sound: ALSA ver: 1.0.24
Network:   Card: Realtek RTL-8169 Gigabit Ethernet driver: r8169 ver: 2.3LK-NAPI port: ac00 bus-ID: 04:00.0
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: 00:0a:cd:1d:12:51
Drives:    HDD Total Size: 500.1GB (1.3% used) 1: /dev/sda ST3500830AS 500.1GB 24C
Partition: ID: / size: 46G used: 6.0G (14%) fs: ext4 ID: swap-1 size: 8.22GB used: 0.00GB (0%) fs: swap
Sensors:   System Temperatures: cpu: 21.8C mobo: N/A gpu: 0.0:42C
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 180 Uptime: 6 min Memory: 413.0/3261.8MB Runlevel: 2 Gcc sys: 4.6.3 Client: Shell inxi: 1.7.33


Code: Select all
Commit Log for Sun Jan 20 22:39:52 2013


Die folgenden Pakete wurden aktualisiert:
bamfdaemon (0.2.118-0ubuntu0.3) to 0.2.124.2-0ubuntu1
duplicity (0.6.18-0ubuntu3) to 0.6.18-0ubuntu3.1
firefox (18.0+build1-0ubuntu0.12.04.3) to 18.0.1+build1-0ubuntu0.12.04.1
firefox-gnome-support (18.0+build1-0ubuntu0.12.04.3) to 18.0.1+build1-0ubuntu0.12.04.1
firefox-locale-de (18.0+build1-0ubuntu0.12.04.3) to 18.0.1+build1-0ubuntu0.12.04.1
firefox-locale-en (18.0+build1-0ubuntu0.12.04.3) to 18.0.1+build1-0ubuntu0.12.04.1
icedtea-7-jre-jamvm (7u9-2.3.3-0ubuntu1~12.04.1) to 7u9-2.3.4-0ubuntu1.12.04.1
libbamf0 (0.2.118-0ubuntu0.3) to 0.2.124.2-0ubuntu1
libbamf3-0 (0.2.118-0ubuntu0.3) to 0.2.124.2-0ubuntu1
libpulse-mainloop-glib0 (1:1.1-0ubuntu15.1) to 1:1.1-0ubuntu15.2
libpulse0 (1:1.1-0ubuntu15.1) to 1:1.1-0ubuntu15.2
libpulsedsp (1:1.1-0ubuntu15.1) to 1:1.1-0ubuntu15.2
linux-generic (3.2.0.35.40) to 3.2.0.36.43
linux-headers-generic (3.2.0.35.40) to 3.2.0.36.43
linux-image-generic (3.2.0.35.40) to 3.2.0.36.43
linux-libc-dev (3.2.0-35.55) to 3.2.0-36.57
mplayer2 (2.0-426-gc32b3ed-2) to 2.0-426-gc32b3ed-2ubuntu0.1
nvidia-current (295.40-0ubuntu1.1) to 295.40-0ubuntu1.2
openjdk-7-jre (7u9-2.3.3-0ubuntu1~12.04.1) to 7u9-2.3.4-0ubuntu1.12.04.1
openjdk-7-jre-headless (7u9-2.3.3-0ubuntu1~12.04.1) to 7u9-2.3.4-0ubuntu1.12.04.1
openjdk-7-jre-lib (7u9-2.3.3-0ubuntu1~12.04.1) to 7u9-2.3.4-0ubuntu1.12.04.1
pulseaudio (1:1.1-0ubuntu15.1) to 1:1.1-0ubuntu15.2
pulseaudio-module-bluetooth (1:1.1-0ubuntu15.1) to 1:1.1-0ubuntu15.2
pulseaudio-module-gconf (1:1.1-0ubuntu15.1) to 1:1.1-0ubuntu15.2
pulseaudio-module-x11 (1:1.1-0ubuntu15.1) to 1:1.1-0ubuntu15.2
pulseaudio-utils (1:1.1-0ubuntu15.1) to 1:1.1-0ubuntu15.2
x11-common (1:7.6+12ubuntu1) to 1:7.6+12ubuntu2
xorg (1:7.6+12ubuntu1) to 1:7.6+12ubuntu2
xserver-xorg (1:7.6+12ubuntu1) to 1:7.6+12ubuntu2
xserver-xorg-input-all (1:7.6+12ubuntu1) to 1:7.6+12ubuntu2
xserver-xorg-video-all (1:7.6+12ubuntu1) to 1:7.6+12ubuntu2

Die folgenden Pakete wurden installiert:
linux-headers-3.2.0-36 (3.2.0-36.57)
linux-headers-3.2.0-36-generic (3.2.0-36.57)
linux-image-3.2.0-36-generic (3.2.0-36.57)


Code: Select all
syslog:Jan 21 20:09:17 voyager kernel: [    2.508347] EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null)
syslog:Jan 21 20:09:17 voyager kernel: [   23.592497] EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro
syslog:Jan 21 20:17:39 voyager kernel: [    2.534190] EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null)
syslog:Jan 21 20:17:39 voyager kernel: [   32.627470] EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro
syslog.1:Jan 20 22:21:23 voyager kernel: [    2.624769] EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null)
syslog.1:Jan 20 22:21:23 voyager kernel: [    5.567437] EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro
syslog.1:Jan 20 22:52:15 voyager kernel: [    2.177807] EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null)
syslog.1:Jan 20 22:52:15 voyager kernel: [    4.940784] EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro
syslog.1:Jan 21 19:56:23 voyager kernel: [    2.272857] EXT4-fs (sda6): orphan cleanup on readonly fs
syslog.1:Jan 21 19:56:23 voyager kernel: [    2.296558] EXT4-fs (sda6): ext4_orphan_cleanup: deleting unreferenced inode 788125
syslog.1:Jan 21 19:56:23 voyager kernel: [    2.296811] EXT4-fs (sda6): ext4_orphan_cleanup: deleting unreferenced inode 788067
syslog.1:Jan 21 19:56:23 voyager kernel: [    2.296821] EXT4-fs (sda6): ext4_orphan_cleanup: deleting unreferenced inode 788086
syslog.1:Jan 21 19:56:23 voyager kernel: [    2.315483] EXT4-fs (sda6): ext4_orphan_cleanup: deleting unreferenced inode 2097279
syslog.1:Jan 21 19:56:23 voyager kernel: [    2.315515] EXT4-fs (sda6): ext4_orphan_cleanup: deleting unreferenced inode 2097206
syslog.1:Jan 21 19:56:23 voyager kernel: [    2.318404] EXT4-fs (sda6): 5 orphan inodes deleted
syslog.1:Jan 21 19:56:23 voyager kernel: [    2.318408] EXT4-fs (sda6): recovery complete
syslog.1:Jan 21 19:56:23 voyager kernel: [    2.384430] EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null)
syslog.1:Jan 21 19:56:23 voyager kernel: [   23.202769] EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro
syslog.2.gz:Jan 15 22:38:04 voyager kernel: [    2.289464] EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null)
syslog.2.gz:Jan 15 22:38:04 voyager kernel: [   20.907563] EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro
syslog.3.gz:Jan 11 22:40:27 voyager kernel: [    2.130815] EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null)
syslog.3.gz:Jan 11 22:40:27 voyager kernel: [   21.198861] EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro
syslog.4.gz:Jan  6 19:13:50 voyager kernel: [    2.212788] EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null)
syslog.4.gz:Jan  6 19:13:50 voyager kernel: [    4.682006] EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro
syslog.4.gz:Jan  9 23:20:15 voyager kernel: [    2.367225] EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null)
syslog.4.gz:Jan  9 23:20:15 voyager kernel: [   20.860619] EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro
syslog.5.gz:Jan  6 18:05:17 voyager kernel: [    2.235916] EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null)
syslog.5.gz:Jan  6 18:05:17 voyager kernel: [   21.155108] EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro
syslog.6.gz:Jan  1 08:38:40 voyager kernel: [    2.195105] EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null)
syslog.6.gz:Jan  1 08:38:40 voyager kernel: [   21.149198] EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro
syslog.7.gz:Dec 29 19:35:49 voyager kernel: [    2.078922] EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null)
syslog.7.gz:Dec 29 19:35:49 voyager kernel: [   21.117084] EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro


Image
(Medion PC Mint 13 x64 disk utility report)
User avatar
karlchen
Level 10
Level 10
 
Posts: 3405
Joined: Sat Dec 31, 2011 7:21 am

Re: Mint13-14 Latest Kernel Version Causing EXT4-fs Errors

Postby AlbertP on Mon Jan 21, 2013 4:14 pm

What bothers me is that searching on "3.2.0-36 ext4" returns nothing on Launchpad bugs, and that both of the systems use an Intel ICH9 SATA controller with ahci. If you're sure that the problem happens too when one of these systems is set to IDE mode (instead of AHCI or RAID) in the BIOS, then it would certainly be worth filing a bug about ext4.

Here you can file a bug against Ubuntu's Linux kernel: https://bugs.launchpad.net/ubuntu/+sour ... x/+filebug
Registered Linux User #528502
Image
Feel free to correct me if I'm trying to write in Spanish, French or German.
AlbertP
Level 16
Level 16
 
Posts: 6515
Joined: Sun Jan 30, 2011 12:38 pm
Location: The Netherlands

Re: Mint13-14 Latest Kernel Version Causing EXT4-fs Errors

Postby karlchen on Mon Jan 21, 2013 8:21 pm

Good night, AlbertP.

Thanks for your advice. May I ask which downside or simply which consuequences I will face when reconfiguring the controller inside the BIOS from AHCI mode to IDE mode?

I do ask this question, because the first machine which I reported about is a company notebook, Dell Latitude E6400. It primary OS is Windows 7 SP1 32-bit. This one runs fine. No trouble. As it is a company machine, I never dared repartitioning it. So the first Linux installation which ran fine for 2.5 years was Ubuntu 10.04 (upgraded till 10.04.4) 32-bit, installed through Wubi. The current Linux installation is Linux Mint 13, 32-bit, installed through Mint4win. And it ran without any filesystem problems until kernel 3.2.0-35.
I am a bit loathe to tinker with the BIOS setup of my office machine.

The second machine which I reported about is my home desktop machine, Medion PC.
Since June 2012, it has been setup as a triple boot system:
+ first OS Windows 7 Home Premium SP1, x64.
+ second OS Ubuntu 10.04.1 x64, Unity desktop
+ third OS Linux Mint 13 x64, Cinnamon desktop
All three OSes have been running fine without causing any filesystem problems, running in AHCI mode.
In particular both Linux editions have not experienced any filesystem problems, in particular like the ones I am seeing now, until kernel 3.2.0-35.
So again I am a bit uncomfortable with changing this mode to IDE without really knowing whether this might break something.

So any hint as to what re-setting the disk from AHCI to IDE mode might mean to the existing systems would be appreciated.

Kind regards,
Karl
User avatar
karlchen
Level 10
Level 10
 
Posts: 3405
Joined: Sat Dec 31, 2011 7:21 am

Re: Mint13-14 Latest Kernel Version Causing EXT4-fs Errors

Postby karlchen on Mon Jan 21, 2013 8:45 pm

Hi, folks.

As anybody reading the posts in here carefully may have suspected when I wrote in my previous post, "In particular both Linux editions have not experienced any filesystem problems, in particular like the ones I am seeing now, until kernel 3.2.0-35", the reported EXT4-fs errors are reporiducible on genuine Ubuntu 12.04.1 x64, Unity desktop, as well. - The desktop edition will be irrelevant.

In short words, on the second machine which I reported about, on /dev/sda5, there is Ubuntu 12.04.1 x64 - Linux Mint 13 x64 is on /dev/sda6.

Sunday at 21:03 kernel 3.2.0-35 was updated to 3.2.0-36. In contrast to the Linux Mint system on the same machine, Ubuntu 12.04.1 survived 2 or 3 reboots runnng on K3.2.0-36 before finally the EXT4-fs error messages started occurring. Yet, once the problem had started it would not go away until after I had reverted to K3.2.0-35 and rebooted twice.
(Remember: the orphaned inodes seem to be left behind during shutdown. So after first rebooting to K3.2.0-35, you will see the EXT-fs error messages caused before this reboot. It is only after the second reboot to K3.2.0-35 that you can hope the errors will not re-occur. And I rebooted several times. Be assured.)

Reproducing the problem on genuine Ubuntu 12.04.1 is important. It suggests that the root cause is not inside Linux Mint. This in turn is important because it will allow me to file a bug report against Ubuntu without even mentioning the term "Mint", because as soon as they read this term, they are likely to turn down the bug report, as if they were unaware of the fact that Linux Mint is 95% Ubuntu plus a different user interface.

Kind regards,
Karl
--
P.S.:
Just for the files and for completeness' sake, here are the results for the Ubuntu 12.04.1 x64 system on the MedionPC:

inxi -Fx Report
Code: Select all
System:    Host: Voyager Kernel: 3.2.0-36-generic x86_64 (64 bit, gcc: 4.6.3) Desktop: Gnome Distro: Ubuntu 12.04 precise
Machine:   System: MEDIONPC product: MS-7358
           Mobo: MICRO-STAR model: MS-7358 version: Fab D Bios: Phoenix version: 6.00 PG date: 07/24/2007
CPU:       Quad core Intel Core2 Quad CPU (-MCP-) cache: 4096 KB flags: (lm nx sse sse2 sse3 ssse3 vmx) bmips: 19140.2
           Clock Speeds: 1: 1600.00 MHz 2: 1600.00 MHz 3: 1600.00 MHz 4: 1600.00 MHz
Graphics:  Card: NVIDIA G86 [GeForce 8500 GT] bus-ID: 01:00.0
           X.Org: 1.11.3 drivers: nvidia (unloaded: nouveau,vesa,fbdev) Resolution: 1280x1024@51.0hz
           GLX Renderer: GeForce 8500 GT/PCIe/SSE2 GLX Version: 3.3.0 NVIDIA 295.40 Direct Rendering: Yes
Audio:     Card: Intel 82801I (ICH9 Family) HD Audio Controller driver: snd_hda_intel bus-ID: 00:1b.0 Sound: ALSA ver: 1.0.24
Network:   Card: Realtek RTL-8169 Gigabit Ethernet driver: r8169 ver: 2.3LK-NAPI port: ac00 bus-ID: 04:00.0
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: 00:0a:cd:1d:12:51
Drives:    HDD Total Size: 507.9GB (2.1% used) 1: id: /dev/sda model: ST3500830AS size: 500.1GB
           2: USB id: /dev/sde model: Premium size: 7.8GB
Partition: ID: / size: 46G used: 7.0G (17%) fs: ext4 ID: swap-1 size: 1.71GB used: 0.00GB (0%) fs: swap
           ID: swap-2 size: 8.22GB used: 0.00GB (0%) fs: swap
RAID:      No RAID devices detected - /proc/mdstat and md_mod kernel raid module present
Sensors:   System Temperatures: cpu: 21.8C mobo: N/A gpu: 0.0:47C
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 184 Uptime: 7 min Memory: 600.0/3261.8MB Runlevel: 2 Gcc sys: 4.6.3 Client: Shell inxi: 1.8.4


Software Update on Sunday inclduing K3.2.0-36:
Code: Select all
Start-Date: 2013-01-20  21:01:57
Commandline: aptdaemon role='role-commit-packages' sender=':1.75'
Install: linux-headers-3.2.0-36:amd64 (3.2.0-36.57), linux-image-3.2.0-36-generic:amd64 (3.2.0-36.57), linux-headers-3.2.0-36-generic:amd64 (3.2.0-36.57)
Upgrade: openjdk-7-jre:amd64 (7u9-2.3.3-0ubuntu1~12.04.1, 7u9-2.3.4-0ubuntu1.12.04.1), linux-generic:amd64 (3.2.0.35.40, 3.2.0.36.43), firefox-globalmenu:amd64 (18.0+build1-0ubuntu0.12.04.3, 18.0.1+build1-0ubuntu0.12.04.1), duplicity:amd64 (0.6.18-0ubuntu3, 0.6.18-0ubuntu3.1), firefox:amd64 (18.0+build1-0ubuntu0.12.04.3, 18.0.1+build1-0ubuntu0.12.04.1), linux-headers-generic:amd64 (3.2.0.35.40, 3.2.0.36.43), linux-image-generic:amd64 (3.2.0.35.40, 3.2.0.36.43), firefox-locale-de:amd64 (18.0+build1-0ubuntu0.12.04.3, 18.0.1+build1-0ubuntu0.12.04.1), firefox-locale-en:amd64 (18.0+build1-0ubuntu0.12.04.3, 18.0.1+build1-0ubuntu0.12.04.1), icedtea-7-jre-jamvm:amd64 (7u9-2.3.3-0ubuntu1~12.04.1, 7u9-2.3.4-0ubuntu1.12.04.1), openjdk-7-jre-lib:amd64 (7u9-2.3.3-0ubuntu1~12.04.1, 7u9-2.3.4-0ubuntu1.12.04.1), linux-libc-dev:amd64 (3.2.0-35.55, 3.2.0-36.57), firefox-gnome-support:amd64 (18.0+build1-0ubuntu0.12.04.3, 18.0.1+build1-0ubuntu0.12.04.1), openjdk-7-jre-headless:amd64 (7u9-2.3.3-0ubuntu1~12.04.1, 7u9-2.3.4-0ubuntu1.12.04.1)
End-Date: 2013-01-20  21:03:46

Log started: 2013-01-20  21:01:57
Selecting previously unselected package linux-image-3.2.0-36-generic.
(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 233526 files and directories currently installed.)
Unpacking linux-image-3.2.0-36-generic (from .../linux-image-3.2.0-36-generic_3.2.0-36.57_amd64.deb) ...
Done.
Preparing to replace openjdk-7-jre 7u9-2.3.3-0ubuntu1~12.04.1 (using .../openjdk-7-jre_7u9-2.3.4-0ubuntu1.12.04.1_amd64.deb) ...
Unpacking replacement openjdk-7-jre ...
Preparing to replace icedtea-7-jre-jamvm 7u9-2.3.3-0ubuntu1~12.04.1 (using .../icedtea-7-jre-jamvm_7u9-2.3.4-0ubuntu1.12.04.1_amd64.deb) ...
Unpacking replacement icedtea-7-jre-jamvm ...
Preparing to replace openjdk-7-jre-headless 7u9-2.3.3-0ubuntu1~12.04.1 (using .../openjdk-7-jre-headless_7u9-2.3.4-0ubuntu1.12.04.1_amd64.deb) ...
Unpacking replacement openjdk-7-jre-headless ...
Preparing to replace openjdk-7-jre-lib 7u9-2.3.3-0ubuntu1~12.04.1 (using .../openjdk-7-jre-lib_7u9-2.3.4-0ubuntu1.12.04.1_all.deb) ...
Unpacking replacement openjdk-7-jre-lib ...
Preparing to replace duplicity 0.6.18-0ubuntu3 (using .../duplicity_0.6.18-0ubuntu3.1_amd64.deb) ...
Unpacking replacement duplicity ...
Preparing to replace firefox-globalmenu 18.0+build1-0ubuntu0.12.04.3 (using .../firefox-globalmenu_18.0.1+build1-0ubuntu0.12.04.1_amd64.deb) ...
Unpacking replacement firefox-globalmenu ...
Preparing to replace firefox 18.0+build1-0ubuntu0.12.04.3 (using .../firefox_18.0.1+build1-0ubuntu0.12.04.1_amd64.deb) ...
Unpacking replacement firefox ...
Preparing to replace firefox-gnome-support 18.0+build1-0ubuntu0.12.04.3 (using .../firefox-gnome-support_18.0.1+build1-0ubuntu0.12.04.1_amd64.deb) ...
Unpacking replacement firefox-gnome-support ...
Preparing to replace firefox-locale-de 18.0+build1-0ubuntu0.12.04.3 (using .../firefox-locale-de_18.0.1+build1-0ubuntu0.12.04.1_amd64.deb) ...
Unpacking replacement firefox-locale-de ...
Preparing to replace firefox-locale-en 18.0+build1-0ubuntu0.12.04.3 (using .../firefox-locale-en_18.0.1+build1-0ubuntu0.12.04.1_amd64.deb) ...
Unpacking replacement firefox-locale-en ...
Preparing to replace linux-generic 3.2.0.35.40 (using .../linux-generic_3.2.0.36.43_amd64.deb) ...
Unpacking replacement linux-generic ...
Preparing to replace linux-image-generic 3.2.0.35.40 (using .../linux-image-generic_3.2.0.36.43_amd64.deb) ...
Unpacking replacement linux-image-generic ...
Selecting previously unselected package linux-headers-3.2.0-36.
Unpacking linux-headers-3.2.0-36 (from .../linux-headers-3.2.0-36_3.2.0-36.57_all.deb) ...
Selecting previously unselected package linux-headers-3.2.0-36-generic.
Unpacking linux-headers-3.2.0-36-generic (from .../linux-headers-3.2.0-36-generic_3.2.0-36.57_amd64.deb) ...
Preparing to replace linux-headers-generic 3.2.0.35.40 (using .../linux-headers-generic_3.2.0.36.43_amd64.deb) ...
Unpacking replacement linux-headers-generic ...
Preparing to replace linux-libc-dev 3.2.0-35.55 (using .../linux-libc-dev_3.2.0-36.57_amd64.deb) ...
Unpacking replacement linux-libc-dev ...
Processing triggers for bamfdaemon ...
Rebuilding /usr/share/applications/bamf.index...
Processing triggers for desktop-file-utils ...
Processing triggers for gnome-menus ...
Processing triggers for hicolor-icon-theme ...
Processing triggers for man-db ...
Setting up linux-image-3.2.0-36-generic (3.2.0-36.57) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/dkms 3.2.0-36-generic /boot/vmlinuz-3.2.0-36-generic
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.2.0-36-generic /boot/vmlinuz-3.2.0-36-generic
update-initramfs: Generating /boot/initrd.img-3.2.0-36-generic
Warning: No support for locale: de_DE.utf8
run-parts: executing /etc/kernel/postinst.d/pm-utils 3.2.0-36-generic /boot/vmlinuz-3.2.0-36-generic
run-parts: executing /etc/kernel/postinst.d/update-notifier 3.2.0-36-generic /boot/vmlinuz-3.2.0-36-generic
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.2.0-36-generic /boot/vmlinuz-3.2.0-36-generic
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-3.2.0-36-generic
Found initrd image: /boot/initrd.img-3.2.0-36-generic
Found linux image: /boot/vmlinuz-3.2.0-35-generic
Found initrd image: /boot/initrd.img-3.2.0-35-generic
Found linux image: /boot/vmlinuz-3.2.0-34-generic
Found initrd image: /boot/initrd.img-3.2.0-34-generic
Found memtest86+ image: /boot/memtest86+.bin
Found Windows 7 (loader) on /dev/sda1
Found Linux Mint 13 Maya (13) on /dev/sda6
done
Setting up duplicity (0.6.18-0ubuntu3.1) ...
Setting up firefox (18.0.1+build1-0ubuntu0.12.04.1) ...
Please restart all running instances of firefox, or you will experience problems.
Setting up firefox-globalmenu (18.0.1+build1-0ubuntu0.12.04.1) ...
Setting up firefox-gnome-support (18.0.1+build1-0ubuntu0.12.04.1) ...
Setting up firefox-locale-de (18.0.1+build1-0ubuntu0.12.04.1) ...
Setting up firefox-locale-en (18.0.1+build1-0ubuntu0.12.04.1) ...
Setting up linux-image-generic (3.2.0.36.43) ...
Setting up linux-headers-3.2.0-36 (3.2.0-36.57) ...
Setting up linux-headers-3.2.0-36-generic (3.2.0-36.57) ...
Examining /etc/kernel/header_postinst.d.
run-parts: executing /etc/kernel/header_postinst.d/dkms 3.2.0-36-generic /boot/vmlinuz-3.2.0-36-generic
Setting up linux-headers-generic (3.2.0.36.43) ...
Setting up linux-generic (3.2.0.36.43) ...
Setting up linux-libc-dev (3.2.0-36.57) ...
Setting up openjdk-7-jre-headless (7u9-2.3.4-0ubuntu1.12.04.1) ...
update-binfmts: warning: current package is openjdk-7, but binary format already installed by openjdk-6
Setting up openjdk-7-jre-lib (7u9-2.3.4-0ubuntu1.12.04.1) ...
Setting up openjdk-7-jre (7u9-2.3.4-0ubuntu1.12.04.1) ...
Setting up icedtea-7-jre-jamvm (7u9-2.3.4-0ubuntu1.12.04.1) ...
Log ended: 2013-01-20  21:03:46


EXT4-fs error messages generated while system ran and shutdown on K3.2.0-36
Code: Select all
syslog:Jan 22 00:44:37 Voyager kernel: [    3.624421] EXT4-fs (sda5): orphan cleanup on readonly fs
syslog:Jan 22 00:44:37 Voyager kernel: [    3.652470] EXT4-fs (sda5): ext4_orphan_cleanup: deleting unreferenced inode 2886456
syslog:Jan 22 00:44:37 Voyager kernel: [    3.652671] EXT4-fs (sda5): ext4_orphan_cleanup: deleting unreferenced inode 2886232
syslog:Jan 22 00:44:37 Voyager kernel: [    3.652688] EXT4-fs (sda5): ext4_orphan_cleanup: deleting unreferenced inode 2886450
syslog:Jan 22 00:44:37 Voyager kernel: [    3.678434] EXT4-fs (sda5): ext4_orphan_cleanup: deleting unreferenced inode 2369342
syslog:Jan 22 00:44:37 Voyager kernel: [    3.689458] EXT4-fs (sda5): 4 orphan inodes deleted
syslog:Jan 22 00:44:37 Voyager kernel: [    3.689462] EXT4-fs (sda5): recovery complete
syslog:Jan 22 00:44:37 Voyager kernel: [    3.708197] EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: (null)
syslog:Jan 22 00:44:37 Voyager kernel: [    6.752703] EXT4-fs (sda5): re-mounted. Opts: errors=remount-ro
syslog:Jan 22 00:48:12 Voyager kernel: [    4.194614] EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: (null)
syslog:Jan 22 00:48:12 Voyager kernel: [   32.989547] EXT4-fs (sda5): re-mounted. Opts: errors=remount-ro
syslog:Jan 22 00:51:08 Voyager kernel: [    4.156948] EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: (null)
syslog:Jan 22 00:51:08 Voyager kernel: [   21.778191] EXT4-fs (sda5): re-mounted. Opts: errors=remount-ro
syslog.1:Jan 22 00:28:31 Voyager kernel: [    3.701504] EXT4-fs (sda5): orphan cleanup on readonly fs
syslog.1:Jan 22 00:28:31 Voyager kernel: [    3.725273] EXT4-fs (sda5): ext4_orphan_cleanup: deleting unreferenced inode 2362508
syslog.1:Jan 22 00:28:31 Voyager kernel: [    3.744737] EXT4-fs (sda5): ext4_orphan_cleanup: deleting unreferenced inode 2363098
syslog.1:Jan 22 00:28:31 Voyager kernel: [    3.744773] EXT4-fs (sda5): ext4_orphan_cleanup: deleting unreferenced inode 2362442
syslog.1:Jan 22 00:28:31 Voyager kernel: [    3.744794] EXT4-fs (sda5): 3 orphan inodes deleted
syslog.1:Jan 22 00:28:31 Voyager kernel: [    3.744798] EXT4-fs (sda5): recovery complete
syslog.1:Jan 22 00:28:31 Voyager kernel: [    3.776762] EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: (null)
syslog.1:Jan 22 00:28:31 Voyager kernel: [   21.199860] EXT4-fs (sda5): re-mounted. Opts: errors=remount-ro
syslog.1:Jan 22 00:34:38 Voyager kernel: [    3.427624] EXT4-fs (sda5): orphan cleanup on readonly fs
syslog.1:Jan 22 00:34:38 Voyager kernel: [    3.455737] EXT4-fs (sda5): ext4_orphan_cleanup: deleting unreferenced inode 2886451
syslog.1:Jan 22 00:34:38 Voyager kernel: [    3.455951] EXT4-fs (sda5): ext4_orphan_cleanup: deleting unreferenced inode 2886450
syslog.1:Jan 22 00:34:38 Voyager kernel: [    3.467807] EXT4-fs (sda5): ext4_orphan_cleanup: deleting unreferenced inode 2885630
syslog.1:Jan 22 00:34:38 Voyager kernel: [    3.467834] EXT4-fs (sda5): 3 orphan inodes deleted
syslog.1:Jan 22 00:34:38 Voyager kernel: [    3.467838] EXT4-fs (sda5): recovery complete
syslog.1:Jan 22 00:34:38 Voyager kernel: [    3.486068] EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: (null)
syslog.1:Jan 22 00:34:38 Voyager kernel: [   20.759245] EXT4-fs (sda5): re-mounted. Opts: errors=remount-ro
syslog.2.gz:Jan 20 21:05:53 Voyager kernel: [    3.694806] EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: (null)
syslog.2.gz:Jan 20 21:05:53 Voyager kernel: [   20.866037] EXT4-fs (sda5): re-mounted. Opts: errors=remount-ro
syslog.2.gz:Jan 21 21:09:06 Voyager kernel: [    3.613566] EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: (null)
syslog.2.gz:Jan 21 21:09:06 Voyager kernel: [   20.852854] EXT4-fs (sda5): re-mounted. Opts: errors=remount-ro
syslog.3.gz:Jan 16 22:39:03 Voyager kernel: [    4.027950] EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: (null)
syslog.3.gz:Jan 16 22:39:03 Voyager kernel: [    6.569392] EXT4-fs (sda5): re-mounted. Opts: errors=remount-ro
syslog.3.gz:Jan 20 20:36:04 Voyager kernel: [    4.150686] EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: (null)
syslog.3.gz:Jan 20 20:36:04 Voyager kernel: [   21.240137] EXT4-fs (sda5): re-mounted. Opts: errors=remount-ro
syslog.4.gz:Jan 16 22:20:13 Voyager kernel: [    3.948676] EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: (null)
syslog.4.gz:Jan 16 22:20:13 Voyager kernel: [    6.438198] EXT4-fs (sda5): re-mounted. Opts: errors=remount-ro
syslog.5.gz:Jan 11 20:05:50 Voyager kernel: [    3.850345] EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: (null)
syslog.5.gz:Jan 11 20:05:50 Voyager kernel: [   21.273220] EXT4-fs (sda5): re-mounted. Opts: errors=remount-ro
syslog.6.gz:Jan  9 21:14:59 Voyager kernel: [    4.079487] EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: (null)
syslog.6.gz:Jan  9 21:14:59 Voyager kernel: [   21.201281] EXT4-fs (sda5): re-mounted. Opts: errors=remount-ro
syslog.7.gz:Jan  4 00:11:27 Voyager kernel: [    3.721318] EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: (null)
syslog.7.gz:Jan  4 00:11:27 Voyager kernel: [    7.231616] EXT4-fs (sda5): re-mounted. Opts: errors=remount-ro
K3.2.0-35 took back over before 00:44 (Jan 22nd), repaired and was rebooted several times. So far the errors have not re-occured.

Disk Utility (palimpsest) Details:

The controller mode can be got from this screenshot a few posts above, same result for Mint13 and Ubuntu 12.04.1 of course.
So here is the disk layout, just in case it may be relevant.

Image
(Medion PC Disk Utility - Disk Partitions)
Last edited by karlchen on Wed Jul 30, 2014 10:48 am, edited 1 time in total.
Reason: replaced local screenshot by screenshot uploaded to imgur.com
User avatar
karlchen
Level 10
Level 10
 
Posts: 3405
Joined: Sat Dec 31, 2011 7:21 am

Re: Mint13-14 Latest Kernel Version Causing EXT4-fs Errors

Postby heavy metal on Tue Jan 22, 2013 2:58 am

Read this post, maybe it can provide some insight in what's happening with EXT4: http://manjaro.org/2012/10/31/the-ext4-corruption-bug-is-fixed/

See this video, maybe it can help you out!: http://www.youtube.com/watch?v=n4YPfyZu7Go
Linux Mint Debian Edition MATE DE 64-bit
Gigabyte G41M-ES2L--->2gb ram
Intel Pentium Dual Core 2.60ghz-->E5300
WD-6400AAKS-Caviar-SE16-640gb
Proud user of LMDE
User avatar
heavy metal
Level 2
Level 2
 
Posts: 90
Joined: Mon Jan 25, 2010 11:00 pm
Location: Puerto Rico

Re: Mint13-14 Latest Kernel Version Causing EXT4-fs Errors

Postby karlchen on Tue Jan 22, 2013 9:14 am

Hello, heavy metal.

Thanks for putting me on the right track: EXT4 Data Corruption Bug Hits Stable Linux Kernels.
So by the end of last year it seems to have been a know fact that a bug affected kernel editons 3.4, 3.5 and 3.6.

This might explain why the first of my systems to exhibit this problem was Linux Mint 14 x86, running kernel 3.5.0-22.
Judging from the symptoms, one might conclude that one way or other, someone has managed to backport the fault to kernel edition 3.2.0 and that it arrived there in version 3.2.0-36.
(This is just a hypothesis and not a fact, because I do not use the mount options that were needed to trigger the bug which was talked about in October 2012.)

So currently the most reliable workaround seems to be sticking with K3.2.0-35 wherever possible. - An alternative might be making a big leap forward and give kernel edition 3.7 a try. Yet, not without making sure it handles EXT4 filesystems properly.

By the way, somehow the quality of the linked tutorial video got worse after the "fsck" commands to the extent that I could not read the e2<something> commands at all. But never mind. As long as K3.2.0-35 works correctly, I assume I will file a bug report soon and wait for further kernel updates ...

Kind regards,
Karl
User avatar
karlchen
Level 10
Level 10
 
Posts: 3405
Joined: Sat Dec 31, 2011 7:21 am

Re: Mint13-14 Latest Kernel Version Causing EXT4-fs Errors

Postby viking777 on Tue Jan 22, 2013 1:44 pm

Hi karlchen, I thought you might be pleased to see this:

Code: Select all
Jan 22 18:44:21 fujitsu kernel: [    2.865532] EXT4-fs (sda2): orphan cleanup on readonly fs
Jan 22 18:44:21 fujitsu kernel: [    2.866295] EXT4-fs (sda2): ext4_orphan_cleanup: deleting unreferenced inode 1310686
Jan 22 18:44:21 fujitsu kernel: [    2.866328] EXT4-fs (sda2): ext4_orphan_cleanup: deleting unreferenced inode 1310684
Jan 22 18:44:21 fujitsu kernel: [    2.866332] EXT4-fs (sda2): ext4_orphan_cleanup: deleting unreferenced inode 1310685
Jan 22 18:44:21 fujitsu kernel: [    2.866339] EXT4-fs (sda2): ext4_orphan_cleanup: deleting unreferenced inode 57
Jan 22 18:44:21 fujitsu kernel: [    2.866361] EXT4-fs (sda2): ext4_orphan_cleanup: deleting unreferenced inode 30
Jan 22 18:44:21 fujitsu kernel: [    2.866368] EXT4-fs (sda2): ext4_orphan_cleanup: deleting unreferenced inode 262369
Jan 22 18:44:21 fujitsu kernel: [    2.866388] EXT4-fs (sda2): 6 orphan inodes deleted


Just came up on my last reboot. No idea why though, or why I haven't seen it before.

Ubuntu 12.10 kernel 3.5.0-22 64bit.
Fujitsu Lifebook AH532. Intel i5 processor, 6Gb ram, Intel HD3000 graphics, Intel Audio/wifi. Realtek RTL8111/8168B Ethernet.Lubuntu 13.10,Ubuntu12.10 (Unity), Mint16 (Cinnamon), Manjaro (Xfce).
Image
User avatar
viking777
Level 14
Level 14
 
Posts: 5153
Joined: Mon Dec 01, 2008 11:21 am

Re: Mint13-14 Latest Kernel Version Causing EXT4-fs Errors

Postby AlbertP on Wed Jan 23, 2013 4:09 am

This ext4 data corruption bug has never been in Ubuntu's kernels. It was fixed long before Ubuntu 12.04 with its 3.5 kernel got released.

About IDE mode, this could slow down disk transfers a bit - but you can revert it to AHCI any time you want. No need to change anything in software (windows/linux). It may or may not help but I think it's worth trying.
Registered Linux User #528502
Image
Feel free to correct me if I'm trying to write in Spanish, French or German.
AlbertP
Level 16
Level 16
 
Posts: 6515
Joined: Sun Jan 30, 2011 12:38 pm
Location: The Netherlands

Re: Mint13-14 Latest Kernel Version Causing EXT4-fs Errors

Postby heavy metal on Wed Jan 23, 2013 8:16 am

I have exchanged EXT4 for XFS Filesystem since Lucid Linx and have stayed with XFS now in LinuxMint, working very fine, no problems @ all! 8)

If you want to give XFS a try you have to partition your disc as follows and in same order:

BOOT: EXT3 (500 MB is enough).
ROOT: XFS (Choose your size).
SWAP: (2000 MB is enough) (Some people doesn't like to add a swap partition since they have more than 4 GB of Ram, but I do just in case).
HOME: XFS (Rest of the disk space).
Linux Mint Debian Edition MATE DE 64-bit
Gigabyte G41M-ES2L--->2gb ram
Intel Pentium Dual Core 2.60ghz-->E5300
WD-6400AAKS-Caviar-SE16-640gb
Proud user of LMDE
User avatar
heavy metal
Level 2
Level 2
 
Posts: 90
Joined: Mon Jan 25, 2010 11:00 pm
Location: Puerto Rico

Re: Mint13-14 Latest Kernel Version Causing EXT4-fs Errors

Postby karlchen on Wed Jan 23, 2013 10:19 am

Hello, viking777.
Hi karlchen, I thought you might be pleased to see this: [...]
Ubuntu 12.10 kernel 3.5.0-22 64bit.

Absolutely so. 8)
In particular because Linux Mint 14 running on K3.5.0-22 x86 was the first system where I came across the orphaned inodes.
By the way, going back to K3.5.0-21 x86 seems to have fixed the issue there as well.
Thanks a lot for confirming I am not alone. :)

Cheers,
Karl
User avatar
karlchen
Level 10
Level 10
 
Posts: 3405
Joined: Sat Dec 31, 2011 7:21 am

Re: Mint13-14 Latest Kernel Version Causing EXT4-fs Errors

Postby viking777 on Wed Jan 23, 2013 10:21 am

You are definitely not alone, I just got a whole load more on my last boot.

And btw I don't have any of those exotic boot options mentioned in the Manjaro post.
Fujitsu Lifebook AH532. Intel i5 processor, 6Gb ram, Intel HD3000 graphics, Intel Audio/wifi. Realtek RTL8111/8168B Ethernet.Lubuntu 13.10,Ubuntu12.10 (Unity), Mint16 (Cinnamon), Manjaro (Xfce).
Image
User avatar
viking777
Level 14
Level 14
 
Posts: 5153
Joined: Mon Dec 01, 2008 11:21 am

Re: Mint13-14 Latest Kernel Version Causing EXT4-fs Errors

Postby karlchen on Wed Jan 23, 2013 10:26 am

Hello, AlbertP.
This ext4 data corruption bug has never been in Ubuntu's kernels.
You may be right. The root cause may be something else now.

About IDE mode [...] it's worth trying.
Well, yes and no. Going back to current kernel minus 1 (k3.2.0-35 / k3.5.0-21) does not come with any performance penalty at all. :D
Yet, in order to find out whether the problem is related to AHCI mode this time, switching to IDE mode might be worthwhile. Definitely.

Cheers,
Karl
User avatar
karlchen
Level 10
Level 10
 
Posts: 3405
Joined: Sat Dec 31, 2011 7:21 am

Re: Mint13-14 Latest Kernel Version Causing EXT4-fs Errors

Postby karlchen on Wed Jan 23, 2013 10:31 am

Hello, heavy metal.

Switching to a different filesystem type might be an option for future installations.
Setting up half a dozen existing systems from the scratch seems too much hassle for my liking considering the fact that reverting them to current kernel minus 1 is extremely simple.

Cheers,
Karl
User avatar
karlchen
Level 10
Level 10
 
Posts: 3405
Joined: Sat Dec 31, 2011 7:21 am

Re: Mint13-14 Latest Kernel Version Causing EXT4-fs Errors

Postby karlchen on Wed Jan 23, 2013 10:42 am

Hello, viking777.

Telling from the time the EXT4 corruption bug had been detected in kernel 3.6.2 and backported to k3.4 and k3.5, October 2012, and comparing this to the timestamps of K3.2.0-35 and K3.5.0-21, I strongly tend to agree with AlbertP: Whatever we see, it is very likely not the bug reported in October 2012.
My mount options are plain vanilla, too, i.e. the ones that Ubuntu and Mint thought were suitable.

Just for curiosity's reason: are you going to return to K3.5.0-21 x64? - As stated before, reverted all my systems to K3.2.0-35 / K3.5.0-21 respectively. I.e. simply changed GRUB_DEFAULT=0 to GRUB_DEFAULT=2 (/etc/default/grub) and executed sudo update-grub.

Anyway, time to create a Launchpad bug report tonight, unless someone else already has, in which case I would support this report.

Cheers,
Karl
User avatar
karlchen
Level 10
Level 10
 
Posts: 3405
Joined: Sat Dec 31, 2011 7:21 am

Linux Mint is funded by ads and donations.
 
Next

Return to Software & Applications

Who is online

Users browsing this forum: iru, niowluka, rotanibod and 18 guests