On Mon, Sep 18, 2017 at 12:23 AM, Andrei Borzenkov wrote:
> 18.09.2017 05:31, Dave пишет:
>> Sometimes when using btrfs send-receive, I get errors like this:
>>
>> ERROR: parent determination failed for
>>
>> When this happens, btrfs send-receive backups fail. And all subsequent
>> backups fail t
18.09.2017 05:31, Dave пишет:
> Sometimes when using btrfs send-receive, I get errors like this:
>
> ERROR: parent determination failed for
>
> When this happens, btrfs send-receive backups fail. And all subsequent
> backups fail too.
>
> The issue seems to stem from the fact that an automated
At Wed, 13 Sep 2017 11:53:35 -0400,
Ruoxin Jiang wrote:
>
> [1 ]
> Hello,
>
> We are researchers from Columbia University, New York. As part of our
> current research we have found some semantic discrepancies between
> btrfs and other popular filesystems.
>
> We have attached two cases. The fir
Sometimes when using btrfs send-receive, I get errors like this:
ERROR: parent determination failed for
When this happens, btrfs send-receive backups fail. And all subsequent
backups fail too.
The issue seems to stem from the fact that an automated cleanup
process removes certain earlier subvol
Tomasz Chmielewski posted on Mon, 18 Sep 2017 00:02:46 +0900 as excerpted:
> I'm trying to run balance on a 4.13.2 kernel without much luck:
>
> # time btrfs balance start -v /var/lib/lxd -dusage=5 -musage=5
> [works, but only 1 chunk balanced]
> # time btrfs balance start -v /var/lib/lxd -dusag
At Mon, 18 Sep 2017 09:47:29 +0900,
Qu Wenruo wrote:
>
> Marc reported that "btrfs check --repair" runs much faster than "btrfs
> check", which is quite weird.
>
> This patch will add time elapsed for each major tree it checked, for
> both original mode and lowmem mode, so we can have a clue what
Marc reported that "btrfs check --repair" runs much faster than "btrfs
check", which is quite weird.
This patch will add time elapsed for each major tree it checked, for
both original mode and lowmem mode, so we can have a clue what's going
wrong.
Reported-by: Marc MERLIN
Signed-off-by: Qu Wenru
At Sun, 17 Sep 2017 14:08:40 +0100,
Mike Fleetwood wrote:
>
> On 17 September 2017 at 01:36, Satoru Takeuchi
> wrote:
> > It's messy to use "" to disable compression. Introduce the new value "no"
> > which can also be used for this purpose.
>
> From an English language point of view, "none" woul
Signed-off-by: Nicholas D Steeves
---
tests/sha-private.h | 4
1 file changed, 4 insertions(+)
diff --git a/tests/sha-private.h b/tests/sha-private.h
index 6e9c4520..d94d4374 100644
--- a/tests/sha-private.h
+++ b/tests/sha-private.h
@@ -1,5 +1,9 @@
/ sha-private.h
Hi,
Thank you very much for fixing up the tests! A couple of releases ago
I noticed that they were reliably passing, but I had to exclude the
tests from my uploads because the BCP 78 license is explicitely banned
from Debian. I plan to study Debian's autopkgtest framework and then
configure the
BCP 78 applies to RFC 6234, but sha224-256.c is Simplified BSD.
This causes the following lintian error when building on Debian and
Debian derivatives:
E: btrfs-progs source: license-problem-non-free-RFC-BCP78
tests/sha224-256.c
Please consult the following email from debian-le...@lis
On 2017年09月17日 22:45, Antoine Belvire wrote:
Hello,
The behavior of 'cp --reflink' puzzles me from the quota point of view.
It looks like it's possible to easily exceeds a qgroup's max_rfer limit
like this:
~# # Create '/test' and '/test/a' subvolumes
~# btrfs subvolume create /test
~# btr
This patch introduces a persisted sysfs knob - qgroup_autoremove.
The purpose of this knob is to cause btrfs (kernel) to automatically
remove level-0 qgroups on subvolume removal. It does not try to
traverse the qgroup tree, and delete other dangling qgroups.
The knob is disabled by default to av
This patch makes it so level-0 qgroups are automatically deleted. The
flag that enables this behaviour is persisted in btrfs_qgroup_status_item.
Although, it may make sense to introduce a btrfs_qgroup_configuration_item,
it seems somewhat overkill to do that just for one simple knob that can
fit in
The function load_chunk_info() doesn't initialize correctly the
sk->min/max_type when it calls the TREE_SEARCH ioctl: these keys are swapped.
Moreover this function assumes that all the items contained in the tree
BTRFS_CHUNK_TREE_OBJECTID are of type BTRFS_CHUNK_ITEM_KEY, however some
items are of
From: Goffredo Baroncelli
The function load_chunk_info() doesn't initialize correctly the
sk->min/max_type when it calls the TREE_SEARCH ioctl: these keys are swapped.
Moreover this function assumes that all the items contained in the tree
BTRFS_CHUNK_TREE_OBJECTID are of type BTRFS_CHUNK_ITEM_KE
Hello,
The behavior of 'cp --reflink' puzzles me from the quota point of view.
It looks like it's possible to easily exceeds a qgroup's max_rfer limit
like this:
~# # Create '/test' and '/test/a' subvolumes
~# btrfs subvolume create /test
~# btrfs subvolume create /test/a
~#
~# # Set limits
~
I'm trying to run balance on a 4.13.2 kernel without much luck:
# time btrfs balance start -v /var/lib/lxd -dusage=5 -musage=5
Dumping filters: flags 0x7, state 0x0, force is off
DATA (flags 0x2): balancing, usage=5
METADATA (flags 0x2): balancing, usage=5
SYSTEM (flags 0x2): balancing, usa
On 17 September 2017 at 01:36, Satoru Takeuchi
wrote:
> It's messy to use "" to disable compression. Introduce the new value "no"
> which can also be used for this purpose.
>From an English language point of view, "none" would be better. None
says the absence of, where as no is more general nega
On 2017年09月17日 15:08, Satoru Takeuchi wrote:
At Mon, 11 Sep 2017 14:26:23 +0900,
Qu Wenruo wrote:
Marc reported that "btrfs check --repair" runs much faster than "btrfs
check", which is quite weird.
This patch will add time elapsed for each major tree it checked, for
both original mode and l
On 2017年09月17日 17:02, Sargun Dhillon wrote:
Previously, we were calling del_qgroup_item, and ignoring the return code
resulting in a potential to have divergent in-memory state without an
error. Perhaps, it makes sense to handle this error code, and put the
filesystem into a read only, or simil
Previously, we were calling del_qgroup_item, and ignoring the return code
resulting in a potential to have divergent in-memory state without an
error. Perhaps, it makes sense to handle this error code, and put the
filesystem into a read only, or similar state.
This patch only adds reporting of the
On Sat 2017-09-16 (22:56), Goffredo Baroncelli wrote:
>> how can a user get a list of his subvolumes? He may created them some
>> time ago and forget it. He now wants to have a list of them.
>
> Far to be perfect, but this could help
>
> find / -inum 256 2>/dev/null
>
> each subvolume has inod
At Fri, 15 Sep 2017 01:57:26 +0300,
Timofey Titovets wrote:
>
> Was added in:
> c8b978188c9a0fd3d535c13debd19d522b726f1f
> "Btrfs: Add zlib compression support"
> Survive to near time (from 08.10.2008).
>
> Because 'start' checked for zero before branch, so it's
> safe to remove that subtract
At Mon, 11 Sep 2017 14:26:23 +0900,
Qu Wenruo wrote:
>
> Marc reported that "btrfs check --repair" runs much faster than "btrfs
> check", which is quite weird.
>
> This patch will add time elapsed for each major tree it checked, for
> both original mode and lowmem mode, so we can have a clue what
25 matches
Mail list logo
