cdrdao-devel

[Cdrdao-devel] On the fly copy in multiple lun devices

[Manuel C. <ll...@ja...>]

Hi all,

In order to prevent an on the fly copy with the same device, I will look 
for this situation. So I will check if the user has selected the same 
device in both Reader and Writer DeviceList.

        if ((targetData->bus == sourceData->bus)
         && (targetData->id == sourceData->id)
         && (targetData->lun == sourceData->lun))

While this is correct for me, I don't know if you can do an on the fly 
copy with different luns on a same device :-?, I think you can only have 
access to one lun at a time, but not sure, so then this should be:

        if ((targetData->bus == sourceData->bus)
         && (targetData->id == sourceData->id))

Anyone can asure me that the last is the correct one?

Thanks.

--
Manuel Clos
ll...@ja...

* Si no puedes hacerlo bien, hazlo bonito (Bill Gates)
* If you can't do it well, do it nice (Bill Gates)

Re: [Cdrdao-devel] On the fly copy in multiple lun devices

[Andreas M. <an...@da...>]

Manuel Clos wrote:

> In order to prevent an on the fly copy with the same device, I will look
> for this situation. So I will check if the user has selected the same
> device in both Reader and Writer DeviceList.
> 
>         if ((targetData->bus == sourceData->bus)
>          && (targetData->id == sourceData->id)
>          && (targetData->lun == sourceData->lun))
> 
> While this is correct for me, I don't know if you can do an on the fly
> copy with different luns on a same device :-?, I think you can only have
> access to one lun at a time, but not sure, so then this should be:
> 
>         if ((targetData->bus == sourceData->bus)
>          && (targetData->id == sourceData->id))
> 
> Anyone can asure me that the last is the correct one?

I'm not sure about the luns. Disk-changer drives usually provide
a lun for each slot and for them we surely have no parallel access.
I've never seen disk-changer writers up to now, though. I would
say the latter test is safer and shouldn't hurt the majority
of the users. We can change the code later whenever we make the
experience that our assumption was wrong.


Andreas
-- 
Andreas Mueller                  Tel: +49 89 67808848
Ramsmeierstr. 1                Email: an...@da...
85579 Neubiberg, Germany