Comment 47 for bug 992424

Revision history for this message
99Sono (nunogdem) wrote :

Same problem here, Ubuntu 3.5.0-25-generic #39-Ubuntu SMP Mon Feb 25 18:26:58 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
running on top of a 120 GB SSD (OCZ Agility 3 ) is systematically getting remounted as read only.

I have already tried to minimize the IO on the / partition, by having some of the folders being mounted as tmpfs.

99sono@99sono-Satellite-A665:/tmp$ mount -l
/dev/sda1 on / type ext4 (rw,noatime,nodiratime,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
none on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
udev on /dev type devtmpfs (rw,mode=0755)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
tmpfs on /tmp type tmpfs (rw,noatime,mode=1777)
tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755)
none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880)
none on /run/shm type tmpfs (rw,nosuid,nodev)
none on /run/user type tmpfs (rw,noexec,nosuid,nodev,size=104857600,mode=0755)
tmpfs on /var/tmp type tmpfs (rw,noatime,mode=1777)
tmpfs on /var/log type tmpfs (rw,noatime,mode=0755)
tmpfs on /var/log/apt type tmpfs (rw,noatime)
/dev/sdb9 on /home/99sono/Documents/workspaceEclipse type ext4 (rw,nosuid,nodev,errors=remount-ro) [EclipseWorkspace]
/dev/sdb5 on /home/99sono/Dropbox type ext4 (rw,nosuid,nodev,errors=remount-ro) [Dropbox]
/dev/sdb6 on /home/99sono/Downloads type ext4 (rw,nosuid,nodev,errors=remount-ro) [Download]
/dev/sdb7 on /home/99sono/SpiderOak type ext4 (rw,noexec,nosuid,nodev,errors=remount-ro) [SpiderOak]
/dev/sdb8 on /var/cache type ext4 (rw,noatime,nodiratime,errors=remount-ro) [VarCache]

(sda would be SSD sdb, is a plain usual SATA disk)

According to all indications, It would appear that I have hardware problems... but in reality, i highly doubt it, the SSD has viratully no use and OCZ SSDs are reputed to be of top quality. So, unless OCZ has an underserved reputation, the ssd should still be in mint condition.

dmesg lists log messages such as (sda1 would be the root partition):
1689 [ 6717.553653] Buffer I/O error on device sda1, logical block 1218984
  1690 [ 6717.553655] Buffer I/O error on device sda1, logical block 1218985
  1691 [ 6717.553657] Buffer I/O error on device sda1, logical block 1218986
  1692 [ 6717.553659] Buffer I/O error on device sda1, logical block 1218987
  1693 [ 6717.553661] Buffer I/O error on device sda1, logical block 1218988
  1694 [ 6717.553663] Buffer I/O error on device sda1, logical block 1218989
  1695 [ 6717.553665] Buffer I/O error on device sda1, logical block 1218990
  1696 [ 6717.553667] Buffer I/O error on device sda1, logical block 1218991
  1697 [ 6717.553669] Buffer I/O error on device sda1, logical block 1218992
  1698 [ 6717.553671] Buffer I/O error on device sda1, logical block 1218993
  1699 [ 6717.553673] Buffer I/O error on device sda1, logical block 1218994
  1700 [ 6717.553675] Buffer I/O error on device sda1, logical block 1218995
  1701 [ 6717.553677] Buffer I/O error on device sda1, logical block 1218996
  1702 [ 6717.553679] Buffer I/O error on device sda1, logical block 1218997
  1703 [ 6717.553681] Buffer I/O error on device sda1, logical block 1218998
  1704 [ 6717.553683] Buffer I/O error on device sda1, logical block 1218999
  1705 [ 6717.553685] Buffer I/O error on device sda1, logical block 1219000
  1706 [ 6717.553687] Buffer I/O error on device sda1, logical block 1219001
  1707 [ 6717.553688] Buffer I/O error on device sda1, logical block 1219002
  1708 [ 6717.553690] Buffer I/O error on device sda1, logical block 1219003
  1709 [ 6717.553693] Buffer I/O error on device sda1, logical block 1219004
  1710 [ 6717.553695] Buffer I/O error on device sda1, logical block 1219005
  1711 [ 6717.553697] Buffer I/O error on device sda1, logical block 1219006
