Hello,
On Sep/24/2008, Phil wrote:
> Just a wild guess but, did you perhaps change the filesystem to a
> journalling filsystem when moving to the different server?
mount reports the same (ext3)
> I once accidently moved my database from an ext2 to an ext3 partition and it
> took me a while to figure out the degradation of queries..
I have problems reading (selecting) and without any writing disk
activity (I mean, no temporary tables, etc.). Journaling could affect
writing but not reading, no?
But I already thought about it :-) and tune2fs -l /dev/partition in both
servers reports something different:
New one:
Filesystem features: has_journal resize_inode dir_index filetype
needs_recovery sparse_super large_file
Old one:
Filesystem features: has_journal filetype needs_recovery
sparse_super large_file
I think that this "resize_inode" is not a problem. I don't know why
appears "needs_recovery". Both filesystems are "Clean", etc.
Thanks for your idea, do we have more ideas? :-) or anything else to
check...
--
Carles Pina i Estany GPG id: 0x17756391
http://pinux.info
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
