Search results

Where did the package go? $ pkg search ImageMagick $ sudo pkg install ImageMagick7 Updating FreeBSD repository catalogue... FreeBSD repository is up to date. All repositories are up to date. pkg: No packages available to install matching 'ImageMagick7' have been found in the repositories $...

From mount_nfs: nolockd Do not forward fcntl(2) locks over the wire via the NLM protocol for NFSv3 mounts or via the NFSv4 protocol for NFSv4 mounts. All locks will be local and not seen by the server and likewise not...

Thread successfully hijacked) We have many VPS hosts, which are constantly created and destroyed, use an NFS-shared file as a lock (via lockf or flock commands). Sometimes some of the locks are never cleared and the file remains locked forever, even if the offending host has been destroyed in...

Doesn't snapshot mean something from the past? In which case this is not a reason to worry, if the unsnapshotted FS is bootable anyway? I think this is the case, it least by looking in freebsd-update: # Create a boot environment if enabled if [ ${BOOTENV} = yes ]; then...

This is the output: $ bectl list BE Active Mountpoint Space Created default NR / 1.90G 2023-05-10 19:57 The machine was freebsd-updated to 13.2-RELEASE-p1 after that time. Does it mean the good BE was lost by deleting the snapshot?

Thanks a lot! Shooot.... this is so unbelievably stupid of me) I removed all snapshots on all servers without waiting for replies here. This means the machine will not come up after next boot? I hope next freebsd-update will make sure the machine is bootable. I will disable this CreateBootEnv...

Hm, I do have them on my 13.1-13.2 machines. Is this unasked creation a new feature? Does freebsd-update create them and leaves them around? [rihad@master ~]$ zfs list -t snap NAME USED AVAIL REFER MOUNTPOINT zroot/ROOT/default@2022-08-17-10:53:03-0...

Yeah, if most files or their final part are much smaller than 4096 bytes it's obviously that much wasted space per entry, unless OS/HW do some tricks to minimize that. So I've decided to play it safe and stay with 512 (ashift=9). Which is quite natural considering I no longer have a choice))

There's no such information it seems. $ sudo smartctl -a /dev/nvme0 smartctl 7.3 2022-02-28 r5338 [FreeBSD 13.2-RELEASE amd64] (local build) Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Number...

Oh, damn, I forgot that it's an existing pool with root FS on it, and it was created with ashift=0 (meaning query disk for its block size) when installing FreeBSD, so got no options here. But still it would be nice to know of pros and cons. Thanks)

I've just temporarily disabled zfs compression, created a file 100mb in size using dd if=/dev/urandom on an "ashift=12" zpool, and its size both in du -sh and du -shA and df -h of the filesystem it's on were exactly 100M. Good.

Does it really matter considering that it's just a maximum? Smaller files can very well have record size equal to the size of the file, not less than 4096 and not more than recordsize. At least this is what st_blksize field from stat implies. I'm currently assessing the possibility to use...

Just tried it. Unforunately augeas (augtool print) doesn't recognize the format of /etc/pkg/FreeBSD.conf or /etc/freebsd-update.conf or /usr/local/etc/tarsnap.conf and probably many others, which limits its usefulness in our case.

Nope, turning on dedup prefetch (like it was in 11.4) decreased performance further. Now I only have this change: vfs.zfs.vdev.async_write_min_active=1 I also reverted vfs.zfs.arc.min from 2gb to 0 as per default. Waiting until tomorrow (c).

Wow, this value in 11.4 defaults to 1, and to 0 in 13.0: vfs.zfs.dedup.prefetch: Enable prefetching dedup-ed blks Maybe this is it. Ok, so just these two values with their defaults after the comment sign: vfs.zfs.vdev.async_write_min_active=1 #2 vfs.zfs.dedup.prefetch=1 #0 Waiting until...

What I'm trying to battle here are absolutely intolerable interactivity blocks for up to 20-60 seconds or so, not performance in the first place (although overall throughput also suffers compared to 11.4 as mentioned previously). During problem times, 20-60sec is how long I need to wait for ssh...

It's a general issue, I guess. Not only PG, ElasticSearch also benefits N-fold from zfs dedup, which starts working instantly and transparently to any app by simply turning the knob. Also, manuals state that clones can only be created from snapshots, and snapshots are read-only. Not sure how to...

Sure. It's a staging environment having a bunch of initially identical PostgreSQL databases. Space-wise zfs dedup suits perfectly.

A tiny bit, maybe. Still tweaking, the 75 above are today's changes and I need to see how it feels. Along with interactivity I'm trying to bring back sheer throughput, because the daily task that took 5 hours in 11.4 is now taking 6+ hours in 13.0, this is 20%+ speed penalty.

I have found that during heavy i/o this sysctl: kstat.zfs.misc.dmu_tx.dmu_tx_dirty_throttle: 53480 keeps increasing in small bursts. These artificial halts hinder interactivity. Trying to find a way to eliminate them completely or considerably increase their activation threshold. Here are my...