Jump to content

WEHA

Members
 View Profile  See their activity

  • Posts

    91

  • Joined

  • Last visited

 Content Type 

Posts posted by WEHA

    BTRFS cache read only mounted

    in General Support

    Posted · Edited by WEHA

    15 minutes ago, johnnie.black said:

    Post new diagnostics

    Everything is now copied back, stopped and started array: no exportable shares.

    New diag attached

    tower-diagnostics-20180414-1538.zip

     

    Something strange though when I "ls /mnt":


    16K drwxrwxrwx  1 nobody users 106 Apr 14 15:32 cache/
      0 drwxrwxrwx  3 nobody users  19 Apr 14 10:00 disk1/
      0 drwxrwxrwx  4 nobody users  43 Apr 14 10:00 disk2/
      0 drwxrwxrwx  3 nobody users  19 Apr 14 10:00 disk3/
      0 drwxrwxrwx  3 nobody users  19 Apr 14 10:00 disk4/
      0 drwxrwxrwx 11 nobody users 167 Apr 14 10:00 disk5/
      0 drwxrwxrwx  5 nobody users 100 Apr 14 15:35 disks/
      ? d?????????  ? ?      ?       ?            ? user/
      0 drwxrwxrwx  1 nobody users  19 Apr 14 10:00 user0/
     

    /bin/ls: cannot access 'user': Transport endpoint is not connected
     

     

    When I "ls user0", those contain the non-cache shares

    BTRFS cache read only mounted

    in General Support

    Posted

    Thank you for your quick reply.

    I was able to copy the data earlier, I hope there is no corruption.

    What are ENOSPC errors exactly? Can't seem to find a simple description :)

     

    What would be the best way to format the drivers:

    - using the gui: just delete the partition and re-add as cache?

    - is a full wipe necesarry?

    - a btrfs command

     

    thanks!

     

     

    BTRFS cache read only mounted

    in General Support

    Posted · Edited by WEHA

    Hello

     

    So I had this issue where unraid started throwing errors, I believe because of cache drive disconnect (if that's possible, doesn't it run from the usb drive?)

    I set the array to not start on boot but because of the errors it apparently didn't save this preference.

    Anyway, after rebooting (not detecting the second cache drive) it started the array, without the second cache drive. (raid1)

    It was mounted read only, I guess because of the disconnect earlier.

    I rebooted to get the second drive detected again and I tried to re-add the drive in unraid.

    It remained mounted read only and btrfs was still saying that it was missing the drive, even though it was looking correct in the unraid gui.

    After searching the internet I found the command to replace the drive in the raid 1 (adding redetected drive and removing missing drive).

    But I'm still at the problem where it says the drive is mounted read only.

    When I execute mount it says rw, so it's btrfs not allowing me to write.

    The only thing I could find for this situation is that there needs to be a kernel patch to get this working.

    I'm not familiar how to check or install this patch in unraid.

     

    Source: 

    https://www.mail-archive.com/search?l=linux-btrfs%40vger.kernel.org&q=subject:"raid1\%3A+cannot+add+disk+to+replace+faulty+because+can+only+mount+fs+as+read\-only."&o=newest

    https://www.mail-archive.com/[email protected]/msg60979.html

     

    Any suggestions?

     

    EDIT: added diagnostics

    tower-diagnostics-20180414-0850.zip

    Recycle Bin (vfs recycle) for SMB Shares

    in Plugin Support

    Posted

    I have a problem that a share is not detected.

    It is one that is not exported via the unraid gui but rather manual config change of samba.

    The reason for this is that it's a users share where the subfolders have different permissions which is not possible from the gui.

     

    Is there a way to enable the recycle bin for this share?

    The plugin does not see it.

     

    thanks!

    [SOLVED] 1 cache disk was missing, now it gives space for RAID 0 but it should be RAID 1

    in General Support

    Posted · Edited by WEHA

    16 minutes ago, johnnie.black said:

    Metadata should be raid1, even when data isn't like with single or raid0 profiles mostly for metadata corruption protection, but in those modes if you lose a disk you'll lose all data.

    Just as I suspected, but then unraid showing it protected is a bug then no?

     

    Balance status: 

    Data, single: total=871.00GiB, used=801.92GiB
