On 04.08.2016 18:53, Lutz Vieweg wrote:
>
> I was today hit by what I think is probably the same bug:
> A btrfs on a close-to-4TB sized block device, only half filled
> to almost exactly 2 TB, suddenly says "no space left on device"
> upon any attempt to write to it. The filesystem was NOT automa
On 08/04/2016 11:01 PM, Dave Chinner wrote:
On Thu, Aug 04, 2016 at 10:28:44AM -0400, Chris Mason wrote:
On 08/04/2016 02:41 AM, Dave Chinner wrote:
Simple test. 8GB pmem device on a 16p machine:
# mkfs.btrfs /dev/pmem1
# mount /dev/pmem1 /mnt/scratch
# dbench -t 60 -D /mnt/scratch 16
An
On Fri, Aug 5, 2016 at 6:12 PM, Chris Mason wrote:
>
> On 08/05/2016 07:08 AM, Nikolay Borisov wrote:
>> Hello,
>>
>> Any ideas how come btrfs_path can be all zero, the one in
>> the first slot comes from the increment in btrfs_next_old_item.
>
> Thanks for all the extra details. It really must b
El sábado, 6 de agosto de 2016 0:45:13 (CEST) Tomasz Chmielewski escribió:
> And, miracle cure O_o
>
> # file ./2016-08-02/serverX/syslog.log
> ERROR: cannot read `./2016-08-02/serverX/syslog.log' (Input/output
> error)
>
> # echo 3 > /proc/sys/vm/drop_caches
>
> # file 2016-08-02/serverX/syslog
On 2016-08-06 00:45, Tomasz Chmielewski wrote:
And, miracle cure O_o
# file ./2016-08-02/serverX/syslog.log
ERROR: cannot read `./2016-08-02/serverX/syslog.log' (Input/output
error)
# echo 3 > /proc/sys/vm/drop_caches
# file 2016-08-02/serverX/syslog.log
2016-08-02/serverX/syslog.log: ASCII
On 08/05/2016 11:45 AM, Tomasz Chmielewski wrote:
> On 2016-08-06 00:38, Tomasz Chmielewski wrote:
>
>>> Too big for the known problem though. Still, can you btrfs-debug-tree
>>> and just make sure it doesn't have inline items?
>>
>> Hmmm
>>
>> # btrfs-debug-tree /dev/xvdb > /root/debug.tre
On 2016-08-06 00:40, Chris Mason wrote:
Too big for the known problem though. Still, can you
btrfs-debug-tree
and just make sure it doesn't have inline items?
Hmmm
# btrfs-debug-tree /dev/xvdb > /root/debug.tree
parent transid verify failed on 355229302784 wanted 49943295 found
4994330
On 2016-08-06 00:38, Tomasz Chmielewski wrote:
Too big for the known problem though. Still, can you btrfs-debug-tree
and just make sure it doesn't have inline items?
Hmmm
# btrfs-debug-tree /dev/xvdb > /root/debug.tree
parent transid verify failed on 355229302784 wanted 49943295 found
4
On 08/05/2016 11:38 AM, Tomasz Chmielewski wrote:
On 2016-08-06 00:15, Chris Mason wrote:
# cat 2016-08-02/serverX/syslog.log
cat: 2016-08-02/serverX/syslog.log: Input/output error
How big is the file? We had one bug with inline files that might have
caused this.
This one's tiny, 158137
On 2016-08-06 00:15, Chris Mason wrote:
# cat 2016-08-02/serverX/syslog.log
cat: 2016-08-02/serverX/syslog.log: Input/output error
How big is the file? We had one bug with inline files that might
have
caused this.
This one's tiny, 158137 bytes.
Too big for the known problem though. Sti
On 08/05/2016 10:44 AM, Tomasz Chmielewski wrote:
On 2016-08-05 23:26, Chris Mason wrote:
On 08/05/2016 07:42 AM, Tomasz Chmielewski wrote:
I'm getting occasional (every few weeks) input/output errors on a btrfs
filesystem with compress-force=zlib, running on Amazon EC2, with 4.5.2
kernel:
#
On 08/05/2016 07:08 AM, Nikolay Borisov wrote:
> Hello,
>
> Recently I started getting the following crashes on some servers,
> running btrfs:
>
> [340435.480338] BTRFS info (device loop7): disk space caching is enabled
> [340435.480509] BTRFS: has skinny extents
> [340441.716174] BTRFS: checking
On 2016-08-05 23:26, Chris Mason wrote:
On 08/05/2016 07:42 AM, Tomasz Chmielewski wrote:
I'm getting occasional (every few weeks) input/output errors on a
btrfs
filesystem with compress-force=zlib, running on Amazon EC2, with 4.5.2
kernel:
# cat 2016-08-02/serverX/syslog.log
cat: 2016-08-02/s
On 08/05/2016 07:42 AM, Tomasz Chmielewski wrote:
I'm getting occasional (every few weeks) input/output errors on a btrfs
filesystem with compress-force=zlib, running on Amazon EC2, with 4.5.2
kernel:
# cat 2016-08-02/serverX/syslog.log
cat: 2016-08-02/serverX/syslog.log: Input/output error
On 08/05/2016 02:12 PM, Austin S. Hemmelgarn wrote:
> If you stick to single disk
We do, all our btrfs filesystems reside on one single block device,
redundancy is provided by a DRBD layer below.
> don't use quota groups
We don't use any quotas.
> stick to reasonably sized filesystems (not mo
On 2016-08-05 06:56, Lutz Vieweg wrote:
On 08/04/2016 10:30 PM, Chris Murphy wrote:
Keep in mind the list is rather self-selecting for problems. People
who aren't having problems are unlikely to post their non-problems to
the list.
True, but the number of people inclined to post a bug report t
I'm getting occasional (every few weeks) input/output errors on a btrfs
filesystem with compress-force=zlib, running on Amazon EC2, with 4.5.2
kernel:
# cat 2016-08-02/serverX/syslog.log
cat: 2016-08-02/serverX/syslog.log: Input/output error
Strangely, nothing gets appended in dmesg:
# dmesg
On 2016-08-04 17:12, Chris Murphy wrote:
On Thu, Aug 4, 2016 at 2:51 PM, Martin wrote:
Thanks for the benchmark tools and tips on where the issues might be.
Is Fedora 24 rawhide preferred over ArchLinux?
I'm not sure what Arch does any differently to their kernels from
kernel.org kernels. Bu
Hello,
Recently I started getting the following crashes on some servers,
running btrfs:
[340435.480338] BTRFS info (device loop7): disk space caching is enabled
[340435.480509] BTRFS: has skinny extents
[340441.716174] BTRFS: checking UUID tree
[340441.912070] BUG: unable to handle kernel NULL
On 08/04/2016 10:30 PM, Chris Murphy wrote:
Keep in mind the list is rather self-selecting for problems. People
who aren't having problems are unlikely to post their non-problems to
the list.
True, but the number of people inclined to post a bug report to
the list is also a lot smaller than the
On 08/05/16 11:24, Holger Hoffstätte wrote:
> On Wed, 03 Aug 2016 12:57:28 -0700, Liu Bo wrote:
>
>> When btree node (level = 1) has nritems which equals to zero,
>> we can end up with panic due to insert_ptr()'s
>>
>> BUG_ON(slot > nritems);
>>
>> where slot is 1 and nritems is 0, as copy_for_spl
Martin writes:
> The smallest disk of the 122 is 500GB. Is it possible to have btrfs
> see each disk as only e.g. 10GB? That way I can corrupt and resilver
> more disks over a month.
Well, at least you can easily partition the devices for that to happen.
However, I would also suggest that would
On Wed, 03 Aug 2016 12:57:28 -0700, Liu Bo wrote:
> When btree node (level = 1) has nritems which equals to zero,
> we can end up with panic due to insert_ptr()'s
>
> BUG_ON(slot > nritems);
>
> where slot is 1 and nritems is 0, as copy_for_split() calls
> insert_ptr(.., path->slots[1] + 1, ...)
On Fri, Aug 05, 2016 at 01:02:12AM -0700, Darrick J. Wong wrote:
> On Fri, Aug 05, 2016 at 03:46:07PM +0800, Eryu Guan wrote:
> > On Fri, Aug 05, 2016 at 12:21:47AM -0700, Darrick J. Wong wrote:
> > > +_count_holes $testdir/file2
> > > +echo "file1 shared extents"
> > > +$XFS_IO_PROG -c 'fiemap -v
Ensure that we can create a file with a single extent, reflink two
blocks out of the middle of that extent, and the resulting fiemap
reports two shared extents, instead of lazily reporting the entire
huge extent as shared.
v2: add _supported_fs
Signed-off-by: Darrick J. Wong
---
tests/generic/9
On Fri, Aug 05, 2016 at 03:46:07PM +0800, Eryu Guan wrote:
> On Fri, Aug 05, 2016 at 12:21:47AM -0700, Darrick J. Wong wrote:
> > Ensure that we can create a file with a single extent, reflink two
> > blocks out of the middle of that extent, and the resulting fiemap
> > reports two shared extents,
B.H.
Hello. I have a setup with 4 RAID10 arrays, 4 drives each (using md).
Device usage is as follows:
# btrfs device usage /storage/bkp1
/dev/md1, ID: 1
Device size:10.92TiB
Device slack: 0.00B
Data,single:10.19TiB
Metadata,RAID1:199.00GiB
On Fri, Aug 05, 2016 at 12:21:47AM -0700, Darrick J. Wong wrote:
> Ensure that we can create a file with a single extent, reflink two
> blocks out of the middle of that extent, and the resulting fiemap
> reports two shared extents, instead of lazily reporting the entire
> huge extent as shared.
>
Ensure that we can create a file with a single extent, reflink two
blocks out of the middle of that extent, and the resulting fiemap
reports two shared extents, instead of lazily reporting the entire
huge extent as shared.
Signed-off-by: Darrick J. Wong
---
tests/generic/929 | 89 +
29 matches
Mail list logo
