On Mo, 2021-07-26 at 11:28 -0500, Benjamin Marzinski wrote:
> On Mon, Jul 26, 2021 at 08:22:49PM +0800, lixiaokeng wrote:
> >
> > > > After sdb mounted to /var, we can start multipathd service
> > > > successfully.
> > >
> > > But when the binaries were compiled, if /var/run existed and was
> > >
On 2021/8/12 19:09, Martin Wilck wrote:
> On Mo, 2021-07-26 at 11:28 -0500, Benjamin Marzinski wrote:
>> On Mon, Jul 26, 2021 at 08:22:49PM +0800, lixiaokeng wrote:
>>>
> After sdb mounted to /var, we can start multipathd service
> successfully.
But when the binaries were compi
On Mon, Jul 26, 2021 at 08:22:49PM +0800, lixiaokeng wrote:
>
> >> After sdb mounted to /var, we can start multipathd service successfully.
> >
> > But when the binaries were compiled, if /var/run existed and was a
> > symlink in your build environment, then RUN should equal "run", and
> > multip
>> After sdb mounted to /var, we can start multipathd service successfully.
>
> But when the binaries were compiled, if /var/run existed and was a
> symlink in your build environment, then RUN should equal "run", and
> multipath should should be using /run instead of /var/run, right?
>
> This i
On Fri, Jul 23, 2021 at 02:27:58PM +0800, lixiaokeng wrote:
>
>
> On 2021/7/23 5:42, Benjamin Marzinski wrote:
> > On Thu, Jul 22, 2021 at 10:51:22AM +0800, lixiaokeng wrote:
> >> When we enable multipathd.service with systemctl and reboot,
> >> multipathd doesn't start and log "failed to create
On 2021/7/23 5:42, Benjamin Marzinski wrote:
> On Thu, Jul 22, 2021 at 10:51:22AM +0800, lixiaokeng wrote:
>> When we enable multipathd.service with systemctl and reboot,
>> multipathd doesn't start and log "failed to create pidfile".
>>
>> The reason is following:
>>
>> The RUN is /var/run in m
On Thu, Jul 22, 2021 at 10:51:22AM +0800, lixiaokeng wrote:
> When we enable multipathd.service with systemctl and reboot,
> multipathd doesn't start and log "failed to create pidfile".
>
> The reason is following:
>
> The RUN is /var/run in multipath-tools. When we start linux, we
> mount a disk
When we enable multipathd.service with systemctl and reboot,
multipathd doesn't start and log "failed to create pidfile".
The reason is following:
The RUN is /var/run in multipath-tools. When we start linux, we
mount a disk to /var. So if multipathd.service start before mount,
it will fail to act