Re: error 2001, no inode item
Hi tried with a newer version of btrfs, but still getting the same error. checking extents checking free space cache checking fs roots root 5 inode 5769204 errors 2001, no inode item, link count wrong unresolved ref dir 5783881 index 3 namelen 38 name 61bd2ed1fba8bc8d2f12766c7e4b3dafff6350 filetype 1 error 4, no inode ref root 5 inode 5899187 errors 2001, no inode item, link count wrong unresolved ref dir 5906761 index 3 namelen 38 name 61bd2ed1fba8bc8d2f12766c7e4b3dafff6350 filetype 1 error 0 Checking filesystem on /dev/sda4 UUID: 98190f1e-426f-433d-8335-1216b9a63d16 found 28521431809 bytes used err is 1 total csum bytes: 124070732 total tree bytes: 722415616 total fs tree bytes: 552411136 total extent tree bytes: 32673792 btree space waste bytes: 171189111 file data blocks allocated: 188149448704 referenced 126695161856 Btrfs v3.14.1+20140502 # uname -a Linux apersaud 3.14.2-25.g1474ea5-desktop #1 SMP PREEMPT Sun Apr 27 14:35:22 UTC 2014 (1474ea5) x86_64 x86_64 x86_64 GNU/Linux Any idea how I can fix the missing inode problem? Arun -- 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
Re: error 2001, no inode item
Hello On 04/08/2014 05:10 AM, Duncan wrote: [...] I copied all the files from my old HD using dd, converted and then resized the file system. However, my old drive already had some errors. There's a page on the wiki specifically covering conversion. Please read it carefully and follow the recommendations, as the post-ext4-subvolume- delete defrag and balance it recommends can prevent problems later. https://btrfs.wiki.kernel.org/index.php/Conversion_from_Ext3 I did follow instructions from a similar website. The fsck on the ext4 system didn't work though. I also ran the balance command on btrfs, but I'm not sure anymore, if I ran the defrag. [...] Btrfs v3.12+20131125 that's the version I have installed at the moment. FWIW, there's a new btrfs-progs v3.14 version available. [...] uname -a Linux apersaud 3.14.0-23.gfa168d7-desktop #1 SMP PREEMPT Tue Apr 1 12:54:08 UTC 2014 (fa168d7) x86_64 x86_64 x86_64 GNU/Linux Looks like you're up on the kernel, anyway. =:^) I'm running opensuse/Tumbleweed. I'll see if I can get an update for btrfs-progs. [...] Don't run btrfs check --repair unless you're either told to do so by a dev after examining the errors you are seeing, or it's the last desperate step before you scrap the filesystem and mkfs anyway, so there's nothing to lose. OK, good to know ;) [...] And one more thing as a hint to save you some trouble. Strongly consider both the noatime (mainly performance) and the autodefrag mount options, I have noatime, but I'll add autodefrag. Thanks Arun -- 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
error 2001, no inode item
Hello my HD recently started crashing, so I rescued all files to a new one and thought that this might be a good time to convert from ext4 to btrfs. I copied all the files from my old HD using dd, converted and then resized the file system. However, my old drive already had some errors. Currently I have one file that I can't rm or overwrite (stale file handle). Here is what I get when running btrfs check: btrfs check /dev/sda4 checking extents checking free space cache checking fs roots root 5 inode 5769204 errors 2001, no inode item, link count wrong unresolved ref dir 5783881 index 3 namelen 38 name 61bd2ed1fba8bc8d2f12766c7e4b3dafff6350 filetype 1 error 4, no inode ref root 5 inode 5899187 errors 2001, no inode item, link count wrong unresolved ref dir 5906761 index 3 namelen 38 name 61bd2ed1fba8bc8d2f12766c7e4b3dafff6350 filetype 1 error 0 Checking filesystem on /dev/sda4 UUID: 98190f1e-426f-433d-8335-1216b9a63d16 cache and super generation don't match, space cache will be invalidated found 6932789174 bytes used err is 1 total csum bytes: 123239772 total tree bytes: 702812160 total fs tree bytes: 534839296 total extent tree bytes: 32509952 btree space waste bytes: 163897229 file data blocks allocated: 349199831040 referenced 126131052544 Btrfs v3.12+20131125 the file is a git object, so that's why the name looks like a hash ;) uname -a Linux apersaud 3.14.0-23.gfa168d7-desktop #1 SMP PREEMPT Tue Apr 1 12:54:08 UTC 2014 (fa168d7) x86_64 x86_64 x86_64 GNU/Linux I'm running opensuse/Tumbleweed. Any idea how I can fix the above? check --repair doesn't seem to help. Any suggestions would be highly appreciated. thanks Arun -- 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