how much overhead would it cause if i tcp connected/disconnected to the ssh port once a minute to check reachability?

looks pretty insignificant re cpu, adds ~26mb ram for a sec or 2

looks like a pretty nice unprivileged ping hack

hello

anyone else testing out the 15 prerelease?

i just installed the openssl package so some code i'm compiling could use it, now anything that uses ssl is broken? like a cargo fetch errored ssl peer ceritificate or ssh remote key was not ok (ssl cert problem: unable to get local issuer cert)

sudo pkg install ca_root_nss fixed it

kerneldove I just had ca_root_nss fail to build with poudriere a second ago

i guess what happened is the tools detected that openssl pkg was now installed so it used that instead of internal code, and openssl pkg needed root cas pkg installed

haven't gotten a chance to look at that log yet though

last installworld/installkernel I did broke "cc" for me LOL

I'm learning to be diligent with bectl though

ya that's smart. zfs snapshots too

I also had to turn off a all my legacy USB support in the UEFI, or it fails to boot the prerelease

gets to the ACPI line and just hangs there, requires hard power

pretty sure i had to do the same thing years ago with a new ryzen cpu box

Normally my rigs work perfect for FreeBSD or Linux, because my platform is a decade old (X99)

ah that's prolly a bug or deprecation then i'd report it

yeah, I will when I get a GUI/Browser up and going

prerelease still has no binary pkg support (waiting on beefy18), so I'm in for a few days of compiling

also not 100% sure how to report it. guess as a regression of some sort, listing my USB legacy support that I had to disable

BUT, guess not needing that legacy support is anymore might actually be an improvment too LOL

ya true but still good to tell them i think. either -current mailing list or bugzilla?

have x11/kde building right now. but honestly considering just doing like cde or xfce or something

kde build might take longer than I want to wait

i3 is nice too fwiw

i3 is a tiler?

yep

i was almost sure i wouldn't like tilers but now i'll never go back

my kid loves bspwm

that a tiler too?

yeah

nice, smart kid

all I remember is ctrl+enter brings up a terminal, and I can launch my stuff from there

I'm not smart enough to do anything else with it, so I get windows crushed in there and just drag the mouse over them for sloppy focus

ya i set up a rofi hot key so i type hotkey into kb, get a 'picker' overlay, type in few letters of app name, enter, it loads in a new tile

hyprland is getting a lot of hype

If I was passionate about getting Wayland going, I'd probably give that a shot

river is just fine

i'm sticking with x11 (and i guess xlibre when it's in pkgs) too much bickering over wayland

i want my software without social drama i can get anywhere else

kerneldove I'm unsure about xlibre and hyprland both. and mainly because of the drama you just mentioned

the only drama for xlibre is ppl that were pissed it didn't participate in the drama. x11 and wayland are both the past to me. xlibre just wants to focus on evolving the code and that's what i want. even if the guy who started it has weird ideas i only care about code

Yeah, I haven't really followed along. But for the most part I'm the same... run whatever code does the best, or at least that is my goal

configuring every package that is a dep for x11/kde would take me a week in itself. but I really don't like the DE depending so much stuff. It even has like 3 different SQL dbs as deps

yep

I just really love the KDE launcher though

ya that's what pushed me away from gnome/kde. too heavy. i don't want a full gui env, just a tiler and launcher is enough

and its all inclusive settings

maybe you can recreate it with a tiler?

ya that part is nice i guess. less learning

well "plank" comes pretty close to being the launcher I want

i'd look into rofi. if it works for you it would cut out lots

I ran xfce+plank for more than a decade

yeah, so many choices

this time I'm gonna make a BE, install kernel, make another BE, install world, and then test to see if I can still rebuild both before doing anything else

if that works, I'll make another BE, and go back to my pkg building LOL

hey what about testing in a vm first?

kerneldove I might do that on my Linux box... I have one vm there for the KDE Desktop folks. But I can spin up another to tinker with

yay for testing

I don't even have virtualization turned on in my UEFI right now. I was having so much trouble even getting this stuff to boot, I went back to "optimized defaults" and started fresh

and for whatever odd reason, VT is OFF by default

It wasn't as popular way back in 2015 when the boards were made

If I was smart, this would have been a 14.3 release install, and the current branch fun would have been in a vm again ;)

was doing Fedora 42 on this box, but everything worked so well it got really boring

kerneldove what branch on are on? and do you daily FreeBSD?

sorry for all the questions, I'm just trying to stay awake

I should probably just call it a night, and check the status of the builds in the morning

14.3 ya i daily, server and workstation

I have been using fail2ban (yes I am aware of blacklistd) and it was woring. But then after upgrades it is not working.

I have this feeling that patterns has changed and it is simply no longer matching the new patterns. Anyone else experienced this? I say as I dig into this.

That swedish mirror is really bad. Fails to deliver big packages (nextcloud, llvm, perl5). I have to use direct links to the pao mirror to get the files I need. Can't we get anything better? Can't we *pay* for anything better?

shoot your feedback to clusteradm@

they may not have any idea the situation it's in

I've adjusted the size of two drives in the AWS freshports instance (which is now offline). zpool data01 cannot be mounted. dpaste.org/hMjS1

how do you set more routes in rc.conf, I have two separate subnets on two separate interfaces, and I want to pass between them, but theres currently no route... whats the best way to do this, or shoudl I simply bridge it?

Interesting, data01 shows up on zpool import, but it says the drive is not available, I see it there: dpaste.org/hLryP#L

I'm sure this zpool, can be recovered, however, I don't know the fix.

polarian, look at the bottom of this section: docs.freebsd.org/en/books/handbook/…d-networking/#network-static-routes

ah I checked the handbook, I must have missed this

CrtxReavr: also your username looks familiar? do you use XMPP?

polarian, there used to be a better syntax example in /etc/defaults/rc.conf

I might still have xmpp records.

hmmm

deja vu...

anyways thanks for the links

I guess I don't anymore. . . it was setup via Google Chat.

I guess I could re-add them.

'Course, I used to have over 300 active trioptimum.com users.

dvl, In your paste dpaste.org/hLryP line 7 "zpool import" it says nda2p1 UNAVAIL due to "cannot open". Line 40 shows it as a swap partition not a zfs partition.

Hi guys

I am Retrofan

but using my ZNC

rwp: Yes... Seems like the swap partition is a dedicated drive.

rwp: did I miss something?

But... "zpool import" wants it for a zfs pool? But gpart show says it is a swap partition. That's conflicting to me.

If it were working I think gpart show would say it was a freebsd-zfs partition.

Since it says it is a swap partition then it can't be imported as a zfs pool partition.

I think something got scrambled there.

the swap partition is on nda1?

[17:09 aws-1 dan ~] % swapinfo

Device 1K-blocks Used Avail Capacity

/dev/nda2p1 262143960 0 262143960 0%

kevans, We are looking at dpaste.org/hLryP and look at the difference between zpool import and the gpart show sections.

Maybe I am scrambled on looking at it...

right, i'm confused because line 40 is nda1p1

Oh I am the confused one. I confused nda1 and nda2 there. Sorry.

but swapinfo doesn't lie

so it seems that you're right but for the wrong reason, and clobbering partition state with swap would probably do it

and swapinfo -h shows a 250G partition. That seems unfortunate.

zpool import wants nda2p1 and gpart show says nda2p1 is labeled freebsd-zfs but import says "cannot open" that partition.

[17:10 aws-1 dan ~] % cat /etc/fstab

/dev/nvd2p1 none swap sw 0 0

rwp: right, presumably all of the zfs label bits got blown away if it ended up as a swap partition

So, that's unfortunate. The devices got renumbered... Ouch.

Sorry I confused things there because I confused nda1 and nda2. Sorry. But nvd2p1 is not nda1p1 either.

rwp: You led us down the correct path.

Question now is to how to avoid this in future...... Stop using a full drive for swap.

It was the lysdexia talking. Or is it dyslexia? That's the problem. One can never know. :-)

dvl: is this specific use a recoverable scenario in some other way, or is this somewhat fatal?

or i guess, rather: can it be rebuilt?

kevans: I have no idea about the first question.

kevans: However, I have a snapshot of the real data volume from last night.

Now, how to get that back in nicely - I can always run without swap.

ah, ok- so you could rebuild it from a snapshot, which is probably less time consuming than trying to get the pool back into a sane state (if even possible)

I am still confused how I helped there, other than by stirring things up, because zpool import wants /dev/nda2p1 and gpart show nda2 lists that as being there okay, but import says "cannot open".

