SayCyberOnceMore

  • 5 Posts
  • 28 Comments
Joined 1 year ago
cake
Cake day: June 17th, 2023

help-circle











  • Weird. netin was busy, yet the bottom of the screen implies more outbound traffic (I guess it’s connected the other way around?)

    And the log looks like a SMB/CIFS issue… maybe not the interweb?

    But, it definitely looks like something got stuck in a loop and triggered a memory leak.

    Whatever VM / CT was using CPUs 7 & 10 at the time was the problem… find that and you’ll find the next step down the rabbit hole…










  • Never had an issue with EXT4.

    Had a problem on a NAS where BTRFS was taking “too long” for systemD to check it, so just didn’t mount it… bit of config tweaking and all is well again.

    I use EXT* and BTRFS where ever I can because I can manipulate it with standard tools (inc gparted).

    I have 1 LVM system which was interesting, but I wouldn’t do it that way in the future (used to add drives on a media PC)

    And as for ZFS … I’d say it’s very similar to BTRFS, but just slightly too complex on Linux with all the licensing issues, etc. so I just can’t be bothered with it.

    As a throw-away comment, I’d say ZFS is used by TrusNAS (not a problem, just sayin’…) and… that’s about it??

    As to the OPs original question, I agree with the others here… something’s not right there, but it’s probably not the filesystem.



  • Yep, Proxmox itself is very light on resources, so most is available for the VMs / containers.

    Just another point… I’ve had some issues with Dell BIOS not respecting the Power On after power loss settings - usually a BIOS upgrade solves that and 99% of Dells still have “just 1 more” update on the website…

    I’d also recommend installing Wake on LAN on that Pi too… then if you VPN in from outside you can SSH into the Pi and power on other things that “accidentally” got shutdown.


  • Yep, now, I initially found the daily journal approach a bit strange, but I use this for work as much as personal stuff, so it actually helps…

    My suggestion to your usecase would be to keep a page per “thing” ie server / container / etc and then when you make a change you can just say (on that day’s journal page):

    ‘’ Setup a backup for [[Server X]] and it’s going to [[NAS2]] (for example) ‘’

    Then, on either of those 2 pages you’ll automatically see the link back to the journal page, so you’ll know when you did it…

    I think you can disable the journal approach if it’s not useful…

    But, the important part is, the files underlying the notes you’re making are in plain text with the page name as the filename, whereas with Joplin you could never find the file…

    Also, if you modify the file (live) outside of Logseq, it copes with that and refreshes the content onscreen.

    And the links are all dynamic… renamed the NAS? Fine, Logseq will reindex all the pages for you…