From: Chris Mason <chris.mason@oracle.com>
To: Peter Stuge <peter@stuge.se>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: BTRFS fsck tool
Date: Thu, 10 Mar 2011 08:58:44 -0500 [thread overview]
Message-ID: <1299765503-sup-219@think> (raw)
In-Reply-To: <20110310132937.11456.qmail@stuge.se>
Excerpts from Peter Stuge's message of 2011-03-10 08:29:37 -0500:
> Chris Mason wrote:
> > Cutting the power isn't problem unless you're using something
> > where cache flushes are not supported.
>
> Nod. I've had very abrupt system outage before, without problems.
>
> > Which kernel were you on?
>
> 2.6.38-rc6 + wireless-testing.git
>
> > Was btrfs directly accessing the disks or were things like LVM in use?
>
> Directly.
>
> > I think with the resize something else went wrong.
>
> I don't know where to look exactly. Any hint on which data structures
> to focus on are welcome.
I moved my questions back to the resize thread ;)
-chris
next prev parent reply other threads:[~2011-03-10 13:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-04 23:59 BTRFS fsck tool Alexey A Nikitin
2011-03-05 0:05 ` cwillu
2011-03-05 1:20 ` Alexey A Nikitin
2011-03-05 3:00 ` cwillu
2011-03-05 3:27 ` Alexey A Nikitin
2011-03-05 7:12 ` Helmut Hullen
2011-03-05 10:55 ` Alexey A Nikitin
2011-03-08 2:17 ` Spelic
2011-03-08 4:52 ` Alexey A Nikitin
2011-03-08 6:52 ` Peter Stuge
2011-03-10 12:21 ` Clemens Eisserer
2011-03-10 13:02 ` Chris Mason
2011-03-10 13:29 ` Peter Stuge
2011-03-10 13:58 ` Chris Mason [this message]
2011-03-10 17:30 ` Alexey A Nikitin
2011-03-10 17:41 ` Chris Mason
2011-03-12 22:49 ` Spelic
2011-03-12 23:53 ` Ric Wheeler
2011-03-15 14:18 ` Hubert Kario
2011-03-15 14:22 ` Peter Stuge
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=1299765503-sup-219@think \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=peter@stuge.se \
/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).