• State Not Answered
  • Replies replies
    14
  • Subscribers subscribers
    16
  • Views views
    800
  • Users 0 members are here
  • Locked Locked
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

GMS attachments - relocate to new volume

MigrationDeletedUser
We are running out of disk space. The server is a virtual and we can add disk with vsphere easy enough, but re-sizing the existing volume is not working. the volume is "busy" - - it is the only volume.

Is there any way to move (relocate) the attachments to a new volume ?
  • 0
    Hi,

    Quick question - when partitioning your disk did you create /var as a separate partition?

    Please let us know.

    Cheers,
  • 0 in reply to 
    laurabuckley;2436555 wrote:
    Hi,

    Quick question - when partitioning your disk did you create /var as a separate partition?

    Please let us know.

    Cheers,


    Addition to what Laura said do you use LVM?

    Thomas
  • 0 in reply to 
    when entering "df" we get:
    dev/sda2
    udev
    tmpfs
    there is also a swap file at dev/sda1

    regarding lvm ... I see an ext3 (/dev/sda2)
  • 0 in reply to 
    Hi,

    Ok, you could create a new virtual disk, present the storage to your VM and move your entire /var directory to the new disk following this TID: https://www.novell.com/support/kb/doc.php?id=7015338

    I do not suggest moving just the attachments folder as that would no doubt break a ton of things. Rather relocate your entire /var directory as that is where GMS stores all of it's data.

    Cheers,
  • 0 in reply to 
    Well, a good option, if not a great option - - thanks. We'll give you an update when we've completed the process. The TID looks within our skills.
  • 0 in reply to 
    Hi,

    If it's any consolation, I'm no OS guru, I play with collaboration systems, but using that TID I've successfully move /var before. Please do let us know how it goes as we'd be very interested to hear back from you.

    Cheers,
  • 0  
    In article <hansoc.7k6mlz@no-mx.forums.microfocus.com>, Hansoc wrote:
    > We are running out of disk space. The server is a virtual and we can add
    > disk with vsphere easy enough, but re-sizing the existing volume is not
    > working. the volume is "busy" - - it is the only volume.

    Another option is to boot to a GParted ISO and use it to expand the
    volume. This is how I've been doing it on the smaller deployments or
    where ever we undersized root.



    Andy of
    http://KonecnyConsulting.ca in Toronto
    Knowledge Partner
    http://forums.novell.com/member.php/75037-konecnya
    If you find a post helpful and are logged in the Web interface, please
    show your appreciation by clicking on the star below. Thanks!
    GMS troubleshooting tips at http://www.konecnyad.ca/andyk/gwmobility.htm


    ________________________

    Andy of KonecnyConsulting.ca in Toronto
    Please use the "Like" and/or "Verified Answers" as appropriate as that helps us all.

  • 0   in reply to   
    Am 09.08.2016 um 22:39 schrieb Andy Konecny:
    > In article <hansoc.7k6mlz@no-mx.forums.microfocus.com>, Hansoc wrote:
    >> We are running out of disk space. The server is a virtual and we can add
    >> disk with vsphere easy enough, but re-sizing the existing volume is not
    >> working. the volume is "busy" - - it is the only volume.
    >
    > Another option is to boot to a GParted ISO and use it to expand the
    > volume. This is how I've been doing it on the smaller deployments or
    > where ever we undersized root.

    1. Gparted needs to be available in every VMWare deployment ready to boot.

    CU,
    --
    Massimo Rosen
    Novell Knowledge Partner
    No emails please!
    http://www.cfc-it.de
  • 0 in reply to   
    Ok - we've looked at this too, and a good solution. We're a bit stuck on the updates and upgrades we've applied over time. Right now we're looking at two options: always nice to be able to choose. Thank you for the direction and we'll let you know.
  • 0 in reply to 
    Not sure but:
    Step 4 = cp to /mnt/newvar ... yet the mount point is /var/newvar ?
    Step 6 = mkdir /var ---> then cp from /var/newvar to the newly createde /var ?

    I've a backup, so trying to work through this.

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.