Hi,

 

I just checked the syslog after re-doing my shares and adding the 'default' unRAID shares for my docker & libvirt images and despite the docker.img being stored on a BTRFS RAID1 pair of SSDs (cache pool) - the below syslog snippet shows that "SSD Detected:   no"

 

I'd assume that's because the .img itself isn't technically an SSD, it's a loop device... Is that the reason?

Or is BTRFS / Docker.img just setup incorrectly by unRAID?

 

fyi, it's causing no issues and I'm not concerned... I was just curious!

 

Thanks!

Mar 16 14:45:14 Raptor root: Creating new image file: /mnt/user/system/docker/docker.img size: 10G
Mar 16 14:45:15 Raptor root: btrfs-progs v4.7.2
Mar 16 14:45:15 Raptor root: See http://btrfs.wiki.kernel.org for more information.
Mar 16 14:45:15 Raptor root: 
Mar 16 14:45:15 Raptor root: Label:              (null)
Mar 16 14:45:15 Raptor root: UUID:               27a7539a-adc2-42b0-8c7e-d59cc40f006a
Mar 16 14:45:15 Raptor root: Node size:          16384
Mar 16 14:45:15 Raptor root: Sector size:        4096
Mar 16 14:45:15 Raptor root: Filesystem size:    10.00GiB
Mar 16 14:45:15 Raptor root: Block group profiles:
Mar 16 14:45:15 Raptor root:   Data:             single            8.00MiB
Mar 16 14:45:15 Raptor root:   Metadata:         DUP               1.00GiB
Mar 16 14:45:15 Raptor root:   System:           DUP               8.00MiB
Mar 16 14:45:15 Raptor root: SSD detected:       no
Mar 16 14:45:15 Raptor root: Incompat features:  extref, skinny-metadata
Mar 16 14:45:15 Raptor root: Number of devices:  1
Mar 16 14:45:15 Raptor root: Devices:
Mar 16 14:45:15 Raptor root:    ID        SIZE  PATH
Mar 16 14:45:15 Raptor root:     1    10.00GiB  /mnt/cache/system/docker/docker.img
Mar 16 14:45:15 Raptor root: 
Mar 16 14:45:15 Raptor kernel: BTRFS: device fsid 27a7539a-adc2-42b0-8c7e-d59cc40f006a devid 1 transid 5 /dev/loop0
Mar 16 14:45:15 Raptor kernel: BTRFS info (device loop0): disk space caching is enabled
Mar 16 14:45:15 Raptor kernel: BTRFS info (device loop0): has skinny extents
Mar 16 14:45:15 Raptor kernel: BTRFS info (device loop0): flagging fs with big metadata feature
Mar 16 14:45:15 Raptor kernel: BTRFS info (device loop0): creating UUID tree

 

46 minutes ago, nexusmaniac said:

I'd assume that's because the .img itself isn't technically an SSD, it's a loop device... Is that the reason?

 

Yes

1 hour ago, johnnie.black said:

 

Yes

Well, that's that answered  

Cheers!