Recent content by godfather007

After creating ceph-squid-bookworm repo through the new 0.7.2-tool, the config file got a wrong pgp (bullseye) entry. Manually adjusting works.

Yeey, 0.7.2 with trixie

Unfortunately, after adding TST repo, installing 0.7.1, the offered releases stick to Bookworm, Bullseye, Buster for all products. Am i doing something wrong? Installed a fresh PBS, updated it with the test-repo, installed 0.7.1 but no trixie in the menu

thx a lot , works!

I'm not sure if we're on the same page.. Let me rephrase. Following is the targetcli from my (still functioning) production environment: /> ls o- / ......................................................................................................................... [...] o- backstores...

Oh, dmesg shows this during boot: [ 11.886889] Loading iSCSI transport class v2.0-870. [ 12.107469] Rounding down aligned max_sectors from 4294967295 to 4294967288 [ 12.107551] db_root: cannot open: /etc/target [ 15.733787] rx_data returned 0, expecting 48. [ 15.733799] iSCSI Login...

Targetcli is empty now, because of the issue /backstores/block> cd / /> ls o- / ......................................................................................................................... [...] o- backstores...

Hi, i'm abusing my PBS installation for some archival requirement. Installed targetcli-fb and assigned a zvol through it to PVE. Using this target directly from windows instead through PVE was working flawless. But now the zvol is being in use after a reboot... It seems the (PVE) LVM is...

Did you get past your end-boss? Did the ceph command alter the centrally used ceph.conf?

Yes, this one works! I tried it on 1 host on my staging environment... the second partition of the drive finally unfolds! Is there some testing with it that needs to be done before it can be taken in production? Martijn Too bad, M$ did not release any recent ReFS info for a linux driver ...

The test-machine stays working. Files can be restored. It feels like it has to do with the disks integrity. I'll investigate and report back here.

Arrrgg.. i cannot re-create the problem... on a fresh machine... i'm starting to realize something else must be wrong on a windows/ntfs level.

Tried 3 different sizes ... all worked well... given I used only some txt files to use during restore testing. Going to start over with dedup as well while throwing a few gb's of data on it as well...

Damn... this one works: Created the VM from the same original template: -add virtio device (TST 200GB), full (no discard) (later changed to discard) -in windows: disk manager (old school NT4) selected gpt device -format: NTFS from default to 16 KB allocation unit (quick format) -made a...

Good morning, i'll create a new machine (smaller one) with the same steps (they were manual but i think i can manage). This will speed up the backup attempt.