Chris Murphy wrote: > On Wed, Jan 21, 2015 at 9:35 AM, Neal Becker <ndbecker2@xxxxxxxxx> wrote: > >> Jan 21 11:32:17 nbecker1 kernel: [ 96.851478] WARNING: CPU: 0 PID: 1749 at >> fs/btrfs/delayed-inode.c:1410 btrfs_assert_delayed_root_empty+0x39/0x40 >> [btrfs] > > Looks like this: > http://www.spinics.net/lists/linux-btrfs/msg40858.html > https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.18.3 > > You should do three things: if the fs is still mounted, update your > backup; then install kernel 3.18.3 from updates-testing repo; then use > btrfs check --repair using btrfs-progs 3.18. > This is on root fs, btrfs check --repair can't be used on a mounted fs, correct? > Since 3.17.8 didn't get this patch, and 3.17 is EOL, it won't ever get > it. Looks like the patch is in 3.18.3, and 3.14.29. And it's easier to > go with 3.18.3, which is in updates-testing. > > Next you should reboot from Fedora 21 live media, and 'dnf upgrade > btrfs-progs' so that you have btrfs-progs 3.18.1, which is stable. And > use 'btrfs check --repair' in case there are any missing files, this > should find it. After this, you'd update the backup again in case the > first one lacks the missing files. > > So you're saying to run btrfs check --repair twice? Once after installing/rebooting 3.18.3, and then a 2nd time with live media? -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
