From: Chen Gang <gang.chen@asianux.com>
To: Garrett Cooper <yanegomi@gmail.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [QUESTION] ltp stress test for RHEL5 and NFS local mount
Date: Tue, 04 Sep 2012 09:06:03 +0800 [thread overview]
Message-ID: <504553FB.3060404@asianux.com> (raw)
In-Reply-To: <CAGH67wTX0Lw_cNZduov1UnsGJLjP5GitJCe_zV64Vs2CtW9VgQ@mail.gmail.com>
于 2012年09月02日 17:28, Garrett Cooper 写道:
> On Sat, Sep 1, 2012 at 10:30 PM, gchen <gang.chen@asianux.com> wrote:
>> Hello ltp-list@lists.sourceforge.net
>>
>>
>> Question:
>>
>> Use ltp stress test (/opt/ltp/ltpstress.sh) with ltp-full-20100331.gz
>> to test RHEL5 (kernel-2.6.18-308.4.1.el5) for 72 hours.
>>
>> Not give any more configurations for NFS (using default configuration:
>> mount NFS locally, so the NFS client and NFS server are on the same
>> machine).
>>
>> My question is that "for stress test, is it suitable to let NFS server and
>> client on the same machine ?"
>>
>>
>> Background;
>>
>> This configuration will cause deadlock for RHEL5, and can not boot
>> machine in normal way.
>>
>> someone from Red Hat has said that:
>> --------------------------------------------------------------------------------------------------------------
>>
>> "Have configuration where the same host is acting as both NFS client
>> and server. That's a configuration known to cause deadlocks."
>>
>> --------------------------------------------------------------------------------------------------------------
>>
>> can reference Red Hat Bugzilla (bug 848706) for more details.
> I've done that occasionally on FreeBSD (mount over nfs into a
> chroot) before I discovered nullfs (sort of like the unionfs
> equivalent on *BSD), but I didn't stress the system. It's an
> interesting scenario, but I would say that this is more of a fringe
> case than something that one would normally do.
> If it helps you better isolate an issue that occurs in scenarios
> where the NFS client/server are separate from one another, I'd say go
> for it.
> Cheers,
> -Garrett
>
>
Thank you for your reply.
It will be better if I can get more confirmation from LTP mailing list.
I think;
If we use /opt/ltp/testscript/ltpstress.sh directly, it will use NFS
local mount for stress test.
If no additional reply within this week, I will believe the conclusion
from Red Hat:
--
Chen Gang
Asianux Corporation
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2012-09-04 1:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-02 5:30 [LTP] [QUESTION] ltp stress test for RHEL5 and NFS local mount gchen
2012-09-02 9:28 ` Garrett Cooper
2012-09-04 1:06 ` Chen Gang [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-09-02 5:51 [LTP] [QUESTION] LTP " gchen
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=504553FB.3060404@asianux.com \
--to=gang.chen@asianux.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=yanegomi@gmail.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