From: Alexey A Nikitin <moonwalker@syrius.us>
To: Chris Mason <chris.mason@oracle.com>
Cc: Peter Stuge <peter@stuge.se>, Spelic <spelic@shiftmail.org>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: BTRFS fsck tool
Date: Thu, 10 Mar 2011 11:30:54 -0600 [thread overview]
Message-ID: <AANLkTimK8LD50ga=uJuJYJ84Y37KoZPRieGmDHt6HncG@mail.gmail.com> (raw)
In-Reply-To: <1299762048-sup-3940@think>
2011/3/10 Chris Mason <chris.mason@oracle.com>
>
> Which kernel were you on? =C2=A0Was btrfs directly accessing the disk=
s 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.
Now that's funny. I'm using 2.6.32-5-amd64 from Debian Wheezy and
while btrfs on top of LVM works perfectly stable I have now trouble
with FS that is directly on partition. Does it make difference
stability-wise if partition table on disk is GPT rather than
old-school MS-DOS? Because all my disks, LVM and non-LVM, are set with
GPT.
Best,
Alexey
--
This message was created with 100% recycled electrons
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-03-10 17:30 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
2011-03-10 17:30 ` Alexey A Nikitin [this message]
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='AANLkTimK8LD50ga=uJuJYJ84Y37KoZPRieGmDHt6HncG@mail.gmail.com' \
--to=moonwalker@syrius.us \
--cc=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--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).