Visit Open-E website
Results 1 to 10 of 23

Thread: Volume manager can not use added space

Thread has average rating 4.50 / 5.00 based on 2 votes.
Thread has been visited 558982 times.

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1

    Default

    Send in a request to support@open-e.com with logs and and ask for remote support - i want them to look into this.
    All the best,

    Todd Maxwell


    Follow the red "E"
    Facebook | Twitter | YouTube

  2. #2
    Join Date
    Sep 2007
    Posts
    80

    Default

    Any update on this one, as we have just seen the same thing on a LSI MegaRaid controller.

    It took a couple of reboots (after the pv resize) just to get the new size to report correctly in Unit size, but as above posts, free space is still incorrect. I have submitted logs to support anyway (Ticket#1010974), this post is just say it's not a 3ware etc. Raid controller-specifc issue. Cheers.

  3. #3

    Default

    I have the very same issue here.
    A disk was added to the array and with some console command I was told to run, the total volume space reflects the new size. However the sum of the used and free space still add up only to the previous volume size.

  4. #4

    Default

    Did you send in the log file to support and what RAID controller are you using.
    All the best,

    Todd Maxwell


    Follow the red "E"
    Facebook | Twitter | YouTube

  5. #5

    Default

    No, 'cos meanwhile I had another problem with lost tape pools and that was a less important issue. I'll open a ticket for this issue together with log files.

  6. #6
    Join Date
    Oct 2009
    Posts
    53

    Exclamation

    Does anybody already know the solution for this issue?

    I've just expanded my Areca 1222 array, succesfully resized the PV and rebooted.
    The volume manager does show the correct, expanded, size, but the free space indicator is stuck at exactly the old volume size.

  7. #7

    Default

    Is the migration complete with the Areca? If so try to reboot one more time, I have seen this happen sometimes. Let me know if that does the trick.
    All the best,

    Todd Maxwell


    Follow the red "E"
    Facebook | Twitter | YouTube

  8. #8

    Default

    The disk is added to the array, I was told to run some console commands.
    Last edited by Gr-R; 04-11-2012 at 09:45 PM.

  9. #9
    Join Date
    Jan 2011
    Posts
    54

    Default

    Just in case, here is the correct procedure when resizing RAID array in DSS V6:

    1). Apply appropriate Storage extension Key or make sure that your current license key is valid also for the storage size after the LUN size extension,
    2). Expand the LUN size using the H/W RAID tools(RAID migration)
    3). Perform "Unit rescan" (DSS webgui -> CONFIGURATION ->volume manager -> Vol. groups)
    4). PV Resize (DSS Console -> ctrl + alt + X -> 11. PV Resize)
    5). Reboot

    In case you are using trial version, you don't have to apply the storage extension key because trail version is for unlimited storage.

    BR,
    Tomek

  10. #10

    Default

    Quote Originally Posted by nhatht View Post
    The raid controller is an ARC-1680 and the controllers reports complete on the array expansion moreover: the volume manager reports 11000Tb.
    Are you saying that your Areca is having the same issue? Try the PV-Resize from the Extended tools in the Console Screen enter CTRL + ALT + X then select PVresize.
    All the best,

    Todd Maxwell


    Follow the red "E"
    Facebook | Twitter | YouTube

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •