Re: [SSI] /devfs

[Bruce W. <br...@ka...>]

Aneesh,
  John is on vacation today.  He may respond Monday if I get it wrong.
The issue is how we did remote device access.  In NSC, and thus SSI, we
do the remote device access at the vnode/inode level, which gives access for
all sorts of devices.  The other approach is to do it at the device switch
level, which is what TruClusters does for disk devices.  There are
advantages and disadvantages to both approaches.  One disadvantage of
the vnode/inode level is that any kernel subsystem accessing a device
directly at the devswitch level won't work to remote devices.  Filesytems
have such a feature, which means in SSI, the filesystem code must
run on the node that has the device driver.  In NSC, I believe we 
caught the mount system call and transparently made it happen on the
correct node for the device.  Apparently we haven't done that in SSI
yet.

bruce

> 
> I tried to mount the cdrom from  both the node. The cdrom is located on
> node1 and when I try to mount it on node2 it gives me the s error "no
> medium "
> 
> node1 -> mount /devfs/node1/cdroms/cdrom0  /mnt/cdrom -> success
> node2 -> mount /devfs/node1/cdroms/cdrom0  /mnt/cdrom -> failed 
> ( mount: No medium found )
> 
> 
>  -aneesh  
> 
>  
> 
> 
> 
> 
> _______________________________________________________________
> 
> Have big pipes? SourceForge.net is looking for download mirrors. We supply
> the hardware. You get the recognition. Email Us: ban...@so...
> _______________________________________________
> ssic-linux-devel mailing list
> ssi...@li...
> https://lists.sourceforge.net/lists/listinfo/ssic-linux-devel