Re: [gentoo-user] Re: Firefox and Adobe's DRM plugin
On Thursday 15 May 2014 22:55:45 »Q« wrote: On Thu, 15 May 2014 20:31:14 +0100 Mick michaelkintz...@gmail.com wrote: Does anyone know if Gentoo will provide a USE flag to enable this if desired? https://hacks.mozilla.org/2014/05/reconciling-mozillas-mission-and-w3c-em e/ It may not even be possible to enable it in Gentoo builds or it may be possible only in firefox-bin builds. From that article (which is by Mozilla's CTO, by the way), Mozilla will distribute the sandbox alongside Firefox, and we are working on deterministic builds that will allow developers to use a sandbox compiled on their own machine with the CDM as an alternative. IMO they *must* make that possible. Otherwise the sandbox itself has to be a binary blob, which would negate much of reason for having a sandbox in the first place -- it would only be an alleged sandbox. He also says, As plugins today, the CDM itself will be distributed by Adobe and will not be included in Firefox. So if/when Gentoo gets around to making the CDM available, ISTM it will almost certainly be a package separate from Firefox. If so, maybe there will be a USE flag for Firefox which pulls the CDM in as a dependency, but that flag should be off by default (again IMO). Yes, I'd rather that it was implemented in this way so that we have to opt in for allowing DRM on our machines, rather than having to opt out. It is worrying to see that HTML5 is being usurped by the likes of Adobe and their media industry friends, as if adobe-flash was not bad enough. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
[gentoo-user] The writing on the wall ... sys-apps/util-linux
I got this message after an update: * Messages for package sys-apps/util-linux-2.24.1-r2: * The mesg/wall/write tools have been disabled due to USE=-tty-helpers. I understand that wall has been moved from sys-apps/sysvinit to sys-apps/util- linux, but I am not sure why USE=-tty-helpers is disabled as a default. I couldn't find anything mentioning this in gentoo-dev, but this could just be my poor searching skills. Does anyone know? -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] problems getting systemd to work
On Thu, May 15, 2014 at 5:01 PM, Stefan G. Weichinger li...@xunil.at wrote: Am 15.05.2014 22:38, schrieb cov...@ccs.covici.com: image=/boot/vmlinuz-3.6.2-gentoo phew. 3.6.2 is from October 2012 ... Did you recompile it with the suggested options for systemd? Maybe it doesn't matter, but just a thought ... that kernel is quite old. It doesn't matter, at least in theory systemd works with linux-3.0. John, could you please send the output from dracut --print-cmdline? In my case, it lists *ALL* my lvms, and (I think) therefore all of them are mounted. Since your lilo.conf only lists rd.lvm.lv=linux-files/64-root and rd.lvm.lv=linux-files/64-usr, I think that would explain why it doesn't mount the others. If dracut --print-cmdline doesn't print the others, could you try to boot with rd.lvm.lv=linux-files/audio in the kernel command line specified in your lilo.conf? If after booting /audio is mounted, then I think we have found the problem. We'll need just to figure out why dracut --print-cmdline does not print the other lvms. Also, could you try to generate your initramfs again, but this time with add_dracutmodules+=systemd lvm? Regards. -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] boot problems
Am 15.05.2014 20:33, schrieb Canek Peláez Valdés: On Thu, May 15, 2014 at 1:27 PM, Stefan G. Weichinger li...@xunil.at wrote: Am 15.05.2014 20:05, schrieb Canek Peláez Valdés: With -H, you don't get the kernel cmdline, and therefore your kernel cannot load your LVM volumes since it doesn't know their... names? I don't knot the terminology. In any case, you need to set --hostonly-cmdline (or hostonly_cmdline=yes in the config file), *besides* -H. ok ... I pulled your changes (kerninst) from github ... on the web I see it, but it doesn't get into my copy here ... strange. As I don't need it right now, I will (a) wait or (b) edit manually. No problem. I actually *removed* -H from kerninst. That should be configured in the user's dracut.conf; now I have: hostonly=yes hostonly_cmdline=yes in my dracut.conf. Yes, I understood ... thanks. Aside from that a more general question: Does it it any way help to have a *small* (= as small as possible) initramfs? Maybe on embedded systems but on the big multi-GB-ram-machines we use it doesn't make much difference, right? I ask because in all my reorganizing furor I also thought that now with btrfs only I could get rid of lvm mdraid as dracut-modules. I can try ... ;-) (don't call me ricer) Additional in this context: does it make a noticeable difference which Kernel compression mode you choose? I assume it is again an issue for systems with (a) small boot-partitions and/or (b) slower CPUs to select something special here. I checked and see that I use LZ4 anyway already ... seems to be the fastest to unpack as far as I understand the help text. - And then, who writes the howto condensed out of this thread? ;-) Much to learn and understand as always, I appreciate it a lot. Stefan
Re: [gentoo-user] Filesystem doesn't mount automatically after unclean shutdown
On Wednesday 14 May 2014 20:29:46 Nikos Chantziaras wrote: I have this weird problem where a filesystem (Ext4) refuses to mount automatically after something like a power loss or forced shutdown. The fstab entry for it is: LABEL=Data /mnt/Data ext4 defaults,relatime,exec 0 2 During boot, this is what OpenRC tells me: Root: clean, 805088/6553600 files, 9129899/26214400 blocks Data: recovering journal Data: clean, 364344/61546496 files, 137312260/246156800 blocks [ ok ] * Mounting local filesystems ...[ ok ] * Remounting root filesystem read/write ... [ ok ] * Remounting filesystems ...[ ok ] * Updating /etc/mtab ...[ ok ] It doesn't show that it failed to mount / What does syslog show? If I reboot the system again, then all works fine and the FS is mounted automatically. So this is a one-time thingy, happening only on the first boot after an unclean power-off. It would seem that I've stumbled across an OpenRC bug? There's no errors anywhere to be seem. According to the log output above, everything should be fine. I suspect that the recovering journal step is what causes this, but I don't know why. Anyone else encountered this? I don't know why your system does this. I have had a few forced shutdowns with root on ext4 and the system mounts / after it recovers and cleans messed up inodes. However this is how fstab looks in my case: /dev/sda7 / ext4noatime 0 1 Could your problem be related to your relatime mount option? -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] boot problems
On Fri, May 16, 2014 at 4:46 AM, Stefan G. Weichinger li...@xunil.at wrote: Am 15.05.2014 20:33, schrieb Canek Peláez Valdés: On Thu, May 15, 2014 at 1:27 PM, Stefan G. Weichinger li...@xunil.at wrote: Am 15.05.2014 20:05, schrieb Canek Peláez Valdés: With -H, you don't get the kernel cmdline, and therefore your kernel cannot load your LVM volumes since it doesn't know their... names? I don't knot the terminology. In any case, you need to set --hostonly-cmdline (or hostonly_cmdline=yes in the config file), *besides* -H. ok ... I pulled your changes (kerninst) from github ... on the web I see it, but it doesn't get into my copy here ... strange. As I don't need it right now, I will (a) wait or (b) edit manually. No problem. I actually *removed* -H from kerninst. That should be configured in the user's dracut.conf; now I have: hostonly=yes hostonly_cmdline=yes in my dracut.conf. Yes, I understood ... thanks. Aside from that a more general question: Does it it any way help to have a *small* (= as small as possible) initramfs? Maybe on embedded systems but on the big multi-GB-ram-machines we use it doesn't make much difference, right? AFAIU, no, it doesn't. As long as the (uncompressed) initramfs fits into the RAM, its size doesn't matter. I ask because in all my reorganizing furor I also thought that now with btrfs only I could get rid of lvm mdraid as dracut-modules. I can try ... ;-) (don't call me ricer) Whatever gets rid of LVM is good on my book. I've never understood why people uses it, and in my experience it only brings headaches. Besides, I've heard from many people that btrfs is the way to go in the future. I'm not ready to make the change yet, but I will at some point. Additional in this context: does it make a noticeable difference which Kernel compression mode you choose? I assume it is again an issue for systems with (a) small boot-partitions and/or (b) slower CPUs to select something special here. Given the size of the kernel, I don't thin the difference can be humanly measured. I checked and see that I use LZ4 anyway already ... seems to be the fastest to unpack as far as I understand the help text. It will be a difference of microseconds, if not nanoseconds. I honestly don't think it matters at all. And then, who writes the howto condensed out of this thread? ;-) Much to learn and understand as always, I appreciate it a lot. Regards. -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] The writing on the wall ... sys-apps/util-linux
On 16/05/14 10:34, Mick wrote: I got this message after an update: * Messages for package sys-apps/util-linux-2.24.1-r2: * The mesg/wall/write tools have been disabled due to USE=-tty-helpers. I understand that wall has been moved from sys-apps/sysvinit to sys-apps/util- linux, but I am not sure why USE=-tty-helpers is disabled as a default. I couldn't find anything mentioning this in gentoo-dev, but this could just be my poor searching skills. Does anyone know? Because upstream util-linux disables tty-helpers by default regarding it's ./configure --help, as they are not deemed important commands - Samuli
Re: [gentoo-user] udev or Gentoo issue?
On 15/05/14 02:59, Grant wrote:
I'm having a problem starting the USB network interfaces properly on
one of my systems. I brought the problem to the udev list and they're
indicating that it's a Gentoo problem:
https://www.mail-archive.com/systemd-devel@lists.freedesktop.org/msg18840.html
Should I file a bug?
- Grant
Like pointed out in the upstream thread, it's either wrongly built
net-misc/dhcpcd (should be with USE=udev)
and if not using dhcpcd, it might be a bug in net-misc/netifrc's
/etc/init.d/net.lo depend() { } section --
it's possible it's missing dependency that forces /etc/init.d/udev start
first, specially if OpenRC is using parallel
startup
So not really a udev bug, rather a misconfiguration in dhcpcd USE flags
OR bug in dependencies of netifrc's net.lo script
I'm starting two interfaces, one that uses dhcpcd and one that does
not. Both fail to start in the default runlevel until they are
hotplugged later. I do have dhcpcd built with USE=udev. The string
udev does not occur in /etc/init.d/net.lo so maybe that's the
problem? Please confirm that I should file a Gentoo bug for this.
- Grant
Try adding 'after udev' to net.lo's depend() { } section and see if that
helps, if it does, file a bug
saying so.
I added it like this and rebooted:
depend()
{
after udev
but the result was the same. I also have udev and udev-mount in the
sysinit runlevel.
It was more of an educated guess than 100% accurate knowledge. I can't
think of an another
way to force netifrc to behave, since it's not coded in C, and it can't
link to libudev, so...
However since you say *both*, even the one with dhcpcd fail to start,
before filing that bug,
see if disabling netifrc hotplugging works:
# ln -s /dev/null /etc/udev/rules.d/90-network.rules
Will that disable interface renaming or hotplugging? The system with
the issue is remote and if the interfaces aren't renamed or if
hotplugging doesn't happen then I won't be able to access the system
for up to 24 hours. That's fine and I'm happy to test stuff like this
anyway but I don't think this particular test will be informative
because:
It will disable the hotplugging, it means you *must* have the net.*
stuff added
to the default to runlevel yourself, like eg.
# rc-update add net.foobar default
They're in the default runlevel:
# rc-update|grep net.enp
net.enp0s20u2u1 | default
net.enp0s20u2u2 | default
I can disable hotplugging with rc_hotplug in rc.conf. Hotplugging is
actually disabled by default there and my network interfaces won't
start automatically that way.
I'm not 100% sure the rc_hotplug will also disable the 90-network.rules
triggered
interface hotplugging
Don't count on that
- Samuli
Re: [gentoo-user] problems getting systemd to work
Canek Peláez Valdés can...@gmail.com wrote: On Thu, May 15, 2014 at 5:01 PM, Stefan G. Weichinger li...@xunil.at wrote: Am 15.05.2014 22:38, schrieb cov...@ccs.covici.com: image=/boot/vmlinuz-3.6.2-gentoo phew. 3.6.2 is from October 2012 ... Did you recompile it with the suggested options for systemd? Maybe it doesn't matter, but just a thought ... that kernel is quite old. It doesn't matter, at least in theory systemd works with linux-3.0. John, could you please send the output from dracut --print-cmdline? In my case, it lists *ALL* my lvms, and (I think) therefore all of them are mounted. Since your lilo.conf only lists rd.lvm.lv=linux-files/64-root and rd.lvm.lv=linux-files/64-usr, I think that would explain why it doesn't mount the others. If dracut --print-cmdline doesn't print the others, could you try to boot with rd.lvm.lv=linux-files/audio in the kernel command line specified in your lilo.conf? If after booting /audio is mounted, then I think we have found the problem. We'll need just to figure out why dracut --print-cmdline does not print the other lvms. Also, could you try to generate your initramfs again, but this time with add_dracutmodules+=systemd lvm? The secret to activate all the volumes, is to specify the volume groups instead of each volume -- that got them all activated, but systemd still is not working well. The print-cmdline still just prints the volumes necessary to mount the root and user file systems, which makes sense, but why the rest of them do not activate, I have no clue. Now for some systemd problems. The root file system was read only when I logged in, but I could remount it rw -- not sure why this was happening. Some units did start, but most did not. Whenever I tried to start one manually, I got a message like the following: I wrote systemctl start /usr/lib/systemd/system/ntpd.service and got the error that it was unable to start because it could not find ntpd.service.mount:] May 16 01:59:52 ccs kernel: 31systemd[1]: Failed to load configuration for usr-lib-systemd-system-ntpd.service.mount: No such file or directory May 16 01:59:52 ccs kernel: 31systemd[1]: Trying to enqueue job usr-lib-systemd-system-ntpd.service.mount/start/replace May 16 01:59:53 ccs kernel: 31systemd[1]: Sent message type=error sender=n/a destination=n/a object=n/a interface=n/a member=n/a cookie=1 reply_cookie=1 erro\r=Unit usr-lib-systemd-system-ntpd.service.mount failed to load: No such file or directory. May 16 01:59:53 ccs kernel: 31systemd[1]: Failed to process message [type=method_call sender=n/a path=/org/freedesktop/systemd1 interface=org.freedesktop.sys\temd1.Manager member=StartUnit signature=ss]: Unit usr-lib-systemd-system-ntpd.service.mount failed to load: No such file or directory. No matter what unit I tried to start I would get such a message about the service.mount. Also, even though my network names were correct, they did not come up, but I will try to look in the logs to see why not. So we have made some progress, but still a long way to go yet. Note also, that I am not booting into a display manager, just a regular console. What a lot of work just to get the system booted! -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici cov...@ccs.covici.com
Re: [gentoo-user] boot problems
On 16/05/2014 12:04, Canek Peláez Valdés wrote: Whatever gets rid of LVM is good on my book. I've never understood why people uses it, and in my experience it only brings headaches. Besides, I've heard from many people that btrfs is the way to go in the future. I'm not ready to make the change yet, but I will at some point. LVM is an excellent solution for what it was designed to do, which is to deal with stuff like this: Oops. I misjudged how big /var/log needed to be and now I need to add 50G to that partition. But it's sda6 and I have up to sda8. Argggh! Now I need 5 hour downtime to play 15-pieces with fdisk. LVM makes that 2 commands and 12 seconds. Yes, it's a bit complex and you have to hold the PV/VG/LV model in your head, but it also *fixes* the issue with rigid MSDOS partition style. Modern filesystems like ZFS and btrfs sidestep the need for LVM in a really elegant and wonderful way, none of which changes the fact that ZFS/btrfs weren't around when LVM was first coded. -- Alan McKinnon alan.mckin...@gmail.com
Re: [gentoo-user] boot problems
Alan McKinnon alan.mckin...@gmail.com wrote: On 16/05/2014 12:04, Canek Peláez Valdés wrote: Whatever gets rid of LVM is good on my book. I've never understood why people uses it, and in my experience it only brings headaches. Besides, I've heard from many people that btrfs is the way to go in the future. I'm not ready to make the change yet, but I will at some point. LVM is an excellent solution for what it was designed to do, which is to deal with stuff like this: Oops. I misjudged how big /var/log needed to be and now I need to add 50G to that partition. But it's sda6 and I have up to sda8. Argggh! Now I need 5 hour downtime to play 15-pieces with fdisk. LVM makes that 2 commands and 12 seconds. Yes, it's a bit complex and you have to hold the PV/VG/LV model in your head, but it also *fixes* the issue with rigid MSDOS partition style. Modern filesystems like ZFS and btrfs sidestep the need for LVM in a really elegant and wonderful way, none of which changes the fact that ZFS/btrfs weren't around when LVM was first coded. So is btrfs ready for production -- all the tools work, etc. to the level that the ext2/3/4 work? Also, what kernel do you need for this to function -- and last question, how to convert an lvm volume to btrfs, or do you just have to make some space somewhere and copy the files? So far, I have liked lvm, what's the advantage of btrfs over lvm? -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici cov...@ccs.covici.com
[gentoo-user] Can't Get Systemd to Work
Hi all. I am having issues with Systemd as well. I added to the GRUB2 configuration file the needed command line to get Systemd to start, but for whatever reason, the kernel is adamant that I must use OrenRC. I recompiled with Genkernel-next a new kernel and initramfs, and that, for whatever reason, doesn't automount my /boot partition. Is there a fix to this?
Re: [gentoo-user] boot problems
On 16 May 2014 7:46:29 PM AEST, Stefan G. Weichinger li...@xunil.at wrote: Am 15.05.2014 20:33, schrieb Canek Peláez Valdés: On Thu, May 15, 2014 at 1:27 PM, Stefan G. Weichinger li...@xunil.at wrote: Am 15.05.2014 20:05, schrieb Canek Peláez Valdés: With -H, you don't get the kernel cmdline, and therefore your kernel cannot load your LVM volumes since it doesn't know their... names? I don't knot the terminology. In any case, you need to set --hostonly-cmdline (or hostonly_cmdline=yes in the config file), *besides* -H. ok ... I pulled your changes (kerninst) from github ... on the web I see it, but it doesn't get into my copy here ... strange. As I don't need it right now, I will (a) wait or (b) edit manually. No problem. I actually *removed* -H from kerninst. That should be configured in the user's dracut.conf; now I have: hostonly=yes hostonly_cmdline=yes in my dracut.conf. Yes, I understood ... thanks. Aside from that a more general question: Does it it any way help to have a *small* (= as small as possible) initramfs? Maybe on embedded systems but on the big multi-GB-ram-machines we use it doesn't make much difference, right? I ask because in all my reorganizing furor I also thought that now with btrfs only I could get rid of lvm mdraid as dracut-modules. I can try ... ;-) (don't call me ricer) If you have a multi-disk btrfs, I think you need to add the btrfs dracut module. At least that's how I remember it, but its been a while my memory could be failing me, or it could well have changed since then. Bruce -- :B
Re: [gentoo-user] boot problems
On Fri, 16 May 2014 07:14:27 -0400, cov...@ccs.covici.com wrote: So far, I have liked lvm, what's the advantage of btrfs over lvm? I have only looked at btrfs, with a consideration for switching from ZFS, but it seems to offer the same advantages as ZFS. That is, it makes things even easier than LVM does. with LVM you can easily resize volumes and the filesystems on them, but it is still two or three steps, more if you add RAID into the equation. The modern filesystems do it all at once. If you need a bigger var, you just tell it so. And it is exactly the same process for shrinking a volume, something that can be tricky with LVM because of the need to handle volume and filesystem separately. -- Neil Bothwick You know the end of the world is near when the Spice Girls start reproducing. signature.asc Description: PGP signature
Re: [gentoo-user] Can't Get Systemd to Work
On Fri, 16 May 2014 07:34:16 -0400, Hunter Jozwiak wrote: Hi all. I am having issues with Systemd as well. I added to the GRUB2 configuration file the needed command line to get Systemd to start, but for whatever reason, the kernel is adamant that I must use OrenRC. You need to tell us what you added and what the kernel complained about. The only information we have is what is in your mail, we are not the NSA, we cannot see what is on your computer. I recompiled with Genkernel-next a new kernel and initramfs, and that, for whatever reason, doesn't automount my /boot partition. Is there a fix to this? It is standard practice to not mount the /boot partition. By the time the boot process gets to mounting what is in /etc/fstab, /boot is no longer needed. That's why it is usually set to noauto in fstab. -- Neil Bothwick Guns don't kill people--it's those little pieces of lead. signature.asc Description: PGP signature
Re: [gentoo-user] boot problems
Am 16.05.2014 13:56, schrieb Bruce Schultz: I ask because in all my reorganizing furor I also thought that now with btrfs only I could get rid of lvm mdraid as dracut-modules. I can try ... ;-) (don't call me ricer) If you have a multi-disk btrfs, I think you need to add the btrfs dracut module. At least that's how I remember it, but its been a while my memory could be failing me, or it could well have changed since then. I currently have in /etc/dracut.conf: add_dracutmodules+=bash systemd hostonly=yes hostonly_cmdline=yes and am able to boot via grub2 and efi, that means, /boot/efi (vfat) on /dev/sda1 (sda is the SSD) and / as btrfs-subvol on /dev/sda2 (with /boot as directory on it). So no multi-disk btrfs for / or /boot on this machine. - removing lvm mdraid from dracut slimmed down the initrd from around 6.8 MB to 5.5 MB ... nice, but not necessary as Canek mentioned. I just play with it to learn and understand even better. I am not sure what the module systemd does or is good for, and https://www.kernel.org/pub/linux/utils/boot/dracut/dracut.html#dracut.kernel does look scary and didn't tell me more about that module yet. I will read more when I find the time, for now it works very well here. Stefan
Re: [gentoo-user] Filesystem doesn't mount automatically after unclean shutdown
On Wednesday 14 May 2014 22:29:46 Nikos Chantziaras wrote: I have this weird problem where a filesystem (Ext4) refuses to mount automatically after something like a power loss or forced shutdown. The fstab entry for it is: LABEL=Data /mnt/Data ext4 defaults,relatime,exec 0 2 During boot, this is what OpenRC tells me: Root: clean, 805088/6553600 files, 9129899/26214400 blocks Data: recovering journal Data: clean, 364344/61546496 files, 137312260/246156800 blocks [ ok ] * Mounting local filesystems ...[ ok ] * Remounting root filesystem read/write ... [ ok ] * Remounting filesystems ...[ ok ] * Updating /etc/mtab ...[ ok ] If I reboot the system again, then all works fine and the FS is mounted automatically. So this is a one-time thingy, happening only on the first boot after an unclean power-off. It would seem that I've stumbled across an OpenRC bug? There's no errors anywhere to be seem. According to the log output above, everything should be fine. I suspect that the recovering journal step is what causes this, but I don't know why. Anyone else encountered this? No, I can't say I have. I do occasionally have to use the reset button to reboot (because the KDM shutdown process had hung), and the system just restarts as Mick says. This is my root fstab entry: /dev/md5/ ext4relatime1 1 The other partitions are similar except for being mounted from /dev/md7. -- Regards Peter
Re: [gentoo-user] boot problems
On 16/05/2014 13:14, cov...@ccs.covici.com wrote: Alan McKinnon alan.mckin...@gmail.com wrote: On 16/05/2014 12:04, Canek Peláez Valdés wrote: Whatever gets rid of LVM is good on my book. I've never understood why people uses it, and in my experience it only brings headaches. Besides, I've heard from many people that btrfs is the way to go in the future. I'm not ready to make the change yet, but I will at some point. LVM is an excellent solution for what it was designed to do, which is to deal with stuff like this: Oops. I misjudged how big /var/log needed to be and now I need to add 50G to that partition. But it's sda6 and I have up to sda8. Argggh! Now I need 5 hour downtime to play 15-pieces with fdisk. LVM makes that 2 commands and 12 seconds. Yes, it's a bit complex and you have to hold the PV/VG/LV model in your head, but it also *fixes* the issue with rigid MSDOS partition style. Modern filesystems like ZFS and btrfs sidestep the need for LVM in a really elegant and wonderful way, none of which changes the fact that ZFS/btrfs weren't around when LVM was first coded. So is btrfs ready for production -- all the tools work, etc. to the level that the ext2/3/4 work? Also, what kernel do you need for this to function -- and last question, how to convert an lvm volume to btrfs, or do you just have to make some space somewhere and copy the files? So far, I have liked lvm, what's the advantage of btrfs over lvm? I don't have enough experience with btrfs to answer, but I believe it's much like ZFS in many ways. So here goes: ZFS dispenses with the entire concept of partitions and rigidly allocated areas of storage on a disk. All you really have is storage. You can divide it up into chunks and sections that look and feel like volumes and partitions but that is not how it's implemented. You don't create a 50G partition for logs, you tell the system to give you 50G of space you will put logs in. And that space is something you can mount, and apply permissions and quotas to. It's a lot like having the best parts of partitions and directories in one unit with none of the rigidity and downsides, and the whole lot is done in a virtual manner by software. You can drop the entire hierarchy of disk/partition/pv/vg/lv/fs right out of your head with these new modern systems, and just not ever have to deal with that complexity at all. -- Alan McKinnon alan.mckin...@gmail.com
Re: [gentoo-user] boot problems
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 16.05.2014 14:03, schrieb Neil Bothwick: On Fri, 16 May 2014 07:14:27 -0400, cov...@ccs.covici.com wrote: So far, I have liked lvm, what's the advantage of btrfs over lvm? I have only looked at btrfs, with a consideration for switching from ZFS, but it seems to offer the same advantages as ZFS. That is, it makes things even easier than LVM does. with LVM you can easily resize volumes and the filesystems on them, but it is still two or three steps, more if you add RAID into the equation. The modern filesystems do it all at once. If you need a bigger var, you just tell it so. And it is exactly the same process for shrinking a volume, something that can be tricky with LVM because of the need to handle volume and filesystem separately. btrfs and zfs are removing the various layers we all had to deal with: partitions, logical volumes, raid-arrays, filesystems, and then snapshots etc. With these modern filesystems you are able to basically say: I have these physical devices/disks, create me a pool of storage with these properties and then just use that pool in a flexible and dynamic way. Your disk based storage is then usable in a way RAM is, you add it and it is available and you can then use it where you like it. No (or let's say much less ...) fixed and hard barriers like partition sizes, if you need space for /var, use it ... if you want to set quotas on /home, just set them for the subvolume, if you add another pair of harddisks, tell btrfs to redistribute redundancy information (re-balance). (I see that Alan right now answered basically the same ;-) ). You get checksums for your blocks and the possibility to repair rotted blocks ... you get snapshots within the filesystem, no more slow rsnapshot-crontabs ... I used zfs-fuse back then and learned about the concepts, and it blew my mind already years ago ;-) zfs on linux ... it works fine for me on one server, but I never really wanted it on my main machines (desktop and laptops) although I once even wrote some how to use zfs on your fully encrypted laptop for a magazine. It always feels like suboptimal because it is not in the kernel to me (think licensing issues here). btrfs is officially in the kernel, still marked experimental because it is in active development, after all I read over the last days it should be quite stable to use if you don't run very complex setups or so ... and doing regular backups should be usual for the people in this list, I assume? Distros like SLES come with btrfs as default fs (soon). I migrated ~3 machines to btrfs in the last days and I really love getting rid of all the partitions and raids that grew over the years ... for now it is cleaned up and flexible and so far solid. btrfs and zfs have different concepts for various aspects, but basically the same goals. I definitely recommend to get in touch with this generation of filesystems. Stefan -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJTdgX8AAoJEClcuD1V0PzmUV0P/1wy3kioRTDQ0YAI8N605wFX wK+FbEXIR09EZ4Q7xukWrJFVo0NGFEU/Sf7N9RomLg83iaDEEaz3HJRGkNotL4aH LeAj0OpILF/7W1lR0bxNAzHNyMawbtrM8mZ9+kNZ8VJFYOq+48tFF/07P18RqDMg 2iw/R6+sXEyS5eMDj32O57uqu8cTK+s8UzIuXABSP/7bFyTj6J5flusZwaKRMtbX iQBdCGasPrDJHIYtEdC3/D/qC+ZJHiNFX8OGNESvDsrAorD38hemuOK3z6oYXegO FxEnF4UvAuBYt+sfYtpvDYyju4IyfGAcbtopPOHDgCrTx/23rqSnreq+OLUEITWL 7mkPnmt3UtkpUDgC8S7y2Xkw5LK9t3espePucv5vKqZJRctRxoMIFeKylPQrrMaP NL6NtrGIBa6iJoPF6lrazNWkaZF6fDUKs6U2BWVReqPZICziUK6T3pLjkNK57tS2 tReLqf8B6OAUHSpWp8lUWBI/Fg+2G4Y4w6mDwxxhUHSuWqQMtZmGTV0BMKHWLJY0 JV8+99dGRcPLNmbocQZqJRrcITMXXEBtMztynXAZ+G4XEwaTgbuH3It3Sp07stiN yns3MN4OoY3/edrOZE653LlX/ffAzQI7HsBo7lXfSBJ5kIHm4QGzls1Lv7DrNJkt ym/IQD3Y8fRBeOtK/vYO =+F6u -END PGP SIGNATURE-
[gentoo-user] How to control SLOT?
After all these years I still can't find my way around SLOT management needed for enlightenment. I want to emerge the latest available in the tree, which right now happens to be (~) 0.18.7. So I added this in my keywords: =x11-wm/enlightenment-0.18.7:0.17 ~amd64 However, if I try: == # emerge -1aDv enlightenment These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild NS] x11-wm/enlightenment-1.0.11:0 [0.18.7:0.17/0.18.7] USE=dbus nls pango -doc -pulseaudio -xcomposite -xinerama -xrandr 2,229 kB Total: 1 package (1 in new slot), Size of downloads: 2,229 kB == It wants to bring in e16, of SLOT 0, instead of 0.18.7 SLOT 0.17. Can you please explain to me how this is meant to work and what the correct syntax is? -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] problems getting systemd to work
Am 16.05.2014 12:53, schrieb cov...@ccs.covici.com: Now for some systemd problems. The root file system was read only when I logged in, but I could remount it rw -- not sure why this was happening. Some units did start, but most did not. Maybe you only got into emergency mode? Also, even though my network names were correct, they did not come up, but I will try to look in the logs to see why not. So we have made some progress, but still a long way to go yet. Note also, that I am not booting into a display manager, just a regular console. What a lot of work just to get the system booted! Oh yes! very complex stuff all around. If you want send me the log off-list, I am curious to read through it. This really gets a challenge here ;-) Stefan
Re: [gentoo-user] boot problems
On Fri, 16 May 2014 14:35:08 +0200, Stefan G. Weichinger wrote: zfs on linux ... it works fine for me on one server, but I never really wanted it on my main machines (desktop and laptops) although I once even wrote some how to use zfs on your fully encrypted laptop for a magazine. It always feels like suboptimal because it is not in the kernel to me (think licensing issues here). That's why I'm looking at btrfs. ZFS is great, it does all I want it to. But it is not in the kernel, which is not a major issue. More important is that it is based on an old version of ZFS, later versions are still closed source. That's a shame, because they support neat things like encryption (yet another separate layer got rid of) and it means ZFS on Linux can't really go anywhere beyond bug fixes and minor tweaks. -- Neil Bothwick There's a fine line between fishing and standing on the shore looking like an idiot. signature.asc Description: PGP signature
Re: [gentoo-user] The writing on the wall ... sys-apps/util-linux
On Friday 16 May 2014 11:35:25 Samuli Suominen wrote: On 16/05/14 10:34, Mick wrote: I got this message after an update: * Messages for package sys-apps/util-linux-2.24.1-r2: * The mesg/wall/write tools have been disabled due to USE=-tty-helpers. I understand that wall has been moved from sys-apps/sysvinit to sys-apps/util- linux, but I am not sure why USE=-tty-helpers is disabled as a default. I couldn't find anything mentioning this in gentoo-dev, but this could just be my poor searching skills. Does anyone know? Because upstream util-linux disables tty-helpers by default regarding it's ./configure --help, as they are not deemed important commands I see. Thank you Samuli for your reply. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] How to control SLOT?
On 16/05/2014 14:38, Mick wrote: After all these years I still can't find my way around SLOT management needed for enlightenment. I want to emerge the latest available in the tree, which right now happens to be (~) 0.18.7. So I added this in my keywords: =x11-wm/enlightenment-0.18.7:0.17 ~amd64 Either drop the = or drop the SLOT :0.17 = always means a specific version is to be specified and a SLOT is not a version However, if I try: == # emerge -1aDv enlightenment These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild NS] x11-wm/enlightenment-1.0.11:0 [0.18.7:0.17/0.18.7] USE=dbus nls pango -doc -pulseaudio -xcomposite -xinerama -xrandr 2,229 kB Total: 1 package (1 in new slot), Size of downloads: 2,229 kB == It wants to bring in e16, of SLOT 0, instead of 0.18.7 SLOT 0.17. Can you please explain to me how this is meant to work and what the correct syntax is? Your keyword entry applies to nothing in the tree, so you get the expected result, the latest stable version of e -- Alan McKinnon alan.mckin...@gmail.com
Re: [gentoo-user] problems getting systemd to work
Canek Peláez Valdés can...@gmail.com wrote: On Thu, May 15, 2014 at 5:01 PM, Stefan G. Weichinger li...@xunil.at wrote: Am 15.05.2014 22:38, schrieb cov...@ccs.covici.com: image=/boot/vmlinuz-3.6.2-gentoo phew. 3.6.2 is from October 2012 ... Did you recompile it with the suggested options for systemd? Maybe it doesn't matter, but just a thought ... that kernel is quite old. It doesn't matter, at least in theory systemd works with linux-3.0. John, could you please send the output from dracut --print-cmdline? In my case, it lists *ALL* my lvms, and (I think) therefore all of them are mounted. Since your lilo.conf only lists rd.lvm.lv=linux-files/64-root and rd.lvm.lv=linux-files/64-usr, I think that would explain why it doesn't mount the others. If dracut --print-cmdline doesn't print the others, could you try to boot with rd.lvm.lv=linux-files/audio in the kernel command line specified in your lilo.conf? If after booting /audio is mounted, then I think we have found the problem. We'll need just to figure out why dracut --print-cmdline does not print the other lvms. Also, could you try to generate your initramfs again, but this time with add_dracutmodules+=systemd lvm? Also, when I booted up, the systemd started a user slice and a new copy of systemd in the slice -- whic I think I don't want -- is this normal? -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici cov...@ccs.covici.com
[gentoo-user] Re: LVM
Am 16.05.2014 13:06, schrieb Alan McKinnon: LVM is an excellent solution for what it was designed to do, which is to deal with stuff like this: Oops. I misjudged how big /var/log needed to be and now I need to add 50G to that partition. But it's sda6 and I have up to sda8. Argggh! Now I need 5 hour downtime to play 15-pieces with fdisk. LVM makes that 2 commands and 12 seconds. Yes, it's a bit complex and you have to hold the PV/VG/LV model in your head, but it also *fixes* the issue with rigid MSDOS partition style. Modern filesystems like ZFS and btrfs sidestep the need for LVM in a really elegant and wonderful way, none of which changes the fact that ZFS/btrfs weren't around when LVM was first coded. exactly. I loved LVM when it was new as it was a way to get the mentioned capability to resize filesystems and underlying partitions. And I still use it for servers, creating a VG on the mdadm-RAID-array and only providing a part of it for the customers ... if they then fill up their samba-shares with cat pictures I can easily ssh in and give them some more space in a minute ... that is nice to have! OK, I also had some issues with LVM over the years ... but not in a regular way, more when physical volumes got flaky or so. In general it just works for me (and show me one piece of tech where you are guaranteed to not have issues with ...) But sure, now I also think of using btrfs on one of the next fileservers I deliver ... and instead of using rsnapshots to give customers a readonly history of their data there could be btrfs-snapshots. time changes, things develop ... Stefan
Re: [gentoo-user] boot problems
Stefan G. Weichinger li...@xunil.at wrote: Am 16.05.2014 14:03, schrieb Neil Bothwick: On Fri, 16 May 2014 07:14:27 -0400, cov...@ccs.covici.com wrote: So far, I have liked lvm, what's the advantage of btrfs over lvm? I have only looked at btrfs, with a consideration for switching from ZFS, but it seems to offer the same advantages as ZFS. That is, it makes things even easier than LVM does. with LVM you can easily resize volumes and the filesystems on them, but it is still two or three steps, more if you add RAID into the equation. The modern filesystems do it all at once. If you need a bigger var, you just tell it so. And it is exactly the same process for shrinking a volume, something that can be tricky with LVM because of the need to handle volume and filesystem separately. btrfs and zfs are removing the various layers we all had to deal with: partitions, logical volumes, raid-arrays, filesystems, and then snapshots etc. With these modern filesystems you are able to basically say: I have these physical devices/disks, create me a pool of storage with these properties and then just use that pool in a flexible and dynamic way. Your disk based storage is then usable in a way RAM is, you add it and it is available and you can then use it where you like it. No (or let's say much less ...) fixed and hard barriers like partition sizes, if you need space for /var, use it ... if you want to set quotas on /home, just set them for the subvolume, if you add another pair of harddisks, tell btrfs to redistribute redundancy information (re-balance). (I see that Alan right now answered basically the same ;-) ). You get checksums for your blocks and the possibility to repair rotted blocks ... you get snapshots within the filesystem, no more slow rsnapshot-crontabs ... I used zfs-fuse back then and learned about the concepts, and it blew my mind already years ago ;-) zfs on linux ... it works fine for me on one server, but I never really wanted it on my main machines (desktop and laptops) although I once even wrote some how to use zfs on your fully encrypted laptop for a magazine. It always feels like suboptimal because it is not in the kernel to me (think licensing issues here). btrfs is officially in the kernel, still marked experimental because it is in active development, after all I read over the last days it should be quite stable to use if you don't run very complex setups or so ... and doing regular backups should be usual for the people in this list, I assume? Distros like SLES come with btrfs as default fs (soon). I migrated ~3 machines to btrfs in the last days and I really love getting rid of all the partitions and raids that grew over the years ... for now it is cleaned up and flexible and so far solid. btrfs and zfs have different concepts for various aspects, but basically the same goals. I definitely recommend to get in touch with this generation of filesystems. Thanks much for that explanation. So where do I find some documentation for btrfs and its user space tools? -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici cov...@ccs.covici.com
Re: [gentoo-user] boot problems
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 16.05.2014 14:43, schrieb Neil Bothwick: On Fri, 16 May 2014 14:35:08 +0200, Stefan G. Weichinger wrote: zfs on linux ... it works fine for me on one server, but I never really wanted it on my main machines (desktop and laptops) although I once even wrote some how to use zfs on your fully encrypted laptop for a magazine. It always feels like suboptimal because it is not in the kernel to me (think licensing issues here). That's why I'm looking at btrfs. ZFS is great, it does all I want it to. But it is not in the kernel, which is not a major issue. More important is that it is based on an old version of ZFS, later versions are still closed source. That's a shame, because they support neat things like encryption (yet another separate layer got rid of) and it means ZFS on Linux can't really go anywhere beyond bug fixes and minor tweaks. Yes, this way one gets stuck somehow with ZFSonLinux. btrfs also does not yet support encryption ... I assume that will come over the time, I don't know if this is still correct: https://btrfs.wiki.kernel.org/index.php/Project_ideas#Encryption But the features available already are great ... https://btrfs.wiki.kernel.org/index.php/Main_Page#Features ;-) -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJTdgyvAAoJEClcuD1V0PzmtWsQAIzyrvFT7gp6WblJi3tXtiDN pj/o4mVLGfQ99jT4eyEi3W3mTs6z1dnLk2tfg5PRmI+tAkV4Y/M/AQ4oKuRWqYGo zK6NFREqTQJlwRvHW1dZAWmOA0Jn2IRqPhfr6Q5ZoBMKhVJhS6zqjTvtxQc7qVwr TZCmkCtBHp8OY/lYD2wZpvqVYjZFcKDvtIXPEwGFCwoeQvn0QcYvdVGWTWe5kCvN JwC3ry6UlKXscqfwTUqqio6vcyxgpr0Pqun908oE0XT0UeIhySB2l6eVVgHc6I4S t5tIOngeqOEaIECchjmkuhau8lkQGUIZyIuzHqi/36TBmiWitHx91FrhONbj1TC7 qQywCcf0oRamBzelYGywqLPmH7Gjh0OXV9eXRNDCeyd5WXOPqBPxdR7jGLNX9G/Z vbD7jiPHOu/DyY96Ks/RiHkiFtfG2pzMivRF8Vu5pUf8H6KmLShm71yOGf+AsxtE BLDR2t1ibscd6FHlZ6kDQHkdDMf4wssDzP2ASiH8Std5vFVSJyNGC4VNkHSkNzLP JTFLAI6Q1hy5k6GkleioVNGVaMQCp09L8aY5pCherAAN+wE2POEyx0z3eHIK3Cxg m1AQWJVOIn7+ykBwJkLF4NgJEDGQ9L4J6GR0rUA+i6/x0nvUiizKPCeNdTv9O4Of GaoiLnwuetJaCLIzDnhY =MTN5 -END PGP SIGNATURE-
Re: [gentoo-user] boot problems
Am 16.05.2014 14:54, schrieb cov...@ccs.covici.com: Thanks much for that explanation. So where do I find some documentation for btrfs and its user space tools? There are many howtos and wiki-pages ... some examples, gentoo-related: https://btrfs.wiki.kernel.org/index.php/Getting_started http://www.funtoo.org/BTRFS_Fun Stefan
RE: [gentoo-user] Can't Get Systemd to Work
-Original Message- From: Neil Bothwick [mailto:n...@digimed.co.uk] Sent: Friday, May 16, 2014 8:06 AM To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Can't Get Systemd to Work On Fri, 16 May 2014 07:34:16 -0400, Hunter Jozwiak wrote: Hi all. I am having issues with Systemd as well. I added to the GRUB2 configuration file the needed command line to get Systemd to start, but for whatever reason, the kernel is adamant that I must use OrenRC. You need to tell us what you added and what the kernel complained about. The only information we have is what is in your mail, we are not the NSA, we cannot see what is on your computer. I recompiled with Genkernel-next a new kernel and initramfs, and that, for whatever reason, doesn't automount my /boot partition. Is there a fix to this? It is standard practice to not mount the /boot partition. By the time the boot process gets to mounting what is in /etc/fstab, /boot is no longer needed. That's why it is usually set to noauto in fstab. -- Neil Bothwick Guns don't kill people--it's those little pieces of lead. GRUB_CMDLINE=init=/usr/lib/system/system And then, grub2-mkconfig -o /boot/grub/grub.cfg.
Re: [gentoo-user] Having Trouble with Wireless Interface
On 05/15/2014 10:50 PM, Mick wrote: On Thursday 15 May 2014 14:24:57 Alexander Kapshuk wrote: On 05/15/2014 11:39 AM, Stroller wrote: On Wed, 14 May 2014, at 12:36 pm, Alexander Kapshuk alexander.kaps...@gmail.com wrote: … If you like to check if RTL8192CE is enabled in your kernel's .config file. If it isn't, you probably want to compile it as a module, and then add rtl8192ce to /etc/conf.d/modules as well. Am pretty sure there's no need to add this one to /etc/conf.d/modules - IME it'll just be found and loaded automagically by the kernel. Thanks for pointing that out. I wasn't aware of that. As I mentioned in my previous post, I do not use genkernel myself. Neither do I - for this reason I found it a little frustrating trying to help in a recent thread, myself. However, I'm pretty sure that loadable kernel modules behave the same whether your kernel is built by hand or by genkernel - if you have modules listed in /etc/conf.d/modules then I have to wonder if you really need them there. I haven't used that file for years, and I prefer to compile everything as a module, too. Stroller. That's interesting. I wasn't aware of that either. So far, I've just been following the instructions given in the handbook, section 7.d, which do recommend explicitly specifying the kernel modules to be loaded at boot time in /etc/conf.d/modules. How does the kernel know then what modules to load at boot time, if it doesn't rely on /etc/conf.d/modules to supply the list of modules to be loaded? Does it use udev, or some other mechanism for that? Thanks. I understand it is udev magic which probes the hardware and it fetches the corresponding module from the kernel, as long as it has been compiled. Incidentally, I noticed that I now have this running on my system: /lib/systemd/systemd-udevd --daemon Understood. Thanks. I too have systemd-udevd running now that you mention it.
RE: [gentoo-user] Can't Get Systemd to Work
-Original Message- From: Neil Bothwick [mailto:n...@digimed.co.uk] Sent: Friday, May 16, 2014 8:06 AM To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Can't Get Systemd to Work On Fri, 16 May 2014 07:34:16 -0400, Hunter Jozwiak wrote: Hi all. I am having issues with Systemd as well. I added to the GRUB2 configuration file the needed command line to get Systemd to start, but for whatever reason, the kernel is adamant that I must use OrenRC. You need to tell us what you added and what the kernel complained about. The only information we have is what is in your mail, we are not the NSA, we cannot see what is on your computer. I recompiled with Genkernel-next a new kernel and initramfs, and that, for whatever reason, doesn't automount my /boot partition. Is there a fix to this? It is standard practice to not mount the /boot partition. By the time the boot process gets to mounting what is in /etc/fstab, /boot is no longer needed. That's why it is usually set to noauto in fstab. -- Neil Bothwick Guns don't kill people--it's those little pieces of lead. GRUB_CMD_LINE_LINUX=init=/usr/lib/system/system, rather.
Re: [gentoo-user] Can't Get Systemd to Work
Am 16.05.2014 15:33, schrieb Hunter Jozwiak: -Original Message- From: Neil Bothwick [mailto:n...@digimed.co.uk] Sent: Friday, May 16, 2014 8:06 AM To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Can't Get Systemd to Work On Fri, 16 May 2014 07:34:16 -0400, Hunter Jozwiak wrote: Hi all. I am having issues with Systemd as well. I added to the GRUB2 configuration file the needed command line to get Systemd to start, but for whatever reason, the kernel is adamant that I must use OrenRC. You need to tell us what you added and what the kernel complained about. The only information we have is what is in your mail, we are not the NSA, we cannot see what is on your computer. I recompiled with Genkernel-next a new kernel and initramfs, and that, for whatever reason, doesn't automount my /boot partition. Is there a fix to this? It is standard practice to not mount the /boot partition. By the time the boot process gets to mounting what is in /etc/fstab, /boot is no longer needed. That's why it is usually set to noauto in fstab. -- Neil Bothwick Guns don't kill people--it's those little pieces of lead. GRUB_CMD_LINE_LINUX=init=/usr/lib/system/system, rather. where is the quote, where is the text? And it's called systemd with a d - GRUB_CMD_LINE_LINUX=init=/usr/lib/system/systemd btw
RE: [gentoo-user] Can't Get Systemd to Work
-Original Message- From: Stefan G. Weichinger [mailto:li...@xunil.at] Sent: Friday, May 16, 2014 9:40 AM To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Can't Get Systemd to Work Am 16.05.2014 15:33, schrieb Hunter Jozwiak: -Original Message- From: Neil Bothwick [mailto:n...@digimed.co.uk] Sent: Friday, May 16, 2014 8:06 AM To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Can't Get Systemd to Work On Fri, 16 May 2014 07:34:16 -0400, Hunter Jozwiak wrote: Hi all. I am having issues with Systemd as well. I added to the GRUB2 configuration file the needed command line to get Systemd to start, but for whatever reason, the kernel is adamant that I must use OrenRC. You need to tell us what you added and what the kernel complained about. The only information we have is what is in your mail, we are not the NSA, we cannot see what is on your computer. I recompiled with Genkernel-next a new kernel and initramfs, and that, for whatever reason, doesn't automount my /boot partition. Is there a fix to this? It is standard practice to not mount the /boot partition. By the time the boot process gets to mounting what is in /etc/fstab, /boot is no longer needed. That's why it is usually set to noauto in fstab. -- Neil Bothwick Guns don't kill people--it's those little pieces of lead. GRUB_CMD_LINE_LINUX=init=/usr/lib/system/system, rather. where is the quote, where is the text? And it's called systemd with a d - GRUB_CMD_LINE_LINUX=init=/usr/lib/system/systemd btw Changed the line to mirror that in the Grub file, no luck. #Append parameters to the Linux Kernel. GRUB_CMD_LINE_LINUX=init=/usr/lib/system/systemd Save the file. Mount /dev/sda2 /boot grub2-mkconfig -o /boot/grub/grub.cfg
Re: [gentoo-user] Can't Get Systemd to Work
Am 16.05.2014 15:50, schrieb Hunter Jozwiak: btw Changed the line to mirror that in the Grub file, no luck. #Append parameters to the Linux Kernel. GRUB_CMD_LINE_LINUX=init=/usr/lib/system/systemd Save the file. Mount /dev/sda2 /boot grub2-mkconfig -o /boot/grub/grub.cfg Why sda2 ? usually sda1 is /boot or / ... Show us lsblk and /etc/fstab ... we have very little information yet. And what is no luck ? What do you get? Stefan
Re: [gentoo-user] Can't Get Systemd to Work
2014-05-16 7:50 GMT-06:00 Hunter Jozwiak hunter.t@gmail.com: -Original Message- From: Stefan G. Weichinger [mailto:li...@xunil.at] Sent: Friday, May 16, 2014 9:40 AM To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Can't Get Systemd to Work Am 16.05.2014 15:33, schrieb Hunter Jozwiak: -Original Message- From: Neil Bothwick [mailto:n...@digimed.co.uk] Sent: Friday, May 16, 2014 8:06 AM To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Can't Get Systemd to Work On Fri, 16 May 2014 07:34:16 -0400, Hunter Jozwiak wrote: Hi all. I am having issues with Systemd as well. I added to the GRUB2 configuration file the needed command line to get Systemd to start, but for whatever reason, the kernel is adamant that I must use OrenRC. You need to tell us what you added and what the kernel complained about. The only information we have is what is in your mail, we are not the NSA, we cannot see what is on your computer. I recompiled with Genkernel-next a new kernel and initramfs, and that, for whatever reason, doesn't automount my /boot partition. Is there a fix to this? It is standard practice to not mount the /boot partition. By the time the boot process gets to mounting what is in /etc/fstab, /boot is no longer needed. That's why it is usually set to noauto in fstab. -- Neil Bothwick Guns don't kill people--it's those little pieces of lead. GRUB_CMD_LINE_LINUX=init=/usr/lib/system/system, rather. where is the quote, where is the text? And it's called systemd with a d - GRUB_CMD_LINE_LINUX=init=/usr/lib/system/systemd btw Changed the line to mirror that in the Grub file, no luck. #Append parameters to the Linux Kernel. GRUB_CMD_LINE_LINUX=init=/usr/lib/system/systemd Save the file. Mount /dev/sda2 /boot grub2-mkconfig -o /boot/grub/grub.cfg The same again you are mistyping systemd, is /usr/lib/systemd/systemd read carefully what you copy, and verify always those paths really exist. If you had done this, you would have noticed /usr/lib/system/system doesn't exist at all.
Re: [gentoo-user] boot problems
Stefan G. Weichinger li...@xunil.at wrote: Am 16.05.2014 14:54, schrieb cov...@ccs.covici.com: Thanks much for that explanation. So where do I find some documentation for btrfs and its user space tools? There are many howtos and wiki-pages ... some examples, gentoo-related: https://btrfs.wiki.kernel.org/index.php/Getting_started Thanks, I will look at this in my copious free time. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici cov...@ccs.covici.com
Re: [gentoo-user] Can't Get Systemd to Work
Am 16.05.2014 16:00, schrieb Jc García: The same again you are mistyping systemd, is /usr/lib/systemd/systemd read carefully what you copy, and verify always those paths really exist. If you had done this, you would have noticed /usr/lib/system/system doesn't exist at all. ( Ah, I only spotted one missing d ... *oops* )
Re: [gentoo-user] How to control SLOT?
On Friday 16 May 2014 13:44:37 Alan McKinnon wrote: On 16/05/2014 14:38, Mick wrote: After all these years I still can't find my way around SLOT management needed for enlightenment. I want to emerge the latest available in the tree, which right now happens to be (~) 0.18.7. So I added this in my keywords: =x11-wm/enlightenment-0.18.7:0.17 ~amd64 Either drop the = or drop the SLOT :0.17 = always means a specific version is to be specified and a SLOT is not a version OK, dropping = still wants to install e16. Dropping still wants to install e16. Dropping the SLOT :0.17 still wants to install e16. There must be some way of bringing in any =0.18.7:0.17, but not 'x11- wm/enlightenment-1.0.11:0' What else could I try? -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] udev or Gentoo issue?
On Friday 16 May 2014 11:43:41 Samuli Suominen wrote:
On 15/05/14 02:59, Grant wrote:
I'm having a problem starting the USB network interfaces properly
on one of my systems. I brought the problem to the udev list and
they're indicating that it's a Gentoo problem:
https://www.mail-archive.com/systemd-devel@lists.freedesktop.org/ms
g18840.html
Should I file a bug?
- Grant
Like pointed out in the upstream thread, it's either wrongly built
net-misc/dhcpcd (should be with USE=udev)
and if not using dhcpcd, it might be a bug in net-misc/netifrc's
/etc/init.d/net.lo depend() { } section --
it's possible it's missing dependency that forces /etc/init.d/udev
start first, specially if OpenRC is using parallel
startup
So not really a udev bug, rather a misconfiguration in dhcpcd USE
flags OR bug in dependencies of netifrc's net.lo script
I'm starting two interfaces, one that uses dhcpcd and one that does
not. Both fail to start in the default runlevel until they are
hotplugged later. I do have dhcpcd built with USE=udev. The string
udev does not occur in /etc/init.d/net.lo so maybe that's the
problem? Please confirm that I should file a Gentoo bug for this.
- Grant
Try adding 'after udev' to net.lo's depend() { } section and see if
that helps, if it does, file a bug
saying so.
I added it like this and rebooted:
depend()
{
after udev
but the result was the same. I also have udev and udev-mount in the
sysinit runlevel.
It was more of an educated guess than 100% accurate knowledge. I can't
think of an another
way to force netifrc to behave, since it's not coded in C, and it
can't link to libudev, so...
However since you say *both*, even the one with dhcpcd fail to start,
before filing that bug,
see if disabling netifrc hotplugging works:
# ln -s /dev/null /etc/udev/rules.d/90-network.rules
Will that disable interface renaming or hotplugging? The system with
the issue is remote and if the interfaces aren't renamed or if
hotplugging doesn't happen then I won't be able to access the system
for up to 24 hours. That's fine and I'm happy to test stuff like this
anyway but I don't think this particular test will be informative
because:
It will disable the hotplugging, it means you *must* have the net.*
stuff added
to the default to runlevel yourself, like eg.
# rc-update add net.foobar default
They're in the default runlevel:
# rc-update|grep net.enp
net.enp0s20u2u1 | default
net.enp0s20u2u2 | default
I can disable hotplugging with rc_hotplug in rc.conf. Hotplugging is
actually disabled by default there and my network interfaces won't
start automatically that way.
I'm not 100% sure the rc_hotplug will also disable the 90-network.rules
triggered
interface hotplugging
Don't count on that
Samuli's right. I was experimenting on a new install how to stop net.eth0
from coming up (it was stalling forever because there was no ethernet cable
present). No matter what I tried with /etc/rc.conf, or eselect rc, I couldn't
stop the darn thing starting up.
--
Regards,
Mick
signature.asc
Description: This is a digitally signed message part.
Re: [gentoo-user] How to control SLOT?
On 16/05/2014 18:03, Mick wrote: On Friday 16 May 2014 13:44:37 Alan McKinnon wrote: On 16/05/2014 14:38, Mick wrote: After all these years I still can't find my way around SLOT management needed for enlightenment. I want to emerge the latest available in the tree, which right now happens to be (~) 0.18.7. So I added this in my keywords: =x11-wm/enlightenment-0.18.7:0.17 ~amd64 Either drop the = or drop the SLOT :0.17 = always means a specific version is to be specified and a SLOT is not a version OK, dropping = still wants to install e16. Dropping still wants to install e16. Dropping the SLOT :0.17 still wants to install e16. There must be some way of bringing in any =0.18.7:0.17, but not 'x11- wm/enlightenment-1.0.11:0' What else could I try? There's nothing special about E anymore, it isn't package.masked, it's simply keyworded ~amd64 ~arm ~x86 Are you running amd64 or ~amd64? Do you have some local package.mask blocking e17? Here's my setting that work for me: $ grep ACCEPT_KEYWORDS /etc/portage/make.conf ACCEPT_KEYWORDS=~amd64 $ grep enlightenment /var/lib/portage/world x11-wm/enlightenment $ grep -ir enlightenment /etc/portage /etc/portage/package.mask/package.mask:x11-wm/enlightenment:0 So you *should be able to just keyword e17 and have it work: echo x11-wm/enlightenment /etc/portage/package.accept_keywords -- Alan McKinnon alan.mckin...@gmail.com
Re: [gentoo-user] problems getting systemd to work
On Fri, May 16, 2014 at 5:53 AM, cov...@ccs.covici.com wrote: Canek Peláez Valdés can...@gmail.com wrote: On Thu, May 15, 2014 at 5:01 PM, Stefan G. Weichinger li...@xunil.at wrote: Am 15.05.2014 22:38, schrieb cov...@ccs.covici.com: image=/boot/vmlinuz-3.6.2-gentoo phew. 3.6.2 is from October 2012 ... Did you recompile it with the suggested options for systemd? Maybe it doesn't matter, but just a thought ... that kernel is quite old. It doesn't matter, at least in theory systemd works with linux-3.0. John, could you please send the output from dracut --print-cmdline? In my case, it lists *ALL* my lvms, and (I think) therefore all of them are mounted. Since your lilo.conf only lists rd.lvm.lv=linux-files/64-root and rd.lvm.lv=linux-files/64-usr, I think that would explain why it doesn't mount the others. If dracut --print-cmdline doesn't print the others, could you try to boot with rd.lvm.lv=linux-files/audio in the kernel command line specified in your lilo.conf? If after booting /audio is mounted, then I think we have found the problem. We'll need just to figure out why dracut --print-cmdline does not print the other lvms. Also, could you try to generate your initramfs again, but this time with add_dracutmodules+=systemd lvm? The secret to activate all the volumes, is to specify the volume groups instead of each volume -- that got them all activated, but systemd still is not working well. The print-cmdline still just prints the volumes necessary to mount the root and user file systems, which makes sense, but why the rest of them do not activate, I have no clue. I don't understand the current situation .So now you get ALL your volumes activated, or not? Now for some systemd problems. The root file system was read only when I logged in, but I could remount it rw -- not sure why this was happening. Set systemd.log_level=debug in your command line, and post the exit from journalctl -b. Some units did start, but most did not. Whenever I tried to start one manually, I got a message like the following: I wrote systemctl start /usr/lib/systemd/system/ntpd.service and got the error that it was unable to start because it could not find ntpd.service.mount:] May 16 01:59:52 ccs kernel: 31systemd[1]: Failed to load configuration for usr-lib-systemd-system-ntpd.service.mount: No such file or directory May 16 01:59:52 ccs kernel: 31systemd[1]: Trying to enqueue job usr-lib-systemd-system-ntpd.service.mount/start/replace May 16 01:59:53 ccs kernel: 31systemd[1]: Sent message type=error sender=n/a destination=n/a object=n/a interface=n/a member=n/a cookie=1 reply_cookie=1 erro\r=Unit usr-lib-systemd-system-ntpd.service.mount failed to load: No such file or directory. May 16 01:59:53 ccs kernel: 31systemd[1]: Failed to process message [type=method_call sender=n/a path=/org/freedesktop/systemd1 interface=org.freedesktop.sys\temd1.Manager member=StartUnit signature=ss]: Unit usr-lib-systemd-system-ntpd.service.mount failed to load: No such file or directory. No matter what unit I tried to start I would get such a message about the service.mount. That sounds like a problem with the cgroups hierarchy (which uses a virtual filesystem). I don't remember seeing a problem like that before. Also, even though my network names were correct, they did not come up, but I will try to look in the logs to see why not. systemd will not (AFAIK) start your network, and before the 209 or 210 version it needed helper program (NetwokrManager, connman, ip, ifconfig, etc.) to do it. Now it includes networkd, but you need to set up .network files (like .service files) to configure it. See [1]. So we have made some progress, but still a long way to go yet. Note also, that I am not booting into a display manager, just a regular console. What a lot of work just to get the system booted! Well, you have a setup that is not, by any means, simple. Also, in my experience old LVM configurations seem to cause a lot of troubles to bring to what systemd expects. John, could you also post here your kernel config? Those cgroups errors *may* be related to some missing functionality from the kernel. Regards. -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] problems getting systemd to work
On Fri, May 16, 2014 at 7:46 AM, cov...@ccs.covici.com wrote: Canek Peláez Valdés can...@gmail.com wrote: On Thu, May 15, 2014 at 5:01 PM, Stefan G. Weichinger li...@xunil.at wrote: Am 15.05.2014 22:38, schrieb cov...@ccs.covici.com: image=/boot/vmlinuz-3.6.2-gentoo phew. 3.6.2 is from October 2012 ... Did you recompile it with the suggested options for systemd? Maybe it doesn't matter, but just a thought ... that kernel is quite old. It doesn't matter, at least in theory systemd works with linux-3.0. John, could you please send the output from dracut --print-cmdline? In my case, it lists *ALL* my lvms, and (I think) therefore all of them are mounted. Since your lilo.conf only lists rd.lvm.lv=linux-files/64-root and rd.lvm.lv=linux-files/64-usr, I think that would explain why it doesn't mount the others. If dracut --print-cmdline doesn't print the others, could you try to boot with rd.lvm.lv=linux-files/audio in the kernel command line specified in your lilo.conf? If after booting /audio is mounted, then I think we have found the problem. We'll need just to figure out why dracut --print-cmdline does not print the other lvms. Also, could you try to generate your initramfs again, but this time with add_dracutmodules+=systemd lvm? Also, when I booted up, the systemd started a user slice and a new copy of systemd in the slice -- whic I think I don't want -- is this normal? Yes: every user session gets its own cgroup and systemd --user instance. You can track them with loginctl. Regards. -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] boot problems
On Fri, May 16, 2014 at 7:10 AM, Stefan G. Weichinger li...@xunil.at wrote: Am 16.05.2014 13:56, schrieb Bruce Schultz: I ask because in all my reorganizing furor I also thought that now with btrfs only I could get rid of lvm mdraid as dracut-modules. I can try ... ;-) (don't call me ricer) If you have a multi-disk btrfs, I think you need to add the btrfs dracut module. At least that's how I remember it, but its been a while my memory could be failing me, or it could well have changed since then. I currently have in /etc/dracut.conf: add_dracutmodules+=bash systemd hostonly=yes hostonly_cmdline=yes and am able to boot via grub2 and efi, that means, /boot/efi (vfat) on /dev/sda1 (sda is the SSD) and / as btrfs-subvol on /dev/sda2 (with /boot as directory on it). So no multi-disk btrfs for / or /boot on this machine. - removing lvm mdraid from dracut slimmed down the initrd from around 6.8 MB to 5.5 MB ... nice, but not necessary as Canek mentioned. I just play with it to learn and understand even better. I am not sure what the module systemd does or is good for, and https://www.kernel.org/pub/linux/utils/boot/dracut/dracut.html#dracut.kernel does look scary and didn't tell me more about that module yet. With the systemd module, dracut uses systemd as init. So you have your initramfs, which executes systemd to setup the machine up until /usr is mounted, and then that instance of systemd calls the instance of systemd in the hard drive. If you don't use the systemd module, your initramfs uses a custom init script to mount /usr and similar stuff. It seems to work, but I trust more systemd to do it, and I certainly prefer not to rely on any script during boot up. Also, for non-trivial setups, I'm sure systemd handles them better that a custom init script; that's why I recommended John to use the systemd module. Regards. -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
[gentoo-user] Re: How to control SLOT?
Mick wrote: On Friday 16 May 2014 13:44:37 Alan McKinnon wrote: On 16/05/2014 14:38, Mick wrote: After all these years I still can't find my way around SLOT management needed for enlightenment. I want to emerge the latest available in the tree, which right now happens to be (~) 0.18.7. So I added this in my keywords: =x11-wm/enlightenment-0.18.7:0.17 ~amd64 Either drop the = or drop the SLOT :0.17 = always means a specific version is to be specified and a SLOT is not a version OK, dropping = still wants to install e16. Dropping still wants to install e16. Dropping the SLOT :0.17 still wants to install e16. There must be some way of bringing in any =0.18.7:0.17, but not 'x11- wm/enlightenment-1.0.11:0' What else could I try? x11-wm/enlightenment:0.17 ~amd64 - Jörg
Re: [gentoo-user] problems getting systemd to work
On Fri, May 16, 2014 at 12:17 PM, cov...@ccs.covici.com wrote:
[snip]
I don't understand the current situation .So now you get ALL your
volumes activated, or not?
Yep, they are all activated and they all get mounted.
Cool, one problem less.
Now for some systemd problems. The root file system was read only when
I logged in, but I could remount it rw -- not sure why this was
happening.
Set systemd.log_level=debug in your command line, and post the exit
from journalctl -b.
I had debug in the command line by itself, would that make the correct
log_level? The file is quite large, should I send it to you privately?
I don't think is necessary, I may have found the real problem (see below).
Some units did start, but most did not. Whenever I tried to
start one manually, I got a message like the following:
[snip]
No matter what unit I tried to start I would get such a message about
the service.mount.
That sounds like a problem with the cgroups hierarchy (which uses a
virtual filesystem). I don't remember seeing a problem like that
before.
Also, even though my network names were correct, they did not come up,
but I will try to look in the logs to see why not.
I wrote a service file to start my network adaptors, here it is:
network@.service
[Unit]
Description=Network Connectivity for %i
Wants=network.target
Before=network.target
BindsTo=sys-subsystem-net-devices-%i.device
After=sys-subsystem-net-devices-%i.device
[Service]
Type=oneshot
RemainAfterExit=yes
EnvironmentFile=/etc/conf.d/network@%i
ExecStart=/usr/bin/ip link set dev %i up
ExecStart=/usr/bin/ip addr add ${address}/${netmask} broadcast ${broadcast}
dev %i
ExecStart=/bin/bash -c 'test -n ${gateway} /usr/bin/ip route add default
via
${gateway}'
ExecStart=/bin/bash -c 'test -f /etc/conf.d/postup@%i.sh/bin/bash
/etc/conf.d/postup@%i.sh
ExecStop=/usr/bin/ip addr flush dev %i
ExecStop=/usr/bin/ip link set dev %i down
[Install]
WantedBy=network.target
Did you enabled network@ifaca.service? Also, WantedBy=network.target
doesn't do what you probably think it does (check [1]... and BTW, I
forgot my last footnote, is now on [2]).
I would use WantedBy=multi-user.target.
systemd will not (AFAIK) start your network, and before the 209 or 210
version it needed helper program (NetwokrManager, connman, ip,
ifconfig, etc.) to do it. Now it includes networkd, but you need to
set up .network files (like .service files) to configure it. See [1].
So we have made some progress, but still a long way to go yet. Note
also, that I am not booting into a display manager, just a regular
console.
What a lot of work just to get the system booted!
Well, you have a setup that is not, by any means, simple. Also, in my
experience old LVM configurations seem to cause a lot of troubles to
bring to what systemd expects.
John, could you also post here your kernel config? Those cgroups
errors *may* be related to some missing functionality from the kernel.
[snip kernel config]
John, your kernel is incorrectly configured to be used by systemd.
When you installed systemd, a warning should have appeared about some
missing configure options; you either didn't saw or ignored those
warnings. Install systemd again so you can see them.
From what I can tell, you are missing *AT LEAST* the following options:
CONFIG_AUTOFS4_FS
CONFIG_DMIID
CONFIG_FANOTIFY
CONFIG_INOTIFY_USER
CONFIG_PROC_FS
CONFIG_SYSFS
John, if you don't set them, systemd *CANNOT WORK PROPERLY*. They are
mandatory. I'm surprised you are able to boot to a semi-working state.
Yes, migrating to systemd is a lot of work. But if you don't see (or
ignore) your system messages, that work gets multiplied several times.
Reconfigure, recompile, and reinstall your kernel (don't forget to
reinstall the modules!), regenerate your initramfs, update lilo (if I
remember correctly, you need to run lilo -something-or-another every
time you change kernel and/or initramfs), and try again.
Regards
[1] http://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/
[2] http://www.freedesktop.org/software/systemd/man/systemd.network.html
--
Canek Peláez Valdés
Profesor de asignatura, Facultad de Ciencias
Universidad Nacional Autónoma de México
Re: [gentoo-user] problems getting systemd to work
Canek Peláez Valdés can...@gmail.com wrote:
On Fri, May 16, 2014 at 12:17 PM, cov...@ccs.covici.com wrote:
[snip]
I don't understand the current situation .So now you get ALL your
volumes activated, or not?
Yep, they are all activated and they all get mounted.
Cool, one problem less.
Now for some systemd problems. The root file system was read only when
I logged in, but I could remount it rw -- not sure why this was
happening.
Set systemd.log_level=debug in your command line, and post the exit
from journalctl -b.
I had debug in the command line by itself, would that make the correct
log_level? The file is quite large, should I send it to you privately?
I don't think is necessary, I may have found the real problem (see below).
Some units did start, but most did not. Whenever I tried to
start one manually, I got a message like the following:
[snip]
No matter what unit I tried to start I would get such a message about
the service.mount.
That sounds like a problem with the cgroups hierarchy (which uses a
virtual filesystem). I don't remember seeing a problem like that
before.
Also, even though my network names were correct, they did not come up,
but I will try to look in the logs to see why not.
I wrote a service file to start my network adaptors, here it is:
network@.service
[Unit]
Description=Network Connectivity for %i
Wants=network.target
Before=network.target
BindsTo=sys-subsystem-net-devices-%i.device
After=sys-subsystem-net-devices-%i.device
[Service]
Type=oneshot
RemainAfterExit=yes
EnvironmentFile=/etc/conf.d/network@%i
ExecStart=/usr/bin/ip link set dev %i up
ExecStart=/usr/bin/ip addr add ${address}/${netmask} broadcast ${broadcast}
dev %i
ExecStart=/bin/bash -c 'test -n ${gateway} /usr/bin/ip route add default
via
${gateway}'
ExecStart=/bin/bash -c 'test -f /etc/conf.d/postup@%i.sh/bin/bash
/etc/conf.d/postup@%i.sh
ExecStop=/usr/bin/ip addr flush dev %i
ExecStop=/usr/bin/ip link set dev %i down
[Install]
WantedBy=network.target
Did you enabled network@ifaca.service? Also, WantedBy=network.target
doesn't do what you probably think it does (check [1]... and BTW, I
forgot my last footnote, is now on [2]).
I would use WantedBy=multi-user.target.
systemd will not (AFAIK) start your network, and before the 209 or 210
version it needed helper program (NetwokrManager, connman, ip,
ifconfig, etc.) to do it. Now it includes networkd, but you need to
set up .network files (like .service files) to configure it. See [1].
So we have made some progress, but still a long way to go yet. Note
also, that I am not booting into a display manager, just a regular
console.
What a lot of work just to get the system booted!
Well, you have a setup that is not, by any means, simple. Also, in my
experience old LVM configurations seem to cause a lot of troubles to
bring to what systemd expects.
John, could you also post here your kernel config? Those cgroups
errors *may* be related to some missing functionality from the kernel.
[snip kernel config]
John, your kernel is incorrectly configured to be used by systemd.
When you installed systemd, a warning should have appeared about some
missing configure options; you either didn't saw or ignored those
warnings. Install systemd again so you can see them.
From what I can tell, you are missing *AT LEAST* the following options:
CONFIG_AUTOFS4_FS
configured as a module.
CONFIG_DMIID
set to Y
CONFIG_FANOTIFY
set to y
CONFIG_INOTIFY_USER
set to y
CONFIG_PROC_FS
set to y
CONFIG_SYSFS
set to y
John, if you don't set them, systemd *CANNOT WORK PROPERLY*. They are
mandatory. I'm surprised you are able to boot to a semi-working state.
Yes, migrating to systemd is a lot of work. But if you don't see (or
ignore) your system messages, that work gets multiplied several times.
Reconfigure, recompile, and reinstall your kernel (don't forget to
reinstall the modules!), regenerate your initramfs, update lilo (if I
remember correctly, you need to run lilo -something-or-another every
time you change kernel and/or initramfs), and try again.
Regards
[1] http://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/
[2] http://www.freedesktop.org/software/systemd/man/systemd.network.html
--
Canek Peláez Valdés
Profesor de asignatura, Facultad de Ciencias
Universidad Nacional Autónoma de México
--
Your life is like a penny. You're going to lose it. The question is:
How do
you spend it?
John Covici
cov...@ccs.covici.com
Re: [gentoo-user] problems getting systemd to work
On Fri, May 16, 2014 at 1:11 PM, cov...@ccs.covici.com wrote:
Canek Peláez Valdés can...@gmail.com wrote:
On Fri, May 16, 2014 at 12:17 PM, cov...@ccs.covici.com wrote:
[snip]
I don't understand the current situation .So now you get ALL your
volumes activated, or not?
Yep, they are all activated and they all get mounted.
Cool, one problem less.
Now for some systemd problems. The root file system was read only when
I logged in, but I could remount it rw -- not sure why this was
happening.
Set systemd.log_level=debug in your command line, and post the exit
from journalctl -b.
I had debug in the command line by itself, would that make the correct
log_level? The file is quite large, should I send it to you privately?
I don't think is necessary, I may have found the real problem (see below).
Some units did start, but most did not. Whenever I tried to
start one manually, I got a message like the following:
[snip]
No matter what unit I tried to start I would get such a message about
the service.mount.
That sounds like a problem with the cgroups hierarchy (which uses a
virtual filesystem). I don't remember seeing a problem like that
before.
Also, even though my network names were correct, they did not come up,
but I will try to look in the logs to see why not.
I wrote a service file to start my network adaptors, here it is:
network@.service
[Unit]
Description=Network Connectivity for %i
Wants=network.target
Before=network.target
BindsTo=sys-subsystem-net-devices-%i.device
After=sys-subsystem-net-devices-%i.device
[Service]
Type=oneshot
RemainAfterExit=yes
EnvironmentFile=/etc/conf.d/network@%i
ExecStart=/usr/bin/ip link set dev %i up
ExecStart=/usr/bin/ip addr add ${address}/${netmask} broadcast
${broadcast} dev %i
ExecStart=/bin/bash -c 'test -n ${gateway} /usr/bin/ip route add
default via
${gateway}'
ExecStart=/bin/bash -c 'test -f /etc/conf.d/postup@%i.sh/bin/bash
/etc/conf.d/postup@%i.sh
ExecStop=/usr/bin/ip addr flush dev %i
ExecStop=/usr/bin/ip link set dev %i down
[Install]
WantedBy=network.target
Did you enabled network@ifaca.service? Also, WantedBy=network.target
doesn't do what you probably think it does (check [1]... and BTW, I
forgot my last footnote, is now on [2]).
I would use WantedBy=multi-user.target.
systemd will not (AFAIK) start your network, and before the 209 or 210
version it needed helper program (NetwokrManager, connman, ip,
ifconfig, etc.) to do it. Now it includes networkd, but you need to
set up .network files (like .service files) to configure it. See [1].
So we have made some progress, but still a long way to go yet. Note
also, that I am not booting into a display manager, just a regular
console.
What a lot of work just to get the system booted!
Well, you have a setup that is not, by any means, simple. Also, in my
experience old LVM configurations seem to cause a lot of troubles to
bring to what systemd expects.
John, could you also post here your kernel config? Those cgroups
errors *may* be related to some missing functionality from the kernel.
[snip kernel config]
John, your kernel is incorrectly configured to be used by systemd.
When you installed systemd, a warning should have appeared about some
missing configure options; you either didn't saw or ignored those
warnings. Install systemd again so you can see them.
From what I can tell, you are missing *AT LEAST* the following options:
CONFIG_AUTOFS4_FS
configured as a module.
CONFIG_DMIID
set to Y
CONFIG_FANOTIFY
set to y
CONFIG_INOTIFY_USER
set to y
CONFIG_PROC_FS
set to y
CONFIG_SYSFS
set to y
I beg your pardon; GMail cut the config file and I didn't notice.
Well then, please send me privately the output from journalctl -b.
Regards.
--
Canek Peláez Valdés
Profesor de asignatura, Facultad de Ciencias
Universidad Nacional Autónoma de México
Re: [gentoo-user] problems getting systemd to work
Canek Peláez Valdés can...@gmail.com wrote:
On Fri, May 16, 2014 at 1:11 PM, cov...@ccs.covici.com wrote:
Canek Peláez Valdés can...@gmail.com wrote:
On Fri, May 16, 2014 at 12:17 PM, cov...@ccs.covici.com wrote:
[snip]
I don't understand the current situation .So now you get ALL your
volumes activated, or not?
Yep, they are all activated and they all get mounted.
Cool, one problem less.
Now for some systemd problems. The root file system was read only
when
I logged in, but I could remount it rw -- not sure why this was
happening.
Set systemd.log_level=debug in your command line, and post the exit
from journalctl -b.
I had debug in the command line by itself, would that make the correct
log_level? The file is quite large, should I send it to you privately?
I don't think is necessary, I may have found the real problem (see below).
Some units did start, but most did not. Whenever I tried to
start one manually, I got a message like the following:
[snip]
No matter what unit I tried to start I would get such a message about
the service.mount.
That sounds like a problem with the cgroups hierarchy (which uses a
virtual filesystem). I don't remember seeing a problem like that
before.
Also, even though my network names were correct, they did not come up,
but I will try to look in the logs to see why not.
I wrote a service file to start my network adaptors, here it is:
network@.service
[Unit]
Description=Network Connectivity for %i
Wants=network.target
Before=network.target
BindsTo=sys-subsystem-net-devices-%i.device
After=sys-subsystem-net-devices-%i.device
[Service]
Type=oneshot
RemainAfterExit=yes
EnvironmentFile=/etc/conf.d/network@%i
ExecStart=/usr/bin/ip link set dev %i up
ExecStart=/usr/bin/ip addr add ${address}/${netmask} broadcast
${broadcast} dev %i
ExecStart=/bin/bash -c 'test -n ${gateway} /usr/bin/ip route add
default via
${gateway}'
ExecStart=/bin/bash -c 'test -f /etc/conf.d/postup@%i.sh/bin/bash
/etc/conf.d/postup@%i.sh
ExecStop=/usr/bin/ip addr flush dev %i
ExecStop=/usr/bin/ip link set dev %i down
[Install]
WantedBy=network.target
Did you enabled network@ifaca.service? Also, WantedBy=network.target
doesn't do what you probably think it does (check [1]... and BTW, I
forgot my last footnote, is now on [2]).
I would use WantedBy=multi-user.target.
systemd will not (AFAIK) start your network, and before the 209 or 210
version it needed helper program (NetwokrManager, connman, ip,
ifconfig, etc.) to do it. Now it includes networkd, but you need to
set up .network files (like .service files) to configure it. See [1].
So we have made some progress, but still a long way to go yet. Note
also, that I am not booting into a display manager, just a regular
console.
What a lot of work just to get the system booted!
Well, you have a setup that is not, by any means, simple. Also, in my
experience old LVM configurations seem to cause a lot of troubles to
bring to what systemd expects.
John, could you also post here your kernel config? Those cgroups
errors *may* be related to some missing functionality from the kernel.
[snip kernel config]
John, your kernel is incorrectly configured to be used by systemd.
When you installed systemd, a warning should have appeared about some
missing configure options; you either didn't saw or ignored those
warnings. Install systemd again so you can see them.
From what I can tell, you are missing *AT LEAST* the following options:
CONFIG_AUTOFS4_FS
configured as a module.
CONFIG_DMIID
set to Y
CONFIG_FANOTIFY
set to y
CONFIG_INOTIFY_USER
set to y
CONFIG_PROC_FS
set to y
CONFIG_SYSFS
set to y
I beg your pardon; GMail cut the config file and I didn't notice.
Well then, please send me privately the output from journalctl -b.
I did find one error so far, I had network@.eth0 and eth2 when I should
have had network@eth0 and eth2 -- thanks to Stefan.
I will send you what logs I have.
Thanks.
Regards.
--
Canek Peláez Valdés
Profesor de asignatura, Facultad de Ciencias
Universidad Nacional Autónoma de México
--
Your life is like a penny. You're going to lose it. The question is:
How do
you spend it?
John Covici
cov...@ccs.covici.com
Re: [gentoo-user] Can't Get Systemd to Work
On May 16, 2014, at 10:00, Jc García jyo.gar...@gmail.com wrote: 2014-05-16 7:50 GMT-06:00 Hunter Jozwiak hunter.t@gmail.com: -Original Message- From: Stefan G. Weichinger [mailto:li...@xunil.at] Sent: Friday, May 16, 2014 9:40 AM To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Can't Get Systemd to Work Am 16.05.2014 15:33, schrieb Hunter Jozwiak: -Original Message- From: Neil Bothwick [mailto:n...@digimed.co.uk] Sent: Friday, May 16, 2014 8:06 AM To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Can't Get Systemd to Work On Fri, 16 May 2014 07:34:16 -0400, Hunter Jozwiak wrote: Hi all. I am having issues with Systemd as well. I added to the GRUB2 configuration file the needed command line to get Systemd to start, but for whatever reason, the kernel is adamant that I must use OrenRC. You need to tell us what you added and what the kernel complained about. The only information we have is what is in your mail, we are not the NSA, we cannot see what is on your computer. I recompiled with Genkernel-next a new kernel and initramfs, and that, for whatever reason, doesn't automount my /boot partition. Is there a fix to this? It is standard practice to not mount the /boot partition. By the time the boot process gets to mounting what is in /etc/fstab, /boot is no longer needed. That's why it is usually set to noauto in fstab. -- Neil Bothwick Guns don't kill people--it's those little pieces of lead. GRUB_CMD_LINE_LINUX=init=/usr/lib/system/system, rather. where is the quote, where is the text? And it's called systemd with a d - GRUB_CMD_LINE_LINUX=init=/usr/lib/system/systemd btw Changed the line to mirror that in the Grub file, no luck. #Append parameters to the Linux Kernel. GRUB_CMD_LINE_LINUX=init=/usr/lib/system/systemd Save the file. Mount /dev/sda2 /boot grub2-mkconfig -o /boot/grub/grub.cfg The same again you are mistyping systemd, is /usr/lib/systemd/systemd read carefully what you copy, and verify always those paths really exist. If you had done this, you would have noticed /usr/lib/system/system doesn't exist at all. Here are the clntents of lsblk and filesystem table, as well as the Grub settings file, https://www.dropbox.com/s/vn6we8gxpccrnpe/infoorforsystemdissue.txt
Re: [gentoo-user] How to control SLOT?
On Friday 16 May 2014 17:30:06 Alan McKinnon wrote: There's nothing special about E anymore, it isn't package.masked, it's simply keyworded ~amd64 ~arm ~x86 Are you running amd64 or ~amd64? Do you have some local package.mask blocking e17? I'm running amd64 with the odd exception (like enlightenment) and I have no enlightenment related masks set up. Here's my setting that work for me: $ grep ACCEPT_KEYWORDS /etc/portage/make.conf ACCEPT_KEYWORDS=~amd64 $ grep enlightenment /var/lib/portage/world x11-wm/enlightenment $ grep -ir enlightenment /etc/portage /etc/portage/package.mask/package.mask:x11-wm/enlightenment:0 Ahh! You have masked SLOT :0 to stop e16 being pulled in. I thought that this would be achievable somehow, merely by keywording SLOT :0.17, but without masking e16. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Re: How to control SLOT?
On Friday 16 May 2014 18:09:08 Jörg Schaible wrote: Mick wrote: What else could I try? x11-wm/enlightenment:0.17 ~amd64 Thanks Jörg, this (partly) worked and put me on the right path. So, now I have in /etc/portage/package.keywords/enlightenment: x11-wm/enlightenment:0.17 ~amd64 and in /etc/portage/sets/enlightenment: x11-wm/enlightenment:0.17 Portage no longer tries to pull in e16 when I emerge set '@enlightenment' because the latter is only asking for SLOT :0.17. Of course, if I try 'emerge -1aDv enlightenment', then all bets are off without explicitly masking e16 off as Alan has done. Thank you both for your help! :-) -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] boot problems
On Fri, 16 May 2014 15:03:43 +0200, Stefan G. Weichinger wrote: That's why I'm looking at btrfs. ZFS is great, it does all I want it to. But it is not in the kernel, which is not a major issue. More important is that it is based on an old version of ZFS, later versions are still closed source. That's a shame, because they support neat things like encryption (yet another separate layer got rid of) and it means ZFS on Linux can't really go anywhere beyond bug fixes and minor tweaks. Yes, this way one gets stuck somehow with ZFSonLinux. btrfs also does not yet support encryption ... I assume that will come over the time, I don't know if this is still correct: https://btrfs.wiki.kernel.org/index.php/Project_ideas#Encryption If it doesn't happen,. it is still on a par with ZFS on that front. But there is always the possibility that someone will want it enough to implement it... looks in the general direction of SUSE. I like the idea of the version of RAID1 they have, where two copies of the data are stored, even if you have multiple disks. It looks like it should provide RAID5 like capacities without some of the overhead. I've been moving my ZFS partitions around, which reminded me how good zfs send/zfs recv are, so I can give btrfs RAID a good try out soon. -- Neil Bothwick LISP: Lots of Infuriating Silly Parentheses signature.asc Description: PGP signature
Re: [gentoo-user] Can't Get Systemd to Work
On Fri, 16 May 2014 14:58:47 -0400, Hunter Jozwiak wrote: Here are the clntents of lsblk and filesystem table, as well as the Grub settings file, https://www.dropbox.com/s/vn6we8gxpccrnpe/infoorforsystemdissue.txt Please post relevant information in your mails, this list is archived, the contents of your dropbox/pastebin/whatever are not. From your /etc/default/grub # Append parameters to the linux kernel command line # GRUB_CMDLINE_LINUX=init=/usr/lib/systemd/systemd The setting is commented out, no wonder it is being ignored. -- Neil Bothwick I have seen the truth, and it makes no sense. signature.asc Description: PGP signature
Re: [gentoo-user] How to control SLOT?
On Fri, 16 May 2014 20:25:21 +0100, Mick wrote: $ grep -ir enlightenment /etc/portage /etc/portage/package.mask/package.mask:x11-wm/enlightenment:0 Ahh! You have masked SLOT :0 to stop e16 being pulled in. I thought that this would be achievable somehow, merely by keywording SLOT :0.17, but without masking e16. You are running emerge enlightenment which defaults to slot 0. you could mask slot 0 like Alan has or you could emerge enlightenment:0.17 -- Neil Bothwick How do I set my laser printer to stun? signature.asc Description: PGP signature
Re: [gentoo-user] boot problems
Am Fri, 16 May 2014 13:06:41 +0200 schrieb Alan McKinnon alan.mckin...@gmail.com: On 16/05/2014 12:04, Canek Peláez Valdés wrote: Whatever gets rid of LVM is good on my book. I've never understood why people uses it, and in my experience it only brings headaches. Besides, I've heard from many people that btrfs is the way to go in the future. I'm not ready to make the change yet, but I will at some point. LVM is an excellent solution for what it was designed to do, which is to deal with stuff like this: Oops. I misjudged how big /var/log needed to be and now I need to add 50G to that partition. But it's sda6 and I have up to sda8. Argggh! Now I need 5 hour downtime to play 15-pieces with fdisk. LVM makes that 2 commands and 12 seconds. Yes, it's a bit complex and you have to hold the PV/VG/LV model in your head, but it also *fixes* the issue with rigid MSDOS partition style. This is precisely why I switched to RAID + LVM several years ago, instead of just RAID. No, wait, that's not correct: I remember now that I in fact started with just LVM on two differently-sized disks. But even without a RAID underneath, you can manage multiple disks (PVs) in one or more VGs and do stuff like move partitions between disks. Modern filesystems like ZFS and btrfs sidestep the need for LVM in a really elegant and wonderful way, none of which changes the fact that ZFS/btrfs weren't around when LVM was first coded. And this is one of the reasons why I switched to btrfs now :) . -- Marc Joliet -- People who think they know everything really annoy those of us who know we don't - Bjarne Stroustrup signature.asc Description: PGP signature
Re: [gentoo-user] boot problems
Am Fri, 16 May 2014 07:14:27 -0400 schrieb cov...@ccs.covici.com: [...] Also, what kernel do you need for this to function -- and last question, how to convert an lvm volume to btrfs, or do you just have to make some space somewhere and copy the files? I am not aware of being able to directly convert an LV; copying your files from a backup (or whatever) to a newly created btrfs is AFAIK your only option. You can directly convert Ext4 partitions, though (and even revert), though I have not tried this myself. As to the kernel version, the recommendation is to use the most recent stable versions of the kernel and btrfs-progs. So far, I have liked lvm, what's the advantage of btrfs over lvm? I also liked LVM while I had it, but I like btrfs even more :) . But yeah, this has already been thoroughly answered. Additionally, you can also check the thread planned btrfs conversion: questions, which I started, where others also posted their experiences with btrfs (and ZFS, too, to a smaller degree). -- Marc Joliet -- People who think they know everything really annoy those of us who know we don't - Bjarne Stroustrup signature.asc Description: PGP signature
Re: [gentoo-user] udev or Gentoo issue?
On Fri, 16 May 2014 17:07:33 +0100, Mick wrote: Samuli's right. I was experimenting on a new install how to stop net.eth0 from coming up (it was stalling forever because there was no ethernet cable present). No matter what I tried with /etc/rc.conf, or eselect rc, I couldn't stop the darn thing starting up. AFAIR you ned to install ifplugd, but not configure or run it. openrc uses it to determine if a cable is plugged in and delay setting up the interface if there is none. -- Neil Bothwick New Intel opcode #007 PUKE: Put unmeaningful keywords everywhere signature.asc Description: PGP signature
[gentoo-user] experience thus far (was: planned btrfs conversion: questions)
So, a week has passed since my conversion to btrfs. So far there seem to have been no problems, my system has been running as if nothing has changed :) . Which, as a friend pointed out, is how it should be. I don't think there is anything particularly interesting to mention in addition to what I already wrote. I can just say that I think the effort was worth it. The one thing that I can tell from reading the past two weeks of the btrfs ML is that the 3.15 Linux kernel series will contain lots of bug fixes (for example in balancing, error handling, and send/receive), and that I will want to use that sooner rather than later. Of course, the severity of the problems varies, and a lot are triggered under odd, or at least uncommon, circumstances. Still, its worth paying attention to. Also, a lot of problem reports I saw came from people using other volume management below btrfs, interestingly enough. As for the future, I think I will wait a while, and get some experience with btrfs first. I suspect that by the time btrfs supports swap files, it will be stable enough that I would consider converting my SSD to also use btrfs anyway :) . Possibly before that, once I am fully convinced of btrfs' stability, I will also convert my backup drive and switch to using snapshots and send/receive to perform backups. Perhaps somebody will have written a backup solution on top of snapshots by then. Have a nice weekend, -- Marc Joliet -- People who think they know everything really annoy those of us who know we don't - Bjarne Stroustrup signature.asc Description: PGP signature
Re: [gentoo-user] experience thus far (was: planned btrfs conversion: questions)
Am Fri, 16 May 2014 22:15:58 +0200 schrieb Marc Joliet mar...@gmx.de: [...] The one thing that I can tell from reading the past two weeks of the btrfs ML is that the 3.15 Linux kernel series will contain lots of bug fixes (for example in balancing, error handling, and send/receive), and that I will want to use that sooner rather than later. Of course, the severity of the problems varies, and a lot are triggered under odd, or at least uncommon, circumstances. Still, its worth paying attention to. [...] Sorry, obviously I didn't mean 3.15, which had its first RC in April, but 3.16 (and later, depending on when the patches get merged), though 3.15 will most likely also have lots of bug fixes. -- Marc Joliet -- People who think they know everything really annoy those of us who know we don't - Bjarne Stroustrup signature.asc Description: PGP signature
Re: [gentoo-user] experience thus far
On 17/05/14 04:15, Marc Joliet wrote: So, a week has passed since my conversion to btrfs. So far there seem to have been no problems, my system has been running as if nothing has changed :) . Which, as a friend pointed out, is how it should be. I don't think there is anything particularly interesting to mention in addition to what I already wrote. I can just say that I think the effort was worth it. The one thing that I can tell from reading the past two weeks of the btrfs ML is that the 3.15 Linux kernel series will contain lots of bug fixes (for example in balancing, error handling, and send/receive), and that I will want to use that sooner rather than later. Of course, the severity of the problems varies, and a lot are triggered under odd, or at least uncommon, circumstances. Still, its worth paying attention to. Also, a lot of problem reports I saw came from people using other volume management below btrfs, interestingly enough. As for the future, I think I will wait a while, and get some experience with btrfs first. I suspect that by the time btrfs supports swap files, it will be stable enough that I would consider converting my SSD to also use btrfs anyway :) . Possibly before that, once I am fully convinced of btrfs' stability, I will also convert my backup drive and switch to using snapshots and send/receive to perform backups. Perhaps somebody will have written a backup solution on top of snapshots by then. Have a nice weekend, Don't forget to have a maintenance program - run a scrub regularly once a week or so - I have enough btrfs drives (22 qemu files, 4 WD Greens att) to see about one or two scrub fixable errors a week with no obvious cause, sometimes serious (in a critical file). My experience is that if you ignore these errors they seem to increase over time resulting in a crash and burn. Keep an eye on your logs as btrfs will list the errors there as well (grep -i btrfs /var/log/messages). For the ones scrub cant fix, delete the file and restore from backup. Errors that require off-line fixing (btrfsck) are the ones where I have lost file systems - though I have not seen this in the last 6 months. I am quite practised in restoring from backups because of btrfs :) BillK
Re: [gentoo-user] experience thus far
Am Sat, 17 May 2014 08:08:17 +0800 schrieb William Kenworthy bi...@iinet.net.au: On 17/05/14 04:15, Marc Joliet wrote: So, a week has passed since my conversion to btrfs. So far there seem to have been no problems, my system has been running as if nothing has changed :) . Which, as a friend pointed out, is how it should be. I don't think there is anything particularly interesting to mention in addition to what I already wrote. I can just say that I think the effort was worth it. The one thing that I can tell from reading the past two weeks of the btrfs ML is that the 3.15 Linux kernel series will contain lots of bug fixes (for example in balancing, error handling, and send/receive), and that I will want to use that sooner rather than later. Of course, the severity of the problems varies, and a lot are triggered under odd, or at least uncommon, circumstances. Still, its worth paying attention to. Also, a lot of problem reports I saw came from people using other volume management below btrfs, interestingly enough. As for the future, I think I will wait a while, and get some experience with btrfs first. I suspect that by the time btrfs supports swap files, it will be stable enough that I would consider converting my SSD to also use btrfs anyway :) . Possibly before that, once I am fully convinced of btrfs' stability, I will also convert my backup drive and switch to using snapshots and send/receive to perform backups. Perhaps somebody will have written a backup solution on top of snapshots by then. Have a nice weekend, Don't forget to have a maintenance program - run a scrub regularly once a week or so - I have enough btrfs drives (22 qemu files, 4 WD Greens att) to see about one or two scrub fixable errors a week with no obvious cause, sometimes serious (in a critical file). My experience is that if you ignore these errors they seem to increase over time resulting in a crash and burn. Keep an eye on your logs as btrfs will list the errors there as well (grep -i btrfs /var/log/messages). For the ones scrub cant fix, delete the file and restore from backup. Errors that require off-line fixing (btrfsck) are the ones where I have lost file systems - though I have not seen this in the last 6 months. I did not forget about scrubbing, though so far I have run them manually (once on Monday after a weekend away from the computer, and once tonight, both without error). Nevertheless, thanks for the reminder and extra info :) . BTW: I came across an interesting tool called dstat (indirectly while looking for which package contained iostat, which was mentioned on the btrfs ML). With dstat -df, you can monitor the I/O of each individual drive. It's fun watching them be used in parallel :) . Anyway, with dstat I discovered that my drives have noticeably different throughput. Of course, I might have deduced that earlier: # btrfs scrub status -d /home scrub status for 472c9290-3ff2-4096-9c47-0612d3a52cef scrub device /dev/sda (id 1) history scrub started at Sat May 17 00:23:33 2014 and finished after 2536 seconds total bytes scrubbed: 215.42GiB with 0 errors scrub device /dev/sdb (id 2) history scrub started at Sat May 17 00:23:33 2014 and finished after 3519 seconds total bytes scrubbed: 216.32GiB with 0 errors scrub device /dev/sdc (id 3) history scrub started at Sat May 17 00:23:33 2014 and finished after 2346 seconds total bytes scrubbed: 216.57GiB with 0 errors scrub device /dev/sdd (id 4) history scrub started at Sat May 17 00:23:33 2014 and finished after 2346 seconds total bytes scrubbed: 215.68GiB with 0 errors Boy, is sdb slow! I might replace it with sde, which is laying around as a spare for now, and make sdb the spare instead. I am quite practised in restoring from backups because of btrfs :) Haha :) . -- Marc Joliet -- People who think they know everything really annoy those of us who know we don't - Bjarne Stroustrup signature.asc Description: PGP signature
Re: [gentoo-user] experience thus far
On 17/05/14 08:08, William Kenworthy wrote: On 17/05/14 04:15, Marc Joliet wrote: So, a week has passed since my conversion to btrfs. ... Have a nice weekend, Don't forget to have a maintenance program - run a scrub regularly once a week or so - I have enough btrfs drives (22 qemu files, 4 WD Greens att) to see about one or two scrub fixable errors a week with no obvious cause, sometimes serious (in a critical file). My experience is that if you ignore these errors they seem to increase over time resulting in a crash and burn. Keep an eye on your logs as btrfs will list the errors there as well (grep -i btrfs /var/log/messages). For the ones scrub cant fix, delete the file and restore from backup. Errors that require off-line fixing (btrfsck) are the ones where I have lost file systems - though I have not seen this in the last 6 months. I am quite practised in restoring from backups because of btrfs :) BillK This is from this mornings grep of the log: May 15 07:00:34 myth kernel: btrfs: checksum error at logical 1775247360 on dev /dev/vda3, sector 5580816, root 5, inode 6423718, offset 1839104, length 4096, links 1 (path: var/log/mythtv/old/mythbackend.20140421061150.6275.log-20140515) May 15 07:00:34 myth kernel: btrfs: bdev /dev/vda3 errs: wr 0, rd 0, flush 0, corrupt 1, gen 0 May 15 07:00:34 myth kernel: btrfs: unable to fixup (regular) error at logical 1775247360 on dev /dev/vda3 May 15 07:41:40 myth kernel: btrfs: bdev /dev/vda3 errs: wr 0, rd 0, flush 0, corrupt 1, gen 0 and May 16 20:40:33 moriah kernel: btrfs: bdev /dev/mapper/vg1-backups errs: wr 0, rd 250, flush 0, corrupt 13, gen 0 sigh BillK
[gentoo-user] Copying data efficiently
Hi, is there any tool in the Gentoo portage which may speed up (make it mopre efficient) the following task: On my HD there are data I want to copy to two identical external HDs. These HDs are of the same type/model and each is separately connectable via USB to my PC (...these two of the typical mobile external USB-HDs). Instead of copying the data twice from my PC to eah of the HDs I want to do it once...like I would be able to give the cp-command two instead of one target where to copy two. The result should be two identically populated external HDs, each of them useable/readable without the need to the other one. What tool of the portage tree I able to accomplish this task? Best regards, mcc
