Task #12355 (closed)
Bug: managed repo broken by omero.data.dir move
Reported by: | jamoore | Owned by: | jamoore |
---|---|---|---|
Priority: | critical | Milestone: | 5.0.3 |
Component: | Deployment | Version: | 5.0.2 |
Keywords: | fs, managedrepo | Cc: | fs@…, sbesson, pwalczysko, khgillen, spli, mlinkert |
Resources: | n.a. | Referenced By: | https://trello.com/c/EOL8YL14/54-bug-import |
References: | n.a. | Remaining Time: | 0.0d |
Sprint: | n.a. |
Description
Seb recently migrated the gretzky server to the new octopus server. The change in the name/location of the ManagedRepository? led to all the data going missing since a new mrepo was created:
[jamoore@ome-c6100-1 ~]$ ~hudson/OMERO-CURRENT/bin/omero fs repos # | Id | UUID | Type | Path ---+-------+--------------------------------------+---------+-------------------------------------------------------------------------------------------- 0 | 17 | ce1e2766-089f-4555-a52a-f75746fd44da | Public | /OMERO 1 | 18 | ScriptRepo | Script | /home/hudson/hudson/workspace/OMERO-merge-stable/src/dist/lib/scripts 2 | 10901 | 28360f82-977c-4764-b52c-f31d677ebbaa | Managed | /nightshade/OMERO/omero-c6100-dec-5-2013-valuable/OMERO-merge-develop-FS/ManagedRepository 3 | 88301 | 7ef9e3dc-20e3-43a2-85f8-223431e40058 | Public | /repositories/OMERO-5.0-merge-deploy
and
OMERO-5.0-merge-deploy=# select repo, count(*) from originalfile group by repo;; repo | count --------------------------------------+------- | 14187 28360f82-977c-4764-b52c-f31d677ebbaa | 57564 ScriptRepo | 23 (3 rows)
Note: symlinks are also broken more thoroughly since the files are not located on the new server but this is an unrelated issue.
Change History (6)
comment:1 Changed 10 years ago by jamoore
- Cc mlinkert added
- Keywords fs managedrepo added
- Summary changed from Bug: managed repo broken by omero.data.dir to Bug: managed repo broken by omero.data.dir move
comment:2 Changed 10 years ago by jburel
- Referenced By set to https://trello.com/c/EOL8YL14/54-bug-import
comment:3 Changed 10 years ago by jamoore
- Owner set to jamoore
PR opened for repository naming: https://github.com/openmicroscopy/openmicroscopy/pull/2673
Haven't begun to look into the file-specific issues yet.
comment:4 Changed 10 years ago by jamoore
- Resolution set to fixed
- Status changed from new to closed
The CZI error seen by Sebastien is almost certainly related to in-place import and so will be handled elsewhere. There *may* still be some issue with the bfmemo files, but at the moment I don't have evidence of any. Closing.
comment:5 Changed 10 years ago by jmoore <josh@…>
- Remaining Time set to 0
(In [310be3f12ea722dddc69a92c0d819c40f9a57599/ome.git] on branch develop) Rename don't recreate repos on move (Fix #12355)
If a sysadmin properly moves the omero.data.dir to
new location via:
`
bin/omero config omero.data.dir NEW
mv OLD NEW
`
then there's no reason that a new repository should
be created. Instead, now a WARN log statement is
printed and the new value should be visible via
bin/omero fs repos. Imports of files from before
and after the renaming should work identically.
comment:6 Changed 10 years ago by Josh Moore <josh@…>
(In [c47c48c8c106f7d7b5330eafacd9d5eacfa95cab/ome.git] on branch develop) Merge pull request #2684 from joshmoore/rebased/develop/12355-move-dir
Rename don't recreate repos on move (Fix #12355) (rebased onto develop)
In addition, the bfmemo files are holding onto filenames: