From: Aric Cyr <Aric.Cyr@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.13 (was 2.6.11.11) and rsync oops (SATA or NFS related?)
Date: Wed, 7 Sep 2005 04:00:16 +0000 (UTC) [thread overview]
Message-ID: <loom.20050907T055454-169@post.gmane.org> (raw)
In-Reply-To: <dfjjp9$f7k$1@sea.gmane.org>
Kalin KOZHUHAROV <kalin <at> thinrope.net> writes:
>
> A closer examination of the drive:
> (Model=ST3300831AS, FwRev=3.03, SerialNo=3NF07KA1 )
> and why is it so slow revealed that it was running not in UDMA.
>
> Got one total oops, even no logs were written to disk.
> Seems that rsync-ing huge amounts of data (200 GB in *many* small files)
streses the system too much.
It seems that you are using the IDE-SATA driver... perhaps you should try the
SCSI-SATA (i.e. libata)? The IDE one is deprecated and should no longer be
used. Disable SATA from in the IDE menu and enable the SCSI libata driver for
your chipset (in the scsi kernel menu).
Also the reason you don't get higher UDMA modes is because your drive is a
blacklisted seagate. There are known problems with some of those drives, and so
they are downgraded to slower modes (this was mentioned in your kernel log if
you look closely). If you upgrade the BIOS on your harddrive, you _might_ be
able to remove the drive from the blacklist in the kernel to improve
performance... this may be dangerous however, so don't complain if you lose your
data.
next prev parent reply other threads:[~2005-09-07 4:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-05 0:17 2.6.11.11 and rsync oops (SATA related?) Kalin KOZHUHAROV
2005-09-05 8:13 ` 2.6.13 (was 2.6.11.11) and rsync oops (SATA or NFS related?) Kalin KOZHUHAROV
2005-09-05 14:12 ` Kalin KOZHUHAROV
2005-09-06 8:24 ` Kalin KOZHUHAROV
2005-09-07 4:00 ` Aric Cyr [this message]
2005-09-07 17:22 ` Kalin KOZHUHAROV
2005-09-08 2:37 ` Aric Cyr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=loom.20050907T055454-169@post.gmane.org \
--to=aric.cyr@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®