Re: scrub: Tree block spanning stripes, ignored

Sorry, I'm a little busy recently. The patch may be delayed to the end of May. Would you please try to paste the output of "btrfs-debug-tree -t 1"? That would include some info for your corrupted space cache of that block group. And also, if you're OK to try some experimental features, would

Re: scrub: Tree block spanning stripes, ignored

Issue persists with btrfs-progs 4.5.1 and linux 4.5.1. Did you have time to implement that option in btrfsck you were talking about? I'm a bit reluctant to use this partition at this point. Regards Ivan On Tue, Apr 12, 2016 at 7:15 PM, Ivan P wrote: > Feel free to send

Re: scrub: Tree block spanning stripes, ignored

Feel free to send me that modified btrfsck when you finish it, I'm open for experiments as long as I have my backup copy. Regards, Ivan. On Mon, Apr 11, 2016 at 3:10 AM, Qu Wenruo wrote: > There seems to be something wrong with btrfsck. > > Not sure if it's kernel

Re: scrub: Tree block spanning stripes, ignored

There seems to be something wrong with btrfsck. Not sure if it's kernel clear_cache mount option or btrfsck to blame. Anyway, it shouldn't be a big problem though. If you want to make sure it won't damage your fs, it's better to mount with nospace_cache mount option. I'd try to implement a

Re: scrub: Tree block spanning stripes, ignored

Well, the message is almost the same after mounting with clear_cache -> unmounting -> mounting with regular options -> unmounting -> running btrfsck --readonly. === Checking filesystem on /dev/sdb UUID: 013cda95-8aab-4cb2-acdd-2f0f78036e02 checking extents checking

Re: scrub: Tree block spanning stripes, ignored

Ivan P wrote on 2016/04/07 17:33 +0200: After running btrfsck --readonly again, the output is: === Checking filesystem on /dev/sdb UUID: 013cda95-8aab-4cb2-acdd-2f0f78036e02 checking extents checking free space cache block group 632463294464 has wrong amount of

Re: scrub: Tree block spanning stripes, ignored

On 7 April 2016 at 17:33, Ivan P wrote: > > After running btrfsck --readonly again, the output is: > > === > Checking filesystem on /dev/sdb > UUID: 013cda95-8aab-4cb2-acdd-2f0f78036e02 > checking extents > checking free space cache > block

Re: scrub: Tree block spanning stripes, ignored

After running btrfsck --readonly again, the output is: === Checking filesystem on /dev/sdb UUID: 013cda95-8aab-4cb2-acdd-2f0f78036e02 checking extents checking free space cache block group 632463294464 has wrong amount of free space failed to load free space cache for

Re: scrub: Tree block spanning stripes, ignored

Ivan P wrote on 2016/04/06 21:39 +0200: Ok, I'm cautiously optimistic: after running btrfsck --init-extent-tree --repair and running scrub, it finished without errors. Will run a file compare against my backup copy, but it seems the repair was successful. Better run btrfsck again, to ensure

Re: scrub: Tree block spanning stripes, ignored

On 04/03/2016 12:29 AM, Ivan P wrote: It's about 800Mb, I think I could upload that. I ran it with the -s parameter, is that enough to remove all personal info from the image? Also, I had to run it with -w because otherwise it died on the same corrupt node. You can also use -c9 to further

Re: scrub: Tree block spanning stripes, ignored

It's about 800Mb, I think I could upload that. I ran it with the -s parameter, is that enough to remove all personal info from the image? Also, I had to run it with -w because otherwise it died on the same corrupt node. On Fri, Apr 1, 2016 at 2:25 AM, Qu Wenruo wrote: >

Re: scrub: Tree block spanning stripes, ignored

Ivan P wrote on 2016/03/28 23:21 +0200: Well, the file in this inode is fine, I was able to copy it off the disk. However, rm-ing the file causes a segmentation fault. Shortly after that, I get a kernel oops. Same thing happens if I attempt to re-run scrub. How can I delete that inode? Could

Re: scrub: Tree block spanning stripes, ignored

Well, the file in this inode is fine, I was able to copy it off the disk. However, rm-ing the file causes a segmentation fault. Shortly after that, I get a kernel oops. Same thing happens if I attempt to re-run scrub. How can I delete that inode? Could deleting it destroy the filesystem beyond

Re: scrub: Tree block spanning stripes, ignored

Ivan P wrote on 2016/03/27 16:31 +0200: Thanks for the reply, the raid1 array was created from scratch, so not converted from ext*. I used btrfs-progs version 4.2.3 on kernel 4.2.5 to create the array, btw. I don't remember any strange behavior after 4.0, so no clue here. Go to the

Re: scrub: Tree block spanning stripes, ignored

On 03/27/2016 05:54 PM, Ivan P wrote: Read the info on the wiki, here's the rest of the requested information: # uname -r 4.4.5-1-ARCH # btrfs fi show Label: 'ArchVault' uuid: cd8a92b6-c5b5-4b19-b5e6-a839828d12d8 Total devices 1 FS bytes used 2.10GiB devid1 size 14.92GiB

Re: scrub: Tree block spanning stripes, ignored

..forgot to paste btrfs-version: 4.4.1 (slightly outdated, but it's the current version on arch linux) On Sun, Mar 27, 2016 at 11:54 AM, Ivan P wrote: > Read the info on the wiki, here's the rest of the requested information: > > # uname -r > 4.4.5-1-ARCH > > # btrfs fi

Re: scrub: Tree block spanning stripes, ignored

Read the info on the wiki, here's the rest of the requested information: # uname -r 4.4.5-1-ARCH # btrfs fi show Label: 'ArchVault' uuid: cd8a92b6-c5b5-4b19-b5e6-a839828d12d8 Total devices 1 FS bytes used 2.10GiB devid1 size 14.92GiB used 4.02GiB path /dev/sdc1 Label: 'Vault'