rwp: he wouldn't have confirmed with swapinfo if you hadn't accidentally thought it was a swap partition

Oh! Now I see it! Gotcha. Victory unintentional then. :-}

rwp: I suspect the root cause is device renumbering combined with two single-partiition drives, one for swap and one for the data01 zpool

yes, i'd take it as an 80%+ win at the very least

rwp: You indeed won this one, thank you.

I will update forums.freebsd.org/threads/zpool-mi…fter-increasing-disk-size-aws.98986

i wonder if we could add some guardrails that would've prevented this

kevans: Yes, I think so.

kevans, BTW... I deduced an rc.conf configuration to use the spawn-fcgi rc script be invoked launching multiwatch to monitor fcgiwrap processes. dpaste.org/f92Yb

I have requested a wiki account and put something similar to this in a page there.

*will put. I actually need something somewhat more complicated. I need multiple pools, in multiple jails. But that's the basic part of it.

rwp: i would argue that that's a good candidate for a /usr/local/etc/rc.conf.d/spawn_fcgi.sample to be packaged with it

Agreed. That would be great info to have.

My random commentary on the existing spawn-fcgi rc script is that it appears to have been written thinking only about use with PHP and not about use with generic FastCGI. I am using it with cgit and gitweb git repo browsing. It would be nice if it were more generically written. But it can be coerced.

And I am not sure why the author defaulted to a Unix domain permission mode of 0777 either. The default spawn-fcgi mode is 0660 which seems much more appropriate. Seems to me that one would *always* want to override that back to the 0660 default. (me shakes my head and wonders...)

Anyway... I just thought I would post that follow-up for the moment. I am still tinkering the target system into shape... Currently trying to figure out why fail2ban stopped working. It was working at one point.

dvl: did it fail immediately on first boot after resizing, or did something else happen?

kevans: Immediately upon first boot after resizing. Let

's check

dvl: if you haven't blown it away yet, try to just swapoff and import the pool

kevans: here's the full boot. Swap is off. Let's try.

^ have not retried the import yet

kevans: fails: dpaste.org/bjnyj

Well, `sudo swapoff -a` does not umount the swap.

... because I commented that line out in /etc/fstab

dum-di-dum, wonder when there's packages for -current again... I don't have hardware to build everything...

kevans: success: forums.freebsd.org/threads/zpool-mi…fter-increasing-disk-size-aws.98986

dvl: scrub the shit out of it just in case, and you might still need to restore some bits from the snapshot

kevans: Brilliaant idea.

kevans: Already started a scrub. ;)

yay

Ltning: typically around 12 +/ a day or two for a full build + sync

You guys rock!

i confirm

Is there a way to switch a zpool from using partition numbers to GPT labels?

divlamir, Yes. But you have to boot an alternate boot path. Then import using the -d option pointing to the /dev/gpt directory.

Here is some doc: openzfs.github.io/openzfs-docs/Proj…nging-dev-names-on-an-existing-pool

That doc is OpenZFS which is Linux centric using /dev/disk/by-vdev but on FreeBSD one would "zpool import -d /dev/gpt" to get that effect and switch to /dev/gpt labels.

It's also possible to do the switch one disk at a time, degrading or using a spare disk as an intermediary, taking a disk offline or replacing a disk with a /dev/gpt label disk, working through each disk one at a time. That works too. That takes a long time to do. But it can be done all online in that case. (I have done it that way.) The import -d /dev/gpt way is all at once and it is done.

Of course if one is not booting from the zfs pool then it is then trivial to change it. But root on zfs is so popular that I think that is the typical case now.

Yes, I am talking about the root pool created by the installer. My data pool is using labels. Seeing that the installer has labled the partitions zfs0 and zfs1, wounder why it wouldn't use this labels instead of nda[01]p4 ...

After reading this, it started looking a bit fragile :)

I wish the installer did this using gpt labels by default.

If this is your system that you just installed then boot the installer again and jump to a shell. It's a live iso boot image usage. Then import the pool using the -d option to switch to gpt labels. Then reboot again to the system. Just after a fresh install that should work easily. I admit I am fuzzy on the details since I have not done that for a while now.

Not fresh at all..

I'd rather try it when I have some time to spare :`)

Is this a single drive or a mirror/raidzX pool? And also swap too. It's easier to switch swap one disk at a time though since there is no data on it to preserve. But anyway...

