Jump to content

JorgeB

Moderators
  • Posts

    67,539
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. These are fatal with btrfs, it means some writes were lost, there are some recovery options here, most likely to work for this is option 2, btrfs restore.
  2. If you don't need a pool or the other btrfs features like snapshots xfs should give much better results.
  3. Hopefully we'll get ZFS in the near future, and that will have some advantages over btrfs (also some disadvantages), but I fear that write amplification might also be an issue, since it's a also a COW filesystem.
  4. So are mine, and like 90% or more are from one Windows Server 2012 R2 VM, I also have WIndows 8.1 and Windows 10 VMs and those don't write much, but total writes were already reduced 15x since -beta25, like mentioned btrfs also will have some write amplification, there's a study about that, I can live with 200GB per day, just couldn't with 3TB per day.
  5. Some extra writes with VMs and btrfs are normal, there's always some write amplification with btrfs compared for example with xfs, but starting with the -beta25 amplication should be noticeably smaller, you can see my experience here: https://forums.unraid.net/bug-reports/stable-releases/683-docker-image-huge-amount-of-unnecessary-writes-on-cache-r733/?do=findComment&comment=10142
  6. Me neither with that, maybe someone else can help, if you are using the plugin you can ask in the plugin support thread.
  7. Sorry, missed your reply, just make sure backups are up to date.
  8. SMART test isn't influenciet by cables, disk should still be under warranty, and a failed SMART test is more than enough to get a replacement.
  9. It will be recognized, -beta25 is where the new alignment was introduced, curiously just recently found out that the new alignment works even in previous releases, but only for pools, though you can still have a single device btrfs "pool".
  10. SMART test failed, disk needs to be replaced.
  11. What raid profile are you using? Raid0/1/10 are considered stable, RAID5/6 still have some issues, though it usually can be used without issues with stable hardware, I do. What do you mean? You can create and share a btrfs cache pool for a long time now.
  12. Should work fine, you need the appropriate cables, also you only need a 16port HBA for dual link (if supported by the backplanes), you can't use 24 ports with that chassis. No gains in that part, unless used with a Datablod support LSI expander, it might still be a little faster because the HBA is PCIe 3.0
  13. New config won't delete any data drive content, it will by default re-sync parity, if parity is still valid you can check that box before array start, still a good idea to run a parity check after.
  14. It would be logged as metadata in the syslog, instead of the file name, though it's strange the scrub aborting. You can try deleting that file and then run another scrub.
  15. You can get it from the diagnostics, but make it's still the same confirguration: Jun 14 17:45:51 Tower kernel: md: import disk0: (sdc) WDC_WD40EZRZ-75GXCB0_WD-WCC7K1HAZY9C size: 3907018532 Jun 14 17:45:51 Tower kernel: md: import disk1: (sdd) WDC_WD40EZRZ-00GXCB0_WD-WCC7K0HN8TLJ size: 3907018532 Jun 14 17:45:51 Tower kernel: md: import disk2: (sdb) WDC_WD40EZRZ-00GXCB0_WD-WCC7K2CVN674 size: 3907018532 Disk0 was parity.
  16. Not if you keep the same flash drive. None of the above, Unraid only supports reiserfs, xfs and btrfs, xfs is the recommended filesystem for most.
  17. You just assign it to a data drive slot and start the array, preclear is optional. Upgrade parity, when that's done upgrade the data drive with the old parity, again preclear is optional. Correct.
  18. Disable array auto-start by editing disk.cfg on your flash drive (config/disk.cfg) and changing startArray="yes" to "no", VMs won't auto-start if the array is started manually.
  19. That's not the part that lists what's affected, please post diags after a scrub.
  20. See here, make sure you're using the correct "power supply idle control" setting.
  21. That's what it will show unless you're running a balance, it's the normal status.
  22. Macvlan call traces are usually related to having dockers with a custom IP address, more info here:
×
×
  • Create New...