Search results for query: bcache

...╭──────────────────────────────────────────────────────────────────────╮ ┊ Node ┊ DRBD ┊ LUKS ┊ NVMe ┊ Cache ┊ BCache ┊ WriteCache ┊ Storage ┊ ╞══════════════════════════════════════════════════════════════════════╡ ┊ gateway ┊ - ┊ - ┊ - ┊ + ┊ - ┊ + ┊ + ┊ ┊...

...section and uncommented it: ACTION!="remove", SUBSYSTEM=="block", \ KERNEL=="loop*|mmcblk*[0-9]|msblk*[0-9]|mspblk*[0-9]|nvme*|sd*|vd*|xvd*|bcache*|cciss*|dasd*|ubd*|ubi*|scm> OPTIONS+="watch" That has the bad effect, that I can access my server only via ssh but no more via web interface...

...small cluster - 2 proxmox nodes, and one PBS node first older proxmox host is a dell - rackmount - has blend of perc hardware raid, plus bcache SSD to make SATA data pool less-slow (in theory) newer-ish proxmox host is a supermicro rackmount, has pure SSD (2.5" drives) hardware raid LSI...

...to the PVE nodes as other firmware updates were available previously and have been applied. proxmox-secure-boot-support fwupd udisks2 udisks2-bcache udisks2-zram udisks2-lvm2 udisks2-btrfs intel-microcode I've updated the /etc/fwupd/daemon.conf changing the below line from EspLocation= to...

Correct i mean the ZFS mirror. Once i have all the necessary components, i'll explore which caching option to implement, considering your advice about RAM. I plan to implement the 3-2-1 backup strategy. I’m considering converting the Dell Optiplex into a Proxmox Backup Server. Additionally, I...

...for VMs, when in fact they would be reading most of what they need off the SSD. Alternatively, you can even considering other caching options (bcache or dm-cache). Note some people do not like L2ARC as it increases your RAM consumption at the same time and if possible, adding RAM is...

...following additional packages on my 3 new PVE nodes apt update && \ apt install -y \ proxmox-secure-boot-support \ fwupd \ udisks2 \ udisks2-bcache \ udisks2-zram \ udisks2-lvm2 \ udisks2-btrfs \ intel-microcode && \ apt full-upgrade -y After the above packages were installed, the following...

Again, I meant the official support. I always look through the enterprise class glasses. Sure there are people on the interwebs helping. I ran flashcache years ago also very successfull with Proxmox VE without any (software) problems. Yes, nomenclature again. I can see your point, yet I would...

Well, strictly speaking that is also not true (in the "help" sense) as e.g. I would be happy to help here with bcache (not fs). I am not saying I have a better vocabulary, but I do not like certain (ambiguous) terms. The most neutral term would be probably non-standard - if one wants to...

Depending on what kind of NVMe it is, the log might not be such a great idea. The cache works well with ZFS. Also, filesystem agnostic you can have a look at bcache: https://docs.kernel.org/admin-guide/bcache.html

...caching with Ceph, and even setups that benchmarked well didn't actually perform particularly well in our real world usage. We did run with bcache backed OSDs for a bit, it was fine when you were dealing with hot data, but cold data could be painfully slow - ultimately this came down to how...

Hello from the future! 2024... did you ever get around to posting and sharing your findings?

I could not find any posts regarding zoned device use on this forum. Be it an HM-SMR (w/bcache?) or NVMe ZNS, has anyone used these setups as it makes perfect sense for a ... well ... hypervisor forum to ask on. Thanks.

...proxmox server is the BIOS boot partition. I see it just now: on the proxmox server ( there /dev/sdb1 ..) the error belongs to the message: "bcache_invalidate: block (0, 0) still dirty" Do you have any idea how to get rid of this? You can leave this posting unpublished .. or you may remove...

...Accepted input: [y] 32.024392 label/label.c:2054 Set last byte mixed block sizes physical 4096 logical 512 using 512 32.024402 device/bcache.c:229 Limit write at 0 len 131072 to len 1082 rounded to 1536 32.836628 label/label.c:2024 Error writing device /dev/sdb1 at 1080 length 2. 32.976061...

...-n docker_home -L 30GB pm01_open .. 18:06:00.034945 label/label.c:1957 Error writing device /dev/sdb1 at 5632 length 1536. 01.051386 device/bcache.c:1374 WARNING: bcache_invalidate: block (0, 0) still dirty. 01.051424 format_text/format-text.c:965 Failed to write metadata to /dev/sdb1...

...kernel. Been suffering from this controller down issue for the last two months. Already destroyed one XFS filesystem backed by bcache in writeback mode. Fortunately backup to the rescue. :/ Three 990 Pro 2TB in my server, all newest firmware 4B2QJXD7. Two of the 990 Pros are of the...

You can mount bachefs somewhere, look at their official documentation for this. Only then you can add this mounted directory via Datacenter --> Storage --> Add "Directory" to hold "Disk image"s. At the end PVE does not know that this involves bachefs.

anyone knows what to write `/etc/pve/strorage.cfg` for bcache in proxmox?

Agreed. And much safer than moving the DB/WAL over to another device. Using bcache, if the cache device fails, it just falls through to the disks. In CEPH if the DB/WAL device fails - you lose all the devices it was serving. :(