speaking about software raid, not hardware controller based.
I am trying to go for some local OpenSuse machine and adding some
storage to it. Was considering Raid6, and now reading about a bit and
people left and right scaremongering about the larger the disks these
days in the double digit terabyte capacities even, the more likely it
is that during a reconstruction of a raid subsequent errors would
I would absolutely like to keep my data consistent, and I am not
thinking about double digit terabytes either, would stick to 2TB or
4TB disks, with Raid6 thats at least 4 physical drives.
Now I am wondering if it possible to use a good robust file system
that can add some more parity or check blocks or redundancy on top of
the hardware disks, to absolutely be able to always read my data.
I can't add multiple machines or like those high availability stuff
like clusters and what not I read about DRBD (Distributed Replicated
Block Device), or maybe I am just too scared by those technical terms
or consider myself to be just a simpleton and wanting to keep it
My use case here is also not constant availablity, when a disk needs
to be replaced, so be it, but I don't want to lose my data that I can
not ever read certain parts of it again or such stuff.
The thing that came to my mind was, if there is some file systems that
would add redundancy and robustness onto the mdraid system of the
Anyone with some useful insights? Roughly speaking, I was considering
some simple pcie esata interfaced controller card and an external case
enclosure with esata port and portmulitplier stuff inside, that can
present at least 4 physical disks as JBOD, just a bunch of disks, so
that the Linux can seem them all separately.
Speed and rebuild times are not my concern, but data persistence and
data integrity. Not even number of physical disks, I could live with
even one of those 8 bay device enclosures and cases that are out there
on the market.
Thanks for any help and hints.
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
I've been using droidcam with an iphone so it can be used with zoom,
skype, duo as a camera. It was working until recently, but now with
google duo it says something has gone wrong, cannot access camera
microphone. Access is allowed in the settings though. This also applies
to chromium. It still works with zoom, and skype.
I suspected a kernel update, so I booted an old installation of 15.1,
which was running kernel 5.4.10, installed the latest google chrome and
I have tried updating my kernel to 5.9 but droidcam would not install.
Currenly 5.3.18-lp152.50-default opensuse 15.2
What can I do? I have spend 3.5 hours!
On 2020-11-20 5:45 p.m., Herbert Graeber wrote:
>>> You need a certificate and key and add them in /etc/sysconfig/unifi.
>> Where would I find those?
> You shall generate your own.
How do I do that?
Hi users @ list opensuse,
maybe I am old school, but from old days of mails and usenet, I always
came from the concept to post URLs, web-addresses and clickable links
into like angle-brackets < > and make various mail clients and places
be able to fully recognize and respect especially very long URLs URIs
and more. Maybe I never fully grasped the concept, or had some
misunderstanding of them to begin with.
As far as I can now tell, the new HyperKitty (?) mechanism on
apparently does not render clickable html links when browsing list
posts e.g. on the new archives areas
Now I was wondering how one should post long links and more safely. I
am writing via google gmail web interface. But also how about other
inbound delivery means e.g. smtp clients etc? What are the exact
technical details about how stuff becomes rendered on this HyperKitty
Also, some while ago, I tried to attempt to log-in or register on the
web interface of the lists.opensuse.org server, but it then denied or
spoke about not having implemented accounts yet or something. These
days, it seems that one could log in to it with all sorts of
credential providers, opensuse id, open id, github, gitlab, stack
exchange, google log on.
Registering apparently is still blocked.
Does this mean we can somehow claim our own account that we already
use (email address as sender) to be able to log into the web interface
as well and post there instead of our own mail clients or mail
concepts? or when will this be available?
we have a filetype with ending "fsp" ,which should be opened with a
I created a xml-file and registered the type "application/x-fsp" with
I also created a Desktop-file /usr/share/applications/mmview.desktop ,
which has an entry "MimeType=application/x-fsp"
When I call "xdg-mime query default application/x-fsp" as my user, I
get "which: no mmviews in (/usr/uti)"
If I call it as root, I get "mmview.desktop".
How do I configure a mime type for alle users under opensuse Leap?
Daniel Spannbauer Systemadministration
marco Systemanalyse und Entwicklung GmbH Tel +49 8333 9233-27 Fax -11
Rechbergstr. 4-6, D 87727 Babenhausen Mobil +49 171 4033220
http://www.marco.de/ Email ds(a)marco.de
Geschäftsführer Martin Reuter HRB 171775 Amtsgericht München
So I spilled some hot chocolate on my keyboard
What's your best advice on cleaning it?
America, it was a wonderful country
Til they took it private
and made it a theme park of itself
Our IT security guys just asked me to remove/sanitize a message that I
posted on the openSUSE mailing list back in 2017. How they came across this
message is mysterious. But I did post some stuff about the company ADS that
I was trying to access from openSUSE/samba. I don't remember the specific
details of the problem, and I do not think it was ever solved. No matter. I
thought I was usually pretty careful about sensitive details in posts.
Seems not always...
Is it possible to remove messages that were posted? As it provides no
solution and is rather old, I cannot see that it is especially useful
I would like to use on Tumbleweed/KDE minidlna to stream
multimedia/pictures to the TV . I installed it from snap, and made
some modifications to the minidlna.config file in /etc. However, I am
not able to use it. When I ask its status, I get:
berci@linux-h9qy:~> systemctl status minidlna
? minidlna.service - MiniDLNA is a DLNA/UPnP-AV server software
Loaded: loaded (/usr/lib/systemd/system/minidlna.service;
enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Tue 2020-11-24 19:48:53
CET; 42s ago
Process: 15219 ExecStart=/usr/sbin/minidlnad -S (code=exited,
Main PID: 15219 (code=exited, status=255/EXCEPTION)
Could you help what could go wrong?
This message was sent using IMP, the Internet Messaging Program.
Hello users-list @ opensuse
anyone using current wireguard on current opensuse leap 15.2?
I see very few posts on the list server archives. I read about some
new version 0.3.1 windows client. I suppose wireguard on the server
side is linux only?
How current and up-to-date is wireguard server side on opensuse leap 15.2?
I like the archlinux documentation pages for a lot of topics
I fail to find some version number or understanding of the linux side
wireguard in terms of release or version numbers. does 0.3.1 on the
windows client side has got to do anything with the server side
Also wondering why
apparently leap 15.1 has some official wireguard package that has a
higher version string or date string that leap 15.2 or even
I am also trying to dig into site-to-site (both linux) connections.