Jump to content
  • [6.7.0-rc1] misreading cache drive size/used/free


    Can0n
    • Solved Minor

    just took the plunge on 6.7.0-rc1 on 1 server with a 1TB SSD for Cache and thought I read somewhere else someone is seeing the same issue but cant find it (sorry if this is a duplicate).

    my 1TB is being reported as a 8.3GB drive showing an unsually low amount of used and free I have tried the BTRS balance and Scrub without a change

     

     

    Screen Shot 2019-01-24 at 6.32.40 AM.png

     

    My disk Log:

     

    Jan 24 04:44:40 Freya kernel: ata2: SATA max UDMA/133 abar m2048@0xfe705000 port 0xfe705180 irq 35
    Jan 24 04:44:40 Freya kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    Jan 24 04:44:40 Freya kernel: ata2.00: supports DRM functions and may not be fully accessible
    Jan 24 04:44:40 Freya kernel: ata2.00: ATA-11: Samsung SSD 860 EVO 1TB, S3Z8NB1KB27695A, RVT02B6Q, max UDMA/133
    Jan 24 04:44:40 Freya kernel: ata2.00: 1953525168 sectors, multi 1: LBA48 NCQ (depth 32), AA
    Jan 24 04:44:40 Freya kernel: ata2.00: supports DRM functions and may not be fully accessible
    Jan 24 04:44:40 Freya kernel: ata2.00: configured for UDMA/133
    Jan 24 04:44:40 Freya kernel: ata2.00: Enabling discard_zeroes_data
    Jan 24 04:44:40 Freya kernel: sd 2:0:0:0: [sdc] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
    Jan 24 04:44:40 Freya kernel: sd 2:0:0:0: [sdc] Write Protect is off
    Jan 24 04:44:40 Freya kernel: sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00
    Jan 24 04:44:40 Freya kernel: sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    Jan 24 04:44:40 Freya kernel: ata2.00: Enabling discard_zeroes_data
    Jan 24 04:44:40 Freya kernel: sdc: sdc1
    Jan 24 04:44:40 Freya kernel: ata2.00: Enabling discard_zeroes_data
    Jan 24 04:44:40 Freya kernel: sd 2:0:0:0: [sdc] Attached SCSI disk
    Jan 24 04:44:40 Freya kernel: BTRFS: device fsid 9b666354-df3d-4e58-a3a7-f79a6d727f7b devid 1 transid 2889 /dev/sdc1
    Jan 24 04:44:57 Freya emhttpd: Samsung_SSD_860_EVO_1TB_S3Z8NB1KB27695A (sdc) 512 1953525168
    Jan 24 04:44:57 Freya emhttpd: import 30 cache device: (sdc) Samsung_SSD_860_EVO_1TB_S3Z8NB1KB27695A
    Jan 24 04:45:01 Freya kernel: BTRFS info (device sdc1): disk space caching is enabled
    Jan 24 04:45:01 Freya kernel: BTRFS info (device sdc1): has skinny extents
    Jan 24 04:45:01 Freya kernel: BTRFS info (device sdc1): enabling ssd optimizations
    Jan 24 04:45:01 Freya kernel: BTRFS info (device sdc1): resizing devid 1
    Jan 24 04:45:01 Freya kernel: BTRFS info (device sdc1): new size for /dev/sdc1 is 1000204853248
    Jan 24 04:45:01 Freya kernel: BTRFS info (device sdc1): resizing devid 2
    Jan 24 04:45:01 Freya kernel: BTRFS info (device sdc1): new size for /dev/sdd1 is 256060481536
    Jan 24 04:50:47 Freya emhttpd: shcmd (113): /usr/sbin/hdparm -S0 /dev/sdc
    Jan 24 04:50:47 Freya root: /dev/sdc:
    Jan 24 04:51:26 Freya emhttpd: Samsung_SSD_860_EVO_1TB_S3Z8NB1KB27695A (sdc) 512 1953525168
    Jan 24 04:51:26 Freya emhttpd: import 30 cache device: (sdc) Samsung_SSD_860_EVO_1TB_S3Z8NB1KB27695A
    Jan 24 04:51:42 Freya kernel: BTRFS info (device sdc1): allowing degraded mounts
    Jan 24 04:51:42 Freya kernel: BTRFS info (device sdc1): disk space caching is enabled
    Jan 24 04:51:42 Freya kernel: BTRFS info (device sdc1): has skinny extents
    Jan 24 04:51:42 Freya kernel: BTRFS info (device sdc1): enabling ssd optimizations
    Jan 24 04:51:42 Freya kernel: BTRFS info (device sdc1): resizing devid 1
    Jan 24 04:51:42 Freya kernel: BTRFS info (device sdc1): new size for /dev/sdc1 is 1000204853248
    Jan 24 04:51:42 Freya kernel: BTRFS info (device sdc1): resizing devid 2
    Jan 24 04:51:42 Freya kernel: BTRFS info (device sdc1): new size for /dev/sdd1 is 256060481536
    Jan 24 04:51:42 Freya kernel: BTRFS info (device sdc1): balance: force reducing metadata integrity
    Jan 24 04:51:42 Freya kernel: BTRFS info (device sdc1): relocating block group 4316987392 flags system|raid1
    Jan 24 04:51:43 Freya kernel: BTRFS info (device sdc1): relocating block group 2169503744 flags data|raid1
    Jan 24 04:51:43 Freya kernel: BTRFS info (device sdc1): found 66 extents
    Jan 24 04:51:43 Freya kernel: BTRFS info (device sdc1): found 66 extents
    Jan 24 04:51:43 Freya kernel: BTRFS info (device sdc1): relocating block group 1095761920 flags metadata|raid1
    Jan 24 04:51:43 Freya kernel: BTRFS info (device sdc1): found 8 extents
    Jan 24 04:51:43 Freya kernel: BTRFS info (device sdc1): device deleted: /dev/sdd1

    DONE

     

     

    freya-diagnostics-20190124-0546.zip




    User Feedback

    Recommended Comments

    I think the other reports had to do with displaying much larger than true, as in PB instead of TB.

     

    Where are your diagnostics?

    • Like 1
    Link to comment

    Looks to me like some confusion because you removed one of the cache devices and that device was later mounted and unmounted by UD, rebooting should clear the issue.

    Link to comment

    i did have a 256GB SSD on there from 6.6.6 and kept it until the 6.7.0-rc1 install I then stopped the array

     

    removed the 256GB one (hated loosing 500GB to the raid 1 setup) and started the array (did not use New Config)...there was a check box to allow the missing cache by the start array option...

    thanks for the advice ill reboot after the mover is done and current downloads from sabnzbd are completed.


     

    Link to comment
    1 hour ago, trurl said:

    I think the other reports had to do with displaying much larger than true, as in PB instead of TB.

    That issue was with the UD plugin and didn't apply to array drives.

    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...