From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 36722] New: TRIM support is broken for Crucial M4 drives
Date: Sun, 5 Jun 2011 15:05:38 GMT [thread overview]
Message-ID: <bug-36722-13602@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=36722
Summary: TRIM support is broken for Crucial M4 drives
Product: File System
Version: 2.5
Kernel Version: 2.6.38.8
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: ext4
AssignedTo: fs_ext4@kernel-bugs.osdl.org
ReportedBy: kernel-bugs.dev1world@spamgourmet.com
Regression: No
Created an attachment (id=60842)
--> (https://bugzilla.kernel.org/attachment.cgi?id=60842)
dmesg output
The TRIM is disabled as per the following messages:
# dmesg | grep "discard not"
[ 18.614000] EXT4-fs warning (device sdi8): release_blocks_on_commit:2674:
discard not supported, disabling
[42486.763000] EXT4-fs warning (device sdi11): release_blocks_on_commit:2674:
discard not supported, disabling
but TRIM support is there:
# hdparm -I /dev/sdi | grep TRIM
* Data Set Management TRIM supported (limit 8 blocks)
* Deterministic read data after TRIM
The drive is on this controller and not part of any RAID:
# lspci | grep LSI
04:00.0 Serial Attached SCSI controller: LSI Logic / Symbios Logic SAS2008
PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03)
The dmesg is attached.
Can someone also say what this message means:
[42087.056000] EXT4-fs (sdi11): Unaligned AIO/DIO on inode 654340 by
VirtualBox; performance will be poor.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next reply other threads:[~2011-06-05 15:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-05 15:05 bugzilla-daemon [this message]
2011-06-06 9:04 ` [Bug 36722] TRIM support is broken for Crucial M4 drives bugzilla-daemon
2011-06-06 14:43 ` bugzilla-daemon
2011-06-06 17:43 ` bugzilla-daemon
2012-08-24 13:01 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-36722-13602@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).