EPrints Technical Mailing List Archive
See the EPrints wiki for instructions on how to join this mailing list and related information.
Message: #08626
< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First
Re: [EP-tech] storage capacity is insufficient
- To: <eprints-tech@ecs.soton.ac.uk>, Ajunk Pracetio <prazetyo@gmail.com>
 - Subject: Re: [EP-tech] storage capacity is insufficient
 - From: David R Newman <drn@ecs.soton.ac.uk>
 - Date: Tue, 25 May 2021 10:11:53 +0100
 
Hi Agung PW,
Yes, this is something we very much accounted for, in fact since the invent of VMs and Logical Volume Manager (LVM) [1] this has become less of a problem.
What you need to do is add your new disk.  You can either mount
      it at
      /usr/share/eprints3/archives/<ARCHIVE_NAME>/documents/disk1
      or mount it wherever and symlink it from
      /usr/share/eprints3/archives/<ARCHIVE_NAME>/documents/disk1:
    
ln -s /path/to/new/disk
      /usr/share/eprints3/archives/<ARCHIVE_NAME>/documents/disk1
      
    
You also need to make sure that this directory is writeable by user who is running the webserver and ideally the eprints user as well, this is often best done by ensure the group is also set to eprints and there are group write privileges:
chown eprints:eprints
      /usr/share/eprints3/archives/<ARCHIVE_NAME>/documents/disk1
      
    
chmod g+w
      /usr/share/eprints3/archives/<ARCHIVE_NAME>/documents/disk1
      
    
If you are symlinking you should also do this on the mounted
      directory as well. (i.e. /path/to/new/disk in the example above).
    
I don't think you need to do anything beyond this for EPrints to
      start using the new disk as it has built-in logic to look for the
      directory disk with the highest number after it.  However, to be
      certain I would reload you webserver and create a new test eprint
      item and check to see it is using the new documents/disk1
      directory after upload a test file.
    
One thing to double-check is that the new disk is automatically
      mounted in the same place after a reboot.  Otherwise you will have
      problems saving uploaded files to disk and probably more problems
      besides, as eprint revision files will not be able to be written
      to disk either.
    
Regards
David Newman
    
[1] https://en.wikipedia.org/wiki/Logical_Volume_Manager_(Linux)
    
CAUTION: This e-mail originated outside the University of Southampton.Hi,
If my eprints storage already run out, is there any tutorial how to add new storage on server? From my observation, is it possible just to add a hard drive, mount it and create a hard link as disk1 in / usr/share/eprints3/archives/archive_name/documents/ ?
Best regards,Agung PW
*** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech *** Archive: http://www.eprints.org/tech.php/ *** EPrints community wiki: http://wiki.eprints.org/
- References:
- [EP-tech] storage capacity is insufficient
- From: Ajunk Pracetio <prazetyo@gmail.com>
 
 
 - [EP-tech] storage capacity is insufficient
 
- Prev by Date: [EP-tech] storage capacity is insufficient
 - Next by Date: Re: [EP-tech] storage capacity is insufficient
 - Previous by thread: [EP-tech] EPrints/CRIS
 - Next by thread: [EP-tech] DOI handling in orcid_support_advance
 - Index(es):
 
