* On-Disk Format
@ 2010-10-11 3:43 Nathan Caza
2010-10-11 4:40 ` Sean Bartell
0 siblings, 1 reply; 4+ messages in thread
From: Nathan Caza @ 2010-10-11 3:43 UTC (permalink / raw)
To: linux-btrfs
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: On-Disk Format
2010-10-11 3:43 On-Disk Format Nathan Caza
@ 2010-10-11 4:40 ` Sean Bartell
2010-10-11 7:28 ` Nathan Caza
2010-10-11 20:20 ` David Nicol
0 siblings, 2 replies; 4+ messages in thread
From: Sean Bartell @ 2010-10-11 4:40 UTC (permalink / raw)
To: Nathan Caza; +Cc: linux-btrfs
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.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: On-Disk Format
2010-10-11 4:40 ` Sean Bartell
@ 2010-10-11 7:28 ` Nathan Caza
2010-10-11 20:20 ` David Nicol
1 sibling, 0 replies; 4+ messages in thread
From: Nathan Caza @ 2010-10-11 7:28 UTC (permalink / raw)
To: Nathan Caza, linux-btrfs
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
<wingedtachikoma@gmail.com> 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.
>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: On-Disk Format
2010-10-11 4:40 ` Sean Bartell
2010-10-11 7:28 ` Nathan Caza
@ 2010-10-11 20:20 ` David Nicol
1 sibling, 0 replies; 4+ messages in thread
From: David Nicol @ 2010-10-11 20:20 UTC (permalink / raw)
To: linux-btrfs
how are inode numbers determined? "dynamic inode numbering" is
included amongst BTRFS's features.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2010-10-11 20:20 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-10-11 3:43 On-Disk Format Nathan Caza
2010-10-11 4:40 ` Sean Bartell
2010-10-11 7:28 ` Nathan Caza
2010-10-11 20:20 ` David Nicol
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.