A simple two drive mirror, mirrored swap, efiboot on both drives

Random tidbit: Don't use dashes in labels used for swap partitions. If a name such as sw-3K1G3T97B (serial number) is used then gmirror insert fails and the mirror lists as degraded. The only thing that can be done is "gmirror forget -v swap" to clear the error then try again.

I experimented to find this as it is not documented. I will guess that the dash is used for in-band control internally and this confuses things.

woudln't you just let the swapper interleave the two swap areas, rather than building a mirror of swap?

Luckily the FreeBSD installer names them simply swap0, swap1 :)

rtprio, If you do that then you have no redundancy. If a device fails then the system /might/ crash because part of its memory went away.

It's the argument mirror vs stripe, do what you need

I won't say that the system will always crash. But it is definitely likely to crash in that case of using a striped swap.

seems unlikely

So in the crazy combinations possible using the bsdinstaller defaults if one is using it to set up an 8x raidz2 for example then by default it will also set up an 8x mirror of swap.

That works. But you probably don't need that much redundancy for swap either! However having tried it I couldn't observe any performance issue with it. It just felt silly. Really for a 2 disk failure tolerance then a swap mirror of 3x devices is all that is needed.

I would partition all devices identically regardless. Anything else leads to insanity.

kevans: scan: scrub repaired 0B in 00:31:09 with 0 errors on Mon Aug 25 18:50:48 2025

dvl: \o/

hell yeah, i can use freshports again now =-)

website loads. Going to reboot.

^ yeah

Woot! Things like this where zfs pulls through in spite of everything is so super awesome. It's definitely superior. (The btrfs fans will never get it, since btrfs raid is, well, insert the usual disparaging remarks here about btrfs raid...)

commits are being processed.

dvl: oh, while you're around: how much of a pain would it be to surface `make -V USE_RC_SUBR` somewhere in the freshports interface? is this something you already collect?

rwp: I onder what would happen if swap was written to.

kevans: Trivial. It's routine to add something like that. Please create an issue and the type of output.

someone elsewhere noted in a roundabout way that it's hard to tell if an rc script is installed by a port because they're handled in a special way, outside of the plist

thanks

... output you want to see on the webpagte

dvl, Normally one might have redundancy and it would still survive. With a single device, well, some data would be lost. But you had that snapshot that could be used for recovery.

On the practical high level view though it was impossible to need swap given that pool offline and so there is that.

arc_prune I'm begging you

seriously arc_prune is the sole reason my load avg goes up and php stalls :|

is it time to go back to 13.x

Hrm. divlamir reminded me that I have a GPT disk that doesn't show up in /dev/gpt or /dev/diskid. So, one of my zpools has all ID's and then one "da5" device in the list. It's very strange.

Remilia, (me laughs) But more seriously with data01 offline freshports.org was offline and therefore the system just idling and it would be impossible for it to need to use significant swap in that case. So things worked out. And it makes sense that it worked out. But it did seem scary in concept! :-)

I think FreshPorts is all caught up.

ek, Uhm... Remember that FreeBSD kernel removes all alternate /dev device names as soon as any of the alternates are opened.

Before the devices mount then all alternate names are available. Open one and the others are removed from view by the kernel. This is most confusing!

rwp: Right. But, why would any alternate have been used in this case? It all functions perfectly normal. It just throws me off to look at.

This was better than a movie night, the day is saved :D Gonna go use your swap now

If it weren't a production system, I'd play with it to see what I could find out. I'll need to note a reminder to take a look at next available reboot.

ek, The device paths are recorded for zfs and used persistently as the first place to look when importing. But if another device path is used to import at any time then that new one becomes the persistent path.

rwp: Yep. I completely understand. Just not sure why this single device doesn't have a GUID (or any other.) When it was specifically created using one originally? I dunno. Something went goofy.

Ah, so that's why I don't see the labels from `gpart show -l` in /dev/gpt. Was wondering what is going wrong too

In any case the presence of /dev/gpt/ labels does not mean that they will be used. They could be used. And if so then would be persistent. But if the /dev/da0p2 type name is used then that becomes persistently opened and the /dev/gpt devices are hidden immediately upon open.

ek: from discussing this at $work, my interpretation is that it's a geom/zfs quirk in how things get ordered (or don't) for tasting

