Good
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => denace (denace03)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/992424
Title:
ext4 filesystem errors on SSD disk
To manage notific
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 po
@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 t
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
1, always check if powermanagement is of for the sata /SSD's
2. always use AHCI
Im having multiple systems.
different SSDS ( ADATA 510, VERTEX 3, CRUCIAL V4 ).
Running Debian Wheezy ( kernel 3.2) of ubuntu kernel 3.2 and 3.8
only 1 problem found.
My OCZ Vertex 3 is running more than 1 year
Wife has a U300s running Debian Mint. Got bit recently w/ custom 3.5.2
(standard .config updated with defaults and compiled). I'm compiling
3.8.4 on it now (again debian mint standard .config updated w/ defaults
for 3.8.4) to see if that fixes it. Filesystem is ext4. I know I'm on
ubuntu launchpad
Same problem here, Ubuntu 3.5.0-25-generic #39-Ubuntu SMP Mon Feb 25 18:26:58
UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
running on top of a 120 GB SSD (OCZ Agility 3 ) is systematically getting
remounted as read only.
I have already tried to minimize the IO on the / partition, by having
some of t
The new ssd (Coursair Force GT) is working great for one month. The old
(Intel 510) is also working great in another computer. So I am wondering
if there is a compatibility problem with my Malibal Lotus P151HM1 and
the Intel ssd.
--
You received this bug notification because you are a member of U
The weirdest thing: I moved the ssd disk to another notebook over a month ago
and no errors. I put an hdd in my primary notebook and no errors too.
Next move: I will bought another ssd to this notebook and see what happens.
--
You received this bug notification because you are a member of Ubunt
** Changed in: linux
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/992424
Title:
ext4 filesystem errors on SSD disk
To manage notifications about this bug g
@Charles Thank you for the news.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/992424
Title:
ext4 filesystem errors on SSD disk
To manage notifications about this bug go to:
https://bugs.launchpad.
Since I've been running days longer than previously (since the trouble
started at the star of October) with no errors at all, it seems to have
been a hardware problem. (One can imagine software problems that
depended on an odd structure in the original file system, and I didn't
copy the file system
i can't even install xubuntu 12.10 (minimal iso + xubuntu-desktop).
sometimes is the mini iso installer that stops due to this bug (when installing
basic system), other times the errors occur when installing xubuntu-desktop
packages.
(ssd: samsung 830; motherboard asus p7p55d-e set in ahci mode)
At 2am, after working away happily for 1.5 days (I copied the work out
regularly), some time after a 45Mbyte Software Update, it
began to go wrong. A reboot prompted the following repair, and I left it:
[6.314129] EXT4-fs (sda1): orphan cleanup on readonly fs
[6.314137] EXT4-fs (sda1): ex
@Charles
I think you are right. Keep us updated with yours tests. :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/992424
Title:
ext4 filesystem errors on SSD disk
To manage notifications about th
If I get through the next day or two without the problems that plagued
me last week, that might suggest trying again with "discard" to see if
problems reappear.
On the other hand, if I have further trouble, I've got a new replacement
SSD to try.
Since my usage doesn't seem to be that unusual, and
It would be very nice if Linus give his opinion on this. He has told that
he doesn't like spinning disks, so besides coordinating the kernel he also
uses solid state disks. Is this a hardware failure? Or a bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
I wondered whether ext4_mb_generate_buddy might be related to
http://help.lockergnome.com/linux/ext4fs-error-ext4_mb_generate_buddy-741-group-16-8160-cluste--ftopict559576.html
so for a final experiment, I've switched off "discard" once more. That bug
seemed confined to scsi_debug, but who knows?
I was wrong about that. fsck -c -c -k ... had found 3 bad blocks, so I thought
"ah! it was device error after all".
Having moved the bad blocks out of the way, I expected all to return to normal,
and would have changed to moaning
about the complete lack of visible diagnostics (including in dmesg)
I think I know what it is, in my case. If my revised system gets through
the next few days, let alone a week, without trouble, I'll think it is
reasonably certain.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
Today's contribution, after hardly any work (allowing for overnight
locatedb updates and anything else the cron might do.
[70391.556798] EXT4-fs error (device sda1): __ext4_ext_check_block:472: inode
#560844: comm Chrome_CacheThr: bad header/extent: invalid magic - magic 3262,
entries 13113, max
@Charles
Ok, I thought you could cause it whenever you want. I agree with you that
it seems to be a function of the amount of file IO. Unfortunately I could
not reproduce when I tried to generate a lot of read and write. But my
files get corrupted after 15-20 days.
I am now testing the same disk (I
@André
By being able to reproduce it, I meant only that it happens so regularly from
day to day that I can try to capture more information: it isn't "once in a blue
moon". It does seem to be a function of the amount of file IO (which makes
sense), so I thought I might risk generating a load synt
@Charles
Can you explain (step by step if possible) how to reproduce the error?
(I am willing to do some tests, but the corruption seems random to me)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/99
Since I seem to be able to reproduce it, not at will, but at least with the
passage of a day or two,
is there something constructive I could do to help track this down? It looks
useful to run with a USB
stick attached and mounted, so I can copy logs etc onto it when things go wrong.
--
You rece
Since I get problems anyway, I've enabled "discard" again.
I might be willing to believe my SSD has hardware problems or is wearing out,
but I've seen trouble on two different systems so far.
Also, int February, when I had corruption with ext2/3, I thought it might be
memory or SSD, but memory t
I turned off the "discard" option last week after the first bout of
trouble, based on a suggestion in a google'd bug tracker that there was
an off-by-one in scsi_debug in the part that implemented trim. (Not that
I thought I was running scsi_debug, but since I was having similar
problems I suspecte
And this just in:
Linux ... 3.6.2-030602-generic #201210121823 SMP Fri Oct 12 22:31:22 UTC 2012
i686 i686 i386 GNU/Linux
[88861.206938] EXT4-fs error (device sda1): __ext4_ext_check_block:472: inode
#1080426: comm Chrome_CacheThr: bad header/extent: invalid magic - magic 81a4,
entries 1000, max
Yep, nasty enough for me to stop using my new 240 GB Intel "520 series"
SSD (model number SSDSC2CW240A3) and return to my old Hitachi 320GB HD
which works perfectly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
It might be worth noting that the bug is fairly nasty. I had to recover my
system yesterday afternoon. Today, after the overnight locatedb build (which
might be disk intensive), but relatively little use of the disk during a few
hours of normal work, the bug was triggered again by my downloading
@Charles: I've had the same problem in the past. :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/992424
Title:
ext4 filesystem errors on SSD disk
To manage notifications about this bug go to:
htt
@Thomas See my last message. I used the web page interface incorrectly
and then could not undo my mistake.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/992424
Title:
ext4 filesystem errors on SSD d
Sorry. I accidentally changed the status from Triaged, thinking I was
clicking through to more details, and it won't let me change it back.
Perhaps someone can revert that change.
I was intending just to add a note that this bug has been affecting
several different Ubuntu systems I maintain for my
@Charles: Can you please explain why this report has been reclassified
as "Fix Released"? Which kernel version contains the fix? How has this
fix been tested?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
** Changed in: linux (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/992424
Title:
ext4 filesystem errors on SSD disk
To manage notifications about thi
Can folks affected by this bug test the latest mainline kernel, which is
v3.6-rc7[0] ?
Thanks in advance.
[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.6-rc7-quantal/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
The same applies for me. It is a nightmare! I have a 90GB SSD and Kubuntu 12.04
64bit.
Since I installed 12.04 in random times the SSD is mounted in read only mode.
When I reboot I have to disconnect the SSD from the power and then the PC is
booted indicating no errors.
I will try to format the
More info, trying to elucidate this issue.
Using btrfs: unintentionally I pressed the evil suspend button and the computer
goes for a loop sleeping and awakening until reboot with a corrupted
filesystem. Btrfs seems to somehow recover itself and after ~300 seconds get to
boot after a few DRDY er
I am using AHCI mode. Now I am testing Btrfs for two days. Although it is
much more slow for boot (11.6 seconds vs 4.8 with ext4) and for
installation, so far I have not experienced any file corruption. I will
report again in a couple of weeks.
Regards.
--
You received this bug notification becau
It seems to related to Chipset and IDE mode in BIOS.
I found this problems only in old server (DELL 860) using IDE Mode on
ICH7/ICH7R.
And not affected only SSD, also HDD.
Another server with ICH10 with AHCI works flawlessly.
--
You received this bug notification because you are a member of Ub
I tested Reiserfs as suggested, but in my case, despite of fsck not showing
disk corruption, I got some others problems like after a few minutes the
read/write goes super-slow (from ~100MB/s to ~1MB/s as showed by hdparm -t
/dev/sda), then I got some "Bus error" when trying to launch some apps (
I am having problems as well. I thought my SSD was dying. During
updates it would receive an input/output error and halt updates. But an
older version of Ubuntu functioned without errors. I switched to
ReiserFS and have not had any errors so far.
--
You received this bug notification because yo
With ThinkPad X220 and 240 GB Intel 520 SSD I also get serious
filesystem corruption errors running Ubuntu 12.04 desktop. "Serious"
means: just now I couldn't boot from the Ubuntu partition on the SSD; I
had to boot from another disk and fsck the Ubuntu partition on the SSD,
and even then the boot
I'm experiencing similar file system corruption issues with my Sandisk
Extreme 120GB SSD. All Ubuntu or Debian based Linux OSes I tried so far,
including Ubuntu 12.04, as well as Fedora 16 and 17, report file system
errors on bootup irregularly. After fsck and fixing the errors (or in
case it boots
Same problem for me with a Seagate Barracuda 7200.9 ST3500641AS using
ata_piix, connected to SATA (IDE interface: Intel Corporation N10/ICH7
Family SATA Controller [IDE mode] (rev 01))/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
** Changed in: linux
Status: Unknown => Confirmed
** Changed in: linux
Importance: Unknown => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/992424
Title:
ext4 filesystem errors on
** Also affects: linux via
http://bugzilla.kernel.org/show_bug.cgi?id=42723
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/992424
Title:
ext4 filesyst
Same problem on SSD boot disk with a recently-updated copy of Linux Mint
10 Julia:
# lsb_release -rd
Description:Linux Mint 10 Julia
Release:10
# apt-cache policy linux-image
linux-image:
Installed: (none)
Candidate: 2.6.35.32.42
Version table:
2.6.35.32.42 0
500 h
Same problem with P-ATA-Harddisk (ATA WDC WD2500BEVE-00WZT0) in Thinkpad T43
Works with Xubuntu 12.04 and kernel 3.0.0-17-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/992424
Title:
ext4 fil
Imho this is upstream Bug# 42723 ->
https://bugzilla.kernel.org/show_bug.cgi?id=42723
I went back to 11.04 with 3.0.0-19-generic which works fine and without
any problems for nearly a week now.
** Bug watch added: Linux Kernel Bug Tracker #42723
http://bugzilla.kernel.org/show_bug.cgi?id=42723
This issue appears to be an upstream bug, since you tested the latest
upstream kernel. Would it be possible for you to open an upstream bug
report at bugzilla.kernel.org [1]? That will allow the upstream
Developers to examine the issue, and may provide a quicker resolution to
the bug.
If you are
Unfortunately it also happened with the upstream kernel:
[14081.450885] EXT4-fs error (device dm-1): ext4_mb_generate_buddy:741: group
904, 32254 clusters in bitmap, 32258 in gd
[14081.450895] Aborting journal on device dm-1-8.
[14081.451151] EXT4-fs (dm-1): Remounting filesystem read-only
[14081
I'm now running a 3.4 kernel. Will report back if there are problems.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/992424
Title:
ext4 filesystem errors on SSD disk
To manage notifications about th
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.4kernel[1] (Not a kernel in the daily directory). Once you've tested
the upstream kernel, please remove the 'needs-upstream-testing' tag(Only
that one
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Tags added: precise
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/992424
Title:
ext4 filesystem errors on SSD disk
To manage notifi
** Package changed: linux-meta (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/992424
Title:
ext4 filesystem errors on SSD disk
To manage notifications about this bug go to
** Attachment added: "dmesg.log"
https://bugs.launchpad.net/bugs/992424/+attachment/3122163/+files/dmesg.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/992424
Title:
ext4 filesystem errors on
$ cat /proc/version_signature
Ubuntu 3.2.0-24.37-generic 3.2.14
$ uname -a
Linux foo 3.2.0-24-generic #37-Ubuntu SMP Wed Apr 25 08:43:22 UTC 2012 x86_64
x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
** Attachment added: "lspci-vnn"
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/992424/+attachment/3122164/+files/lspci-vnn.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/992424
Titl
59 matches
Mail list logo
