From: Kalin KOZHUHAROV <kalin@thinrope.net>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.13 (was 2.6.11.11) and rsync oops (SATA or NFS related?)
Date: Mon, 05 Sep 2005 23:12:15 +0900 [thread overview]
Message-ID: <dfhjp3$fd4$1@sea.gmane.org> (raw)
In-Reply-To: <dfguoq$eng$1@sea.gmane.org>
Kalin KOZHUHAROV wrote:
> Kalin KOZHUHAROV wrote:
>
>> Hi, there.
>> Long time no posting - didn't have kernel problems for long time :-)
>>
>> That is why I am still running 2.6.11.11 (2.6.12 elsewhere). Will move
>> to 2.6.13 soon.
>>
>> Yesterday just bought a new SATAII drive (Seagate Barracuda 7200.8
>> ST3300831AS) and while trying to rsync some data from the old drives the
>> rsync process died with segfault. My SiI3112 controller is not SATAII,
>> but it should work in SATA mode, have another drive for year+. Looking
>> at the dmesg I saw 3 oopses (see the shortened .dmesg file). Run the
>> ksymoops and got some output (see .ksymoops.bz2).
>>
>> Although it does not seem very related to the drive, that is the only
>> recent change in hardware, in software: udev . The machine (MB: A7V8X
>> Deluxe) was working stable for 6 months with a few restarts.
>>
>> As far as reproducibility goes, apart from those 3 oopses everything is
>> OK, didn't even have to restart and am now continuing to rsync some
>> 200GB more.
>>
>> Any ideas as to what caused this?
>
>
> OK, I upgraded to the latest 2.6.13 kernel and still got (similar?) oops.
>
> Looking again at it it might be NFS (using v4 recently) related.
After stopping nfs (both v3 and v4) and rebooting, I could finish the
required 170GB rsync without more oopses. But I am still not convinced
whether this is a nfs issue or just I am being lucky this time. Will
keep on eye on the machine and report here again.
Kalin.
/ When nobody answers, try answering yourself :-| /
--
|[ ~~~~~~~~~~~~~~~~~~~~~~ ]|
+-> http://ThinRope.net/ <-+
|[ ______________________ ]|
next prev parent reply other threads:[~2005-09-05 14:15 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 [this message]
2005-09-06 8:24 ` Kalin KOZHUHAROV
2005-09-07 4:00 ` Aric Cyr
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='dfhjp3$fd4$1@sea.gmane.org' \
--to=kalin@thinrope.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.