All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rupert Heesom <raheesom@navpoint.com>
To: linux-lvm@sistina.com
Subject: [linux-lvm] CDRECORD not working when LVM loaded.
Date: 16 Apr 2001 23:34:20 -0400	[thread overview]
Message-ID: <200104170441.f3H4fuW29720@west.navpoint.com> (raw)

I'm running a RH7 system on which I have the Logical Volume Management
of kernel 2.4.3 installed,but not configured (LVM not doing anything
yet).

I had some trouble using cdrecord, and saw the man page for cdrecord,
particularly the following part where it says that cdrecord cannot be
used in conjunction with volume management.

I don't really know what  is meant in the paragraph about USCSI fallback
SCSI transport code.


        On Solaris you need to stop the volume management  if  you
        like  to  use the USCSI fallback SCSI transport code. Even
        things like cdrecord -scanbus will not work if the  volume
        management is running.


I unloaded the "lvm-mod" kernel module, and cdrecord works fine without
it.

Basically I'm merely trying to find out whether I can get my system
working with both LVM and cdrecord concurrently.

I assume in order to use LVM, I would need to keep the lvm kernel module
loaded.   Since I had to unload this module in order to use cdrecord, I
assume that I can only use cdrecord OR LVM on any one system.   Am I
correct here?

Is there any workaround for my situation?  Perhaps not using the USCSI
fallback code when using cdrecord?


-- 
regs
rupert

             reply	other threads:[~2001-04-17  3:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-17  3:34 Rupert Heesom [this message]
2001-04-17  5:33 ` [linux-lvm] CDRECORD not working when LVM loaded Jay Weber
2001-04-17  5:53 ` Andreas Dilger

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=200104170441.f3H4fuW29720@west.navpoint.com \
    --to=raheesom@navpoint.com \
    --cc=linux-lvm@sistina.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 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.