On Wed, Jan 18, 2012 at 11:59 PM, Fajar A. Nugraha <list@xxxxxxxxx> 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@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
