Posts by gprsnik

  • OMV Qemu-KVM

    Thank you for ideas!
    it's possible to enable SMART and HDD sleep of native disks from OMV VM?
    HDDs conneted to VM as VirtIO, HDDs inside VM OMV reports what it's "Unable to detect device type" and unfrequently used HDD doesn't sleeps...

    Code
    smartctl -a /dev/vdb

    /dev/vdb: Unable to detect device type

    Please specify device type with the -d option.

  • OMV Qemu-KVM

    Quote from ryecoaaron

    I think you might be better to do what I do - run proxmox on the physical system and OMV as a VM. proxmox is much better than virtualbox or cockpit.

    what is the real perfomance degradation OMV as VM vs OMV native install? - percents?
    i'm lookng for manual to install an ideal pair: proxmox + OMV in a one native installation, found only whis one https://habr.com/ru/post/328048/ but it's a little bit obsolete
    where is some of dependencies are breaks when i trying to install them together, so updates will be only by manual

  • SMART error (CurrentPendingSector) detected on host: server

    every day i receiving a message like this:


    notting changes day to day - 1 pending + 1 offline, smart messaging is disabled, monitoring is active = once a week


    how to fix it?

  • OMV 1.18 CRON-APT Error: The value 'stable' is invalid for APT::Default-Release as such a release is not available in the sources

    i had a error undating apt-get like this
    W: Недоступен открытый ключ для следующих ID ключей:
    7638D0442B90D010
    W: Недоступен открытый ключ для следующих ID ключей:
    7638D0442B90D010
    W: Недоступен открытый ключ для следующих ID ключей:
    9D6D8F6BC857C906


    fix:


  • Quota for NFS share?

    Quote from "davidh2k"

    And if the size of the storage is limited they then restart overwriting like a normal camera would do?


    Greetings
    David


    no.. :( db says what huge amount of space is available, but really NFS declines to write to new files. Here is one of ways - to create DB for each camera with small HDD, and after move DB's to each folder on big HDD. Each camera's DB will think what it has only 200 gb and will automatically delete old files round-robin limiting DB size to 200 gb...


    I've found the way - create for each camera a logical volume via LVM. For each vol - create a share, for each share - nfs share


    thank you, davidh2k!

  • Some partitions on 1 physical HDD? hard size limit for share


    i'm sorry for slightly same questions,
    authentication (via UID/GID) is not accessible from GUI, it's hard for linux novice, but I will try to MAN it ! :)
    cameras algorithm i written in nfs thread.


    may be the best way is to connect HDD to PC and to make partitions by other software?...


    THANK YOU FOR AN IDEA! I've fogot about LVM feature plugin...
    everything is fine - 5 shares with fixed size.


    please - kill this stupid question :)

  • Quota for NFS share?

    Quote from "davidh2k"

    Maybe you should configure the IP Cameras to generate a new file once a day... then can delete old files with a bash script after X days.


    each ip-camera creates own file archive (in own folder) with an index of segments and events to exclude fragmentation. Size of archive is limited by share size. So if I delete some old files I will corrupt camera's database and recording will stop.
    if i have 5 cameras, which created their databases assuming what share size is 1 tb, after some time each will write ~200mb and storage will be full, but database will show to each what ~800 mb is empty...
    so i must to create 5 shares with hard limited size... (sorry for duplicated question - here is some ways to solve the problem)

  • Quota for NFS share?

    is it any way to limit an NFS share size now? (or only manual partitioning?) setting up some ip-cameras to 1 nfs nas (each to own folder, but everyone eats all hdd place)