Task #9801 (closed)
Bug: OMERO.data dismount allows undesired behaviour
| Reported by: | drussell-x | Owned by: | jamoore |
|---|---|---|---|
| Priority: | critical | Milestone: | OMERO-4.4.7 |
| Component: | Deployment | Version: | n.a. |
| Keywords: | n.a. | Cc: | cxallan, hflynn |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | 0.0d |
| Sprint: | Bugs Fixing |
Description
If OMERO.data is NFS (or otherwise) mounted and this mount fails to mount or is dismounted, OMERO will happily continue operating using the mount point instead. I doubt this would ever be desired behaviour as the administrator will then be faced with the task of merging the systems back together.
Easy fix is simply to make the mount for OMERO read only for the OMERO user, that way, uploads etc will simply fail. So adding a section on remote mounting to the docs might be useful.
I guess OMERO server prcoess could also check this, but that would require it to understand the mounts it needed which I think is overkill.
Change History (5)
comment:1 Changed 12 years ago by jmoore
- Summary changed from OMERO.data dismount allows undesired behaviour to Bug: OMERO.data dismount allows undesired behaviour
- Type changed from Bug to Task
comment:2 Changed 12 years ago by jmoore
- Cc cxallan added
- Component set to Deployment
- Milestone set to Unscheduled
- Priority changed from minor to critical
comment:3 Changed 11 years ago by jmoore
- Cc hflynn added
- Milestone changed from Unscheduled to OMERO-4.5
- Owner set to jmoore
- Remaining Time set to 0.2
- Status changed from new to accepted
comment:4 Changed 11 years ago by jmoore
- Remaining Time changed from 0.2 to 0
- Resolution set to fixed
- Status changed from accepted to closed
comment:5 Changed 11 years ago by jmoore
- Sprint set to Bugs Fixing
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
Essentially a doc bug then. Making a blurb for Helen to tear apart now.