[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#691427: marked as done (journal commit I/O error on brand-new Thinkpad T430s ext4 on lvm on SSD)

Your message dated Sat, 1 May 2021 16:46:24 +0200
with message-id <YI1pwKwzogff8TPU@eldamar.lan>
and subject line Re: Bug#691427: journal commit I/O error on brand-new Thinkpad T430s ext4 on lvm on SSD
has caused the Debian Bug report #691427,
regarding journal commit I/O error on brand-new Thinkpad T430s ext4 on lvm on SSD
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
691427: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691427
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: linux
Version: 3.2.32-1
Severity: important
Tags: upstream

Hi dear linux maintainers,

I have setup a Debian Wheezy on a brand new Lenovo Thinkpad T430s with a
SSDSC2BW180A3L SSD drive. After the install, the user installed his usual
softwares (solr, apache, nodejs, …) and started work.

Under some load (importing thousands of records in MySQL via a hand-called PHP
script), the system reliably stops working fine enough because of "journal
commit I/O error" leading to a readonly filesystem. Then Gnome becomes
(obviously) unuseable and the only way out is a hard-reboot.

The disk looks fine (and is brand new), according to the BIOS disk report and
SMART tests, so the usual suspiscion that it might be broken is improbable.

We have reproduced this bug under 3.2.0-4 (3.2.23-1), 3.2.0-5 (3.2.32-1) and
3.5-trunk (3.5.5-1~experimental.1). The setup is an ext4 / (and /home) on LVM,
on the mentionned SSD.

What are the things we could do to help resolve this bug? Are there logs that
you might want to get? Please advise!

Cheers,

OdyX, on behalf of Dorian Villet, owner of the (unuseable) T430s.

--- End Message ---
--- Begin Message --- 
Hi,

On Tue, Oct 28, 2014 at 12:06:26PM +0100, Petter Reinholdtsen wrote:
> 
> Just for the record, I believe this is a firmware bug in the Intel SSD
> 520 180GB disks used by Lenovo, causing the disks to lock up under heavy
> load.  Perhaps this bug should be closed, or tagged as wontfix, or
> something else?

Let's close it.

Regards,
Salvatore

--- End Message ---
Reply to: