I did a preemptive fsck after a RAID crash and got many errors, is there something I should do if everything I use works? root 412 inode 427 errors 400 root 412 inode 430 errors 400 root 412 inode 434 errors 400 root 412 inode 436 errors 400 root 412 inode 440 errors 400 root 412 inode 446 errors 400 root 412 inode 448 errors 400 root 412 inode 452 errors 400 root 412 inode 458 errors 400 root 412 inode 464 errors 400 root 412 inode 466 errors 400 root 412 inode 476 errors 400 root 412 inode 479 errors 400 root 412 inode 495 errors 400 root 412 inode 498 errors 400 root 412 inode 515 errors 400 root 412 inode 518 errors 400 root 412 inode 522 errors 400 root 412 inode 524 errors 400 root 412 inode 534 errors 400 root 412 inode 537 errors 400 root 412 inode 541 errors 400 root 412 inode 543 errors 400 root 412 inode 560 errors 400 root 412 inode 563 errors 400 root 412 inode 580 errors 400 root 412 inode 583 errors 400 root 412 inode 600 errors 400 root 412 inode 603 errors 400 root 412 inode 607 errors 400 root 412 inode 620 errors 400 root 412 inode 623 errors 400 root 412 inode 627 errors 400 root 412 inode 640 errors 400 root 412 inode 643 errors 400 root 412 inode 647 errors 400 root 412 inode 649 errors 400 root 412 inode 660 errors 400 root 412 inode 663 errors 400 root 412 inode 667 errors 400 root 412 inode 669 errors 400 root 412 inode 680 errors 400 root 412 inode 683 errors 400 root 412 inode 700 errors 400 root 412 inode 703 errors 400 root 412 inode 719 errors 400 root 412 inode 722 errors 400 root 412 inode 726 errors 400 root 412 inode 739 errors 400 root 412 inode 742 errors 400 root 412 inode 746 errors 400 root 412 inode 748 errors 400 root 412 inode 752 errors 400 root 412 inode 754 errors 400 root 412 inode 771 errors 400 root 412 inode 774 errors 400 root 412 inode 780 errors 400 root 412 inode 782 errors 400 root 412 inode 786 errors 400 root 412 inode 788 errors 400 root 412 inode 792 errors 400 root 412 inode 794 errors 400 root 412 inode 798 errors 400 root 412 inode 800 errors 400 root 412 inode 804 errors 400 root 412 inode 806 errors 400 root 412 inode 810 errors 400 root 412 inode 812 errors 400 root 412 inode 816 errors 400 root 412 inode 818 errors 400 root 412 inode 822 errors 400 root 412 inode 824 errors 400 root 412 inode 828 errors 400 root 412 inode 830 errors 400 root 412 inode 834 errors 400 root 412 inode 836 errors 400 root 412 inode 840 errors 400 root 412 inode 846 errors 400 root 412 inode 852 errors 400 root 412 inode 854 errors 400 root 412 inode 858 errors 400 root 412 inode 864 errors 400 root 412 inode 866 errors 400 root 412 inode 870 errors 400 root 412 inode 872 errors 400 root 412 inode 876 errors 400 root 412 inode 878 errors 400 root 412 inode 882 errors 400 root 412 inode 885 errors 400 root 412 inode 888 errors 400 root 412 inode 891 errors 400 root 412 inode 894 errors 400 root 412 inode 897 errors 400 root 412 inode 900 errors 400 root 412 inode 903 errors 400 root 412 inode 906 errors 400 root 412 inode 909 errors 400 root 412 inode 912 errors 400 root 412 inode 938 errors 400 root 412 inode 940 errors 400 root 412 inode 944 errors 400 root 412 inode 946 errors 400 root 412 inode 950 errors 400 root 412 inode 963 errors 400 root 412 inode 966 errors 400 root 412 inode 983 errors 400 root 412 inode 986 errors 400 root 412 inode 990 errors 400 root 412 inode 1002 errors 400 root 412 inode 1005 errors 400 root 412 inode 1022 errors 400 root 412 inode 1025 errors 400 root 412 inode 1029 errors 400 root 412 inode 1031 errors 400 root 424 inode 291690 errors 400 found 222893703168 bytes used err is 1 total csum bytes: 217378224 total tree bytes: 288571392 total fs tree bytes: 23961600 btree space waste bytes: 29683827 file data blocks allocated: 11876872372224 referenced 226945392640 Btrfs Btrfs v0.19 -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Thu, Jan 19, 2012 at 9:02 AM, Jérôme Poulin <jeromepoulin@gmail.com> wrote:> I did a preemptive fsck after a RAID crash and got many errors, is > there something I should do if everything I use works?Probably just ignore it. Recent kernels (e.g. 3.1 or 3.2) is smart enough to automatically fix certain types of errors. Watch syslog when you mount the fs, access some files, unmount, and mount it again. If second mount does not show any error message then I''m pretty sure you''re safe. -- Fajar -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Wed, Jan 18, 2012 at 11:59 PM, Fajar A. Nugraha <list@fajar.net> wrote:> Recent kernels (e.g. 3.1 or 3.2) is smart enough to automatically fix > certain types of errors. Watch syslog when you mount the fs, access > some files, unmount, and mount it again. If second mount does not show > any error message then I''m pretty sure you''re safe.I just upgraded from 3.0 to 3.2.1 and mounted the filesystem, tried find > /dev/null and only got messages about old space inode. I then used btrfsck again for the same exact result, I''ll ignore them for now, let''s see what the shiny new btrfsck will do about them! -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Fri, Jan 20, 2012 at 11:24 AM, Jérôme Poulin <jeromepoulin@gmail.com> wrote:> On Wed, Jan 18, 2012 at 11:59 PM, Fajar A. Nugraha <list@fajar.net> wrote: >> some files, unmount, and mount it again. If second mount does not show >> any error message then I''m pretty sure you''re safe. > > I just upgraded from 3.0 to 3.2.1 and mounted the filesystem, tried > find > /dev/null and only got messages about old space inode.That''s normal. You''ll also get the message if you switch back to 3.0, but it should be harmless.> I then > used btrfsck again for the same exact result, I''ll ignore them for > now, let''s see what the shiny new btrfsck will do about them!who knows when it will be available :) Then again, most fsck feature has been implemented in kernel space so a mount will automatically "fix" some types of problems (somewhat similar to what zfs does, which has no fsck whatsoever). So just watch syslog for any unusual error messages. -- Fajar -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Fri, Jan 20, 2012 at 2:19 AM, Fajar A. Nugraha <list@fajar.net> wrote:> Then again, most fsck feature has been implemented in kernel space so > a mount will automatically "fix" some types of problems (somewhat > similar to what zfs does, which has no fsck whatsoever). So just watch > syslog for any unusual error messages.However it has a way to be fully backed up without losing space which have been saved using snapshot and reflinks. Right now, this is not production critical data, so I''ve got backups only of files I think are critical to me, not reflinks and snapshots. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html