On Mon, 16 Mar 2020, Mantas Mikulėnas wrote:
On Mon, Mar 16, 2020 at 11:52 AM Thomas Blume wrote:
On Fri, 13 Mar 2020, Alexander E. Patrakov wrote:
> On Fri, Mar 13, 2020 at 7:07 PM Andrei Borzenkov
wrote:
>
>> And what is the "official" way to prevent various units r
On Mon, Mar 16, 2020 at 11:52 AM Thomas Blume wrote:
> On Fri, 13 Mar 2020, Alexander E. Patrakov wrote:
>
> > On Fri, Mar 13, 2020 at 7:07 PM Andrei Borzenkov
> wrote:
> >
> >> And what is the "official" way to prevent various units required by root
> >> mount from being stopped during shutdown
On Fri, 13 Mar 2020, Alexander E. Patrakov wrote:
On Fri, Mar 13, 2020 at 7:07 PM Andrei Borzenkov wrote:
And what is the "official" way to prevent various units required by root
mount from being stopped during shutdown? There could be arbitrarily
deep stack (NIC - iSCSI - multipath - raid -
On Fri, Mar 13, 2020 at 7:07 PM Andrei Borzenkov wrote:
> And what is the "official" way to prevent various units required by root
> mount from being stopped during shutdown? There could be arbitrarily
> deep stack (NIC - iSCSI - multipath - raid - lvm - crypto - ...).
https://systemd.io/ROOT_ST
13.03.2020 11:19, Mantas Mikulėnas пишет:
> On Fri, Mar 13, 2020 at 10:03 AM Thomas Blume wrote:
>
>> Hi,
>>
>> I have a SUSE SLES system where system root is provided via iscsi firmware
>> (ibft).
>> The installer automatically adds the _netdev parameter to the system root
>> mount.
>> The order
On Fri, Mar 13, 2020 at 10:03 AM Thomas Blume wrote:
> Hi,
>
> I have a SUSE SLES system where system root is provided via iscsi firmware
> (ibft).
> The installer automatically adds the _netdev parameter to the system root
> mount.
> The ordering when applying the _netdev parameter is documented
Hi,
I have a SUSE SLES system where system root is provided via iscsi firmware
(ibft).
The installer automatically adds the _netdev parameter to the system root
mount.
The ordering when applying the _netdev parameter is documented as:
-->
Network mount units are ordered between remote-fs-pre.ta