System, single: total=32.00MiB, used=128.00KiB
Metadata, single: total=4.00GiB, used=1.25GiB
GlobalReserve, single: total=512.00MiB, used=0.00B

     

    So nothing is raid 1...

    [SOLVED] 1 cache disk was missing, now it gives space for RAID 0 but it should be RAID 1

    in General Support

    Posted

    12 hours ago, johnnie.black said:

    RADI1 for both:

     

    Alright Thanks, 2 questions though. If you don't mind. :)

     

    Do I need to move the data first or can I be sure not to loose any data with the conversion?

    This is not mentioned in the post so I'd like to be sure, I can imagine btrfs is smart enough to do this when enough space is available.

     

    Reading your faq post properly I see that metadata can be in raid 1 mode separately, what exactly does this mean -> are the files protected or not?

    Unraid indicates they are but I would think metadata is not enough, this confuses me as you would surely understand.

     

    thanks again!

     

    [SOLVED] 1 cache disk was missing, now it gives space for RAID 0 but it should be RAID 1

    in General Support

    Posted · Edited by WEHA
    mark as solved

    So I was adding a pcie card in the unraid system and booted it back up.

    Array was on auto start so this started but I noticed one of the cache disks was missing.

    Not sure why this would be allowed to happen as an array disk missing would prevent the array from starting, is this normal behavior?

     

    Anyway, I removed the card and I got the cache disk back and it was balancing.

    The strange was that the used data status was dropping so it scared me at first but when checking with du, nothing changed.

    The balance finished and now I have a 2TB cache disk where this should be 1TB (2 x 1TB nvme sdd).

    Cache shares are still showing green meaning protected but when I check balance on the cache page it says no balance found.

    Stopping and starting the array does not change anything.

     

    So 2 questions:

    - How do I fix this? unless the only way is remaking the cache...

    - How can I make unraid not mount the cache when one of the disks is missing?

     

    Diagnostics attached

    tower-diagnostics-20170730-1757.zip

    Image file uses more space then allowed

    in VM Engine (KVM)

    Posted

    So, I made a cache with 2 ssd's of 120 GB (112GB irl)

    I made a VM with a 100GB img file.

    When I put the VM on the cache, everything is fine.

    When things are being written to the image the cache fills up but the img file is still 100GB

    If I move it to the array and back to the cache I can use it again until the remaining 12GB  get's written again.

    The img file is the only thing on the cache:

    /dev/sde1        112G  112G   72K 100% /mnt/cache

     100G -rwxrwxrwx 1 root   users 100G Jul 22 10:01 vdisk1.img*

     

    Can anyone explain to me why this is happening and how I can stop it?

     

    thanks!

    [SOLVED] Cache disks as "new disk", not possible to get cache pool working

    in General Support

    Posted

    Your commands did not do/find anything:

    wipefs -o 0x10040 /dev/sdg
    wipefs: /dev/sdg: offset 0x10040 not found

     

    wipefs -o 0x10040 /dev/sdf
    wipefs: /dev/sdf: offset 0x10040 not found

     

    One disk was empty so I wiped the other one with the other command:

     wipefs -a /dev/sdf1
    /dev/sdf1: 8 bytes were erased at offset 0x00010040 (btrfs): 5f 42 48 52 66 53 5f 4d

    wipefs -a /dev/sdf
    /dev/sdf: 2 bytes were erased at offset 0x000001fe (dos): 55 aa
    /dev/sdf: calling ioctl to re-read partition table: Success

     

    I recreated the cache with only sdg, mounted fine.

     

    The next command returned nothing:

    btrfs device add /dev/sdf1 /mnt/cache

     

    I stopped the array and from the moment I selected 2 slots the green dot went to blue, adding the second disk made 2 blue icons

     

    Started the array and tried the following command anyway: 

    btrfs balance start --bg --full-balance /mnt/cache

    Checking status:

    Every 2.0s: btrfs balance status /mnt/cache

    ERROR: cannot access '/mnt/cache': No such file or directory
     

     btrfs fi show /mnt/cache
    ERROR: superblock checksum mismatch
    ERROR: cannot scan /dev/sdc1: Input/output error
    ERROR: not a valid btrfs filesystem: /mnt/cache
     

    sdc is an array disk formatted as btrfs

    [SOLVED] Cache disks as "new disk", not possible to get cache pool working

    in General Support

    Posted · Edited by WEHA
    Extra info

    Ok I've been trying some things:

    Cache slots was set on 2 because I wanted to add 2 drives.

    When I set cache slots to 1, it works?! Disk is then tagged as normal (green icon)

    From the moment I set the slots to 2 the first disk is tagged as new (blue icon) and unmountable

    This with either disk.

     

    EDIT: in disk.cfg cacheUUID is still empty, whereas on another test server I have an SSD mounted for cache and that actually shows an UUID

    [SOLVED] Cache disks as "new disk", not possible to get cache pool working

    in General Support

    Posted

    Same result

     

    sdg: 

    Jun 29 18:01:03 unNeptunus rc.diskinfo[8978]: PHP Warning: Missing argument 2 for force_reload() in /etc/rc.d/rc.diskinfo on line 634
