***BOGO*** Re: myisamchk makes file system go read-only

["Ben Lavender" <blavender@xxxxxxxxx>]

There were indeed plenty of errors when fsck ran, but the filesystem
wasn't noticing it at mount time--perhaps because this filesystem
wasn't in fstab, as it was managed by heartbeat.

Whether the root was DRBD or hardware has yet to be seen, but I'm
running at the moment and can sort this out on a 'hurry' timeframe
instead of 'emergency'.  Thanks.

Ben

On Tue, May 27, 2008 at 6:58 PM, Kevin Hunter <hunteke@xxxxxxxxxxx> wrote:
> At 12:32p -0400 on Tue, 27 May 2008, Gerald L. Clark wrote:
>> Ben Lavender wrote:
>>> For whatever reason, running myisamchk makes the filesystem become
>>> read-only.  The only thing I can do is shut down Mysql, unmount the
>>> file system, remount it, and restart Mysql.  I'm currently walking on
>>> eggshells, and the site that I'm trying to correct here is offline.
>
>>> This file system was originally running on DRBD, but I've taken that
>>> out of the loop at this point, so this is just mounting a straight LVM
>>> partition.  The file system is ext3.    Myisamchk -o does the same
>>> thing.
>
>> Run fsck on the filesystem. It is probably marked as crashed.
>
> Indeed.  This likely isn't a myisamchk problem rather a
> bad-hardware/disk problem.  Do you have a 'errors=remount-ro' (Remount
> Read Only when errors occur) in /etc/fstab for that filesystem?
> myisamchk is probably just accessing a bad sector or more, so the
> filesystem driver says "Whoa, raise shields!"
>
> Likely time to utilize those backups, and get a new drive.
>
> Kevin
>

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/mysql?unsub=royale@xxxxxxxxxx