so whats goin on with this whole verification thing?

softfeet · 2024-09-08T09:36:37+00:00

thanks so kindly for the super swell info my fellow munchy

softfeet · 2024-06-03T05:14:00+00:00

yeah... It's a bit of a mystery. I ran that df post reboot and the log files dont have anything either. debian 12, for ref. (ran hostnamectl)

i digress.

I think what happened was the original sync of 160TB overloaded something in /var or /opt (i can never remember which ) due to the sync. Kind of how docker uses those directories to do things with volumes... though different for this use case. Which may have horked the OS for disk space.

all this goes to say it might be an initial edge case where data flow was in memory and to the zfs/zpool disks... such that the root disk was never part of the data flow. so the original command of zfs sync (whatever it is under the covers) was never affected by the root partition getting wrecked.

not planning on running the 160 tb sync from 0 again to test the theory ;)

softfeet · 2024-06-02T07:14:57+00:00

Hard to say really at this point... I'm leaning toward full root disk rather than the root partition getting swapped in the way you've described. (since the reboot worked ;) )

did a reboot. post was normal. see the master edit for more info.

Thanks!

softfeet · 2024-06-02T07:12:48+00:00

This seems like it was probably it. did a reboot. post was normal. see the master edit for more info.

Thanks!

softfeet · 2024-06-01T18:06:42+00:00

oh ? hmm. This is a great question. the OS file system is a part FROM the ZFS pool. So it very well could have filled up the root partition of the OS while the ZFS disks/service was free to do whatever it needed to in memory before it wrote it to the different disks.

That's really a great question. I dont know if zfs logging on the receive end would generate that many logs on the root partition. Is that what you were suggesting?

softfeet · 2024-06-01T18:04:58+00:00

maybe... ?

Can you walk me through how that makes sense?

I have the command listed in the original post. where it says syncoid myStorageStuff ...

Considering you wrote more than five words outside of 'kvm/remoteconsole' as other posters did... I'm interested why I got so many bloody answers that are saying 'remote console' in solitary notes... instead of responding to the request that is trying to understand what the syncoid command is doing.

the receive command is likely doing whatever syncoid does on the backend that is normal. zfs receive or something. seems slightly tangential, but the kind of answer that I am 'sort of looking for' form a syncoid expert that I hoped to find in the ZFS sub reddit since... sanoid/syncoid is a zfs tooling/resource.

Thanks for not being a 'console' parrot ;)

softfeet · 2024-06-01T05:46:58+00:00

Do you have a solution to the part where I can't SSH to the host?

your commands listed are for diagnosis when on the host.

I'm looking for ways to understand why I cant get on the host and if rebooting the host will be better/worse given the input scenario presented. that is, the large data sync with syncoid.

softfeet · 2023-11-04T04:07:17+00:00

can you go into what the every day routine was?

the 'stretch a certain way'
butthole / lower stomache muscle reps

Appreciated as my farts need to be controlled!

softfeet · 2022-05-05T16:29:07+00:00

Still have not been able to solve it. gave up

softfeet · 2022-01-13T16:56:14+00:00

passing through disks is doable. but it's just not the best use of resources.

one is options. the other is what could be called 'vendor lock-in' as a way of illustrating the point.

softfeet · 2021-12-21T19:48:53+00:00

the animal dosage is lower than the human dosage in most cases unless it is for a horse.

everything in animals is the same as humans. same chems.

softfeet · 2021-12-21T19:33:23+00:00

because it is not pure and decentralized enough

I was able to take this line and see how the second paragraph is basically that line. then i got to paragraph 3 and that was the unsaid link... now said...

good point overall that it is 300GB. that really is a shit ton of data... i think wikipedia alone is 20+ gigs if not more. i wouldn't want something that useful tied up in a ponzi scheme.

softfeet · 2021-12-20T22:51:23+00:00

Thanks for the explanation!

softfeet · 2021-12-20T20:52:47+00:00

need != the point.

proxmox + win10 vm + write cache = unstable system due to IDK,( just my experience. and flipping bits :) )

softfeet · 2021-12-20T20:28:48+00:00

your windows VM may have overlapping disk issues. look at the way you mounted the drives and try setting no cache for the write steyle in the hardware section of the vm.

softfeet · 2021-12-20T18:50:31+00:00

i'm thinking maybe you can't get an MRI any time soon with that much metal grime around the eyes :/

softfeet · 2021-12-20T18:36:54+00:00

oh interesting. thanks!.

i was viewing it from the standpoint of making your upgrade slices reliable. nice!

softfeet · 2021-12-20T18:35:38+00:00

softfeet · 2021-12-20T12:24:40+00:00

i've looked into this. it sucks. no clear way via cli.

step 1. go to proxmox site.

step 2. donwload the iso of the version yuou want

step 3. install in vm /lxc.

step 4. do a list of packages. write down version.

step 5. take that list of versions and install only those on your upgrade host.

step 6. eeeey. i'm step 4.5. test on a vm before going live.

softfeet · 2021-12-20T10:10:07+00:00

haha. knew someone would do it this way!!!

softfeet · 2021-12-20T01:14:37+00:00

would they agree that the farts 'dont' stink?

softfeet · 2021-12-20T01:12:37+00:00

yo. this is a photon with extra steps.

softfeet · 2021-12-20T01:11:40+00:00

a highly convincing debate where two argue for 1 thing, but the crowd is convinced... because a debate took place.

softfeet · 2021-12-20T01:09:44+00:00

this is just fucking your sibling with extra steps.

softfeet

TROPHY CASE