On Mon, Jan 29, 2018 at 2:04 PM, Qu Wenruo <quwenruo.bt...@gmx.com> wrote: > > > On 2018年01月29日 21:58, ^m'e wrote: >> Thanks for the advice, Qu! >> >> I used the system for a while, did some package upgrades -- writing in >> the suspect corrupted area. Then tried a btrfs-send to my backup vol, >> and it failed miserably with a nice kernel oops. >> >> So I went for a lowmem repair: >> ---------------------------------------------------------------------------------------- >> # ./btrfsck.static check --repair --mode=lowmem /dev/sdb3 2>&1 | tee >> /mnt/custom/rescue/btrfs-recovery/btrfs-repair.BTR-POOL.1.log >> WARNING: low-memory mode repair support is only partial >> Fixed 0 roots. >> checking extents >> checking free space cache >> checking fs roots >> ERROR: failed to add inode 28891726 as orphan item root 257 >> ERROR: root 257 INODE[28891726] is orphan item > > At least I need dig the kernel code further to determine if the orphan > inode handling in btrfs-progs is correct or not. > > So there won't be more dirty fix soon. > > Hopefully you could get some good backup and restore the system. > > At least the problem is limited to a very small range, and it's > something we could handle easily. > > Thanks for all your report, > Qu > >
Right. Meanwhile, could you please suggest the best course of action? btrfs rescue or restore? I have snapshots of my two subvols (rootfs, home -- now fs-checking them just in case...) Cheers, Marco -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
