Not as long as OPs but has some real goodies.
Not as long as OPs but has some real goodies.
If you want to be super exact about it it would be roughly 4 times the mass of limescale + mass of already dissolved CaCO3 in your tap water (you can look that up if you know the hardness index of your water).
But really just don’t be stingy with citric acid and it will be fine is what i am saying.
Here is the math:
2 frac {210.14 g/mol } {100.0869 g/mol} approx 4.2
<math xmlns=“http://www.w3.org/1998/Math/MathML” display=“block”> <semantics> <mrow> <mn>2</mn> <mrow> <mfrac> <mrow> <mn>210.14</mn> <mrow> <mi>g</mi> <mo stretchy=“false”>/</mo> <mi mathvariant=“italic”>mol</mi> </mrow> </mrow> <mrow> <mn>100.0869</mn> <mrow> <mi>g</mi> <mo stretchy=“false”>/</mo> <mi mathvariant=“italic”>mol</mi> </mrow> </mrow> </mfrac> <mo stretchy=“false”>≈</mo> <mn>4.2</mn> </mrow> </mrow> <annotation encoding=“StarMath 5.0”>2 frac {210.14 g/mol } {100.0869 g/mol} approx 4.2</annotation> </semantics> </math>
Note that citric acid works a bit more nuanced than many other descalers: it acts as a chelating agent at high concentrations (2x the Ca2+ concentration) and is more effective at removing scale because of this effect, but at lower concentrations the effect might actually be reversed because it can form solid calcium citrate, which has a very low solubility in water.
If you are using citric acid based descaler you should make sure that you are always using enough of it to avoid the formation of calcium citrate.
also: you can calculate the carnot cycle efficiency of a solar cell as if it was a classical heat-power-machine, even though it has no visible moving parts.
the reason why this works and yields realistic results is because the basic principles of thermodynamics stay the same no matter if you are working with steam, combustion gasses or photons and electron gas inside a semiconductor.
vasistas
https://en.wiktionary.org/wiki/vasistas
its real, though not necessarily the type of window that you described. also exists in Turkish. i have a Turkish colleague who was very proud to explain the origin of that word to us in Germany :D .
this is extra tricky because they did not specify the exact kernel. mainline could be any of the kernels tagged as stable that you can build from linus’ git tree. i know that in the past you could run a mainline linux on intel 368 chips but today you probably can not because official support was dropped a while ago.
datasheet for one of the drive models apparently these have a dual SAS interface, so what you are seing could be completely normal. i dont have any experience with this type of setup though.
btw you can uniquely identify partitions by using something like lsblk -o+PARTUUID,FSTYPE
the partuuid should never repeat in the output even if the partition table was somehow used as a template (though "dd"ing from disk to disk will duplicate those of course)
also check out the “SERIAL” column for lsblk to uniquely identify the drives themselves.
could you run something like sudo lsblk -o+MODEL
and note down the model for the drives? i kind of suspect that the HBA you are using is still doing some abstraction and is not in IT mode. the duplication could come from connecting two SAS cables to the same backplane, thus creating a sort of double image of the enclosure. this is usually handled and hidden by the HBA though if it is configured correctly.
pls also check that you are in fact using the correct ports on the enclosure. if you are not building a SAN only the “A” ports are supposed to be used and the “B” ports should be unused/free.
just a bunch of individuals drives
that is literally what JBOD means so congratulations you already have one. a classical RAID would show up as a single drive.
Initiator-target (IT) mode enables creating a JBOD with zfs vdevs on it. You can have the zfs vdevs in raidz configuration (which would give you the same drive redundancy as a hardware raid, with raidz1 performing similar to RAID5)
zfs is commonly used with a JBOD configuration on a raid controller but you can also use any other kind of controller as long as the individual drives can be written to. examples for this would be NVMe drives directly attached to the PCIe bus or normal SATA controllers. This is more a performance optimization than an issue with compatibility.
Wir haben Grund zum saufen!