From: John Lightsey <john@nixnuts.net>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] Bug#841144: kernel BUG at /build/linux-Wgpe2M/linux-4.8.11/fs/ocfs2/alloc.c:1514!
Date: Tue, 21 Nov 2017 15:05:01 -0600 [thread overview]
Message-ID: <1511298301.2735.1.camel@nixnuts.net> (raw)
In-Reply-To: <63ADC13FD55D6546B7DECE290D39E373CED7CDDB@H3CMLB14-EX.srv.huawei-3com.com>
On Tue, 2017-11-21 at 05:58 +0000, Changwei Ge wrote:
> Can your tell me how did you format your volume?
> What's your _cluster size_ and _block size_?
> Your can obtain such information via debugfs.ocfs2 <your volume> -R?
> 'stats' | grep 'Cluster Size'
>
> It's better for you provide a way to reproduce this issue so that we
> can?
> perform some test.
>
The issue recurred in our cluster today, so at best my patch is just
decreasing the frequency of the crashes.
Our setup has 10 machines sharing two OCFS2 mountpoints over fibre
channel.
Both OCFS2 partitions have block size bits set to 12 and cluster size
bits set to 20.
The two partitions contain around 310 files total with 200 of those
being qcow2 files. The only inodes getting any read and write activity
are the qcow2 files.
The qcow2 files were created as sparse files (preallocation=metadata)
and some are reflinked copies.
It's not clear to me exactly why it's passing through
ocfs2_lock_allocators() without allocating meta_ac. These qcow files
wouldn't be written concurrently by different systems in the OCFS2
cluster.
Is it possible the 2 x multiplier in the ocfs2_lock_allocators call is
not large enough?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
Url : http://oss.oracle.com/pipermail/ocfs2-devel/attachments/20171121/29b65745/attachment.bin
next prev parent reply other threads:[~2017-11-21 21:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-20 18:54 [Ocfs2-devel] [PATCH] Bug#841144: kernel BUG at /build/linux-Wgpe2M/linux-4.8.11/fs/ocfs2/alloc.c:1514! John Lightsey
2017-11-21 0:58 ` Changwei Ge
2017-11-21 2:45 ` John Lightsey
2017-11-21 5:58 ` Changwei Ge
2017-11-21 21:05 ` John Lightsey [this message]
2017-11-24 5:46 ` alex chen
2017-11-24 7:03 ` Changwei Ge
2017-11-24 10:06 ` alex chen
2017-11-28 14:34 ` John Lightsey
2017-11-29 4:37 ` alex chen
2017-11-21 3:04 ` piaojun
2017-11-21 4:24 ` John Lightsey
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=1511298301.2735.1.camel@nixnuts.net \
--to=john@nixnuts.net \
--cc=ocfs2-devel@oss.oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.