linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 63981] Bad: Buffer I/O errors make disk unusable
Date: Tue, 29 Oct 2013 08:28:48 +0000	[thread overview]
Message-ID: <bug-63981-13602-uHncRYJZgR@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-63981-13602@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=63981

--- Comment #5 from Giuseppe Scalzi <scalg1@bfh.ch> ---
(In reply to Theodore Tso from comment #4)
> BTW, I'm using a 512GB Samsung 840 PRO (2.5" SATA SSD) and an 240GB Intel
> 525 SSD (mSata) on my Lenovo T430s, and they both work like a charm.
> 
> Hmm... I wasn't able to get detailed specs on your SAMSUNG
> MZNTD256HAGL-00000, but upon doing some further research, it appears to be a
> new-fangled M.2 PCIe interface.  So it's not a mSATA nor a 2.5" SATA
> interface, but Something New.
> 
> So whether or not this is a Linux bug, or an implementation bug in this new
> Samsung part (or a failure in the standardization of this new M.2 PCIe
> interface), I can't say, but this looks like the most likely cause is a
> problem with this new SSD or its new M.2 interface[1].
> 
> [1] http://en.wikipedia.org/wiki/Next_Generation_Form_Factor

Ok, thank you for you reply, I understand that isn't a problem related to EXT4.

I noticed from the archlinux wiki of my laptop model
(https://wiki.archlinux.org/index.php/Sony_Vaio_Pro_SVP-1x21) that they suggest
to use this option:

- When booting from USB, append libata.force=noncq to the kernel parameters to
avoid problems with the SSD.

Well they say "when booting from USB" but I'll try "libata.force=noncq" anyway.

We will see what happens.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2013-10-29  8:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-28 19:38 [Bug 63981] New: Bad: Buffer I/O errors make disk unusable bugzilla-daemon
2013-10-28 22:35 ` [Bug 63981] " bugzilla-daemon
2013-10-28 23:01 ` bugzilla-daemon
2013-10-28 23:20 ` bugzilla-daemon
2013-10-28 23:31 ` bugzilla-daemon
2013-10-29  8:28 ` bugzilla-daemon [this message]
2013-10-29 15:14 ` 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-63981-13602-uHncRYJZgR@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).