last1: features only can be turned on

k

I have a different question, I'm trying to remove this dataset that I brought in over zfs receive ( from another FreeBSD system )

can you just try it and see if it recv's ?

and it keeps on saying the dataset is busy

cannot destroy snapshot zfs/liveindexes@liveindexes-20230509233628: dataset is busy

I've unmounted the dataset, I've rebooted the box

lsof shows nothing using that location

last1: did you zfs hold it?

what's that ?

zfs-hold – hold ZFS snapshots to prevent their removal

If a hold exists on a snapshot, attempts to destroy that snapshot by

using the zfs destroy command return EBUSY.

`zfs holds zfs/liveindexes@liveindexes-20230509233628` would show them

oh wow, yep, my zfs backup had done that

yep, it's gone now

let me try receiving from debian now

last1: i used to use them when i'd create a bunch of hourly snapshots; hold a weekly and monthly one so they don't get culled after 2 weeks

it appears to be working from debian

it's a 180Gb dataset so it might take a bit

trafshow shows healthy data transfers

you could create a fresh dataset with a couple of files to use as a test

true, I jumped right on the real deal :)

rathre than transfer the 180gb and then watch it fail

should take about 10-12 minutes

*should have*

still ongoing

I also should have used |pv

haha, yep

well, it completed

no errors

just that on origin it says to occupy 300Gb and here only 128

I'm doing a du -mc

on the receive side it shows as 128Gb with lz4 compression on ( it was off on source ) and 2.88X compressratio

128 x 2.88 gives about the right size

nice

Is there an interface type that can be used to alias an interface (not just rename it)? Like create an alias interface mynic0 that is the same as physical interface em0?

_xor: i don't think so, unless it's a vlan or a lagg with a single interface

but that's not an alias

I accidentally made a little mess of a zfs pool the other day - i had data in a zfs send id redirected to a file and needed that so i did a recv to that drive and in the process it left my server unusable since it remapped some directories on my root. I am looking to get my storage pool back today.

A bit of reading this mkrning i think i figured it but want to see if i missed something..

If what i have read is true.. i should take a memstick image, boot it. Import the pool. Then export it. After which i boot my normal server boot drive.. zfs import it with -R with an /alternate root mountpoint. Kill the offending stuff that steps on my server's directories export. reboot with my normal system and then import it

as normal..

that sounds like it could work

so, my arch arm installation on the rpi 4 killed itself again I think i'll move it to BSD. I'm running bsd on an x86 server already. as arm64 is a T1 platform for freebsd I hope it'll be more stable

hi, I want record the default audio output. I mean, I have virtualbox with a bsd vm and I want record the audio output from the virtualmachine.. If I try with ffmpeg -i /dev/dsp3.0 I have "device busy" error. I'm pretty sure that /dev/dsp3.0 is the right device... If I poweroff the vm the device is free and I can access it.

yourfate: dunno how upto date this is: wiki.freebsd.org/arm/Raspberry%20Pi but some things say they're unsupported

Title: arm/Raspberry Pi - FreeBSD Wiki