On Sa, 04.01.20 18:58, Georg Großmann (ge...@grossmann-technologies.de) wrote:
> Has this issue been fixed on either systemd or on BTRFS side in the
> meantime? I am currently testing a BTRFS raid1 with two disk in my
> virtualbox. I have installed a bootloader on both disks. After removing
> one
04.01.2020 20:58, Georg Großmann пишет:
> Has this issue been fixed on either systemd or on BTRFS side in the
> meantime?
No. Each project says that from its side there is nothing to fix.
> I am currently testing a BTRFS raid1 with two disk in my
> virtualbox. I have installed a bootloader on bot
Has this issue been fixed on either systemd or on BTRFS side in the
meantime? I am currently testing a BTRFS raid1 with two disk in my
virtualbox. I have installed a bootloader on both disks. After removing
one of the disks I always get stuck at "timed out waiting for device
dev-disk-by\x2duuid". O
On Mon, Sep 29, 2014 at 8:29 PM, Thomas Meyer wrote:
> Hi,
>
> I get a timeout in the Fedora 21 alpha:
>
> [ TIME ] Timed out waiting for device
> dev-disk-by\x2duuid-008af19d\x2d2562\x2d49bd\x2d8907\x2d721ea08f3e14.device.
>
> But all devices are available from early kernel start:
> # ls -l /dev
Hi,
I get a timeout in the Fedora 21 alpha:
[ TIME ] Timed out waiting for device
dev-disk-by\x2duuid-008af19d\x2d2562\x2d49bd\x2d8907\x2d721ea08f3e14.device.
But all devices are available from early kernel start:
# ls -l /dev/disk/by-uuid/
total 0
lrwxrwxrwx 1 root root 11 Sep 29 20:17 008af19
On May 17, 2014, at 5:30 PM, Chris Murphy wrote:
>
> No, the system definitely does not attempt to mount it if there's a missing
> device. Systemd never executes /bin/mount at all in that case. A prerequisite
> for the mount attempt is this line:
>
> [1.621517] localhost.localdomain syste
On May 16, 2014, at 11:31 AM, Goffredo Baroncelli wrote:
> On 05/15/2014 11:54 PM, Chris Murphy wrote:
>>
>> On May 15, 2014, at 2:57 PM, Goffredo Baroncelli
>> wrote:
> []
>>
>> The udev rule right now is asking if all Btrfs member devices are
>> present and it sounds like that answer is
And this is the output when working properly;
[1.509163] localhost.localdomain systemd[1]: Expecting device
dev-disk-by\x2duuid-8c618270\x2d30ae\x2d4a18\x2da921\x2d1d99034c35a5.device...
-- Subject: Unit
dev-disk-by\x2duuid-8c618270\x2d30ae\x2d4a18\x2da921\x2d1d99034c35a5.device has
fini
Here's an example;
$ cat /etc/fstab
UUID=8c618270-30ae-4a18-a921-1d99034c35a5 / ext4
defaults1 1
UUID=c40ada21-740e-49d9-bbd1-2c2a7c10b028 /boot ext4
defaults1 2
UUID=85e74fda-7354-4384-8baf-4338e84b9ebe swapswap
On Thu, 15.05.14 15:54, Chris Murphy (li...@colorremedies.com) wrote:
> The udev rule right now is asking if all Btrfs member devices are
> present and it sounds like that answer is no with a missing device; so
> a mount isn't even attempted by systemd rather than attempting a
> degraded mount spe
On May 15, 2014, at 2:57 PM, Goffredo Baroncelli wrote:
> On 05/15/2014 08:16 PM, Lennart Poettering wrote:
>> On Thu, 15.05.14 19:29, Lennart Poettering (lenn...@poettering.net) wrote:
>>
>>> On Mon, 12.05.14 20:48, Chris Murphy (li...@colorremedies.com) wrote:
>>>
> [...]
>>
>> So, as it tu
On Thu, May 15, 2014 at 10:57 PM, Chris Murphy wrote:
> On May 15, 2014, at 12:16 PM, Lennart Poettering
> wrote:
>> On Thu, 15.05.14 19:29, Lennart Poettering (lenn...@poettering.net) wrote:
>>> On Mon, 12.05.14 20:48, Chris Murphy (li...@colorremedies.com) wrote:
>>>
Two device Btrfs volu
On Thu, May 15, 2014 at 10:57 PM, Goffredo Baroncelli
wrote:
> On 05/15/2014 08:16 PM, Lennart Poettering wrote:
>> On Thu, 15.05.14 19:29, Lennart Poettering (lenn...@poettering.net) wrote:
>>
>>> On Mon, 12.05.14 20:48, Chris Murphy (li...@colorremedies.com) wrote:
>>>
> [...]
>>
>> So, as it tu
On May 15, 2014, at 12:16 PM, Lennart Poettering wrote:
> On Thu, 15.05.14 19:29, Lennart Poettering (lenn...@poettering.net) wrote:
>
>> On Mon, 12.05.14 20:48, Chris Murphy (li...@colorremedies.com) wrote:
>>
>>> Two device Btrfs volume, with one device missing (simulated) will not
>>> boot,
On 05/15/2014 08:16 PM, Lennart Poettering wrote:
> On Thu, 15.05.14 19:29, Lennart Poettering (lenn...@poettering.net) wrote:
>
>> On Mon, 12.05.14 20:48, Chris Murphy (li...@colorremedies.com) wrote:
>>
[...]
>
> So, as it turns out there's no kernel APi available to check whether a
> btrfs rai
On Thu, 15.05.14 19:29, Lennart Poettering (lenn...@poettering.net) wrote:
> On Mon, 12.05.14 20:48, Chris Murphy (li...@colorremedies.com) wrote:
>
> > Two device Btrfs volume, with one device missing (simulated) will not
> > boot, even with rootflags=degraded set which is currently required to
On Mon, 12.05.14 20:48, Chris Murphy (li...@colorremedies.com) wrote:
> Two device Btrfs volume, with one device missing (simulated) will not
> boot, even with rootflags=degraded set which is currently required to
> enable Btrfs degraded mounts. Upon reaching a dracut shell after
> basic.target fa
On 13.05.2014 04:48, Chris Murphy wrote:
...
> The problem seems to be that systemd (udev?) is not finding the volume by
> uuid for some reason, and therefore not attempting to mount it. But I don't
> know why it can't find it, or even how the find by uuid mechanism works this
> early in boot. S
Two device Btrfs volume, with one device missing (simulated) will not boot,
even with rootflags=degraded set which is currently required to enable Btrfs
degraded mounts. Upon reaching a dracut shell after basic.target fails with
time out, I can mount -o subvol=root,degraded and exit and continue
19 matches
Mail list logo