[Loris-dev] another LORIS question

[Cecile Madjar]

Hi Louis,

I am cc'ing the loris-dev mailing list in case someone wants to jump in and
either rectify or add information to my reply. :)

I don't see why what you propose would not work. In our MCIN setup, the VM
hosting LORIS and the MRI files are on two different filesystems:
- one filesystem that is hosting LORIS
- one filesystem that is hosting the MRI data and (other large datasets).
This one is then mounted on the VM that hosts LORIS so that LORIS can have
access to the files and display it in the imaging browser.

Separating the two also helps for the backup of the VM (way shorter without
terabytes of data). Of course, back of the MRI data is done separately as
well since we don't want to lose those precious datasets!

All that will be needed once this is done would be to change a few config
path in LORIS (in the Config module) to point to the mounted directory and
voilà!

Hopefully that answers your question.
Best,

Cécile



On Thu, Jul 18, 2019 at 1:18 PM Louis Collins, Dr. <louis.collins at mcgill.ca>
wrote:

> Cecile,
>
> I have another question about LORIS.  It is taking us a huge amount of
> time to upload clinical data into the LORIS DB.  I think the slowdown may
> be caused by NFS delays because the DB is hosted on network drives in the
> computer science building on lower campus.
>
> Do you think it is possible to store a local copy of the DB on a machine
> in the lab in the MNI, where the DB would point to MRI minc volumes that
> are on the network drives?  This way, the DB would be local, and I assume
> that access would be (almost) instantaneous.  In addition, because the MRI
> data is not local, we would not need 13-15 TB of space locally…
>
> What do you think?
>
> -Louis
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.bic.mni.mcgill.ca/pipermail/loris-dev/attachments/20190718/de0f9c40/attachment.html>