Mounted partition is suddenly read only

[JD]

On 12/18/2012 04:05 AM, Steve Flynn wrote:
> On 18 December 2012 05:38, JD <jd1008 at gmail.com 
> <mailto:jd1008 at gmail.com>> wrote:
>
>     Rebooting into rescue mode, running fsck and then going multiuser
>     works, but only for a while (i.e. until I leave the system idle
>     for a while),
>     and the issue repeats itself.
>
>
>
> Nothing in the syslog to give any indication when/why the filesystem 
> was remounted?
>
> I take it this drive is one of the ones you mentioned a few days ago, 
> when we discussed brute force ways to keep the buggers awake when they 
> won't/can't listen to hdparm instructions to stay awake and suchlike.
> -- 
> Steve
>
> When one person suffers from a delusion it is insanity. When many 
> people suffer from a delusion it is called religion.
>
>
>
Yes Steve, it is one of those drives.
The problem is, only ONE mounted partition out of 4 mounted partitions
of the drive got remounted read only. The other ones remained read/write.
So, it is not the case that the drive went to sleep.

I really should have looked at syslog. My bad!!
Syslog says:

syslog.1:Dec 17 19:12:34 cme kernel: [160907.464516] Aborting journal on 
device sdb3.
syslog.1:Dec 17 19:12:34 cme kernel: [160907.464611] EXT3-fs (sdb3): 
error in ext3_reserve_inode_write: Journal has aborted
syslog.1:Dec 17 19:12:34 cme kernel: [160907.464617] EXT3-fs (sdb3): 
error: remounting filesystem read-only
syslog.1:Dec 17 21:43:58 cme kernel: [169991.763211] EXT3-fs (sdb3): 
error: ext3_remount: Abort forced by user
syslog.1:Dec 17 21:59:22 cme kernel: [170915.743954] EXT3-fs (sdb3): 
error: ext3_remount: Abort forced by user
syslog.1:Dec 17 22:01:25 cme kernel: [171039.429121] EXT3-fs (sdb3): 
error: ext3_remount: Abort forced by user
syslog.1:Dec 17 22:29:57 cme kernel: [172750.931413] EXT3-fs (sdb3): 
error: ext3_remount: Abort forced by user
syslog.1:Dec 17 22:44:59 cme kernel: [173653.286490] EXT3-fs (sdb3): 
error: ext3_put_super: Couldn't clean up the journal
syslog.1:Dec 17 22:49:54 cme kernel: [173948.443870] EXT3-fs (sdb3): 
using internal journal
syslog.1:Dec 17 22:49:54 cme kernel: [173948.443877] EXT3-fs (sdb3): 
mounted filesystem with ordered data mode

And so I wonder what caused
EXT3-fs (sdb3): error in ext3_reserve_inode_write: Journal has aborted ?

Guess I will be googling this for a while :)