useful link to disable wake up all drives by proxmox (even sleeping)
Beiträge von gprsnik
-
-
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... -
can you describe promox settings for optimal perfomance OMV VM?
-i'm thinking about optimal connection OMV from VM to HDDs -
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 -
i'm about the latest version of course,
i wrote here simply because there is no another theme with this question...
https://sourceforge.net/p/minidlna/patches/92/?page=2
do ./configure --enable-thumbnail -
it's able to recompile minidlna plugin with additional thumbnails support?
https://sourceforge.net/p/minidlna/patches/92/ -
anyone installed ati/nvidia display drivers? everything looks like OK, exept high cpu load at files larger than 2-3 gb
i thing there is no hardware acceleration actually used in decompression and video output processes -
every day i receiving a message like this:
This email was generated by the smartd daemon running on:host name: xxx
DNS domain: xxx
NIS domain: (none)The following warning/error was logged by the smartd daemon:
Device: /dev/disk/by-id/wwn-0x50014ee0592fde30 [SAT], 1 Offline uncorrectable sectors
For details see host's SYSLOG.
You can also use the smartctl utility for further investigation.
The original email about this issue was sent at Sat Jun 6 21:46:22 2015 MSK
Another email message will be sent in 24 hours if the problem persists.notting changes day to day - 1 pending + 1 offline, smart messaging is disabled, monitoring is active = once a week
how to fix it?
-
i had a error undating apt-get like this
W: Недоступен открытый ключ для следующих ID ключей:
7638D0442B90D010
W: Недоступен открытый ключ для следующих ID ключей:
7638D0442B90D010
W: Недоступен открытый ключ для следующих ID ключей:
9D6D8F6BC857C906fix:
Code
Alles anzeigenroot@nas:/etc/apt# apt-get update Игн file: Release.gpg Игн file: Release Игн file: Translation-ru_RU Игн file: Translation-ru Игн file: Translation-en В кэше http://mirror.yandex.ru wheezy Release.gpg В кэше http://mirror.yandex.ru wheezy-updates Release.gpg В кэше http://mirror.yandex.ru wheezy Release В кэше http://packages.openmediavault.org kralizec Release.gpg В кэше http://security.debian.org wheezy/updates Release.gpg В кэше http://mirror.yandex.ru wheezy-updates Release В кэше http://packages.openmediavault.org kralizec Release В кэше http://security.debian.org wheezy/updates Release В кэше http://mirror.yandex.ru wheezy/main Sources В кэше http://mirror.yandex.ru wheezy/main i386 Packages В кэше http://mirror.yandex.ru wheezy/main Translation-ru В кэше http://mirror.yandex.ru wheezy/main Translation-en В кэше http://mirror.yandex.ru wheezy-updates/main Sources В кэше http://mirror.yandex.ru wheezy-updates/contrib Sources В кэше http://mirror.yandex.ru wheezy-updates/non-free Sources В кэше http://mirror.yandex.ru wheezy-updates/main i386 Packages/DiffIndex В кэше http://mirror.yandex.ru wheezy-updates/contrib i386 Packages В кэше http://packages.openmediavault.org kralizec/main i386 Packages В кэше http://mirror.yandex.ru wheezy-updates/non-free i386 Packages В кэше http://mirror.yandex.ru wheezy-updates/contrib Translation-en В кэше http://mirror.yandex.ru wheezy-updates/main Translation-en/DiffIndex В кэше http://mirror.yandex.ru wheezy-updates/non-free Translation-en В кэше http://security.debian.org wheezy/updates/main Sources В кэше http://security.debian.org wheezy/updates/contrib Sources В кэше http://security.debian.org wheezy/updates/non-free Sources В кэше http://security.debian.org wheezy/updates/main i386 Packages В кэше http://security.debian.org wheezy/updates/contrib i386 Packages В кэше http://security.debian.org wheezy/updates/non-free i386 Packages В кэше http://security.debian.org wheezy/updates/contrib Translation-en В кэше http://security.debian.org wheezy/updates/main Translation-en В кэше http://security.debian.org wheezy/updates/non-free Translation-en Игн http://packages.openmediavault.org kralizec/main Translation-ru_RU Игн http://packages.openmediavault.org kralizec/main Translation-ru Игн http://packages.openmediavault.org kralizec/main Translation-en Creating index of upgradeable packages ... Creating index of OpenMediaVault plugins ... Чтение списков пакетов… Готово W: Недоступен открытый ключ для следующих ID ключей: 7638D0442B90D010 W: Недоступен открытый ключ для следующих ID ключей: 7638D0442B90D010 W: Недоступен открытый ключ для следующих ID ключей: 9D6D8F6BC857C906 [b]root@nas:/etc/apt# apt-get install debian-archive-keyring Чтение списков пакетов… Готово Построение дерева зависимостей Чтение информации о состоянии… Готово Пакеты, которые будут обновлены: debian-archive-keyring обновлено 1, установлено 0 новых пакетов, для удаления отмечено 0 пакетов, и 86 пакетов не обновлено. Необходимо скачать 60,7 kБ архивов. После данной операции, объём занятого дискового пространства возрастёт на 20,5 kB. Получено:1 http://mirror.yandex.ru/debian/ wheezy/main debian-archive-keyring all 2014.3~deb7u1 [60,7 kB] Получено 60,7 kБ за 0с (473 kБ/c) (Чтение базы данных … на данный момент установлено 28078 файлов и каталогов.) Подготовка к замене пакета debian-archive-keyring 2014.1~deb7u1 (используется файл …/debian-archive-keyring_2014.3~deb7u1_all.deb) … Распаковывается замена для пакета debian-archive-keyring … Настраивается пакет debian-archive-keyring (2014.3~deb7u1) … Creating index of upgradeable packages ... Creating index of OpenMediaVault plugins ...[/b] root@nas:/etc/apt# apt-get update Игн file: Release.gpg Игн file: Release Игн file: Translation-ru_RU В кэше http://mirror.yandex.ru wheezy Release.gpg Игн file: Translation-ru Игн file: Translation-en В кэше http://mirror.yandex.ru wheezy-updates Release.gpg В кэше http://mirror.yandex.ru wheezy Release В кэше http://packages.openmediavault.org kralizec Release.gpg В кэше http://mirror.yandex.ru wheezy-updates Release В кэше http://packages.openmediavault.org kralizec Release В кэше http://mirror.yandex.ru wheezy/main Sources В кэше http://mirror.yandex.ru wheezy/main i386 Packages В кэше http://mirror.yandex.ru wheezy/main Translation-ru В кэше http://mirror.yandex.ru wheezy/main Translation-en В кэше http://security.debian.org wheezy/updates Release.gpg В кэше http://mirror.yandex.ru wheezy-updates/main Sources В кэше http://mirror.yandex.ru wheezy-updates/contrib Sources В кэше http://mirror.yandex.ru wheezy-updates/non-free Sources В кэше http://mirror.yandex.ru wheezy-updates/main i386 Packages/DiffIndex В кэше http://mirror.yandex.ru wheezy-updates/contrib i386 Packages В кэше http://security.debian.org wheezy/updates Release В кэше http://mirror.yandex.ru wheezy-updates/non-free i386 Packages В кэше http://mirror.yandex.ru wheezy-updates/contrib Translation-en В кэше http://mirror.yandex.ru wheezy-updates/main Translation-en/DiffIndex В кэше http://mirror.yandex.ru wheezy-updates/non-free Translation-en В кэше http://packages.openmediavault.org kralizec/main i386 Packages В кэше http://security.debian.org wheezy/updates/main Sources В кэше http://security.debian.org wheezy/updates/contrib Sources В кэше http://security.debian.org wheezy/updates/non-free Sources В кэше http://security.debian.org wheezy/updates/main i386 Packages В кэше http://security.debian.org wheezy/updates/contrib i386 Packages В кэше http://security.debian.org wheezy/updates/non-free i386 Packages В кэше http://security.debian.org wheezy/updates/contrib Translation-en В кэше http://security.debian.org wheezy/updates/main Translation-en В кэше http://security.debian.org wheezy/updates/non-free Translation-en Игн http://packages.openmediavault.org kralizec/main Translation-ru_RU Игн http://packages.openmediavault.org kralizec/main Translation-ru Игн http://packages.openmediavault.org kralizec/main Translation-en Creating index of upgradeable packages ... Creating index of OpenMediaVault plugins ... Чтение списков пакетов… Готово root@nas:/etc/apt#
-
Zitat von "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!
-
Zitat von "davidh2k"
I already answered to you in the other Thread...
NFS itself supports authentication (via UID/GID), you sure your Cameras don't?
I'm not used to LVM, but maybe it is possible to create one (or multiple) LVM ontop of a Filesystem?
PS: Not that it bothers me, but aren't your IP Cameras out of use if the filesystem runs full... that sounds kinda ridiculous to look at maxing the space it can use instead of solving the problem of the ip Cameras to only write an amount of X (with multiple files for each day) to your share and then delete the first file after X days...
Greetings
Davidi'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
-
Zitat von "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) -
Looking for a way to limit an NFS share size without quotas
some ip-cameras to 1 nfs nas, each to own folder, but everyone eats all hdd place and filally they kill it-selves allocating last free byte...
cameras does not support authorization, so quotas is not acceptablehow to manually create partitions on OMV?
-
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)