From: "George Spelvin" <linux@horizon.com>
To: adilger@dilger.ca, linux@horizon.com
Cc: jack@suse.cz, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, viro@zeniv.linux.org.uk
Subject: Re: 3.11.4: kernel BUG at fs/buffer.c:1268
Date: 31 Oct 2013 15:43:48 -0400 [thread overview]
Message-ID: <20131031194348.29940.qmail@science.horizon.com> (raw)
In-Reply-To: <A80E174D-DCB8-41B2-84DF-38CAB9473AEE@dilger.ca>
Andreas Dilger asked:
> What kind of storage stack is underneath this filesystem? If
> it is deep (e.g. DM + LVM + iSCSI) then the stack overflow is
> definitely possible.
ext4 on md raid1 on SATA. Nothing too complicated.
Personalities : [raid0] [raid1]
md1 : active raid1 sdb2[1] sda2[0] # Root partition
41942976 blocks [2/2] [UU]
md2 : active raid1 sdb3[1] sda3[0] # /home partition
100663232 blocks [2/2] [UU]
md0 : active raid1 sdb1[1] sda1[0] # Swap partition
25165696 blocks [2/2] [UU]
unused devices: <none>
There's 8G of RAM, and a large swap partition because I download
a lot of videos to tmpfs on /tmp. (/tmp is capped at 16G, and swap
is 24G, so I shouldn't run out, but there was certainly quite
a few GB of stuff there.)
prev parent reply other threads:[~2013-10-31 19:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-09 11:55 3.11.4: kernel BUG at fs/buffer.c:1268 George Spelvin
2013-10-09 15:18 ` Jan Kara
2013-10-09 17:23 ` Al Viro
2013-10-17 21:11 ` George Spelvin
2013-10-17 21:31 ` Jan Kara
2013-10-31 9:58 ` George Spelvin
2013-10-31 14:25 ` Jan Kara
2013-10-31 16:30 ` George Spelvin
2013-10-31 20:37 ` Jan Kara
2013-10-31 20:43 ` Jan Kara
2013-11-01 0:50 ` George Spelvin
2013-11-28 5:09 ` George Spelvin
2013-11-28 15:34 ` Jan Kara
2013-12-10 9:35 ` George Spelvin
2013-12-10 15:27 ` Jan Kara
2013-12-10 16:21 ` Jan Kara
2013-12-11 0:57 ` George Spelvin
2013-10-17 22:14 ` Al Viro
2013-10-31 18:33 ` Andreas Dilger
2013-10-31 18:33 ` Andreas Dilger
2013-10-31 19:43 ` George Spelvin [this message]
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=20131031194348.29940.qmail@science.horizon.com \
--to=linux@horizon.com \
--cc=adilger@dilger.ca \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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.