From: Andrew Morton <akpm@osdl.org>
To: nkiesel@tbdnetworks.com (Norbert Kiesel)
Cc: bfennema@falcon.csc.calpoly.edu, linux-kernel@vger.kernel.org
Subject: Re: OOPS in UDF
Date: Fri, 23 Jun 2006 17:50:33 -0700 [thread overview]
Message-ID: <20060623175033.664ddcce.akpm@osdl.org> (raw)
In-Reply-To: <20060615155828.GA14257@defiant.tbdnetworks.com>
On Thu, 15 Jun 2006 08:58:28 -0700
nkiesel@tbdnetworks.com (Norbert Kiesel) wrote:
> I just got an OOPS while copying between two loopback-mounted UDF filesystems.
> One or both of the UDF file systems are corrupted (some files not readable by
> root), but kernel should not OOPS anyway.
>
> I get the corrupted file systems reliably by rsync'ing big directories onto the
> UDF filesystem (while trying to prepare a backup DVD). I saw the OOPS only once
> so far. The system continued to work after the OOPS.
Are you able to get a copy of one of these filesystem images up onto a
server somewhere so others can reproduce the crash?
next prev parent reply other threads:[~2006-06-24 0:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-15 15:58 Norbert Kiesel
2006-06-24 0:50 ` Andrew Morton [this message]
2006-06-24 1:22 ` Norbert Kiesel
2006-06-25 1:40 ` Norbert Kiesel
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=20060623175033.664ddcce.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=bfennema@falcon.csc.calpoly.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=nkiesel@tbdnetworks.com \
/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®