Scheduler? filesystem?

[ShadowAce]

I recently performed a clean install of Fedora 12 on my Sager 8890.
I backed up my /home dir beforehand using rsync without any problems to an external 320G USB drive.
With F12 installed, I proceeded to restore my /home dir using rsync again.

The script works fine--it's been tested through previous installs without issue.

The symptom:

The rsync process starts up just fine and begins copying files over at ~10-20MB/s--just fine.

After a file hits ~145G transferred, rsync suddenly slows to ~2-3MB/s, and also hangs for periods of time. While the transfer eventually completes, it takes MUCH longer than it should. Also, tje CPU starts getting very busy.

top and htop show nothing out of the ordinary.

Here is the output from /var/log/messages when the slowdown happens:

EXT3 FS on sdc1, internal journal
Dec 4 13:06:24 localhost kernel: EXT3-fs: mounted filesystem with ordered data mode.
Dec 4 13:07:20 localhost kernel: ata4: lost interrupt (Status 0x51)
Dec 4 13:07:20 localhost kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Dec 4 13:07:20 localhost kernel: ata4.00: cmd ca/00:00:77:80:32/00:00:00:00:00/e5 tag 0 dma 131072 out
Dec 4 13:07:20 localhost kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec 4 13:07:20 localhost kernel: ata4.00: status: { DRDY }
Dec 4 13:07:20 localhost kernel: ata4: soft resetting link
Dec 4 13:07:20 localhost kernel: ata4.00: configured for UDMA/100
Dec 4 13:07:20 localhost kernel: ata4.00: device reported invalid CHS sector 0
Dec 4 13:07:20 localhost kernel: ata4: EH complete
Dec 4 13:07:22 localhost kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
Dec 4 13:07:22 localhost kernel: ata4.00: BMDMA stat 0x4
Dec 4 13:07:22 localhost kernel: ata4.00: cmd ca/00:00:bf:02:35/00:00:00:00:00/e5 tag 0 dma 131072 out
Dec 4 13:07:22 localhost kernel: res 51/84:01:be:03:35/00:00:00:00:00/e5 Emask 0x10 (ATA bus error)
Dec 4 13:07:22 localhost kernel: ata4.00: status: { DRDY ERR}
Dec 4 13:07:22 localhost kernel: ata4.00: error: { ICRC ABRT }
Dec 4 13:07:22 localhost kernel: ata4: soft resetting link
Dec 4 13:07:22 localhost kernel: ata4.00: configured for UDMA/100
Dec 4 13:07:22 localhost kernel: ata4: EH complete
Dec 4 13:07:23 localhost kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
Dec 4 13:07:23 localhost kernel: ata4.00: BMDMA stat 0x4
Dec 4 13:07:23 localhost kernel: ata4.00: cmd ca/00:00:bf:62:35/00:00:00:00:00/e5 tag 0 dma 131072 out
Dec 4 13:07:23 localhost kernel: res 51/84:01:be:63:35/00:00:00:00:00/e5 Emask 0x10 (ATA bus error)
Dec 4 13:07:23 localhost kernel: ata4.00: status: { DRDY ERR }
Dec 4 13:07:23 localhost kernel: ata4.00: error: { ICRC ABRT }
Dec 4 13:07:23 localhost kernel: ata4: soft resetting link
Dec 4 13:07:23 localhost kernel: ata4.00: configured for UDMA/100
Dec 4 13:07:23 localhost kernel: ata4: EH complete
Dec 4 13:07:54 localhost kernel: ata4: lost interrupt (Status 0x51)
Dec 4 13:07:54 localhost kernel: ata4.00: limiting speed to UDMA/66:PIO4
Dec 4 13:07:54 localhost kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Dec 4 13:07:54 localhost kernel: ata4.00: cmd ca/00:00:bf:e2:35/00:00:00:00:00/e5 tag 0 dma 131072 out
Dec 4 13:07:54 localhost kernel: res 40/00:01:be:63:35/00:00:00:00:00/e5 Emask 0x4 (timeout)
Dec 4 13:07:54 localhost kernel: ata4.00: status: { DRDY }
Dec 4 13:07:54 localhost kernel: ata4: soft resetting link
Dec 4 13:07:54 localhost kernel: ata4.00: configured for UDMA/66
Dec 4 13:07:54 localhost kernel: ata4: EH complete
Dec 4 13:08:26 localhost kernel: ata4: lost interrupt (Status 0x51)
Dec 4 13:08:26 localhost kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Dec 4 13:08:26 localhost kernel: ata4.00: cmd ca/00:00:bf:a2:37/00:00:00:00:00/e5 tag 0 dma 131072 out
Dec 4 13:08:26 localhost kernel: res 40/00:01:be:63:35/00:00:00:00:00/e5 Emask 0x4 (timeout)
Dec 4 13:08:26 localhost kernel: ata4.00: status: { DRDY }
Dec 4 13:08:26 localhost kernel: ata4: soft resetting link
Dec 4 13:08:26 localhost kernel: ata4.00: configured for UDMA/66
Dec 4 13:08:26 localhost kernel: ata4: EH complete
Dec 4 13:09:59 localhost ntpd[1292]: synchronized to 207.171.7.152, stratum 2
Dec 4 13:14:02 localhost pcscd: winscard.c:309:SCardConnect() Reader E-Gate 0 0 Not Found
Dec 4 13:14:02 localhost pcscd: winscard.c:309:SCardConnect() Reader E-Gate 0 0 Not Found
Dec 4 13:14:02 localhost pcscd: winscard.c:309:SCardConnect() Reader E-Gate 0 0 Not Found
Dec 4 13:14:02 localhost pcscd: winscard.c:309:SCardConnect() Reader E-Gate 0 0 Not Found


Can someone please interpret this for me? Is it the scheduler, the EXT-3 filesystem on a EXT-4 system?

Thanks!

[ShadowAce]

As a follow-up, I tried a standard "cp" command as well. I am getting the same behavior.

Also, this is the i686 version of Fedora 12.

[ShadowAce]

I have performed the following actions:
I moved the disk (MyBook 320G) to a Ubuntu 8.04 machine, and tested it there. It works flawlessly.
I tried to downgrade my kernel from 2.6.31.6-166 to 2.6.31.5-127. Still have no luck.

Any guesses out there?

[CSchwangler]

What file system do you have on Ubuntu 8.04? Maybe this is an issue of ext4?

[ShadowAce]

The Ubuntu 8.04 system has a ext3 file system, so you may be correct.