Hi, thanks Dave
So I posted there :
https://askubuntu.com/questions/938568/lights-on-trim-in-14-04-5
I hope I'll read you there
Bye bye
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
@bybeu, please do not post questions like this to ancient bugs.
Instead use askubuntu or ubuntuforums.
Back to your problem at hand though. You are free to manually add your
ssd's to the whitelist. Unfortunately the way you asked your question
makes it very unclear what you've done or what
Mine in my XPS13(L322X developer edition) is a LITEONIT LMT-256M6M mSATA 256GB,
but with firmware DM8110C.
I wander why I have in /etc/cron.weekly both scripts trim (... fstrim -v / >>
$LOG) and fstrim (... exec fstrim-all). I can't remember I tweaked this,
neither I have a clean Trusty install
This device is blacklisted now in the kernel:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/ata
/libata-core.c Thus this should be fixed for utopic.
I dropped our whitelisting now as the kernel already does the
blacklisting and it does not seem to affect lots of
@Juan Manuel Cabo:
Look at: https://bugzilla.kernel.org/show_bug.cgi?id=71371
And this:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/ata?id=3b8d2676d15d6b2326757adb66b70a9cd6650373
** Bug watch added: Linux Kernel Bug Tracker #71371
OMG!
Has anyone besides the OP reproduced the issue on these drives?
I'm not even sure that his FS corruption, in this particular instance,
is because of the hardware layer:
The Original Poster (Ritesh), states in post #31
@Martin you're right, thanks for the correction.
This means my drive has the same controller as OP's faulty Crucial
drive. How probable is it that the corruption problem has anything to do
with the flash controller (as opposed to, let's say, the drive's
firmware)?
Regards,
--
You received this
@Jeffrey, I don't know for sure, but I'd say it's likely that two drives
from the same manufacturer using the same controller will at the very
least be both derived from the same firmware code base, and their
firmware will therefore likely have a lot of bugs (and features) in
common. Since your
Hi,
I also ran Martin's test on my XPS 13 (9333) SDD and I didn't detect any
issue.
This is hdparm's output:
$ sudo hdparm -I /dev/sda | head -n 10
/dev/sda:
ATA device, with non-removable media
Model Number: LITEONIT LMT-256M6M mSATA 256GB
Serial Number:
@Jeffrey
AFAIK, the Crucial M500 uses the Marvell 88SS9187 controller, while the
M550 and MX100 both use the Marvell 88SS9189 controller, and therefore
probably share the same firmware (or maybe the MX100 firmware was forked
off of the M550 firmware):
These new Crucial MX100 SSD series features
@Martin, When I look in my dmesg log I found out that Ubuntu is ineed
blocking the trim.
allard@ubuntu-pc-allard:~$ dmesg | grep ata1
[0.949268] ata1: SATA max UDMA/133 abar m2048@0xfe30c000 port 0xfe30c100
irq 50
[1.439698] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[
@Allard, OK, that's good to know that a message shows up in dmseg saying
the queued trim is disabled. I don't have that message for my MX100, so
it seems trim isn't disabled in the kernel for the MX100:
$ dmesg | grep ata1
[1.995490] ata1: SATA max UDMA/133 abar m2048@0xf2627000 port
Note that there are reports on the Crucial forum that the Crucial M550
has the same problem, and therefore because it uses the same controller
(and firmware?), the MX100 does too:
http://forum.crucial.com/t5/Solid-State-Drives-SSD/M500-M5x0-QUEUED-
@Martin: The --no-model-check has no effect at the moment anyway
because trim is disabled for these crucial SSDs in all recent kernel
versions.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
@Martin: I'm also using a Crucial M500 which had the MU03 firmware. I
updated to MU05 and I did run trim manually. When I execute the command
I get a message which saying there a bytes trimmed. When I run it again
I also get the 0 bytes trimmed message. I don't know that this is normal
behavior.
@penalvch,
Huh? I'm not currently having this problem. Just reporting that my
Crucial CT512MX100SSD1 currently doesn't seem to exhibit the problem,
and therefore should maybe be added to the whitelist.
If you still want me to file a separate bug report (to get more hardware
details?), please let
@Offtopic: Isn't it possible to edit previous posts? Because it feels
like an monologue to post news comments all the time.
However I opened a thread on the Crucial forum [1] and a nice guy
referred me to another thread [2] which tells that the bug is fixed with
firmware MU05. And there a two
Has anyone already tried to report this issue to Crucial?
--
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/1259829
Title:
htree_dirblock_to_tree:920: inode #53629599: block 214443464:
@Ritesh, there is a newer firmware [1] available for your device, could
you test if this fixes the issue?
[1] http://forum.crucial.com/t5/Solid-State-Drives-SSD/Feedback-Thread-
Firmware-MU05-for-the-M500/td-p/146872
--
You received this bug notification because you are a member of Kernel
I could test my KINGSTON SV300S37A120G with firmware 521ABBF0.
I used Martin's test:
sudo dd if=/dev/sda of=/dev/zero
sudo find / /dev/null 21
sudo grep -r . / /dev/null
and manual fstrim -v / several times.
I did this for about 5 minutes.
No problems and fsck.ext4 /dev/sda said, CLEAN.
KINGSTON SV200S364G with fw E111008a seems OK too
--
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/1259829
Title:
htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm
rm:
Also KINGSTON SVP200S37A60G with fw 502ABBF0
--
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/1259829
Title:
htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm
rm: bad
I tested on a KINGSTON v300 and a v100 and everything works fine.
I used the discard mount option as it seems to be the most efficient to detect
this misbehavior.
And then I started:
sudo apt-get build-dep libreoffice; apt-get source -b libreoffice
It worked fine, I also tried with periodic
Hello, yesterday I installed trusty on my Kingston 60GB SSD
(Model=KINGSTON SV300S37A60G, FwRev=525ABBF0)
After running the simple test with no error I added --no-model-check to
/etc/cron.weekly/fstrim...so far so good
--
You received this bug notification because you are a member of Kernel
A simple smoke test might be to run something like
sudo dd if=/dev/sda of=/dev/zero
sudo find / /dev/null 21
sudo grep -r . / /dev/null
and run fstrim-all in parallel. You can of course do the original thing
of setting up a schroot and sbuild libreoffice in that (or just sudo
apt-get
What kind of heavy simple test can I run on my Kingston and Kingspec
SSDs to know if they also are affected by this kind of problems ?
A simple testing method should help build the whitelist/blacklist.
I have access to several SSDs from a lot of manufacturers, the only ones
that are not already
Dave, thanks; so smartctl and hdparm indeed show the same model number,
just wanted to confirm. I whitelisted these in
http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/util-
linux/trusty/revision/103
--
You received this bug notification because you are a member of Kernel
Packages,
We were using smartctl -a /dev/sdblah from smartmontools.
ATA device, with non-removable media
Model Number: OCZ-VERTEX3 MI
Serial Number: OCZ-D38A6W57990V6TG5
Firmware Revision: 2.25
Transport: Serial, ATA8-AST,
If we have evidence that Ritesh's SSD is the only (or one of very few)
affected models, I'm also not opposed to just blacklisting that. But we
really can't know. At least it's now fairly easy to enable in
/etc/cron.weekly/fstrim on all models, but of course that whole TRIM
business is still way
ATA device, with non-removable media
Model Number: Crucial_CT960M500SSD1
Serial Number: 1335094BE7CA
Firmware Revision: MU03
Transport: Serial, ATA8-AST, SATA 1.0a, SATA II Extensions,
SATA Rev 2.5, SATA Rev 2.6, SATA Rev
@pitti As it appears that we are going for a whitelist.
I have
Device Model: Patriot Wildfire
Serial Number:PT1145A00024835
LU WWN Device Id: 0 000120 0
Firmware Version: 502ABBF0
User Capacity:120,034,123,776 bytes [120 GB]
Device Model: OCZ-VERTEX3 MI
Serial Number:
For the record, due to this bug we limited automatic fstrim to Samsung
and Intel drives for now: https://launchpad.net/ubuntu/+source/util-
linux/2.20.1-5.1ubuntu14
I can't say I like that much as it excludes a lot of other good SSDs
from being trimmed by default, but better safe than sorry. We
ubuntu should enabled discard by default.
---
http://article.gmane.org/gmane.comp.file-systems.ext4/41974
From Theodore Ts'o via thunk.org
This is a hardware bug, unfortunately. And it's also the reason why
discard is not on by default.
These days,
Posted this to linux-ext4 list, on my second attempt. They reject
multipart ( containing html) messages.
http://thread.gmane.org/gmane.comp.file-systems.ext4/41969 .
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
[0.00] Initializing cgroup subsys cpuset
[0.00] Initializing cgroup subsys cpu
[0.00] Linux version 3.2.53-030253-generic (apw@gomeisa) (gcc version
4.6.3 (Ubuntu/Linaro 4.6.3-1
ubuntu5) ) #201311281435 SMP Thu Nov 28 19:36:21 UTC 2013
[0.00] Command line:
fs layout
/boot - sda2, ext4 with discard
/boot/efi - sda1, vfat
/ - sda3_crypt ( luks with lvm w/ discard enabled )
I enable discard as described using -
http://askubuntu.com/a/122206/125818 .
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Description changed:
- fs goes into read-only mode while building LibreOffice.
-
- I dont see these error message with 3.12 kernel, or if I boot with ncq
- disabled.
+ fs goes into read-only mode while building LibreOffice. I dont see these
+ error message with 3.12 kernel.
+
+ WORKAROUND:
Ritesh Khadgaray, thank you for your testing results. Given you tested
this in a recent mainline kernel (although not the most recent), and you
have a SSD (relatively newer HW from kernel perspective), I'm going to
mark this Traiged for now. Hence, the issue you are reporting is an
upstream one.
Ritesh Khadgaray, thank you for your testing. I would avoid using the
mainline daily folder as this would be a downstream construct, and
upstream may not be terribly interested in it. Given you tested
v3.13-rc3, this would be fine.
Despite this, would you mind testing a 3.2.x Ubuntu kernel series
** Tags removed: kernel-bug-exists-upstream
** Tags added: kernel-bug-exists-upstream-v3.13-rc3
--
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/1259829
Title:
** Description changed:
- fs goes into read-only mode while build lo
+ fs goes into read-only mode while building LibreOffice.
+
+ I dont see these error message with 3.12 kernel, or if I boot with ncq
+ disabled.
$ dmesg
...
[ 2045.473249] virbr0: port 1(vnet0) entered forwarding state
** Changed in: linux (Ubuntu)
Status: Incomplete = New
--
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/1259829
Title:
htree_dirblock_to_tree:920: inode #53629599: block
apport information
** Description changed:
fs goes into read-only mode while build lo
$ dmesg
...
[ 2045.473249] virbr0: port 1(vnet0) entered forwarding state
[ 2045.473283] IPv6: ADDRCONF(NETDEV_CHANGE): virbr0: link becomes ready
[10660.961381] perf samples too long (2505
I dont see these error message with 3.12 kernel, or if I boot with ncq
disabled.
$ echo 1 /sys/block/sda/device/queue_depth
Additionally, fstrim seems to return the same upon reboot
first run
# fstrim -v /
/: 920118112256 bytes were trimmed
second run ( after reboot )
/: 920175951872 bytes
The system did not reboot; after enabling discard and running
fstrim/discard; due to corrupted partition table. I was unable to test
this any further.
The disk seems to be fine,based on badblock check. memtest86 seems to
show a clean system.
--
You received this bug notification because you
Unable to reproduce this issue anymore. Another odd thing which I
noticed fstrim -v / , now returns 0 bytes trimmed on multiple run.
This was not the case earlier.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Ritesh Khadgaray, thank you for your comments. Are you unable to
reproduce this in the trusty kernel or mainline?
--
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/1259829
Title:
** Tags added: latest-bios-211 regression-potential
** Changed in: linux (Ubuntu)
Status: Confirmed = Incomplete
--
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/1259829
Title:
Did this issue occur in a previous version of Ubuntu, or is this a new
issue?
This is a new disk, with the latest firmware ( purchased on 25th Nov).
This issue was first seen when I tried to build libreoffice ( the build
goes from 256mb to 32gb , and goes down to 18gb) .
Worked fine when
apport information
** Tags added: apport-collected staging
** Description changed:
fs goes into read-only mode while build lo
$ dmesg
...
[ 2045.473249] virbr0: port 1(vnet0) entered forwarding state
[ 2045.473283] IPv6: ADDRCONF(NETDEV_CHANGE): virbr0: link becomes ready
disabling discard option fixed this for me.
--
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/1259829
Title:
htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm
rm: bad
** Changed in: linux (Ubuntu)
Status: Incomplete = New
--
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/1259829
Title:
htree_dirblock_to_tree:920: inode #53629599: block
Did this issue occur in a previous version of Ubuntu, or is this a new
issue?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.12 kernel[0].
If this bug is fixed in the mainline kernel, please add
53 matches
Mail list logo