Jun 29 18:01:03 unNeptunus rc.diskinfo[8978]: SIGHUP received, forcing refresh of disks info.
Jun 29 18:01:03 unNeptunus rc.diskinfo[8978]: PHP Warning: Missing argument 2 for force_reload() in /etc/rc.d/rc.diskinfo on line 634
Jun 29 18:01:03 unNeptunus rc.diskinfo[8978]: SIGHUP received, forcing refresh of disks info.
Jun 29 18:01:03 unNeptunus rc.diskinfo[8978]: PHP Warning: Missing argument 2 for force_reload() in /etc/rc.d/rc.diskinfo on line 634
Jun 29 18:01:03 unNeptunus rc.diskinfo[8978]: SIGHUP ignored - already refreshing disk info.
Jun 29 18:01:03 unNeptunus emhttp: shcmd (2453): set -o pipefail ; mkfs.btrfs -f -K -dsingle -msingle /dev/sdg1 |& logger
Jun 29 18:01:04 unNeptunus root: btrfs-progs v4.7.2
Jun 29 18:01:04 unNeptunus root: See http://btrfs.wiki.kernel.org for more information.
Jun 29 18:01:04 unNeptunus root: 
Jun 29 18:01:04 unNeptunus root: Label: (null)
Jun 29 18:01:04 unNeptunus root: UUID: f9d1f8b9-2e2f-44a8-b3af-7148521794b3
Jun 29 18:01:04 unNeptunus root: Node size: 16384
Jun 29 18:01:04 unNeptunus root: Sector size: 4096
Jun 29 18:01:04 unNeptunus root: Filesystem size: 1.82TiB
Jun 29 18:01:04 unNeptunus root: Block group profiles:
Jun 29 18:01:04 unNeptunus root: Data: single 8.00MiB
Jun 29 18:01:04 unNeptunus root: Metadata: single 8.00MiB
Jun 29 18:01:04 unNeptunus root: System: single 4.00MiB
Jun 29 18:01:04 unNeptunus root: SSD detected: no
Jun 29 18:01:04 unNeptunus root: Incompat features: extref, skinny-metadata
Jun 29 18:01:04 unNeptunus root: Number of devices: 1
Jun 29 18:01:04 unNeptunus root: Devices:
Jun 29 18:01:04 unNeptunus root: ID SIZE PATH
Jun 29 18:01:04 unNeptunus root: 1 1.82TiB /dev/sdg1
Jun 29 18:01:04 unNeptunus root: 
Jun 29 18:01:04 unNeptunus emhttp: check_pool: /sbin/btrfs filesystem show /dev/sdg1 2>&1
Jun 29 18:01:04 unNeptunus kernel: BTRFS: device fsid f9d1f8b9-2e2f-44a8-b3af-7148521794b3 devid 1 transid 5 /dev/sdg1
Jun 29 18:01:04 unNeptunus emhttp: cacheUUID: 
Jun 29 18:01:04 unNeptunus emhttp: cacheNumDevices: 1
Jun 29 18:01:04 unNeptunus emhttp: cacheTotDevices: 0
Jun 29 18:01:04 unNeptunus emhttp: cacheNumMissing: 0
Jun 29 18:01:04 unNeptunus emhttp: cacheNumMisplaced: 0
Jun 29 18:01:04 unNeptunus emhttp: cacheNumExtra: 1
Jun 29 18:01:04 unNeptunus emhttp: shcmd (2463): mkdir -p /mnt/cache
Jun 29 18:01:04 unNeptunus emhttp: mount error: No file system (no btrfs UUID)
Jun 29 18:01:04 unNeptunus emhttp: shcmd (2464): umount /mnt/cache |& logger
Jun 29 18:01:04 unNeptunus root: umount: /mnt/cache: not mounted
Jun 29 18:01:04 unNeptunus emhttp: shcmd (2465): rmdir /mnt/cache

    sdf: 

    Jun 29 18:02:27 unNeptunus emhttp: writing MBR on disk (sdf) with partition 1 offset 64, erased: 0