1758 [ 6717.553790] Buffer I/O error on device sda1, logical block 1219053
  1759 [ 6717.553793] EXT4-fs warning (device sda1): ext4_end_bio:250: I/O error writing to inode 1970257 (offset 228065280 size 450560 starting block 1219310)
  1760 [ 6717.553799] sd 1:0:0:0: [sda]
  1761 [ 6717.553800] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
  1762 [ 6717.553802] sd 1:0:0:0: [sda]
  1763 [ 6717.553804] Sense Key : Aborted Command [current] [descriptor]
  1764 [ 6717.553806] Descriptor sense data with sense descriptors (in hex):
  1765 [ 6717.553807] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
  1766 [ 6717.553815] 0a 80 09 30
  1767 [ 6717.553819] sd 1:0:0:0: [sda]
  1768 [ 6717.553820] Add. Sense: No additional sense information
  1769 [ 6717.553822] sd 1:0:0:0: [sda] CDB:
  1770 [ 6717.553824] Write(10): 2a 00 0a 2b f9 b0 00 00 08 00
  1771 [ 6717.553830] end_request: I/O error, dev sda, sector 170654128
  1772 [ 6717.553833] Buffer I/O error on device sda1, logical block 21331510
  1773 [ 6717.553836] EXT4-fs warning (device sda1): ext4_end_bio:250: I/O error writing to inode 2759709 (offset 0 size 4096 starting block 21331767)
  1774 [ 6717.553841] sd 1:0:0:0: [sda]
  1775 [ 6717.553843] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
  1776 [ 6717.553845] sd 1:0:0:0: [sda]
  1777 [ 6717.553846] Sense Key : Aborted Command [current] [descriptor]
  1778 [ 6717.553849] Descriptor sense data with sense descriptors (in hex):
  1779 [ 6717.553850] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
  1780 [ 6717.553858] 0a 80 09 30
  1781 [ 6717.553861] sd 1:0:0:0: [sda]
  1782 [ 6717.553863] Add. Sense: No additional sense information
  1783 [ 6717.553865] sd 1:0:0:0: [sda] CDB:
  1784 [ 6717.553866] Write(10): 2a 00 00 81 0e c8 00 00 08 00
  1785 [ 6717.553873] end_request: I/O error, dev sda, sector 8457928
  1786 [ 6717.553875] Buffer I/O error on device sda1, logical block 1056985
  1787 [ 6717.553878] EXT4-fs warning (device sda1): ext4_end_bio:250: I/O error writing to inode 2759709 (offset 458752 size 4096 starting block 1057242)
  1788 [ 6717.553883] sd 1:0:0:0: [sda]
  1789 [ 6717.553884] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
  1790 [ 6717.553887] sd 1:0:0:0: [sda]
  1791 [ 6717.553888] Sense Key : Aborted Command [current] [descriptor]
  1792 [ 6717.553890] Descriptor sense data with sense descriptors (in hex):
  1793 [ 6717.553891] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
  1794 [ 6717.553899] 0a 80 09 30
  1795 [ 6717.553902] sd 1:0:0:0: [sda]

....
2028 [ 6717.554576] Sense Key : Aborted Command [current] [descriptor]
  2029 [ 6717.554578] Descriptor sense data with sense descriptors (in hex):
  2030 [ 6717.554579] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
  2031 [ 6717.554587] 0a 80 09 30
  2032 [ 6717.554591] sd 1:0:0:0: [sda]
  2033 [ 6717.554592] Add. Sense: No additional sense information
  2034 [ 6717.554594] sd 1:0:0:0: [sda] CDB:
  2035 [ 6717.554595] Write(10): 2a 00 0a 80 09 30 00 00 08 00
  2036 [ 6717.554602] end_request: I/O error, dev sda, sector 176163120
  2037 [ 6717.554608] ata2: EH complete
  2038 [ 6717.554893] JBD2: Detected IO errors while flushing file data on sda1-8
  2039 [ 6725.996860] EXT4-fs error (device sda1) in ext4_new_inode:935: IO failure
  2040 [ 6725.996867] EXT4-fs (sda1): previous I/O error to superblock detected
  2041 [ 6725.996984] Aborting journal on device sda1-8.

And then The Grand finally.
  2042 [ 6725.997084] EXT4-fs (sda1): Remounting filesystem read-only
  2043 [ 6725.997096] EXT4-fs error (device sda1) in ext4_create:2120: IO failure

I restart the system, get told there were file system errors, press F to try to fix, and in a couple of hours if I see a movie or start working on Eclipse, well, same story.