Bug#563602: I had a similar issue

2010-01-13 Thread Виталий Филиппов

Hi!

The problem was much simpler: I had partially broken hardware (RAM module)
on that server =)
Database corruption was probably caused simply by some changes of memory
read/write activity on the resync under load.
All the same, thank you for the answer! And sorry for incorrect bug report
:)

--
With best regards,
Vitaliy Filippov



--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#563602: I had a similar issue

2010-01-12 Thread Виталий Филиппов

Hi!

I was running MySQL InnoDB databases on mdadm RAID5 partition with XFS  
file system when I discovered that if /etc/cron.d/mdadm (checkarray) of  
this partition concurs with some database updates, database file is  
corrupted and needs some kind of recovery, which is not always simple.


This bug does reproduce on my server with, for example, on FeedOnFeeds  
database (server-side rss aggregator) when it's cronjob is updating rss  
feeds.


RAID array, though, does not degrade, and it seems that MyISAM  
(non-transactional) tables are OK even when checkarray concurs with  
database updates. So I suppose the data loss is caused by some  
sync/barrier issues... Is that so? And if so, what I'm supposed to do to  
get rid of this problem?


--
With best regards,
  Vitaliy Filippov



--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#563602: I had a similar issue

2010-01-12 Thread martin f krafft
also sprach Виталий Филиппов vfilip...@custis.ru [2010.01.13.0028 +1300]:
 I was running MySQL InnoDB databases on mdadm RAID5 partition with
 XFS file system when I discovered that if /etc/cron.d/mdadm
 (checkarray) of this partition concurs with some database updates,
 database file is corrupted and needs some kind of recovery, which
 is not always simple.

There is no way that mdadm's checking of arrays can interfere with
your filesystem operations. It's more likely that MySQL loses data.

 RAID array, though, does not degrade, and it seems that MyISAM
 (non-transactional) tables are OK even when checkarray concurs with
 database updates. So I suppose the data loss is caused by some
 sync/barrier issues... Is that so? And if so, what I'm supposed to do
 to get rid of this problem?

Barriers are only really relevant if you lose the power at some
point and the system reboots. Is that what happened?

-- 
martin | http://madduck.net/ | http://two.sentenc.es/
 
a bachelor is a man who never made the same mistake once.
 
spamtraps: madduck.bo...@madduck.net


digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/)