lucid has seen the end of its life and is no longer receiving any
updates. Marking the lucid task for this ticket as "Won't Fix".
** Changed in: linux (Ubuntu Lucid)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
It occurs more frequently using RAID0 with mdadm, and also (less
frequent) using dmraid.
This problem does NOT occur using a Virtual Machine under Windows.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
I'm using Quantal, Kernel 3.5.0-17-generic . The problem still occurs
for me. Using ext4. I've replaced the Hard DIsk five times. It occurs
with my 3 Western Digital Caviar Blacks (1 TB 64 MB cache), and with my
Caviar Green (1.5 TB, 64 MB cache), and also (at least until now) my old
Seagate Barrac
Dear all I'm having the same problem in 10.0.4 using kernel 2.6.32-34
I will try the 2.6.34 but I would like to have a script to guarantee that the
problem really disapear
A script to crash the system
Regarding post 25 I can't execute the second script My ubuntu does not have
does power manage
Hello, I've spend the past two days troubleshooting this issue with my
Ubuntu 10.04 VirtualBox machine. I first upgraded the kernel to 2.6.35
and still had the problems. Long story short - what fixed this issue
for me (running Ubuntu 10.04 (EXT4) as a guest on a Windows 7 x64 host)
was the follow
I just wanted to note that it appears that the update to qemu 0.12.5 has
fixed my problem. I will submit a bug report for this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/528981
Title:
Repetitiv
The 2.6.34 mainline kernel didn't help. This appears to be the bug I am
running into:
https://bugzilla.redhat.com/show_bug.cgi?id=626684
I'm having trouble searching the ubuntu bug database right now, so I
can't tell if there is a bug report for this or not. I am building the
10.10 qemu-kvm pac
I'll give that a shot. I also had a similar issue when attempting the
same copy with ext3.
Let's hope that the mainline kernel works for me. It would probably be
a good idea to identify what changed between 2.6.32 and 2.6.34 with
respect to ext4 and ext3 file systems. It can't be good to have t
I’m not sure; I’m using 2.6.34-020634-generic (so yeah, that old, not-RC
one) and it works ok. You can also try looking for Lucid backports of
newer mainline (vanilla) kernels.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
Shot:
Do I have to use one with "lucid" in the name? The most recent kernel
version like that is somewhat old.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/528981
Title:
Repetitive massive filesy
> I think that I will be using a different filesystem for this.
Simply install a vanilla (mainline) kernel from http://kernel.ubuntu.com
/~kernel-ppa/mainline
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
I just had this happen with 2.6.32-27-server on 10.04 server. The
filesystem was a 4TB ext4 volume, and I was copying millions of small
files to it.
I think that I will be using a different filesystem for this. =/
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
** Changed in: linux (Ubuntu Lucid)
Status: Incomplete => Confirmed
--
Repetitive massive filesystem corruption
https://bugs.launchpad.net/bugs/528981
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ub
It was noted above that kernel 2.6.33 was, in one case, 'cured' of this
bug, but 2.6.33-02063305-generic on my MacBook2,1 still had file
corruption (all-be-it after much more time than 2.6.32-23). Now that
2.6.32-24 is the default for Ubuntu 10.04, I am testing it and it has
gone longer than usual
i have this problem with the 2.6.31-11-rt kernel:
EXT4-fs error (device sda3): ext4_lookup: deleted inode referenced
--
Repetitive massive filesystem corruption
https://bugs.launchpad.net/bugs/528981
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
This problem is no longer present in the default Maverick Meerkat kernel
(currently 2.6.35-9-generic #14-Ubuntu SMP).
--
Repetitive massive filesystem corruption
https://bugs.launchpad.net/bugs/528981
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Changed in: linux (Ubuntu Lucid)
Assignee: Andy Whitcroft (apw) => (unassigned)
--
Repetitive massive filesystem corruption
https://bugs.launchpad.net/bugs/528981
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs ma
I hope that this is helpful. My computer is running well with kernel
2.6.34 using Ubuntu Lucid 10.04. My computer freezes if I boot using
kernel 2.6.32-22.
I am able to keep my computer functioning after the events causing a
freeze by mounting my root filesystem using the option data=writeback
ins
Hi Andy,
I'm also seeing this issue on my MacBook 2,1 with an Intel SSD.
Typically it will go for long periods of time (days) without a problem
before seeing the failure. Often times it is when switching to a
different commit on my Linux-2.6 git tree that the failure will occur.
I've now switched
... and the updated kernel 2.6.32-22-generic pushed out by update today
caused a freeze, after which I had to manually correct the filesystem
(twice). The first run reported empty indoes in /tmp/stuart-orbit/ and
now, for the first time, I have some recovered inodes:
ls -al /lost+found/
total 20
d
Just 50 minutes in and I suspended (to go to bed) and just tried testing
resume, various parts of the desktop failed (Network Manager for one)
and the filesystem was readonly. Attempting to open a terminal locked it
completely - the Caps Lock light did not function, but Alt Sysreq REISUB
rebooted,
Andy Whitcroft, if I understood message #34 correctly, then the kernel
2.6.32-22 contains the libata patch. I am running with this kernel now
in Lucid on a laptop previously affected by this bug. I will let you
know after 24 hours if it is still running.
I was running kernel 2.6.34 previously and
As this issue is not seen in 2.6.34 I am marking this Fix Released for
Maverick. Lucid remains open.
--
Repetitive massive filesystem corruption
https://bugs.launchpad.net/bugs/528981
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Ok I have pulled back the patch which was suggested in comment #25, and
built some test kernels. If anyone is able to test these and confirm
whether this fix is indeed the solution that would be helpful. Of
course there is significant risk it is not, so don't do it with your
favourite data. If y
** Tags added: kernel-candidate kernel-reviewed
** Tags removed: kernel-needs-review
--
Repetitive massive filesystem corruption
https://bugs.launchpad.net/bugs/528981
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs maili
** Tags added: kernel-fs kernel-needs-review
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
--
Repetitive massive filesystem corruption
https://bugs.launchpad.net/bugs/528981
You received this bug notification be
I would like to report that I've been using the Ubuntu kernel
2.6.34-52.1 from Brian Rogers's PPA located at
https://launchpad.net/~brian-rogers/+archive/graphics-fixes
with considerable success. For those who use an i852/855 chipset and
are having problems with the Intel graphics, in addition t
Thanks Scott. I will check to see if a bug report has already been
submitted on this issue. It appears that the kernel upgrade was
successful in stabilizing my system, so thanks anyway.
--
Repetitive massive filesystem corruption
https://bugs.launchpad.net/bugs/528981
You received this bug notif
Dr. Burnett:
Please note that this bug report does not involve a wake from sleep trigger.
The corruption events reported here are spontaneous, with the system up and
running.
If your filesystem is being corrupted on wake from sleep, please file a
new bug report with the circumstances of the dif
Just saw Scott's post and I am applying it now. Will report any further
problems.
Thanks.
--
Repetitive massive filesystem corruption
https://bugs.launchpad.net/bugs/528981
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bug
I am having the same (read-only file system) problem after wake from
sleep triggered by opening the lid on the laptop. I have included all
the useful information I gathered from logs. I will also, as previously
described, attempt to capture more relevant data if/when phenomenon
occurs again.
##m
Everyone is welcome to the fruits of my pain with this problem. I was
hoping to get the problem solved before Lucid so I could use a
completely standard Lucid install, but my hopes were dashed and I have
to target Maverick instead.
The current stock Lucid kernel is just stable enough on my system
Thanks a lot, Scott, for your through summary.
Is there a good way to install Lucid with the mainline kernels without
ever booting with kernels affected by this issue, or would this require
a custom install image (with one of the mainline kernels on the
installation medium, and one being able to i
No further patches are needed regarding the reported bug. Kernel 2.6.33
has been released and does not experience the bug described in this
report. Kernel 2.6.34 is also released (and queued for inclusion in
Maverick) and does not experience the bug described in this report.
You can use the main
Bugzilla bug #14543 describes a very similar issue involving ata flushing which
is RESOLVED and available in patch "libata: retry failed FLUSH if device didn't
fail it" which is applied from kernel 2.6.33-rc1
http://mirror.celinuxforum.org/gitstat//commit-detail.php?commit=6013efd8860bf15c1f86f36
The grub option "radeon.modeset=0" does not prevent X freezes. My system
appears to last much longer between freezes / failures to resume, but
still does so.
I can repeatably cause the machine to freeze by mounting cifs locations
- the computer will freeze shortly into use after the next resume
fo
Running kernel 2.6.34-020634rc6-generic (mainline 2.6.34-rc6-lucid) I am
experiencing exactly the same behavior as I previously reported in
comment #7. It seems clear that the problem was fixed in 2.6.33.
** Tags removed: needs-upstream-testing
--
Repetitive massive filesystem corruption
https:
This message clearly does not apply directly to all subscribers to this
bug, because some have NVidia graphics. However I noticed that I had an
error in dmesg "[drm:rs400_gart_adjust_size] *ERROR* Forcing to 32M GART
size (because of ASIC bug ?)" and that this is solved in Bug #562843
https://bugs.
I'm experiencing what appears to be the same issue, on a Dell XPS M1330.
So far the problem appears to be fixed running http://kernel.ubuntu.com
/~kernel-ppa/mainline/v2.6.34-rc6-lucid/
--
Repetitive massive filesystem corruption
https://bugs.launchpad.net/bugs/528981
You received this bug notifi
I would strongly advise against trying to force your primary filesystem
to remount writeable, especially since it may introduce additional
corruption that will make this bug more difficult to troubleshoot.
Filesystem bugs like this one are quite difficult to troubleshoot
because, for instance, this
I have tried inserting a USB memory stick, but it seems that the system
is unable to mount it once the root partition has been remounted
readonly. Is there any command to remount the filesystem rw, at my own
risk?
I also collected some possibly duplicate launchpad bugs here
http://www.iol.ie/~stua
Thanks for your update, Stuart. In trying to save log files when the
filesystem goes read-only, I've found it helpful to use either a USB key
or SD Card, which can be mounted even when the boot filesystem has gone
read-only. In most cases when testing for this problem, I even mount an
SD Card as
I am still having this issue in a fresh install of the release candidate
of Ubuntu 10.04, using the default kernel. Both the root partition and
separate home partition are remounted readonly, so pretty much
everything is disabled (including the ability to save any log data).
--
Repetitive massive
Thanks Jeremy!
By "latest upstream," are you referring to 2.6.33.2-lucid (the series
I've already tested with success) or 2.6.34-rc5-lucid (which I haven't
tested at all)?
Please allow a few days for me to perform the testing and I'll report
back here.
--
Repetitive massive filesystem corruptio
Hi Scott,
If you could also please test the latest upstream kernel available that would
be great. It will allow additional upstream developers to examine the issue.
Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the
upstream kernel, please remove the 'needs-upstre
** Tags removed: needs-upstream-testing
--
Repetitive massive filesystem corruption
https://bugs.launchpad.net/bugs/528981
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://
Still running Debian Squeeze with kernel 2.6.32-3-686, and still no
corruption. The Debian configuration appears to be using CONFIG_IDE
instead of CONFIG_ATA, since the hard drive is reported as hda rather
than sda.
I've found an upstream bug report / flame war that may or may not
provide any use
Debian Squeeze kernel 2.6.32-3-686 and kernel 2.6.32-trunk-686 do not
exhibit any corruption at all. This leads me to believe the problem is
a configuration problem, and not a problem inherent to the 2.6.32 kernel
itself.
--
Repetitive massive filesystem corruption
https://bugs.launchpad.net/bug
Kernel 2.6.32-18-generic no longer has spontaneous corruption at all.
When the system hard locks due to other problems (an xserver lockup, for
instance), the system still requires running e2fsck from a CD, and can
still experience significant corruption. This is distinctly different
from 2.6.33, w
Have now been running kernel 2.6.33-020633-generic for over 24 hours
with no read-only events. Even better, after the system locks up due to
various i855 xorg problems, on reboot the machine is experiencing no
data loss at all. Seems clear the data loss issue has been resolved
upstream.
--
Repe
Still happens under 2.6.32-17-generic #26-Ubuntu. It's now much less
pronounced, but the system more frequently hard locks when the
filesystem goes read-only, and so requires a power cycle to restart.
This situation also leads to the requirement to run e2fsck from a CD.
--
Repetitive massive fil
** Tags added: karmic
--
Repetitive massive filesystem corruption
https://bugs.launchpad.net/bugs/528981
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/m
And again on EXT3, following a fresh install, with all packages updated
to latest available. This is running the 2.6.32-16 kernel.
[ 329.714992] EXT3-fs error (device sda1): htree_dirblock_to_tree: bad entry
in directory #7192587: rec_len % 4 != 0 - offset=0, inode=539167267,
rec_len=28483, na
More errors related to 2.6.32-16.24, but they happened after an
unexplained system lockup. Unfortunately, the error also destroyed
Firefox, which was the open application when the lockup occurred.
Fortunately, enough of the system was still functioning that error
messages were logged at the end of
I have now tested mainline kernel 2.6.33-999.201003071003 (i386) and
have experienced absolutely NO filesystem corruption under it.
Rebooting from 2.6.33 to 2.6.32-16.24 resulted in the following error:
EXT4-fs error (device sda1): ext4_lookup; deleted inode referenced: 3409181
Aborting journal o
As an additional troubleshooting step, I decided to run memtest86+ to
verify that my RAM is OK, and the result was that everything checks out
just fine.
--
Repetitive massive filesystem corruption
https://bugs.launchpad.net/bugs/528981
You received this bug notification because you are a member o
Bug 438379 does look quite similar to my problem, but I should note that
I've never suspended nor resumed before experiencing fs corruption, so
suspend/resume issues may or may not be relevant.
--
Repetitive massive filesystem corruption
https://bugs.launchpad.net/bugs/528981
You received this bu
I have very similar symptoms following a fresh install of Ubuntu 9.10 on
a Dell Inspiron 1501, which I have installed once in a single ext3
partition and subsequently in two (/ and /home) ext3 partitions, with
the same symptoms both times. I have records of an orphan node cleanup
in logs (similar t
Using mainline kernel 2.6.32.8 results in the same sort of corruption,
but it appears to be somewhat less pronounced. Unfortunately, the
corruption also blew up the kernel itself, so the system could no longer
boot. Since further blind experimentation seems pointless, I've
reinstalled Kubuntu 9.0
Once again, the filesystem switched to read-only while the system was in
use. The resulting fsck log is attached. This is using the standard
2.6.32-14-generic kernel immediately after a fresh install. Total
uptime before the problem was discovered was under five minutes.
** Attachment added: "e
** Attachment added: "Corruption detected by e2fsck on ext4"
http://launchpadlibrarian.net/39853984/e2fsck.log
** Attachment added: "AlsaDevices.txt"
http://launchpadlibrarian.net/39853985/AlsaDevices.txt
** Attachment added: "AplayDevices.txt"
http://launchpadlibrarian.net/39853986/Apl
61 matches
Mail list logo
