I suspect that somebody here knows why, but all mounts now fail... well all but
/.
Has anyone run across this before? What did I miss?
I accidentally messed up my boot mbr. and I did a rescue cd and chroot in order
to rerun grub2-mkconfig and do a grub2-install.
Now the system boots to a gr
Andrei Borzenkov writes:
> So that it the problem. Does it happen if you use cryptsetup directly?
Yes, with cryptsetup behavior is the same.
I have cryptsetup (1.6.7) and lvm2 (2.02.116).
Btw, does your system behave differently?
//wbr
//Oleksii Shevchuk
__
В Sun, 26 Jul 2015 11:39:17 +0300
Oleksii Shevchuk пишет:
> Andrei Borzenkov writes:
>
> >
> > Could you verify with e.g. inotifywatch whether inotify event was
> > generated by kernel?
> >
>
> It turns out, that for some reason I have several dm devices:
>
> # ls -l /dev/mapper/
> crw-rw
On Sun, Jul 26, 2015 at 6:50 PM, SF Markus Elfring <
elfr...@users.sourceforge.net> wrote:
> Hello,
>
> I would like to clarify the combination of commands like
> "udevadm control -p" and "udevadm trigger" a bit more.
>
Hmm, I'm not sure when `control -p` could ever be useful...
> How do device
Hello,
I would like to clarify the combination of commands like
"udevadm control -p" and "udevadm trigger" a bit more.
How do device properties differ from attributes in this
use case?
I imagine that additional properties can be set before
a corresponding addition of matching devices would
be tr
>> Jul 26 15:03:38 Sonne systemd-udevd[5347]: auid=1000 uid=0
>> gid=0 ses=1 pid=5347 comm="systemd-udevd"
>> exe="/home/elfring/Projekte/Bau/systemd/systemd-udevd" sig
>> Jul 26 15:03:38 Sonne kernel: systemd-udevd[5347]: segfault at 438 ip
>> 76fefc78 sp 7fffc6b0 error 4 in
>
On Sun, Jul 26, 2015 at 3:22 PM, SF Markus Elfring
wrote:
>> It should print the backtrace with the location where the error happened.
>
> Unfortunately, no.
>
>
> Sonne:/home/elfring/Projekte/Bau/systemd # systemctl stop
> systemd-udevd.service systemd-udevd-kernel.socket
> systemd-udevd-contro
> It should print the backtrace with the location where the error happened.
Unfortunately, no.
Sonne:/home/elfring/Projekte/Bau/systemd # systemctl stop systemd-udevd.service
systemd-udevd-kernel.socket systemd-udevd-control.socket && gdb systemd-udevd
…
worker [5347] terminated by signal 11 (S
> No, nothing needs more discussion or attention in the context of systemd.
I disagree here. - I would appreciate if return value ignorance can be still
reduced at more source code places.
Do you distinguish any update candidates which belong to a subsystem
in this software?
> None of the above
Andrei Borzenkov writes:
>
> Could you verify with e.g. inotifywatch whether inotify event was
> generated by kernel?
>
It turns out, that for some reason I have several dm devices:
# ls -l /dev/mapper/
crw-rw 1 root dialout 10, 236 ??? 25 09:52 control
brw--- 1 root root254, 12 ?
10 matches
Mail list logo
