linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guoqing Jiang <guoqing.jiang@linux.dev>
To: Heming Zhao <heming.zhao@suse.com>,
	Mikulas Patocka <mpatocka@redhat.com>, Song Liu <song@kernel.org>
Cc: Zdenek Kabelac <zkabelac@redhat.com>,
	linux-raid@vger.kernel.org, dm-devel@redhat.com
Subject: Re: A crash caused by the commit 0dd84b319352bb8ba64752d4e45396d8b13e6018
Date: Fri, 4 Nov 2022 09:23:40 +0800	[thread overview]
Message-ID: <c31fdd20-c736-5d65-e82e-338e7ed1571c@linux.dev> (raw)
In-Reply-To: <11a466f0-ecfe-c1e2-d967-2d648ce65bcb@suse.com>



On 11/3/22 10:46 PM, Heming Zhao wrote:
> On 11/3/22 11:47 AM, Guoqing Jiang wrote:
>> Hi,
>>
>> On 11/3/22 12:27 AM, Mikulas Patocka wrote:
>>> Hi
>>>
>>> There's a crash in the test shell/lvchange-rebuild-raid.sh when running
>>> the lvm testsuite. It can be reproduced by running "make check_local
>>> T=shell/lvchange-rebuild-raid.sh" in a loop.
>>
>> I have problem to run the cmd (not sure what I missed), it would be 
>> better if
>> the relevant cmds are extracted from the script then I can reproduce 
>> it with
>> those cmds directly.
>>
>> [root@localhost lvm2]# git log | head -1
>> commit 36a923926c2c27c1a8a5ac262387d2a4d3e620f8
>> [root@localhost lvm2]# make check_local T=shell/lvchange-rebuild-raid.sh
>> make -C libdm device-mapper
>> [...]
>> make -C daemons
>> make[1]: Nothing to be done for 'all'.
>> make -C test check_local
>> VERBOSE=0 ./lib/runner \
>>          --testdir . --outdir results \
>>          --flavours ndev-vanilla --only 
>> shell/lvchange-rebuild-raid.sh --skip @
>> running 1 tests
>> ###      running: [ndev-vanilla] shell/lvchange-rebuild-raid.sh 0
>> | [ 0:00] lib/inittest: line 133: 
>> /tmp/LVMTEST317948.iCoLwmDhZW/dev/testnull: Permission denied
>> | [ 0:00] Filesystem does support devices in 
>> /tmp/LVMTEST317948.iCoLwmDhZW/dev (mounted with nodev?)
>
> I didn't read other mails in this thread, only for above issue.
> If you use opensuse, systemd service tmp.mount uses nodev option to 
> mount tmpfs on /tmp.
> From my experience, there are two methods to fix(work around):
> 1. systemctl disable tmp.mount && systemctl mask tmp.mount && reboot
> 2. mv /usr/lib/systemd/system/tmp.mount /root/ && reboot

I am using centos similar system, I can try leap later. Appreciate for 
the tips, Heming.

Thanks,
Guoqing

  reply	other threads:[~2022-11-04  1:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-02 16:27 A crash caused by the commit 0dd84b319352bb8ba64752d4e45396d8b13e6018 Mikulas Patocka
2022-11-03  3:47 ` Guoqing Jiang
2022-11-03  7:28   ` Guoqing Jiang
2022-11-03 13:00   ` Mikulas Patocka
2022-11-03 15:20     ` Mikulas Patocka
2022-11-04  2:41       ` Guoqing Jiang
2022-11-04 13:40         ` Mikulas Patocka
2022-11-07  9:32           ` Guoqing Jiang
2022-11-03 14:46   ` Heming Zhao
2022-11-04  1:23     ` Guoqing Jiang [this message]
2022-11-04 11:10       ` Zdenek Kabelac
2022-11-04 15:18         ` [dm-devel] " Xiao Ni
2022-11-07  1:52         ` Guoqing Jiang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c31fdd20-c736-5d65-e82e-338e7ed1571c@linux.dev \
    --to=guoqing.jiang@linux.dev \
    --cc=dm-devel@redhat.com \
    --cc=heming.zhao@suse.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=mpatocka@redhat.com \
    --cc=song@kernel.org \
    --cc=zkabelac@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).