How is a device checked (when being scanned) to contain a btrfs filesystem? I have a filesystem spread across two devices; one of them is not being detected; the first (@64KiB) superblock is missing (not sure why); but the second one (64MiB) seems valid (fs uuid + dev uuid and all); would i have to create a superblock for the beginging of the drive? (or mirror the 64mb one and change the physical address and checksum)??
On Sun, Oct 10, 2010 at 11:40 PM, Sean Bartell <[email protected]> wrote: > On Sun, Oct 10, 2010 at 10:43:56PM -0500, Nathan Caza wrote: >> Is this up-to-date? if not, has anyone put together something like >> this more recent?? >> >> https://btrfs.wiki.kernel.org/index.php/User:Wtachi/On-disk_Format > > It should be up-to-date, to the extent that it contains any useful > information at all. It's basically a sketch I wrote when I was first > figuring out btrfs, and I haven't gotten around to filling in the > details. > -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
