Have just changed the state of this report from "Confirmed" to "Fix released",
because as a matter of fact the reported kernel bug has been fixed by
+ Kernel 3.2.0-37 (and later) ... applying to Ubuntu 12.04
+ Kernel 3.5.0-23 (and later) ... applying to Ubuntu 12.10 (and 12.04 with
Kernel series
Hello, folks.
I know it has been a really long time since I have last posted in this
bug report which after all has been opened by me.
Ubuntu 12.04 Kernel 3.2.0-37
In post #17
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1105900/comments/17) I
Presently have updated to kernel 3.2.0-49-generic-pae and have monitored
over two weeks and not a single ext4 buddy error has been created.
Can others move up to this kernel and validate. This seems to have cured
my issue. Think I'll lock myself down at this one.
--
You received this bug notific
** Tags added: needs-computer-model needs-upstream-testing regression-
update
** Tags added: quantal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1105900
Title:
Latest Kernel Version 3.2.0-36 Caus
After one week my log shows a single buddy error. This is a distinct
improvement. Hopefully the next kernel update will totally cure it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1105900
Title:
This is interesting.
Just put on kernel 3.2.0-48 pae and over the past three days no buddy errors
reported in the logs.
Will monitor over the next couple of weeks, so far, whatever was done to
the kernel, appears to have cured my issue.
--
You received this bug notification because you are a me
I am experiencing the same issue in Ubuntu 12.04 with kernel version
3.2.0-45 in a EXT4 volume. The error messages on init are similar to the
listed before in this log.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
I too am experiencing buddy errors with EXT4.
using 3.2.0-39-generic-pae
The volume giving the errors is a RAID 1 setup using dmraid. So I wonder if in
this situation there is an issue there. This volume was upgraded from ext3 as
well.
I don't see errors in the other ext4 volumes.
The errors
I've faced the same bug on Ubuntu 12.04 with both 3.2.0-36 and 3.5.0-22 . And
besides numerous " inode xxx has zero dtime DELETED" at each reboot ,there was
something even more sophisticated ...
Acronis linux based livecd fails to backup ext2 partition with those kernels !
Or rather not exactly
I get the same problem using 3.5.0-23 and an ext2 filesystem on my root
partition.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1105900
Title:
Latest Kernel Version 3.2.0-36 Causing EXT4-fs Errors
Hello, Luis Henriques, viking777.
With respect to
+ Ubuntu edition: Ubuntu 12.10 x86
+ Kernel version : Kernel 3.5.0-23
I am afraid I have to confirm your reports, viking777.
Same behaviour here. "/" is busy on every single shutdown right before the
sysem gets halted or rebooted. So "/" is never
Hello, Luis Henriques, folks.
As announced in comment #11
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1105900/comments/11),
I have checked /var/log/syslog on my Ubuntu 12.04.1 x64 system running
kernel 3.2.0-37 for a few more days.
---(z)grep "EXT4-fs" syslog.?gz syslog.1 syslog---
sy
Update to comment 15. Ubuntu12.10, kernel 3.5.0-23 64bit.
After 2 days of use (mount count now 14) the 'recovery' error message
recurred (see comment #13). The file system was "recovered" on every
boot until I forced an fsck from another distro. As before, the fsck
reported no file system errors,
Since forcing fsck from another distro, the warning on file system
recovery on my Ubuntu partition (given in post 13), has not returned.
Prior to forcing this check it occurred on every boot. This makes me
wonder if the decision to set maximum mount count for all ext4 files
systems to -1 was actual
For my next experiment I rebooted from Ubuntu12.10 into Mint14 and forced an
fsck on the Ubuntu partition.
Fsck found no errors.
However when I rebooted into Ubuntu the 'recovery' error was not present this
time.
There continue to be no 'orphan' errors.
--
You received this bug notification bec
These are my initial results. Using the 3.5.0-23 kernel 64 bit on Ubuntu 12.10.
Installed the kernel and did 5 reboots. No instance of orphaned inodes occurred:
grep -i orphan /var/log/syslog
ubuntu@fujitsu
The 'recovery' message occurred on every boot, but then again it also
occurs on every boot
I can confirm that I am using AHCI mode also. I will start testing the
3.5.0-23 kernel today.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1105900
Title:
Latest Kernel Version 3.2.0-36 Causing EXT4
Good evening, Luis Henriques, folks.
Coming back to the Ubuntu 12.04.1 x64 system running kernel 3.2.0-36
which made me open this bug report. (cf.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1105900/comments/0):
Tonight at 19:50 the kernel was updated to K3.2.0-37.
---Synaptic history--
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1105900
Title:
Latest Kernel Version 3.2.0-36 Causing EXT4-fs Errors
To manage notific
Hello, Luis Henriques.
This seems to be good news indeed.
Started with my 32-bit Ubuntu 12.10 running on kernel 3.5.0-22, added
quantal-proposed to the /etc/apt/sources.list file, updated to kernel
3.5.0-23 and rebooted in order to activate the new kernel.
---Synaptic history entry logging inst
Karlchen and viking777, we have identified a regression on the
3.5.0-22.34 (12.10) and 3.2.0-36.57 (12.04) kernels. This regression
could in fact be causing the problems you're seing in your systems. It
should have been solved by the kernels that are currently in -proposed
(3.2.0-37.58 and 3.5.0-
Disk controller operating mode as reported by palimpsest (disk utility) might
be relevant, too.
In fact, all affected systems that I have seen work in AHCI mode.
** Attachment added: "Disk controller operating mode AHCI"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1105900/+attachment
I have an identical problem on Ubuntu 12.10 when using kernel 3.5.0-22
but not kernel 3.5.0-21
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 in
inix -Fx screen output, escape sequences removed, 3rd attempt finally
worked, attachment is in pure text format and readable.
** Attachment added: "inxi -Fx screen output, escape sequences removed"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1105900/+attachment/3501162/+files/inxi-Fx.
Oops, the saved "inxi -Fx" output holds escape sequences making the text
file unreadable. Here is the pure screen output:
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
Here is a concise hard- and software configuration of the system "Voyager"
which this report is based on.
Installed inxi 1.84.1 on Ubuntu 12.04.1 x64, which does not bring inxi along by
default, and ran "inxi -Fx", because inxi can sum up the system configuration
in a really concise way.
After a
** Description changed:
System: Ubuntu 12.04.1 x64 Unity desktop
---
lsb_release -rd; uname -a
Description: Ubuntu 12.04.1 LTS
Release: 12.04
Linux Voyager 3.2.0-36-generic #57-Ubuntu SMP Tue Jan 8 21:44:52 UTC 2013
x86_64 x86_64 x86_64 GNU/Linux
--
Have not experienced any
Correction:
---
Item (2) under "Note:" in my bug report should of course read:
(2) I have seen the same problem after updating Ubuntu 12.10 from K3.5.0-17 to
K3.5.0-22.
Karl
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
28 matches
Mail list logo
