From: Chris Mason <chris.mason@oracle.com>
To: Peter Stuge <peter@stuge.se>
Cc: Alexey A Nikitin <moonwalker@syrius.us>,
Spelic <spelic@shiftmail.org>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: BTRFS fsck tool
Date: Thu, 10 Mar 2011 08:02:41 -0500 [thread overview]
Message-ID: <1299762048-sup-3940@think> (raw)
In-Reply-To: <20110308065255.24100.qmail@stuge.se>
Excerpts from Peter Stuge's message of 2011-03-08 01:52:55 -0500:
> Hi,
>
> Alexey A Nikitin wrote:
> > I went experimenting with btrfs RAID0 on my USB setup .. because
> > I'm a reckless experimenter when it doesn't involve production
> > systems.
>
> I encountered the same broken root node issue. (see thread resize ate
> my root node) and I'd like to understand it better. Hopefully there
> will come something out of this. I'm surprised that my resize broke
> the filesystem for mounting, when it looked good right after the
> resize.
>
> When I looked through the archive and found your thread I started
> thinking, and I am not absolutely sure if there was some disk
> activity when I cut power to my system, but I believe there was not.
> (I ran reboot, but soft poweroff doesn't work with recent kernels. At
> the Rebooting system message I switched hard power off.)
Cutting the power isn't problem unless you're using something
where cache flushes are not supported.
Which kernel were you on? Was btrfs directly accessing the disks or
were things like LVM in use?
Recent kernels (.37 and higher) have improved support for barriers in
LVM and friends, but btrfs directly using the disks should have been
safe for a long time.
I think with the resize something else went wrong.
-chris
next prev parent reply other threads:[~2011-03-10 13:02 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 [this message]
2011-03-10 13:29 ` Peter Stuge
2011-03-10 13:58 ` Chris Mason
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=1299762048-sup-3940@think \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=moonwalker@syrius.us \
--cc=peter@stuge.se \
--cc=spelic@shiftmail.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).