public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Noah L. Meyerhans" <frodo@morgul.net>
To: linux-kernel@vger.kernel.org
Subject: ext3 related oops in 2.4.{18,20} on sparc
Date: Mon, 6 Jan 2003 22:36:47 -0500	[thread overview]
Message-ID: <20030107033647.GD25227@morgul.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 1332 bytes --]

I consistantly get a kernel oops in 2.4.18 and 2.4.20 on my SPARC Ultra
1 when copying lots of data between two filesystems on the same disk.
The latest command I've been using is: "cd /mnt && rsync -var /usr/ ."
The command runs for a while, copying data, but then, before it
completes, rsync dies with the following error:
rsync: error writing 25 unbuffered bytes - exiting: Broken pipe
rsync error: error in rsync protocol data stream (code 12) at io.c(463)
rsync: error writing 69 unbuffered bytes - exiting: Broken pipe
rsync error: error in rsync protocol data stream (code 12) at io.c(463)

and an oops is generated.  The machine still seems to run OK, though I
can't unmount the destination filesystem.

The oops message is attached, having been decoded with ksymoops.  I
don't have any reason to believe there are hardware issues with this
machine.  It has been very reliable for quite some time, and there are
no signs of problems up to the very instant that the oops is generated,
which seems to happen at a different point in the copying process each
time.

Thanks for any help you can offer.  Let me know if you need more info.

noah

-- 
 _______________________________________________________
| Web: http://web.morgul.net/~frodo/
| PGP Public Key: http://web.morgul.net/~frodo/mail.html 

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

             reply	other threads:[~2003-01-07  3:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-07  3:36 Noah L. Meyerhans [this message]
2003-01-07  3:39 ` ext3 related oops in 2.4.{18,20} on sparc Noah L. Meyerhans

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=20030107033647.GD25227@morgul.net \
    --to=frodo@morgul.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox