Re: Incremental send/receive broken after snapshot restore

2018-06-30 Thread Andrei Borzenkov
01.07.2018 02:16, Marc MERLIN пишет: > Sorry that I missed the beginning of this discussion, but I think this is > what I documented here after hitting hte same problem: This is similar, yes. IIRC you had different starting point though. Here it should have been possible to use only standard docum

[PATCH] btrfs-progs: free-space-cache: Don't panic when free space cache is corrupted

2018-06-30 Thread Qu Wenruo
In btrfs_add_free_space(), if the free space to be added is already here, we trigger ASSERT() which is just another BUG_ON(). Let's remove such BUG_ON() at all. Reported-by: Lewis Diamond Signed-off-by: Qu Wenruo --- free-space-cache.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-)

Re: btrfs check --readonly crash

2018-06-30 Thread Qu Wenruo
On 2018年07月01日 09:59, Lewis Diamond wrote: > Hi, > I've been told to report this issue to this mailing list. > > sudo btrfs check --readonly /dev/sdc > Checking filesystem on /dev/sdc > UUID: 2630aec8-8399-4bd8-9397-8c04953a35d5 > checking extents > checking free space cache > there is no free s

btrfs check --readonly crash

2018-06-30 Thread Lewis Diamond
Hi, I've been told to report this issue to this mailing list. sudo btrfs check --readonly /dev/sdc Checking filesystem on /dev/sdc UUID: 2630aec8-8399-4bd8-9397-8c04953a35d5 checking extents checking free space cache there is no free space entry for 1596152365056-1596152381440 there is no free spa

Re: A list of bugs in btrfs found by fuzzing

2018-06-30 Thread Xu, Wen
Dear BTRFS developers, I would like to know if these issues are fixed or handled? Thanks. -Wen > On Jun 3, 2018, at 6:22 PM, Wen Xu wrote: > > Hi btrfs maintainers and developers, > > Here are a list of bugs found in upstream kernel recently. Please check: > > https://bugzilla.kernel.org/sho

Re: Incremental send/receive broken after snapshot restore

2018-06-30 Thread Marc MERLIN
Sorry that I missed the beginning of this discussion, but I think this is what I documented here after hitting hte same problem: http://marc.merlins.org/perso/btrfs/post_2018-03-09_Btrfs-Tips_-Rescuing-A-Btrfs-Send-Receive-Relationship.html Marc On Sun, Jul 01, 2018 at 01:03:37AM +0200, Hannes Sc

Re: Incremental send/receive broken after snapshot restore

2018-06-30 Thread Hannes Schweizer
On Sat, Jun 30, 2018 at 10:02 PM Andrei Borzenkov wrote: > > 30.06.2018 21:49, Andrei Borzenkov пишет: > > 30.06.2018 20:49, Hannes Schweizer пишет: > ... > >> > >> I've tested a few restore methods beforehand, and simply creating a > >> writeable clone from the restored snapshot does not work for

Re: So, does btrfs check lowmem take days? weeks?

2018-06-30 Thread Marc MERLIN
On Sat, Jun 30, 2018 at 10:49:07PM +0800, Qu Wenruo wrote: > But the last abort looks pretty possible to be the culprit. > > Would you try to dump the extent tree? > # btrfs inspect dump-tree -t extent | grep -A50 156909494272 Sure, there you go: item 25 key (156909494272 EXTENT_ITEM 55

Re: Incremental send/receive broken after snapshot restore

2018-06-30 Thread Andrei Borzenkov
30.06.2018 21:49, Andrei Borzenkov пишет: > 30.06.2018 20:49, Hannes Schweizer пишет: ... >> >> I've tested a few restore methods beforehand, and simply creating a >> writeable clone from the restored snapshot does not work for me, eg: >> # create some source snapshots >> btrfs sub create test_root

Re: Incremental send/receive broken after snapshot restore

2018-06-30 Thread Andrei Borzenkov
30.06.2018 20:49, Hannes Schweizer пишет: > On Sat, Jun 30, 2018 at 8:24 AM Andrei Borzenkov wrote: >> >> Do not reply privately to mails on list. >> >> 29.06.2018 22:10, Hannes Schweizer пишет: >>> On Fri, Jun 29, 2018 at 7:44 PM Andrei Borzenkov >>> wrote: 28.06.2018 23:09, Hannes Sc

Re: Incremental send/receive broken after snapshot restore

2018-06-30 Thread Hannes Schweizer
On Sat, Jun 30, 2018 at 8:24 AM Andrei Borzenkov wrote: > > Do not reply privately to mails on list. > > 29.06.2018 22:10, Hannes Schweizer пишет: > > On Fri, Jun 29, 2018 at 7:44 PM Andrei Borzenkov > > wrote: > >> > >> 28.06.2018 23:09, Hannes Schweizer пишет: > >>> Hi, > >>> > >>> Here's my e

Re: So, does btrfs check lowmem take days? weeks?

2018-06-30 Thread Qu Wenruo
On 2018年06月30日 10:44, Marc MERLIN wrote: > Well, there goes that. After about 18H: > ERROR: extent[156909494272, 55320576] referencer count mismatch (root: 21872, > owner: 374857, offset: 235175936) wanted: 1, have: 1452 > backref.c:466: __add_missing_keys: Assertion `ref->root_id` failed, val

Re: btrfs suddenly think's it's raid6

2018-06-30 Thread Qu Wenruo
On 2018年06月30日 06:11, marble wrote: > Hey, > Thanks for the quick reply :-) > >> Is there anything like unexpected power loss happens? > Power loss may have happened. >> And would you provide the following data for debugging? >> >> # btrfs ins dump-super -fFa /dev/mapper/black > I attached it.

[josef-btrfs:blk-iolatency-v7 14/14] mm/readahead.c:504:6: error: implicit declaration of function 'blk_cgroup_congested'

2018-06-30 Thread kbuild test robot
tree: https://git.kernel.org/pub/scm/linux/kernel/git/josef/btrfs-next.git blk-iolatency-v7 head: 4f16e9aa09862911cb7ec38061a48b91a72142c3 commit: 4f16e9aa09862911cb7ec38061a48b91a72142c3 [14/14] skip readahead if the cgroup is congested config: openrisc-or1ksim_defconfig (attached as .config

[josef-btrfs:blk-iolatency-v7 14/14] mm/readahead.c:504:6: error: implicit declaration of function 'blk_cgroup_congested'; did you mean 'bdi_rw_congested'?

2018-06-30 Thread kbuild test robot
tree: https://git.kernel.org/pub/scm/linux/kernel/git/josef/btrfs-next.git blk-iolatency-v7 head: 4f16e9aa09862911cb7ec38061a48b91a72142c3 commit: 4f16e9aa09862911cb7ec38061a48b91a72142c3 [14/14] skip readahead if the cgroup is congested config: sh-allnoconfig (attached as .config) compiler:

Re: btrfs send/receive vs rsync

2018-06-30 Thread Duncan
Marc MERLIN posted on Fri, 29 Jun 2018 09:24:20 -0700 as excerpted: >> If instead of using a single BTRFS filesystem you used LVM volumes >> (maybe with Thin provisioning and monitoring of the volume group free >> space) for each of your servers to backup with one BTRFS filesystem per >> volume yo