On Wed, 18 Oct 2017 08:42:32 -0400 Phil Susi wrote:
> On 10/18/2017 3:54 AM, Bernhard Schmidt wrote:
> > Accessing /home leads to a blocked process. The reason is that (for
> > numerous years, due to reasons I don't remember) I had
> > x-systemd.automount in my fstab for /home
>
> That makes sens
On 10/18/2017 3:54 AM, Bernhard Schmidt wrote:
> Accessing /home leads to a blocked process. The reason is that (for
> numerous years, due to reasons I don't remember) I had
> x-systemd.automount in my fstab for /home
That makes sense. Now I wonder why is fsck trying to open /home? You
run it on
Am 17.10.2017 um 18:10 schrieb Michael Biebl:
Hi Michael,
> Bernhard, could you try to run a git bisect to find the relevant change
> which broke fsck for you.
> https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/log/disk-utils/fsck.c?h=stable/v2.30
>
> There aren't that many changes
Bernhard, could you try to run a git bisect to find the relevant change
which broke fsck for you.
https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/log/disk-utils/fsck.c?h=stable/v2.30
There aren't that many changes for fsck.
--
Why is it that all of the instruments seeking intellig
On 10/17/2017 2:42 AM, Bernhard Schmidt wrote:
> close(3)= 0
> open("/home", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXECstrace: Process 1677
> detached
>
So it hangs in a call to open() on /home? That looks like a kernel bug.
Is /home mounted at the time, or is i
Package: util-linux
Version: 2.30.2-0.1
Severity: critical
Justification: breaks the whole system
Dear Maintainer,
after upgrading src:util-linux from 2.29.2-5+b1 to 2.30.2-0.1 my system
does not reach multiuser anymore.
My /home is btrfs on a cryptsetup luks container. The password is
queried,
6 matches
Mail list logo
