Search results

  1. J

    Boot problem on ZFS 3 way mirror

    now running a scrub on the rpool, looks like this will take a while
  2. J

    Boot problem on ZFS 3 way mirror

    Sorry the title of this post is wrong, its a 4 way mirror. mirror-0 sda sdb mirror-1 sdc sdd mirror-2 sde sdf mirror 3 sdg sdh
  3. J

    Boot problem on ZFS 3 way mirror

    Thanks for replying, I only did the dnodesize on the dataset rpool/data not on the rpool itself. I even went back into the live chroot env and changed it back, but to no avail. I am using legacy boot, not UEFI. Thanks, John
  4. J

    Boot problem on ZFS 3 way mirror

    As you can see I get this when doing an update-grub
  5. J

    Boot problem on ZFS 3 way mirror

    hd3,gtp9 and hd2,gtp9 only have the checksum errors out of the rest of the partitions. Is there a way to repair this?
  6. J

    Boot problem on ZFS 3 way mirror

    After setting zfs set xattr=sa dnodesize=auto RPOOL/data ( I read that you shouldnt set this on the RPOOL, so im not sure if this problem is due to this) I can not boot any longer. I get this: Attempting Boot From Hard Drive (C:) error: no such device "SOME HEX NUMBER" error: unknown...
  7. J

    when writing to disk and memory being swallowed up

    Well Bil, what a newbie I feel. After all these years..... just seems like something I've never whiteness, or that I've never even opened my eyes to such inappropriate well-seasoned Linux admin behavior :D
  8. J

    when writing to disk and memory being swallowed up

    proxmox is on the latest version and using ZFS rpool for everything. Can someone at least say why this is the case when writing to disk within the VM. The VM's memory us used up to the size of the file written to disk. Once you reboot the machine or delete the file, the memory is returned...
  9. J

    when writing to disk and memory being swallowed up

    Hello, I'm seeing when I write a large file within a VM linux, I'm also filing up the VM systems memory. This memory is released when I delete the file. dd if=/dev/zero of=test1.img bs=512k count=1000000 Is this normal? Cheers
  10. J

    PVE 5.2: netlink: 'ovs-vswitchd': attribute type 5 has an invalid length.

    # network interface settings; autogenerated # Please do NOT modify this file directly, unless you know what # you're doing. # # If you want to manage part of the network configuration manually, # please utilize the 'source' or 'source-directory' directives to do # so. # PVE will preserve these...
  11. J

    PVE 5.2: netlink: 'ovs-vswitchd': attribute type 5 has an invalid length.

    I'm seeing the same thing! [ 12.708936] Netfilter messages via NETLINK v0.30. [ 13.129192] audit: type=1400 audit(1527669328.323:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/lxc-start" pid=3049 comm="apparmor_parser" [ 13.147092] audit: type=1400...