rwp: Right. I used /dev/diskid to create the pool. It was fine originally. Not sure what would have changed.

divlamir, Hmm... I think gpart show -l should always show the labels. They just don't show in /dev/gpt after a /dev/da0p2 is opened.

kevans: That's kinda my guess. Like, on last boot something happened with the device and, for whatever reason, the ID's weren't used but the disk was still picked up during the pool import. So, it's just running like this now.

ek, I am sure that if we knew exactly what happened along the way it would make sense. Not knowing it is impossible to guess now. Other than knowing that "something happened" which caused the pool to import using the other names.

Obviously, I can't export and re-import using -d since the ID currently doesn't exist. So, I'll just wait until next reboot opportunity.

ek: if it's just da5 and not da5pX, doesn't that mean it is not a GPT disk?

rwp: Exactly. It's just... weird. *shrugs*

(in zpool status I mean)

I keep saying computers are like cats. Subtle and quick to anger! :-)

subtle???

You ever had cats??

lol

Remilia: That was my thought initially. But, the other disks weren't partitioned or anything either. All brand new and just used via ID's to create the pool.

Remilia, If it is /dev/da5 not /dev/da5p2 then that is the entire disk and not a partition. That works but we kind'a frown on doing full disk without (GPT) partition tables now.

Originally, I was under the impression that a "zpool create" would partition the disks if they were empty. But, I see no partitions. So, yup, it's just a full disk.

Tenkawa, Yes, I have had cats, plural, before. Currently no cats now. But when I had two cats one would make trouble and would them implicate the other one who mostly liked to watch.

then it shouldn't be anywhere under gpt/

diskid is different but in my experience those are kinda... random

you might get either the id or the device name

rwp: thats not subtle... thats devious... which cats are...

ek, With "zpool create" it uses whatever device you tell it to use. If da5 then that would be the full disk. If da5p2 then that is a partition on the disk. If gpt/zK1234 (serial numbers I use) then it uses those. But whatever is used must exist at time of pool creation.

export/import might switch or might not, but the device name is stored in the imported pool

so rebooting will not change it

Rebooting will not change it.

rwp: Correct. I used /dev/diskid/DISK-* to create the pool.

If the pool is a secondary data pool then simply export and then import -d pointing to /dev/gpt to search the devices in that path and it is trivial. But if booting root on zfs then one will need to boot something like the bsdinstaller iso, launch a shell, import -d there, then reboot to the system again.

