> Changing O_DIRECT in flight has always been a deep dark corner case, and
> crc errors are the expected result. Have you found anyone doing this in
> real life?
Agreed; and no, I haven't heard of people accidentally modifying stable
pages.
> I do like the small test program though, we should ex
Quoting Zach Brown (2013-05-30 18:36:10)
> 'stable' pages have always been a bit of a fiction. It's easy to
> intentionally modify stable pages under io with some help from page
> references that ignore mappings and page state.
>
> Here's little test that uses O_DIRECT to get the pinned aio ring
'stable' pages have always been a bit of a fiction. It's easy to
intentionally modify stable pages under io with some help from page
references that ignore mappings and page state.
Here's little test that uses O_DIRECT to get the pinned aio ring pages
under IO and then has event completion stores
Dave reported a panic because the extent_root->commit_root was NULL in the
caching kthread. That is because we just unset it in free_root_pointers, which
is not the correct thing to do, we have to either wait for the caching kthread
to complete or hold the extent_commit_sem lock so we know the thr
On 05/30/2013 13:17, Papp Tamas wrote:
hi All,
I'm new on the list.
System:
Distributor ID:Ubuntu
Description:Ubuntu 13.04
Release:13.04
Codename:raring
Linux ctu 3.8.0-19-generic #30-Ubuntu SMP Wed May 1 16:35:23 UTC 2013
x86_64 x86_64 x86_64 GNU/Linux
The symptom is the same
Hi Josef,
> You are running on an unmounted fs right? Also please make sure you are
> running
> the git version
Yes, the fs was properly unmounted.
> git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-progs.git
I still get those errors, I'll try to file a bug-report with the
tools/data
On Thu, May 30, 2013 at 12:06:50PM -0600, Clemens Eisserer wrote:
> Hi again,
>
> I am able to induce the btrfsck errors I experienced using a synthetic
> workload on a fresh filesystem with linux-3.10.0.rc2.
> However as filing the bug-report would take quite some time (uploading
> 512mb trace-fi
Oh, I see... Well at least now I know. Thanks!
I'll probably go for the "safer" route of using 3.10... Though I'd like to know
how stable the current RC is wrt btrfs, if instead I should wait for the
release.
~Alex
On May 30, 2013, at 8:52 AM, Josef Bacik wrote:
> On Wed, May 29, 2013 at 08:
Hi again,
I am able to induce the btrfsck errors I experienced using a synthetic
workload on a fresh filesystem with linux-3.10.0.rc2.
However as filing the bug-report would take quite some time (uploading
512mb trace-files, writing a short read-me, ...) I wonder whether this
is an issue woth of r
On Wed, May 29, 2013 Miao Xie wrote:
On wed, 29 May 2013 10:55:11 +0900, Liu Bo wrote:
On Tue, May 28, 2013 at 09:22:11AM -0500, Kyle Gates wrote:
From: Liu Bo
Subject: [PATCH] Btrfs: fix broken nocow after a normal balance
[...]
Sorry for the long wait in replying.
This patch was unsucces
On Tue, May 28, 2013, Liu Bo wrote:
On Tue, May 28, 2013 at 09:22:11AM -0500, Kyle Gates wrote:
>From: Liu Bo
>
>Subject: [PATCH] Btrfs: fix broken nocow after a normal balance
>
[...]
Sorry for the long wait in replying.
This patch was unsuccessful in fixing the problem (on my 3.8 Ubuntu
Rari
Quoting Stefan Behrens (2013-05-30 10:59:59)
> On Thu, 30 May 2013 10:03:29 -0400, Chris Mason wrote:
> > Quoting Stefan Behrens (2013-05-30 08:55:58)
> >> Papp is using an Intel X18-M/X25-M/X25-V G2 SSD. At least with an Intel
> >> X25 SSD that identifies itself with "INTEL SSDSA2M080" and on one
On Thu, 30 May 2013 10:03:29 -0400, Chris Mason wrote:
> Quoting Stefan Behrens (2013-05-30 08:55:58)
>> Papp is using an Intel X18-M/X25-M/X25-V G2 SSD. At least with an Intel
>> X25 SSD that identifies itself with "INTEL SSDSA2M080" and on one with
>> the ID "INTEL SSDSA2M040", I've tested whethe
Quoting Stefan Behrens (2013-05-30 08:55:58)
> On Thu, 30 May 2013 08:32:35 -0400, Josef Bacik wrote:
> > On Thu, May 30, 2013 at 05:17:06AM -0600, Papp Tamas wrote:
> >> hi All,
> >>
> >> I'm new on the list.
> >>
> >> System:
> >> Distributor ID: Ubuntu
> >> Description: Ubuntu 13.04
> >> Re
On Thu, 30 May 2013 08:32:35 -0400, Josef Bacik wrote:
> On Thu, May 30, 2013 at 05:17:06AM -0600, Papp Tamas wrote:
>> hi All,
>>
>> I'm new on the list.
>>
>> System:
>> Distributor ID: Ubuntu
>> Description: Ubuntu 13.04
>> Release: 13.04
>> Codename:raring
>>
>> Linux ctu 3.8.0-19-
On Wed, May 29, 2013 at 08:55:31PM -0600, Alex Marquez wrote:
> I'm not entirely sure what went completely wrong. Three possibilities are
> most likely, and they're listed below.
> For reference, here are supplemental materials split out into their own
> pastebins:
> * btrfs-debug-tree -R log ht
On Thu, May 30, 2013 at 05:17:06AM -0600, Papp Tamas wrote:
> hi All,
>
> I'm new on the list.
>
> System:
> Distributor ID: Ubuntu
> Description: Ubuntu 13.04
> Release: 13.04
> Codename: raring
>
> Linux ctu 3.8.0-19-generic #30-Ubuntu SMP Wed May 1 16:35:23 UTC 2013 x86_64
>
hi All,
I'm new on the list.
System:
Distributor ID: Ubuntu
Description:Ubuntu 13.04
Release:13.04
Codename: raring
Linux ctu 3.8.0-19-generic #30-Ubuntu SMP Wed May 1 16:35:23 UTC 2013 x86_64
x86_64 x86_64 GNU/Linux
The symptom is the same with Saucy 3.9 kernel.
ii btrfs-
18 matches
Mail list logo
