My Oracle Support Banner

'beadm create' failed with error: No such file or directory: 'legacy/.bemgmt.lock' (Doc ID 2704998.1)

Last updated on AUGUST 27, 2020

Applies to:

Solaris Operating System - Version 11.4 to 11.4 [Release 11.0]
Information in this document applies to any platform.

Symptoms

When trying to create a new boot environment, the command failed with the following error: 

    # beadm create solaris-19-August-2020
    Creating new BE solaris-19-August-2020 failed.
    [Errno 2] No such file or directory: 'legacy/.bemgmt.lock'
    Please see logfile /var/share/beadm/beadm.19838.20200819_103333.log for additional details

 

Checking the log file showed:

    # cat logfile: /var/share/beadm/beadm.19838.20200819_10333.log
    ...
    2020-08-19 11:33:27 - DEBUG - Retrieving list of nested datasets under rpool/ROOT/11.4
    2020-08-19 11:33:27 - DEBUG - In-BE datasets:
    2020-08-19 11:33:27 - DEBUG - Getting dataset properties for rpool/ROOT/11.4/var
    2020-08-19 11:33:27 - DEBUG - rpool/ROOT/11.4/var
    2020-08-19 11:33:27 - DEBUG - Trying to get an exclusive lock for BE copy
    2020-08-19 11:33:27 - ERROR - Traceback (most recent call last):
    File "/usr/lib/python2.7/vendor-packages/bemgmt/cli.py", line 928, in main
    ret = args.func(bemgr, args)
    File "/usr/lib/python2.7/vendor-packages/bemgmt/cli.py", line 211, in do_create
    be_desc=args.d, be_props=be_props)
    File "/usr/lib/python2.7/vendor-packages/bemgmt/__init__.py", line 1107, in copy
    dst_bename_suffix=dst_bename_suffix)
    File "/usr/lib/python2.7/vendor-packages/bemgmt/global_zone.py", line 455, in copy
    dst_bename_suffix=dst_bename_suffix)
    File "/usr/lib/python2.7/vendor-packages/bemgmt/be_group.py", line 381, in copy
    with Lockfile(self.bemgmt_lockfile, timeout=600):
    File "/usr/lib/python2.7/vendor-packages/solaris_install/__init__.py", line 1164, in __enter__
    raise err
    IOError: [Errno 2] No such file or directory: 'legacy/.bemgmt.lock'

 

Checking the 'beadm list' and 'beadm list -a' command outputs showed nothing out of the ordinary.

 

Checking rpool and rpool/ROOT mount points showed:

    # zfs list -ro name,mountpoint rpool
    NAME MOUNTPOINT
    rpool legacy
    rpool/ROOT legacy

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.