Jun 29 18:02:28 unNeptunus emhttp: re-reading (sdf) partition table
Jun 29 18:02:28 unNeptunus emhttp: shcmd (2620): udevadm settle
Jun 29 18:02:28 unNeptunus kernel: sdf: sdf1
Jun 29 18:02:28 unNeptunus kernel: sdf: sdf1
Jun 29 18:02:28 unNeptunus rc.diskinfo[8978]: PHP Warning: Missing argument 2 for force_reload() in /etc/rc.d/rc.diskinfo on line 634
Jun 29 18:02:28 unNeptunus rc.diskinfo[8978]: SIGHUP received, forcing refresh of disks info.
Jun 29 18:02:28 unNeptunus rc.diskinfo[8978]: PHP Warning: Missing argument 2 for force_reload() in /etc/rc.d/rc.diskinfo on line 634
Jun 29 18:02:28 unNeptunus rc.diskinfo[8978]: SIGHUP received, forcing refresh of disks info.
Jun 29 18:02:28 unNeptunus rc.diskinfo[8978]: PHP Warning: Missing argument 2 for force_reload() in /etc/rc.d/rc.diskinfo on line 634
Jun 29 18:02:28 unNeptunus rc.diskinfo[8978]: SIGHUP ignored - already refreshing disk info.
Jun 29 18:02:28 unNeptunus emhttp: shcmd (2621): set -o pipefail ; mkfs.btrfs -f -K -dsingle -msingle /dev/sdf1 |& logger
Jun 29 18:02:29 unNeptunus root: btrfs-progs v4.7.2
Jun 29 18:02:29 unNeptunus root: See http://btrfs.wiki.kernel.org for more information.
Jun 29 18:02:29 unNeptunus root: 
Jun 29 18:02:29 unNeptunus root: Label: (null)
Jun 29 18:02:29 unNeptunus root: UUID: 49350932-ba89-4fd9-8fe0-2a81800e7e3c
Jun 29 18:02:29 unNeptunus root: Node size: 16384
Jun 29 18:02:29 unNeptunus root: Sector size: 4096
Jun 29 18:02:29 unNeptunus root: Filesystem size: 1.82TiB
Jun 29 18:02:29 unNeptunus root: Block group profiles:
Jun 29 18:02:29 unNeptunus root: Data: single 8.00MiB
Jun 29 18:02:29 unNeptunus root: Metadata: single 8.00MiB
Jun 29 18:02:29 unNeptunus root: System: single 4.00MiB
Jun 29 18:02:29 unNeptunus root: SSD detected: no
Jun 29 18:02:29 unNeptunus root: Incompat features: extref, skinny-metadata
Jun 29 18:02:29 unNeptunus root: Number of devices: 1
Jun 29 18:02:29 unNeptunus root: Devices:
Jun 29 18:02:29 unNeptunus root: ID SIZE PATH
Jun 29 18:02:29 unNeptunus root: 1 1.82TiB /dev/sdf1
Jun 29 18:02:29 unNeptunus root: 
Jun 29 18:02:29 unNeptunus emhttp: check_pool: /sbin/btrfs filesystem show /dev/sdf1 2>&1
Jun 29 18:02:29 unNeptunus kernel: BTRFS: device fsid 49350932-ba89-4fd9-8fe0-2a81800e7e3c devid 1 transid 5 /dev/sdf1
Jun 29 18:02:29 unNeptunus emhttp: cacheUUID: 
Jun 29 18:02:29 unNeptunus emhttp: cacheNumDevices: 1
Jun 29 18:02:29 unNeptunus emhttp: cacheTotDevices: 0
Jun 29 18:02:29 unNeptunus emhttp: cacheNumMissing: 0
Jun 29 18:02:29 unNeptunus emhttp: cacheNumMisplaced: 0
Jun 29 18:02:29 unNeptunus emhttp: cacheNumExtra: 1
Jun 29 18:02:29 unNeptunus emhttp: shcmd (2631): mkdir -p /mnt/cache
Jun 29 18:02:29 unNeptunus emhttp: mount error: No file system (no btrfs UUID)
Jun 29 18:02:29 unNeptunus emhttp: shcmd (2632): umount /mnt/cache |& logger
Jun 29 18:02:29 unNeptunus root: umount: /mnt/cache: not mounted
Jun 29 18:02:29 unNeptunus emhttp: shcmd (2633): rmdir /mnt/cache

     

    [SOLVED] Cache disks as "new disk", not possible to get cache pool working

    in General Support

    Posted 

    wipefs -a /dev/sdg1
/dev/sdg1: 8 bytes were erased at offset 0x00010040 (btrfs): 5f 42 48 52 66 53 5f 4d

