Hi, Does anyone know why the ext3 code in the 2.6 kernel series seems to bitch so much about one of my partitions when it gets some I/O errors, and then aborts the journal and in doing so turns that partition to read-only. I ran 2.6.0.11r2 for about 2 days w/no problem till it happed multiple times in succession and forced me to reboot each time that I had to switch back to 2.4.20....and in the end upgraded to the newer 2.4.22 instead.
The disk errors do not show up when I am in 2.4 and even when some do appear, no journal aborting occurs. I mean the partition which is causing the errors probably does have some issues with it, I mean cos it burps with I/O errors every now and then when I manually run a fsck on it and once even a S.M.A.R.T warning...I am not worried too much becuase it has never lost any data from it and I have recent backups...well to be honest I am just buying time to buy a new hd early next year..I guess the 2.6 kernel doesn;t want me to do that? Simon -- [EMAIL PROTECTED] mailing list
