On Wed, 2011-06-22 at 12:09 -0400, Josef Bacik wrote:
On 06/10/2011 05:52 PM, Marek Otahal wrote:
On Friday 10 of June 2011 16:52:36 Josef Bacik wrote:
On 06/10/2011 02:43 PM, Marek Otahal wrote:
On Friday 10 of June 2011 15:33:20 Josef Bacik wrote:
On 06/09/2011 10:06 PM, Daniel J
Hi Chris,
On 19.07.2011 19:30, Chris Mason wrote:
Hi everyone,
I've pushed out a new integration-test branch, and it includes a new
reader/writer locking scheme for the btree locks.
I rebased my for-chris branch containing the readahead patches for scrub
to your integration-test branch.
Excerpts from Tsutomu Itoh's message of 2011-07-19 22:08:38 -0400:
(2011/07/20 2:30), Chris Mason wrote:
Hi everyone,
I've pushed out a new integration-test branch, and it includes a new
reader/writer locking scheme for the btree locks.
We've seen a number of benchmarks dominated by
Excerpts from Li Zefan's message of 2011-07-19 21:26:43 -0400:
01:32, Chris Mason wrote:
I haven't yet tested this on x86-32, if someone is willing to try this
on non-critical test machines I'd appreciate it.
Great work!
I pulled the integration-test branch, and I got this when
(2011/07/20 16:58), Chris Mason wrote:
Excerpts from Tsutomu Itoh's message of 2011-07-19 22:08:38 -0400:
(2011/07/20 2:30), Chris Mason wrote:
Hi everyone,
I've pushed out a new integration-test branch, and it includes a new
reader/writer locking scheme for the btree locks.
We've seen a
Excerpts from David Woodhouse's message of 2011-07-20 02:05:02 -0400:
On Wed, 2011-06-22 at 12:09 -0400, Josef Bacik wrote:
Hello,
the issue happens every time when i have to hard power-off my
notebook
(suspend problems).
With kernel 2.6.39 the partition is unmountable,
ping?
On 07/04/2011 04:07 PM, WuBo wrote:
I've been diging into the idea of chunk tree backups. Here is the
design, before finishing chunk alloc, the first block in this
chunk will be written in some information, these information will be
useful for chunk tree rebuilding if crash, also the
Hi Chris,
When my Sheevaplug's btrfs partition gets near-full (df will report 1.8
or 1.9 gigs free), the filesystem hangs. I get messages as seen below,
and I can no longer read or write.
This occurs with Debian's linux-image-2.6.39-2-kirkwood and
3.0.0~rc5-1~experimental.1 as well. It is
On Wed, 2011-07-20 at 04:44 -0400, Chris Mason wrote:
Oh, the dirty little secret of loop devices is they don't actually write
things to disk properly. They are not power off safe. But you can
trigger this without a loop device, correct?
Yes. I would have liked to reproduce it last night
Excerpts from Andi Kleen's message of 2011-07-02 13:04:43 -0400:
The two big features of btrfs are self-healing and online fsck, those have
to
Are they?
be implemented in kernel space.
Why? There have been online fscks in user space in the past,
e.g. the various schemes using LVM
read_extent_buffer_pages currently has two modes, either trigger a read
without waiting for anything, or wait for the I/O to finish. The former
also bails when it's unable to lock the page. This patch now adds an
additional parameter to allow it to block on page lock, but don't wait
for
On 20.07.2011 08:55, Arne Jansen wrote:
Hi Chris,
On 19.07.2011 19:30, Chris Mason wrote:
Hi everyone,
I've pushed out a new integration-test branch, and it includes a new
reader/writer locking scheme for the btree locks.
I rebased my for-chris branch containing the readahead patches for
Excerpts from Chris Mason's message of 2011-07-19 13:30:22 -0400:
Hi everyone,
I've pushed out a new integration-test branch, and it includes a new
reader/writer locking scheme for the btree locks.
We've seen a number of benchmarks dominated by contention on the root
node lock. This
Excerpts from Chris Mason's message of 2011-07-20 13:21:47 -0400:
Excerpts from Chris Mason's message of 2011-07-19 13:30:22 -0400:
Hi everyone,
I've pushed out a new integration-test branch, and it includes a new
reader/writer locking scheme for the btree locks.
We've seen a number
On Mon, Jul 18, 2011 at 11:47 PM, Josef Bacik jo...@redhat.com wrote:
On 06/06/2011 06:58 PM, Nirbheek Chauhan wrote:
What can I do to debug this issue? What other information should I
supply? Could someone guide me on how to figure out why my machine is
unusable now?
I've been looking into
(2011/07/21 2:21), Chris Mason wrote:
Excerpts from Chris Mason's message of 2011-07-19 13:30:22 -0400:
Hi everyone,
I've pushed out a new integration-test branch, and it includes a new
reader/writer locking scheme for the btree locks.
We've seen a number of benchmarks dominated by
Chris Mason wrote:
Excerpts from Chris Mason's message of 2011-07-20 13:21:47 -0400:
Excerpts from Chris Mason's message of 2011-07-19 13:30:22 -0400:
Hi everyone,
I've pushed out a new integration-test branch, and it includes a new
reader/writer locking scheme for the btree locks.
We've
On 20.07.2011 19:21, Chris Mason wrote:
Excerpts from Chris Mason's message of 2011-07-19 13:30:22 -0400:
Hi everyone,
I've pushed out a new integration-test branch, and it includes a new
reader/writer locking scheme for the btree locks.
We've seen a number of benchmarks dominated by
On 21.07.2011 02:48, Tsutomu Itoh wrote:
(2011/07/21 2:21), Chris Mason wrote:
Excerpts from Chris Mason's message of 2011-07-19 13:30:22 -0400:
Hi everyone,
I've pushed out a new integration-test branch, and it includes a new
reader/writer locking scheme for the btree locks.
We've seen a
19 matches
Mail list logo
