All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Olaf Fr?czyk <olaf@cbk.poznan.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.3 BUG - can't write DVD-RAM - reported as write-protected
Date: Fri, 5 Mar 2004 09:23:50 +0100	[thread overview]
Message-ID: <20040305082350.GO31750@suse.de> (raw)
In-Reply-To: <1078434953.1961.13.camel@venus.local.navi.pl>

On Thu, Mar 04 2004, Olaf Fr?czyk wrote:
> Hi,
> I switched to 2.6.3 from 2.4.x serie.
> When I mount DVD-RAM it is mounted read-only:
> 
> [root@venus olaf]# mount /dev/dvdram /mnt/dvdram
> mount: block device /dev/dvdram is write-protected, mounting read-only
> [root@venus olaf]#
> 
> In 2.4 it is mounted correctly as read-write.
> 
> Drive: Panasonic LF-201, reported in Linux as:
> MATSHITA        DVD-RAM LF-D200         A120
> 
> SCSI controller: Adaptec 2940U2W

What does cat /proc/sys/dev/cdrom/info say? Do you get any kernel
messages in dmesg when the rw mount fails?

-- 
Jens Axboe


  reply	other threads:[~2004-03-05  8:23 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-04 21:15 2.6.3 BUG - can't write DVD-RAM - reported as write-protected Olaf Frączyk
2004-03-05  8:23 ` Jens Axboe [this message]
2004-03-05 11:45   ` Olaf Frączyk
2004-03-05 20:51     ` Daniel Egger
2004-03-07 10:59     ` Jens Axboe
2004-03-09  7:59       ` Olaf Frączyk
2004-03-09  9:12         ` Jens Axboe
2004-03-11  1:48           ` Thomas Duda
2004-03-12 20:03             ` News on: " Thomas Duda
2004-03-12 20:03               ` Thomas Duda
2004-03-14 11:17           ` Olaf Frączyk
2004-03-14 11:22             ` Jens Axboe
2004-03-14 11:23               ` Jens Axboe
2004-03-23 14:50               ` Olaf Frączyk
2004-03-23 15:23                 ` Jens Axboe
2004-03-23 15:36                   ` Olaf Frączyk
2004-03-23 15:32                 ` Olaf Frączyk

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=20040305082350.GO31750@suse.de \
    --to=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olaf@cbk.poznan.pl \
    /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.