check the GRUB_CMDLINE_LINUX key in /etc/default/grub it should contain the info about any subvolume. if it does not then there might be another grub config hook that is used by Fedora to add that info.
If you want to be able to change subvol names without having to touch the grub config you might also want to switch to using subvolid instead of subvol keys on the kernel command line, because the id will stay the same after a rename (this could backfire though if you assign functions to certain names like "fallback" etc.).
Edit: found the hook that adds the kernel command line option for btrfs subvolumes. in /etc/grub.d/10_linux there is this bit of code:
case x"$GRUB_FS" in
xbtrfs)
rootsubvol="`make_system_path_relative_to_its_root /`"
rootsubvol="${rootsubvol#/}"
if [ "x${rootsubvol}" != x ]; then
GRUB_CMDLINE_LINUX="rootflags=subvol=${rootsubvol} ${GRUB_CMDLINE_LINUX}"
fi;;
xzfs)
[skipped for brevity]
;;
esac
so it seems it is always looking at the subvol name of the currently mounted root fs.
that sounds almost exactly like the Reichsbürger in Germany. They also claim the current German state is actually just a corporation and the laws of the German empire are somehow still applicable. They also create their own passports. And of course they are deeply interconnected with Neo-nazis.
oh i must have missed a few orders of magnitude there. 6Mt of helium is a ridiculous amount though ... what is all that used for? according to WA that is about the water volume of the three gorges dam at STP
Edit: just read the report, wow, more than a quarter of all the helium is used just for "breathing mixes" which i assume means its for scuba diving.
an estimated 3000 metric tons of helium are generated per year throughout the lithosphere.
I think the main issue here is not that we are loosing helium on a planetary scale but that the easy to reach helium from gas wells is wasted. We will never run out of helium at our current rate of consumption before the sun goes nova, if we consider all sources on earth, but it will get a lot more expensive and the supply will get less steady.
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.
most dishwasher detergent formulations contain corrosion inhibitors for steel, some even contain corrosion inhibitors for aluminium though those are usually in the upper price segment.
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.
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.
In the Netherlands you can legally buy grow kits for magic mushrooms. They are fairly easy to use, mostly just weekly/daily checks to keep moisture at the right level and making sure to harvest at the right times (you usually get multiple harvests from just one kit).
Personally i think doing a shroom trip alone is too dangerous … so maybe find a group first?
I think what he was trying to point out is that you should not expect a direct visible effect of the dwindling funds on the events on the battlefield. It will be much more indirect and delayed by month, maybe years.
your text seems to agree 100% with one of the examples in the original posts text: ”[…] immigrants who […] simply sought better lives for themselves and their descendants“.
”nitrogen-rich fossil fuels that feed our culture“ wow this article is really badly researched. the problem is of course real and has been described very well by William Crookes in 1898. The answer back then was the development of the Haber-Bosch process.
The input was originally hydrogen from coal not natural gas which shows that the process is a bit more adaptable than this article makes us believe.
hydrogen can be obtained from many sources (including as a pure substance from wells as white hydrogen) and the reason why we use natural gas today is because it is much cheaper than the alternatives, not because other source materials would not scale as well.
how we will be creating inorganic nitrogen fertilizer in the future is a question to be solved but it is not an insurmountable problem – more like an upcoming shift in our economic practice because we will have to switch to more expensive sources.
check the
GRUB_CMDLINE_LINUXkey in/etc/default/grubit should contain the info about any subvolume. if it does not then there might be another grub config hook that is used by Fedora to add that info. If you want to be able to change subvol names without having to touch the grub config you might also want to switch to usingsubvolidinstead ofsubvolkeys on the kernel command line, because the id will stay the same after a rename (this could backfire though if you assign functions to certain names like "fallback" etc.).Edit: found the hook that adds the kernel command line option for btrfs subvolumes. in
/etc/grub.d/10_linuxthere is this bit of code:case x"$GRUB_FS" in xbtrfs) rootsubvol="`make_system_path_relative_to_its_root /`" rootsubvol="${rootsubvol#/}" if [ "x${rootsubvol}" != x ]; then GRUB_CMDLINE_LINUX="rootflags=subvol=${rootsubvol} ${GRUB_CMDLINE_LINUX}" fi;; xzfs) [skipped for brevity] ;; esacso it seems it is always looking at the subvol name of the currently mounted root fs.