On Fri, Jan 20, 2012 at 11:24 AM, Jérôme Poulin <jeromepoulin@xxxxxxxxx> wrote: > On Wed, Jan 18, 2012 at 11:59 PM, Fajar A. Nugraha <list@xxxxxxxxx> 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@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
