From: Marc MERLIN <marc@merlins.org>
To: Russell Coker <russell@coker.com.au>, 1i5t5.duncan@cox.net
Cc: linux-btrfs@vger.kernel.org
Subject: Re: NMI from btrfs cron jobs in 3.11.6
Date: Sun, 17 Nov 2013 07:16:18 -0800 [thread overview]
Message-ID: <20131117151618.GG9725@merlins.org> (raw)
In-Reply-To: <201311180143.51552.russell@coker.com.au>
On Mon, Nov 18, 2013 at 01:43:51AM +1100, Russell Coker wrote:
> On Thu, 14 Nov 2013, Duncan <1i5t5.duncan@cox.net> wrote:
> > > It appears that running two scripts that create snapshots at the same
> > > time as a script that removes maybe 97 snapshots causes an NMI.
> >
> > This is a known bug in 3.11 (and presumably earlier). Snapshot
> > manipulation concurrency evidently wasn't originally well considered, and
Not super important, but the bug does go farther back in time, I
reported it here too some time back (although didn't hear anything back
at the time).
But for me I had
/var/local/scr/btrfs_snaps: line 23: 26017 Segmentation fault (core dumped) /sbin/btrfs subvolume
delete "$sub"
with details on the BT pasted in the mail:
http://permalink.gmane.org/gmane.comp.file-systems.btrfs/28770
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/ | PGP 1024R/763BE901
next prev parent reply other threads:[~2013-11-17 15:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 14:45 NMI from btrfs cron jobs in 3.11.6 Russell Coker
2013-11-13 15:15 ` Duncan
2013-11-17 14:43 ` Russell Coker
2013-11-17 15:16 ` Marc MERLIN [this message]
2013-11-28 17:10 ` David Sterba
2013-11-28 17:37 ` David Sterba
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=20131117151618.GG9725@merlins.org \
--to=marc@merlins.org \
--cc=1i5t5.duncan@cox.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=russell@coker.com.au \
/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.