<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: [Bug] Orphan storage location in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/bug-orphan-storage-location/m-p/157295#M54527</link>
    <description>&lt;P&gt;this is not helpful. Orphaned objects are not shown in account console&lt;/P&gt;</description>
    <pubDate>Tue, 19 May 2026 23:24:14 GMT</pubDate>
    <dc:creator>salavatov</dc:creator>
    <dc:date>2026-05-19T23:24:14Z</dc:date>
    <item>
      <title>[Bug] Orphan storage location</title>
      <link>https://community.databricks.com/t5/data-engineering/bug-orphan-storage-location/m-p/64400#M32563</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I'm not able to re-create an external location after removing its owner from Databricks Account. I'm getting the following error:&lt;BR /&gt;&lt;EM&gt;Input path url 'abfss://foo@bar.dfs.core.windows.net/' overlaps with an existing external location within 'CreateExternalLocation' call&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;I've tried to re-create the workspace but it seems that the information about the external location is stored somewhere inside the account metastore. I'm not able to find an API to list all external locations at the account level and since the workspace has been re-created the old workspace URL is no more accessible.&amp;nbsp;Is there a way to remove the orpahned external location?&lt;/P&gt;</description>
      <pubDate>Fri, 22 Mar 2024 13:52:02 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/bug-orphan-storage-location/m-p/64400#M32563</guid>
      <dc:creator>RTabur</dc:creator>
      <dc:date>2024-03-22T13:52:02Z</dc:date>
    </item>
    <item>
      <title>Re: [Bug] Orphan storage location</title>
      <link>https://community.databricks.com/t5/data-engineering/bug-orphan-storage-location/m-p/64403#M32565</link>
      <description>&lt;UL&gt;
&lt;LI&gt;Your metastore admin can &lt;A href="https://docs.databricks.com/en/sql/language-manual/sql-ref-syntax-aux-show-locations.html" target="_self"&gt;list all external locations&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;
&lt;LI&gt;Your metastore admin can then &lt;A href="https://docs.databricks.com/en/sql/language-manual/sql-ref-syntax-ddl-drop-location.html" target="_self"&gt;drop the external location&lt;/A&gt;&amp;nbsp;&lt;/LI&gt;
&lt;/UL&gt;</description>
      <pubDate>Fri, 22 Mar 2024 14:32:07 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/bug-orphan-storage-location/m-p/64403#M32565</guid>
      <dc:creator>PL_db</dc:creator>
      <dc:date>2024-03-22T14:32:07Z</dc:date>
    </item>
    <item>
      <title>Re: [Bug] Orphan storage location</title>
      <link>https://community.databricks.com/t5/data-engineering/bug-orphan-storage-location/m-p/64413#M32567</link>
      <description>&lt;P&gt;I have already tried this, I am an account admin I see everything but not the old external location, it is not listed but it's there somewhere because I get the error...&lt;BR /&gt;&lt;BR /&gt;That's why I think it's bug.&lt;/P&gt;&lt;P&gt;Thank you anyway!&lt;/P&gt;</description>
      <pubDate>Fri, 22 Mar 2024 16:41:34 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/bug-orphan-storage-location/m-p/64413#M32567</guid>
      <dc:creator>RTabur</dc:creator>
      <dc:date>2024-03-22T16:41:34Z</dc:date>
    </item>
    <item>
      <title>Re: [Bug] Orphan storage location</title>
      <link>https://community.databricks.com/t5/data-engineering/bug-orphan-storage-location/m-p/157295#M54527</link>
      <description>&lt;P&gt;this is not helpful. Orphaned objects are not shown in account console&lt;/P&gt;</description>
      <pubDate>Tue, 19 May 2026 23:24:14 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/bug-orphan-storage-location/m-p/157295#M54527</guid>
      <dc:creator>salavatov</dc:creator>
      <dc:date>2026-05-19T23:24:14Z</dc:date>
    </item>
    <item>
      <title>Re: [Bug] Orphan storage location</title>
      <link>https://community.databricks.com/t5/data-engineering/bug-orphan-storage-location/m-p/157296#M54528</link>
      <description>&lt;P&gt;I'm having the similar issue. Metastore somehow has some data which cannot be modified or deleted effectively preventing us to use same storage account container name. You might try using different name&lt;/P&gt;</description>
      <pubDate>Tue, 19 May 2026 23:26:05 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/bug-orphan-storage-location/m-p/157296#M54528</guid>
      <dc:creator>salavatov</dc:creator>
      <dc:date>2026-05-19T23:26:05Z</dc:date>
    </item>
  </channel>
</rss>

