From: Jens Axboe <axboe@suse.de>
To: cacook@freedom.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: Writing to Pana DVD-RAM
Date: Sun, 15 Apr 2001 16:20:01 +0200 [thread overview]
Message-ID: <20010415162001.E1982@suse.de> (raw)
In-Reply-To: <20010414213259Z132548-682+222@vger.kernel.org> <3AD8CC04.EA5022C1@coplanar.net> <20010415135500Z132658-682+339@vger.kernel.org>
In-Reply-To: <20010415135500Z132658-682+339@vger.kernel.org>; from cacook@freedom.net on Sun, Apr 15, 2001 at 07:53:22AM -0600
On Sun, Apr 15 2001, cacook@freedom.net wrote:
> DOH! You're right.
>
> I can now write to it, but only get one chance. Copy a file to
> DVDRAM, read, print, etc, but when I try to rm or mv, segfault.
> Foreverafter the DVDRAM is 'busy'. Cannot umount. Must reboot then
> umount. Remount, get another write, but on subsequent write,
> segfault.
Please decode that oops and send it along, see REPORTING-BUGS
--
Jens Axboe
next prev parent reply other threads:[~2001-04-15 14:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-14 21:31 Writing to Pana DVD-RAM cacook
2001-04-14 22:15 ` Jeremy Jackson
2001-04-15 13:53 ` cacook
2001-04-15 14:20 ` Jens Axboe [this message]
[not found] ` <20010416153103.5D6F11E0FC@Cantor.suse.de>
2001-04-16 16:28 ` Problem: " Jens Axboe
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=20010415162001.E1982@suse.de \
--to=axboe@suse.de \
--cc=cacook@freedom.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