linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
* [linux-lvm] CDRECORD not working when LVM loaded.
@ 2001-04-17  3:34 Rupert Heesom
  2001-04-17  5:33 ` Jay Weber
  2001-04-17  5:53 ` Andreas Dilger
  0 siblings, 2 replies; 3+ messages in thread
From: Rupert Heesom @ 2001-04-17  3:34 UTC (permalink / raw)
  To: linux-lvm

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2001-04-17  5:53 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2001-04-17  3:34 [linux-lvm] CDRECORD not working when LVM loaded Rupert Heesom
2001-04-17  5:33 ` Jay Weber
2001-04-17  5:53 ` Andreas Dilger

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).