I made a btrfs on five disks using RAID5 (-d raid5 for mount option). When a power failure occurs, I can not remount btrfs after my system reboots. Dmesg for remount is presented as following: [ 192.713953] bio: create slab <bio-1> at 1 [ 192.716230] Btrfs loaded [ 192.717177] device fsid a0dff7ea-9354-43fd-8516-0e17f370991d devid 1 transid 6 /dev/sdb [ 192.717712] btrfs: disk space caching is enabled [ 192.720572] btrfs: failed to read the system array on sdb [ 192.723398] btrfs: open_ctree failed linux md raid5 have resync , the test seems btrfs raid5 have not resync,how fix the bug? -- 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, Aug 29, 2013 at 10:34:00AM +0800, lilofile wrote:> I made a btrfs on five disks using RAID5 (-d raid5 for mount option). When a power failure occurs, I can not remount btrfs after my system reboots. Dmesg for remount is presented as following: > > [ 192.713953] bio: create slab <bio-1> at 1 > [ 192.716230] Btrfs loaded > [ 192.717177] device fsid a0dff7ea-9354-43fd-8516-0e17f370991d devid 1 transid 6 /dev/sdb > [ 192.717712] btrfs: disk space caching is enabled > [ 192.720572] btrfs: failed to read the system array on sdb > [ 192.723398] btrfs: open_ctree failed > > linux md raid5 have resync , the test seems btrfs raid5 have not resync,how fix the bug?Have you tried ''btrfs device scan'' before mounting it? -liubo -- 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, Aug 29, 2013 at 10:34:00AM +0800, lilofile wrote:> I made a btrfs on five disks using RAID5 (-d raid5 for mount option). > When a power failure occurs, I can not remount btrfs after my system > reboots. Dmesg for remount is presented as following:Please note that current implementation of raid5/6 is not completely crash-safe, as was mentioned in the announcement (eg. here http://lwn.net/Articles/536038/). The mount could fail if the parity of metadata blocks is corrupted due to crash. david -- 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