also rwp thank you for explaining but I really should think of a more gender neutral IRC nickname :(

?! :o

every time I try to answer someone I get 'answered'

rwp: That would be ideal. However, the device doesn't exist in /dev/gpt or /dev/diskid at the moment.

Remilia, Did I misgender? I am sorry and apologize if I did.

How well/possible have any of you cloned /usr from ufs to a zfs volume and remounted it on next boot? I have most of /usr already running on the volume... just not all of it and nervous ...

you probably did not

but I really did not need that explanation, when it was what I myself said above

Don't take what I say like this personally. Just a bit ago I was chatting like that with dvl and that's DVL for goodness sake! It's just me. I do that to everyone. Sorry.

Remilia: I think my biggest hurdle will be finding out why I do not get the GUID or disk ID available at boot for the pool (I think?) I won't be sure until I reboot again.

Remilia: But, the other non-partitioned disks (non-GPT) do have GUID's and disk ID's in /dev/diskid/.

Remilia, Oh, I see now, "so rebooting will not change it" if that had either a "." or a "?" on the end that would have changed how I read it entirely. I read it as a ? and answered and did not read any . there and did not see it as a statement of fact.

ek: you will not get the GUID because there is no GUID Partition Table; as for diskid, do you mean the FreeBSD boot manager or loader?

the ZFS loader would likely pull metadata from zpool, which does not have a diskid for that drive

(don't quote me on that, it's an 'educated' guess)

There's kern.geom.label.gptid.enable="0" in my loader.conf

Tenkawa, You would need to describe your system in more detail. You have a UFS install and want to convert it to ZFS? It's more than just /usr in that conversion.

Remilia: It must be. I don't see gptid's for those disks in that pool. But, each disk (aside from da5) has the /dev/diskid.

as I said, da5 was stored in zpool metadata on zpool creation/import

the other disks were stored with their diskids instead of device names

Remilia: What I'm saying is I used the diskid's to create the pool. So, somewhere along the line, that was no longer available and I'm not sure why.

it is random

I had the same issue in my pools before

... or how the pool was imported without it. Unless it just searched /dev/diskid *AND* /dev for matching metadata, maybe?

I could never get it to be 100% uniform back then and just ignored it

Remilia: Yeah. It's quite strange. It is working fine, though. There aren't any problems. Just weird to look at in zpool status output.

Remilia: Haha. That's pretty much what I've been doing.

ek: I think the pool metadata keeps old device names after export and they might just carry over like that as long as the zpool ID matches

When I was in a flaky system I had a disk dropped out of the array. Then hotswapped. Then it listed as /dev/da5p2 at that point. I could have zpool online /dev/gpt/zK1234 I think but instead I took the hint and online'd the da5p2 name, and it stuck. That's all easy to do.

Remilia: Yep. That would make sense. So, now I'm wondering if I export the pool before my next reboot, and then import the pool with -d /dev/diskid if it'll be uniform again.

ek: if I recall right I even tried playing with glabel and it did not work either

Depending upon your raid level you can probably take that device offline, then online it with the label. Pretty sure. I think. I feel I should try it before recommending that.

Of course, that all depends on if the diskid comes back after reboot. I'd try it now, but the diskid isn't there.

rwp: I'd do that right now if I had an ID to import it with. :(

Remilia: Hrm. That's no bueno. Again, I suppose it doesn't really matter. It's working.

if you release the disk from the pool it might regain the ID, or you could camcontrol detach/reattach the disk

ek, I think that taking the disk offline will close the device and then the diskid will appear again. I think. But I am using gpt labels not the older disklabels, which are now deprecated according to the handbook (again I think).

I don't wanna botch anything up trying to make it pretty for no reason.

(after removing from the pool)

Remilia: That is true! Could be worth a shot.

personally I would just forget about it

ek, How many devices are in the pool? And in the system in total?

plus my current server is a guaranteed resources VPS so there's just a single device pool

Remilia: Same and same. I was just bringing it up since divlamir's somewhat similar situation reminded me of it.

Otherwise, my silly little cron checks will let me know if there's a problem.

rwp: 6 in the pool, 8 total (2 in mirror for zroot and 6 in z2 for storage.)

Remilia: That's handy.

... the guaranteed resources bit.

ek, That is enough devices that it is worthwhile to use persistent gpt labels. And I suggest using something like device serial numbers or other identification.

I don't have a situation, all is good. It's just that dvl's little hurdle reminded me that lables are _good_ and _numbers_ are bad

Device renumbering is pain. But having swap suddenly occupy your zpool device is next-level evil.

rwp: I agree. I *MAY* be able to migrate or zfs send/recv the data and just rebuild the pool with GPT at some point.

divlamir: Glad you have no situation!

aren't labels kinda just very big numbers?

Remilia: Did you figure out the arc_prune thing? It sounds familiar ..

Earlier this summer a friend had a RAID10 setup with a striped 2x mirror configuration. Had a device fail. Removed and replaced one disk. Was confused about devices and left the system down one disk. Later another device apparently failed and it was the degraded mirror already and it left him with an array offline missing the striped mirror. Too many devices.

Llampec, GPT labels are strings. You put anything you want in them. (But no dashes or gmirror fails)

And they don't get renumbered

rwp: i'm... sorta trolling, lol.

happy adherent of gpt label with drive serial

I'll also throw kern.geom.label.disk_ident.enable="0" and kern.geom.label.gptid.enable="0" in there as things that bsdinstaller defaults to now and things are different with different values there.

I ended up just offlining the disks from the pool, creating a GPT partition on each one using serial number as labels, and replacing them in the pool with gpt/label.

Since the resilver was so quick due to not a lot of data at the moment (1.5 minutes each), I just did it. Whatever. Problem solved!

Dropped the fragmentation down to 0%, so I guess that's nice (not that it really matters, I suppose.)

Cool ^^ I think I'll wait till next reboot to do it the `zpool import -d` way suggested by rwp

Doing it disk by disk is fast if there is only small amount of data. It's data dependent. You can guess by how long a full scrub takes. If a full scrub is a few minutes then that's how long. If a full scrub is many hours then also that's how long.

Yep. Not a lot of data in there. Figured I'd snapshot backup and give it a shot. Worked out fine.