Re: invalid files names, btrfs check can't repair it

On 2018-01-16 19:20:56 [+0800], Qu Wenruo wrote: > This is a very minor problem. > > btrfs check --repair should handle it without problem. awesome, thank you! After the --repair completed, the following didn't report the error anymore. And now I was able to remove the two files. Thank you. >

Re: invalid files names, btrfs check can't repair it

On 2018-01-16 18:22:14 [+0800], Qu Wenruo wrote: > Btrfs check is always recommended before really mount it. # btrfs check -p /dev/sdb4 Checking filesystem on /dev/sdb4 UUID: b3bfb56e-d445-4335-93f0-c1fb2d1f6df1 checking extents [O] cache and super generation don't match, space cache will

Re: invalid files names, btrfs check can't repair it

On 2018-01-16 13:19:50 [+0800], Qu Wenruo wrote: > Usage: > ./btrfs-corrupt-block -X # ./btrfs-corrupt-block -X /dev/sdb4 Fix is done successfully may I mount it now or should I run btrfs check or something first? > Thanks, > Qu Sebastian -- To unsubscribe from this list: send the line

Re: invalid files names, btrfs check can't repair it

On 16 January 2018 05:51:23 CET, Qu Wenruo wrote: >Since there is no other hit, I assume it's root subvolume (5), but I >still need the extra confirm since the fix will be hard-coded. Yes, 5 is correct. > >Thanks, >Qu Sebastian -- To unsubscribe from this list: send

Re: invalid files names, btrfs check can't repair it

On 2018-01-15 12:23:05 [+0800], Qu Wenruo wrote: > Right, I'll fix it soon. > > And BTW what makes the the output different from the original one? > > Sebastaian, did you do extra write or other operation to the fs after > previous btrfs check? Well the filesystem is in use but there should be

Re: invalid files names, btrfs check can't repair it

On 2018-01-15 09:26:27 [+0800], Qu Wenruo wrote: > Please run the following command too: > > # btrfs inspect dump-tree | grep -C20 \(57923894 ~# btrfs inspect dump-tree /dev/sdb4 | grep -C20 \(57923894 ctime 1515602448.66422211 (2018-01-10 17:40:48) mtime

Re: invalid files names, btrfs check can't repair it

On 2018-01-14 08:36:41 [+0800], Qu Wenruo wrote: > Still needs more. (and maybe even more depending on the output) > > The original mode doesn't report error clear enough, so it would help if > --mode=lowmem can be used. > > # btrfs check --mode=lowmem /dev/sdb4 ~# btrfs check --mode=lowmem

Re: invalid files names, btrfs check can't repair it

On 2018-01-13 08:56:24 [+0800], Qu Wenruo wrote: > 'Btrfs check' output please. ~# btrfs check --repair -p /dev/sdb4 enabling repair mode Checking filesystem on /dev/sdb4 UUID: b3bfb56e-d445-4335-93f0-c1fb2d1f6df1 Fixed 0 roots. checking extents [o] No device size related problem found cache and

invalid files names, btrfs check can't repair it

Hi, so I had bad memory and before I realized it and removed it btrfs took some damage. Now I have this: |ls -lh crap/ |ls: cannot access 'crap/2f3f379b2a3d7499471edb74869efe-1948311.d': No such file or directory |ls: cannot access 'crap/454bf066ddfbf42e0f3b77ea71c82f-878732.o': No such file

Re: [btrfs/rt] lockdep false positive

On 2017-01-25 19:29:49 [+0100], Mike Galbraith wrote: > On Wed, 2017-01-25 at 18:02 +0100, Sebastian Andrzej Siewior wrote: > > > > [ 341.960794]CPU0 > > > [ 341.960795] > > > [ 341.960795] lock(btrfs-tree-00); > >

Re: [PATCH 1/2] btrfs: drop trace_btrfs_all_work_done() from normal_work_helper()

On 2016-12-21 16:45:06 [+0800], Qu Wenruo wrote: > > | DECLARE_EVENT_CLASS(btrfs__work__done, > > | > > | TP_PROTO(struct btrfs_work *work), > > | > > | TP_ARGS(work), > > | > > | TP_STRUCT__entry_btrfs( > > | __field(void *, work

Re: [PATCH 1/2] btrfs: drop trace_btrfs_all_work_done() from normal_work_helper()

On 2016-12-21 08:33:03 [+0800], Qu Wenruo wrote: > The trace point only uses the pointer, and this helps us to pair with > btrfs_work_queued/sched. | /* For situiations that the work is freed */ | DECLARE_EVENT_CLASS(btrfs__work__done, | | TP_PROTO(struct btrfs_work *work), | |

[RFC] btrfs: lockdep says "possible recursive locking detected" in btrfs_clear_lock_blocking_rw()

With lockdep enabled I managed to trigger the following lockdep splat: | = | [ INFO: possible recursive locking detected ] | 4.9.0-rt0 #804 Tainted: GW | - | kworker/u16:4/154 is trying to acquire

[PATCH 2/2] btrfs: swap free() and trace point in run_ordered_work()

: - run_one_async_free() - async_cow_free() Both of them free the `work' item so a later use in the tracepoint is not possible. This patch swaps the order so we first have the trace point and then free the struct. Signed-off-by: Sebastian Andrzej Siewior <bige...@linutronix.de> --- fs/btrfs/async-thread.c | 2

[PATCH 1/2] btrfs: drop trace_btrfs_all_work_done() from normal_work_helper()

der to avoid this, I remove the trace point. Signed-off-by: Sebastian Andrzej Siewior <bige...@linutronix.de> --- fs/btrfs/async-thread.c | 2 -- 1 file changed, 2 deletions(-) diff --git a/fs/btrfs/async-thread.c b/fs/btrfs/async-thread.c index e0f071f6b5a7..d0dfc3d2e199 100644 --- a/fs/bt

oops in wait_block_group_cache_progress() while accessing removed media

I manage to crash now and then by removing the mounted mmc card. This happens randomly. This log is from -rc3 but it also triggered on -rc4: | BTRFS: bdev /dev/root errs: wr 0, rd 2, flush 0, corrupt 0, gen 0 | BTRFS error (device mmcblk0p2): error reading free space cache | BTRFS warning (device