Jump to content
  • [6.12.6-6.12.8] partition size reported incorrectly


    Videodr0me
    • Minor

    I just updated from 6.9.2 to 6.12.6 and while everything seems to work as expected, if i click on the main tab and then on the cache drive the partition size is reported as 0. This is clearly wrong as i can access all files and fdsk or lblk report the correct partition size, also on 6.9.2 it was reported correctly . Is this just a cosmetic bug?

    Addition: The bug persists with 6.12.8

     

    tower-ii-diagnostics-20240112-1055.zip

    partition_size.jpg




    User Feedback

    Recommended Comments

    2 hours ago, JorgeB said:
    fdisk -l /dev/nvme0n1

    root@Tower-II:~# fdisk -l /dev/nvme0n1
    Disk /dev/nvme0n1: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors
    Disk model: Samsung SSD 970 EVO Plus 2TB            
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disklabel type: dos
    Disk identifier: 0x00000000

    Device         Boot Start        End    Sectors  Size Id Type
    /dev/nvme0n1p1       2048 3907029167 3907027120  1.8T 83 Linux

    Link to comment

    That looks normal, not sure what it could be, cannot reproduce, I would think it would just be a cosmetic thing, but maybe someone from LT can take a look.

    Link to comment


    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.

×
×
  • Create New...