From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 63981] Bad: Buffer I/O errors make disk unusable
Date: Mon, 28 Oct 2013 23:20:20 +0000 [thread overview]
Message-ID: <bug-63981-13602-nyg7e499aw@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 #3 from Theodore Tso <tytso@mit.edu> ---
It's possible there is some kind of compatibility issue with the SATA driver on
your Sony Viao, but the point is with errors like these:
[13546.661310] ata4.00: failed command: WRITE FPDMA QUEUED
[13546.661315] ata4.00: cmd 61/08:00:2f:1d:0a/00:00:00:00:00/40 tag 0 ncq 4096
out
[13546.661315] res 40/00:01:00:00:00/00:00:00:00:00/40 Emask 0x4
(timeout)
[13546.661318] ata4.00: status: { DRDY }
[13546.661319] ata4.00: failed command: WRITE FPDMA QUEUED
[13546.661323] ata4.00: cmd 61/08:08:27:1d:0a/00:00:00:00:00/40 tag 1 ncq 4096
out
[13546.661323] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[13546.661325] ata4.00: status: { DRDY }
... and like these:
[13606.886264] EXT4-fs warning (device sda1): ext4_end_bio:316: I/O error
writing to inode 2097393 (offset 0 size 0 starting block 82853)
[13606.886267] Buffer I/O error on device sda1, logical block 82845
[13606.886268] sd 3:0:0:0: [sda] Unhandled error code
[13606.886270] sd 3:0:0:0: [sda]
[13606.886271] Result: hostbyte=0x04 driverbyte=0x00
[13606.886273] sd 3:0:0:0: [sda] CDB:
[13606.886274] cdb[0]=0x2a: 2a 00 00 00 00 3f 00 00 08 00
[13606.886282] sd 3:0:0:0: [sda] Unhandled error code
[13606.886283] Buffer I/O error on device sda1, logical block 0
[13606.886285] lost page write due to I/O error on sda1
[13606.886288] sd 3:0:0:0: [sda]
[13606.886289] Result: hostbyte=0x04 driverbyte=0x00
[13606.886293] sd 3:0:0:0: [sda] CDB:
[13606.886294] EXT4-fs error (device sda1): ext4_journal_check_start:56:
[13606.886294] cdb[0]=0x2a: 2a 00
... there's little that we can do at the ext4 level. Basically, the disk
device (or the Sony Viao's SATA chipset) is refusing to talk to Linux.
The Sony Viao has, historically, been notorious for using Windows-specific
hardware that doesn't work well with Linux. I don't know anything about your
specific model, but there have been enough problems in the past that I avoid
Sony laptops like the plague if I intend to use Linux on them. It's not by
accident that most Linux kernel developers tend to use Lenovo Thinkpads...
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2013-10-28 23:20 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 [this message]
2013-10-28 23:31 ` bugzilla-daemon
2013-10-29 8:28 ` bugzilla-daemon
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-nyg7e499aw@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).