[gentoo-user] [OT] Using an odd number of drives in ZFS RaidZ
Hello fellows This is not really a Gentoo question, but at least my NAS (which this mail is about) is running Gentoo. :) There are some people amongst this esteemed group that know their stuff about storage and servers and things, so I thought I might try my luck here. I’ve already looked on the Webs, but my question is a wee bit specific and I wasn’t able to find the exact answer (yet). And I’m a bit hesitant to ask this newbie-ish question in a ZFS expert forum. ;-) Prologue: Due to how records are distributed across blocks in a parity-based ZFS vdev, it is recommended to use 2^n data disks. Technically, it is perfectly fine to deviate from it, but for performance reasons (mostly space efficiency) it is not the recommended way. That’s because the (default) maximum record size of 128 k itself is a power of 2 and thus can be distributed evenly on all drives. At least that’s my understanding. Is that correct? So here’s the question: If I had three data drives, (c|w)ould I get around that problem by setting a record size that is divisible by 3, like 96 k, or even 3 M? Here’s the background of my question: Said NAS is based on a Mini-ITX case which has only four drive slots (which is the most common configuration for a case of this formfactor). I started with two 6 TB drives, running in a mirror configuration. One year later space was running out and I filled the remaining slots. To maximise reliability, I went with RaidZ2. I reached 80 % usage (which is the recommended maximum for ZFS) and am now evaluating my options for the coming years. 1) Reduce use of space by re-encoding. My payload is mainly movies, among which are 3 TB of DVDs which can be shrunk by at least ⅔ by re-encoding. → this takes time and computing effort, but is a long-term goal anyway. 2) Replace all drives with bigger ones. There are three counter arguments: • 1000 € for four 10 TB drives (the biggest size available w/o helium) • they are only available with 7200 rpm (more power, noise and heat) • I am left with four perfectly fine 6 TB drives 3) Go for 4+2 RaidZ2. This requires a bigger case (with new PSU due to different form factor) and a SATA expansion card b/c the Mobo only has six connectors (I need at least one more for the system drive), costing 250 € plus drives. 4) Convert to RaidZ1. Gain space of one drive at the cost of resilience. I can live with the latter; the server only runs occasionally and not for very long at a time. *** This option brings me to my question above, because it is easy to achieve and costs no €€€. -- Grüße | Greetings | Qapla’ Please do not share anything from, with or about me on any social network. In this sentance are definately three error’s! signature.asc Description: PGP signature
Re: [gentoo-user] [FIXED] New install - Wayland and graphical login
On Tuesday, 29 June 2021 11:32:52 BST antlists wrote: > On 29/06/2021 10:44, Michael wrote: > > In Plasma this would be kwin, which acts as a window manager and a > > compositor. If you had installed Plasma in accordance with the URL I > > shared in previous emails you shouldn't have this problem, because from > > what I recall kwin is being drawn in as a dependency of Plasma. > > And Plasma is a dependency of what? Again, this is down to me not fully > understanding everything, but surely if I selected the > desktop/plasma/systemd profile, that should call in the basic plasma > packages by default? Maybe even the kde ones? The make.profile choice switches on/off certain USE flags and specifies a set of system packages for the particular profile. These will in turn drag in other packages as dependencies when you update your system. Therefore, unless you go for a minimalist make.profile you should not need to be emerging packages one at a time to get a functional desktop, although you will need to emerge individual applications of choice if these are not already included in the DE default set of packages. More details: https://wiki.gentoo.org/wiki/Profile_(Portage) KDE applications are mostly grouped in meta packages. These are meant to be installed selectively. For example I install 'kde-apps/kdepim-meta' because I use Kmail, but will not install 'kde-apps/kdegames-meta' because I don't run any games applications. > (Having re-read the KDE page, it's suddenly making a lot more sense, but > that's with hindsight. But am I right that the profile modifies the > system set of packages?) Yes, as I mention above, it modifies USE flags and specifies a set of system packages too. You could have started with a stripped down profile, like 'default/linux/ amd64/17.1/systemd (stable)' and then spend a lot of time tweaking USE flags and installing various packages and meta packages to get to the same end result. Thanks to Gentoo devs, all this work is no longer necessary since there are more make.profile options to choose from. :-) signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] [FIXED] New install - Wayland and graphical login
On 29/06/2021 10:44, Michael wrote: On Tuesday, 29 June 2021 08:49:49 BST Wols Lists wrote: On 28/06/21 20:23, antlists wrote: On 26/06/2021 13:00, Michael wrote: X11 will ask for twm if there is no other Window Manager available, or a Display Environment not configured. Have you sorted out your ~/.xinitrc, or have you added your startup command in /etc/env.d/90xsession? There used to be a time when you could drop in your startup command in /etc/ X11/Sessions/, but I think this is no longer used. You should spend sometime reading: https://wiki.gentoo.org/wiki/Xorg/Guide Well, I hadn't originally intended to set up X, so I was a little slapdash. I will investigate deeper at some point, I expect ... Wayland is interesting ... if I try to startplasma-wayland, it comes up with the starting plasma stuff, and there's a mouse cursor, but nothing except a black screen and the cursor. When I kill it from a root tty, there's an error Failed to create wl_display (No such file or directory) which a google tells me I haven't got a compositor ... In Plasma this would be kwin, which acts as a window manager and a compositor. If you had installed Plasma in accordance with the URL I shared in previous emails you shouldn't have this problem, because from what I recall kwin is being drawn in as a dependency of Plasma. And Plasma is a dependency of what? Again, this is down to me not fully understanding everything, but surely if I selected the desktop/plasma/systemd profile, that should call in the basic plasma packages by default? Maybe even the kde ones? (Having re-read the KDE page, it's suddenly making a lot more sense, but that's with hindsight. But am I right that the profile modifies the system set of packages?) I also get further errors, but they're probably a consequence - Could not load the Qt platform plugin "Wayland" in "" even though it was found and the same error for xcb. So simple. I was missing "emerge plasma-meta". Heh! Yes, you can't expect a DE to work if major packages are missing. ;-) This is where it would be nice to have something like the handbook, or a chapter in the handbook, on bringing up a working graphical environment. It is not in the Handbook, which has the purpose of installing the Gentoo OS itself, but it is in the Gentoo Documentation - look at the dropdown menu 'Documentation' of the Handbook web pages: https://wiki.gentoo.org/wiki/Category:Desktop In your case, as I posted previously, you need: https://wiki.gentoo.org/wiki/KDE I'm currently emerging kde-apps-meta, because I discovered that plasma (once I'd got it working) was missing all sorts of things - like konsole! But that kde page you pointed me at only mentions it in passing! It's the classic problem that man pages are very good as reference, but if you don't know what they're talking about they are very bad at enlightening you. A "dummies guide to plasma" would have been very useful telling me the packages I needed to emerge and why would have been very useful. Now I'm getting my head round it it's all falling into place, but I've been unable to see the trees for the forest :-) But, from the errors you've been getting with startx it seems you haven't read relevant Xorg documentation either. Now to get something like sddm working :-) For SDDM you better read this first: https://wiki.gentoo.org/wiki/SDDM And I'll probably be tearing my hair out screaming because I'm straying into unknown territory again :-) I doubt many people run multi-seat, so that'll be fun ... (and I gather some of these greeters don't support it, either :-( (Plus updating my SUSE version to 15.3, re-organising my hardware, blah blah blah :-) Cheers, Wol Glad you got your desktop going! :-) Thanks. At least I'm back on familiar territory there. Here's hoping for a lot more foresight :-) Cheers, Wol
Re: [gentoo-user] [FIXED] New install - Wayland and graphical login
On Tuesday, 29 June 2021 08:49:49 BST Wols Lists wrote: > On 28/06/21 20:23, antlists wrote: > > On 26/06/2021 13:00, Michael wrote: > >> On Saturday, 26 June 2021 11:50:01 BST antlists wrote: > >>> I just want a working systemd/wayland desktop system. So basically, a > >>> full-weight normal desktop. > >> > >> [snip ...] > >> > >>> I've got this one selected, /desktop/plasma/systemd > >> > >> Select default/linux/amd64/17.1/desktop/plasma/systemd (stable). > >> > >> Then update @world. You should be good to go as long as video drivers > >> and > >> firmware are in place, but if X11 is not working this could be an area > >> meriting further investigation. > > > > Okay, ... > > > > One new kernel later (along with some grub debugging :-), world updated, > > ... > > > > X11 still isn't working - first it complained it couldn't find twm, so I > > emerged that, now startx just runs and exits, and the log doesn't seem > > to show anything wrong ... X11 will ask for twm if there is no other Window Manager available, or a Display Environment not configured. Have you sorted out your ~/.xinitrc, or have you added your startup command in /etc/env.d/90xsession? There used to be a time when you could drop in your startup command in /etc/ X11/Sessions/, but I think this is no longer used. You should spend sometime reading: https://wiki.gentoo.org/wiki/Xorg/Guide > > Wayland is interesting ... if I try to startplasma-wayland, it comes up > > with the starting plasma stuff, and there's a mouse cursor, but nothing > > except a black screen and the cursor. When I kill it from a root tty, > > there's an error > > > > Failed to create wl_display (No such file or directory) > > > > which a google tells me I haven't got a compositor ... In Plasma this would be kwin, which acts as a window manager and a compositor. If you had installed Plasma in accordance with the URL I shared in previous emails you shouldn't have this problem, because from what I recall kwin is being drawn in as a dependency of Plasma. > > I also get further errors, but they're probably a consequence - > > > > Could not load the Qt platform plugin "Wayland" in "" even though it was > > found > > > > and the same error for xcb. > > So simple. I was missing "emerge plasma-meta". Heh! Yes, you can't expect a DE to work if major packages are missing. ;-) > This is where it would be nice to have something like the handbook, or a > chapter in the handbook, on bringing up a working graphical environment. It is not in the Handbook, which has the purpose of installing the Gentoo OS itself, but it is in the Gentoo Documentation - look at the dropdown menu 'Documentation' of the Handbook web pages: https://wiki.gentoo.org/wiki/Category:Desktop In your case, as I posted previously, you need: https://wiki.gentoo.org/wiki/KDE But, from the errors you've been getting with startx it seems you haven't read relevant Xorg documentation either. > Now to get something like sddm working :-) For SDDM you better read this first: https://wiki.gentoo.org/wiki/SDDM > (Plus updating my SUSE version to 15.3, re-organising my hardware, blah > blah blah :-) > > Cheers, > Wol Glad you got your desktop going! :-) signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] 502 Bad Gateway when accessing gitweb.gentoo.org
Just saw the post on gentoo-dev. It'll be interesting to see the postmortem as not being able to update the infra status page during an outage is a bit of a problem ;) Thanks for the reply Hayley On Mon, 2021-06-28 at 23:37 -0500, Dale wrote: > Hayley wrote: > > Hey all, > > Since yesterday I've getting 502 Bad Gateway when trying to access > > gitweb.gentoo.org and was wondering if anyone else is having the > > same > > issue? > > The gentoo infra status page says that it should be up so I'm not > > sure > > what could be causing the problem but it's a 502 so I'm guessing it > > must be a server side issue? > > > > Thanks, > > Hayley > > > > > > > > > I just read a message on -project I think that was about some upgrade > problems and some parts of infra not working correctly. That could > be > the problem you were seeing. I think fixing the problem is still in > progress so may be a few days before everything is back up to 100%. > This is the message: > > > Alec Warner wrote: > > > Hi, > > > > > > Many of you reported that various infra-owned services were not > > > functioning properly these past two days. We had some package > > > upgrades roll out that were bad, and a subset of services were > > > non-functional while we worked through the incident. > > > > > > (a) The upgrades did not appear to cause any data loss, but > > > service > > > availability was reduced (500s / 502s for some HTTP services.) > > > (b) Some hosts may have had problems running some commands. E.g. > > > I > > > know that 'grep' didn't work for a while. If you observed errors > > > related to missing 'GLIBC_2.33' symbols then this was likely > > > related. > > > (c) Many replicated services (including infra-status) rely on > > > gitweb > > > to take updates from git; and gitweb was not up, so they were > > > unable > > > to receive updates. > > > (d) More impacted notes will follow in a postmortem that will > > > come > > > later this week for this incident. > > > > > > Thanks to all of you who reported problems and apologies for the > > > service disruptions. > > > > > > -A > > > Hope that helps. Should keep you from looking for the problem on > your > end at least. > > Dale > > :-) :-) >
Re: [gentoo-user] [FIXED] New install - Wayland and graphical login
On 28/06/21 20:23, antlists wrote: > On 26/06/2021 13:00, Michael wrote: >> On Saturday, 26 June 2021 11:50:01 BST antlists wrote: >> >>> I just want a working systemd/wayland desktop system. So basically, a >>> full-weight normal desktop. >> [snip ...] >> >>> I've got this one selected, /desktop/plasma/systemd >> >> Select default/linux/amd64/17.1/desktop/plasma/systemd (stable). >> >> Then update @world. You should be good to go as long as video drivers >> and >> firmware are in place, but if X11 is not working this could be an area >> meriting further investigation. >> > Okay, ... > > One new kernel later (along with some grub debugging :-), world updated, > ... > > X11 still isn't working - first it complained it couldn't find twm, so I > emerged that, now startx just runs and exits, and the log doesn't seem > to show anything wrong ... > > Wayland is interesting ... if I try to startplasma-wayland, it comes up > with the starting plasma stuff, and there's a mouse cursor, but nothing > except a black screen and the cursor. When I kill it from a root tty, > there's an error > > Failed to create wl_display (No such file or directory) > > which a google tells me I haven't got a compositor ... > > I also get further errors, but they're probably a consequence - > > Could not load the Qt platform plugin "Wayland" in "" even though it was > found > > and the same error for xcb. > So simple. I was missing "emerge plasma-meta". This is where it would be nice to have something like the handbook, or a chapter in the handbook, on bringing up a working graphical environment. Now to get something like sddm working :-) (Plus updating my SUSE version to 15.3, re-organising my hardware, blah blah blah :-) Cheers, Wol
[gentoo-user] 502 Bad Gateway when accessing gitweb.gentoo.org
Hey all, Since yesterday I've getting 502 Bad Gateway when trying to access gitweb.gentoo.org and was wondering if anyone else is having the same issue? The gentoo infra status page says that it should be up so I'm not sure what could be causing the problem but it's a 502 so I'm guessing it must be a server side issue? Thanks, Hayley