wipefs -a /dev/sdg
/dev/sdg: 2 bytes were erased at offset 0x000001fe (dos): 55 aa
/dev/sdg: calling ioctl to re-read partition table: Success

wipefs -a /dev/sdf1

wipefs -a /dev/sdf
/dev/sdf: 2 bytes were erased at offset 0x000001fe (dos): 55 aa
/dev/sdf: calling ioctl to re-read partition table: Success

    Executed, same result

     

    Log: 

    Jun 29 17:24:24 unNeptunus rc.diskinfo[8978]: PHP Warning: Missing argument 2 for force_reload() in /etc/rc.d/rc.diskinfo on line 634
Jun 29 17:24:24 unNeptunus rc.diskinfo[8978]: SIGHUP received, forcing refresh of disks info.
Jun 29 17:24:24 unNeptunus rc.diskinfo[8978]: PHP Warning: Missing argument 2 for force_reload() in /etc/rc.d/rc.diskinfo on line 634
Jun 29 17:24:24 unNeptunus rc.diskinfo[8978]: SIGHUP received, forcing refresh of disks info.
Jun 29 17:24:24 unNeptunus rc.diskinfo[8978]: PHP Warning: Missing argument 2 for force_reload() in /etc/rc.d/rc.diskinfo on line 634
Jun 29 17:24:24 unNeptunus rc.diskinfo[8978]: SIGHUP received, forcing refresh of disks info.
Jun 29 17:24:24 unNeptunus emhttp: shcmd (2222): set -o pipefail ; mkfs.btrfs -f -K -dsingle -msingle /dev/sdg1 |& logger
Jun 29 17:24:25 unNeptunus root: btrfs-progs v4.7.2
Jun 29 17:24:25 unNeptunus root: See http://btrfs.wiki.kernel.org for more information.
Jun 29 17:24:25 unNeptunus root: 
Jun 29 17:24:25 unNeptunus root: Label: (null)
Jun 29 17:24:25 unNeptunus root: UUID: 093ff426-5de6-46b3-ac66-46b4f70b8314
Jun 29 17:24:25 unNeptunus root: Node size: 16384
Jun 29 17:24:25 unNeptunus root: Sector size: 4096
Jun 29 17:24:25 unNeptunus root: Filesystem size: 1.82TiB
Jun 29 17:24:25 unNeptunus root: Block group profiles:
Jun 29 17:24:25 unNeptunus root: Data: single 8.00MiB
Jun 29 17:24:25 unNeptunus root: Metadata: single 8.00MiB
Jun 29 17:24:25 unNeptunus root: System: single 4.00MiB
Jun 29 17:24:25 unNeptunus root: SSD detected: no
Jun 29 17:24:25 unNeptunus root: Incompat features: extref, skinny-metadata
Jun 29 17:24:25 unNeptunus root: Number of devices: 1
Jun 29 17:24:25 unNeptunus root: Devices:
Jun 29 17:24:25 unNeptunus root: ID SIZE PATH
Jun 29 17:24:25 unNeptunus root: 1 1.82TiB /dev/sdg1
Jun 29 17:24:25 unNeptunus root: 
Jun 29 17:24:25 unNeptunus emhttp: check_pool: /sbin/btrfs filesystem show /dev/sdg1 2>&1
Jun 29 17:24:25 unNeptunus kernel: BTRFS: device fsid 093ff426-5de6-46b3-ac66-46b4f70b8314 devid 1 transid 5 /dev/sdg1
Jun 29 17:24:25 unNeptunus emhttp: cacheUUID: 
Jun 29 17:24:25 unNeptunus emhttp: cacheNumDevices: 2
Jun 29 17:24:25 unNeptunus emhttp: cacheTotDevices: 0
Jun 29 17:24:25 unNeptunus emhttp: cacheNumMissing: 0
Jun 29 17:24:25 unNeptunus emhttp: cacheNumMisplaced: 0
Jun 29 17:24:25 unNeptunus emhttp: cacheNumExtra: 2
Jun 29 17:24:25 unNeptunus emhttp: shcmd (2232): mkdir -p /mnt/cache
Jun 29 17:24:25 unNeptunus emhttp: mount error: No file system (no btrfs UUID)
Jun 29 17:24:25 unNeptunus emhttp: shcmd (2233): umount /mnt/cache |& logger
Jun 29 17:24:25 unNeptunus root: umount: /mnt/cache: not mounted
Jun 29 17:24:25 unNeptunus emhttp: shcmd (2234): rmdir /mnt/cache

     

×
×
  • Create New...