From: ajh mls <ajhmls@gmail.com>
To: dave@jikos.cz
Cc: chris.mason@oracle.com, linux-btrfs@vger.kernel.org
Subject: Re: btrfs hang on brd
Date: Wed, 01 Jun 2011 13:30:30 +0300 [thread overview]
Message-ID: <4DE614C6.4080909@gmail.com> (raw)
In-Reply-To: <4DE60F44.6090400@linux.intel.com>
On 01/06/11 13:07, Adrian Hunter wrote:
> On 01/06/11 11:54, David Sterba wrote:
>> On Tue, May 31, 2011 at 10:03:12AM +0300, Adrian Hunter wrote:
>>> Hi
>>>
>>> I seem to be able to get btrfs reproducibly to
>>> produce warnings and finally hang when running
>>> a stress test on a ramdisk.
>>>
>>> Testing was done using the "integration-test"
>>> branch of btrfs-unstable. Note that I also tested
>>> v2.6.39 and "integration-test" took much longer to
>>> hang i.e. it is an improvement
>>>
>>> The test script and stack dumps are below.
>>>
>>> Is this a valid test?
>>>
>>> Is it worth me investigating these?
>>
>> I've tried to reproduce myself, but the fsstress utility (taken from
>> latest LTP suite) crashes sometimes and I cannot take it as a proper
>> reproduction. Can you point me to the exact version you used?
>
> The LTP version does not compile properly:
>
> make[4]: Entering directory
> `/home/ahunter/Desktop/Projects/ltp/ltp-full-20110228/testcases/kernel/fs/fsstress'
>
> gcc -g -O2 -g -O2 -fno-strict-aliasing -pipe -Wall -DNO_XFS
> -I/home/ahunter/Desktop/Projects/ltp/ltp-full-20110228/testcases/kernel/fs/fsstress
> -D_LARGEFILE64_SOURCE -D_GNU_SOURCE -Wno-error -I../../../../include
> -I../../../../include -L../../../../lib fsstress.c -o fsstress
> fsstress.c: In function 'dread_f':
> fsstress.c:1829:2: warning: implicit declaration of function 'memalign'
> fsstress.c:1829:6: warning: assignment makes pointer from integer
> without a cast
> fsstress.c: In function 'dwrite_f':
> fsstress.c:1912:6: warning: assignment makes pointer from integer
> without a cast
> fsstress.c:1844:17: warning: 'diob.d_miniosz' may be used uninitialized
> in this function
> fsstress.c:1844:17: warning: 'diob.d_maxiosz' may be used uninitialized
> in this function
> fsstress.c:1844:17: warning: 'diob.d_mem' may be used uninitialized in
> this function
> fsstress.c: In function 'dread_f':
> fsstress.c:1750:17: warning: 'diob.d_miniosz' may be used uninitialized
> in this function
> fsstress.c:1750:17: warning: 'diob.d_maxiosz' may be used uninitialized
> in this function
> fsstress.c:1750:17: warning: 'diob.d_mem' may be used uninitialized in
> this function
>
>
> I hacked a couple of changes but I need to check them before
> mailing to the ltp-list:
>
In fact there is already a fix here:
http://sourceforge.net/mailarchive/message.php?msg_id=27212868
next prev parent reply other threads:[~2011-06-01 10:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-31 7:03 btrfs hang on brd Adrian Hunter
2011-06-01 8:54 ` David Sterba
2011-06-01 10:07 ` Adrian Hunter
2011-06-01 10:30 ` ajh mls [this message]
2011-06-03 9:41 ` Adrian Hunter
2011-06-07 5:35 ` Adrian Hunter
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=4DE614C6.4080909@gmail.com \
--to=ajhmls@gmail.com \
--cc=chris.mason@oracle.com \
--cc=dave@jikos.cz \
--cc=linux-btrfs@vger.kernel.org \
/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).