Stats

  • Locked Locked
  • Replies 3
  • Subscribers 126
  • Views 17760
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Cadence schematic access permission issues with mounted folders

KSANK

 Hi,

We recently moved from a 'Samba' based remote file mounting to  "sshfs" based file mounting . After the migration, we are unable to open any schematic in the mounted folders with write permission.

Upon trying to open the files we get an error

('SCH-1217') : Could not open'schamtic' for edit.

(DB-270000)  dBOpenCellViewByType: Unable to lock  database file for  'filepath'

Would you like to open it for read?

 The native linux permissions of the mounted folders look good and we are able to read/write files into the mounted folders from the command prompt. Any clues on why virtuoso thinks the mounted folders as 'read only' when linux permissions are good??

  • Not sure any testing on such a file system is done (even Samba is probably asking for trouble, because Windows file systems typically don't handle everything well that Linux does). Can you show what an "ls -al" of a cellView directory looks like?

    Regards,

    Andrew.

  • Hi,
    was there any solution for the problem?
    I am experiencing the same issue when accessing an open access library with virtuoso which is mounted over "sshfs". Interestingly this only happens when accessing symbol or schematic views. textviews (like verilog) work fine...
    Interestingly when looking at the lock files normally for symbol and schematic two files get created, whereas for textviews only one files which does not contain the host and domain name. Example:

    schematic view:
    sch.oa.cdslck.RHEL30.hostname.domainname.10893
    sch.oa.cdslck

    symbol view:
    symbol.oa.cdslck.RHEL30.hostname.domainname.10893
    symbol.oa.cdslck

    verilog/functional view:
    verilog.v.cdslck

    I suspect that the locking of virtuoso gets confused somehow together with sshfs...When using a different lock mechanism (why?) for schematic views and lock files refering the remote hostname, "thinking" the file is already locked by the remote (filesystem exporting host) somehow.

    Any ideas?

    Best regards, Markus

  • The two lock files are for different aspects. One is the general Cadence "CLS" locking mechanism, and the other is the OpenAccess locking mechanism.

    I found two similar questions to R&D about support for sshfs, one specifically about locking. The answer was that this is not supported (the reason is almost certainly that it doesn't support certain file operations that Virtuoso needs).

    So you should not use sshfs with Virtuoso data. It has not been tested with sshfs and there are no plans to do so.

    Regards,

    Andrew.

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.