From: Goffredo Baroncelli <kreijack@tiscalinet.it>
To: Hugo Mills <hugo@carfax.org.uk>,
dsterba@suse.cz, util-linux@vger.kernel.org,
linux-btrfs <linux-btrfs@vger.kernel.org>,
Chris Mason <chris.mason@fusionio.com>,
Chris Murphy <lists@colorremedies.com>
Subject: Re: Btrfs: wipe all the superblock [redhat bugzilla 889888]
Date: Mon, 07 Jan 2013 19:33:31 +0100 [thread overview]
Message-ID: <50EB14FB.3080002@tiscalinet.it> (raw)
In-Reply-To: <20130107182426.GM19051@carfax.org.uk>
Hi hugo
On 01/07/2013 07:24 PM, Hugo Mills wrote:
[...]
>> print "Superblock #%d - %20d - '%s'"%(i,pos,sign)
>>
>> $ python extract-sign.py
>> Superblock #0 - 65600 - '_BHRfS_M'
>
> 64 KiB
OK, (above)
>
>> Superblock #1 - 67108928 - '_BHRfS_M'
>
> 256 MiB
.... above is 64M, below is 256M !
>
>> Superblock #2 - 274877907008 - '_BHRfS_M'
>
> 1 TiB
>
>> Superblock #3 - 1125899906842688 - ''
>
> 4 PiB
>
>> Superblock #4 - 4611686018427387968 - ''
>
> 16 EiB
Not reachable in linux. There is a VFS limits to 8EB.
>
>
>> To me it seems that in a 7TB filesystem there is only 3 superblocks.
>
> That would be as expected. How many on a 5 PiB filesystem, though?
> Or a 20 EiB one?
I wrote 7TB, but I meant 8EB. I first tried a test with 7TB and I wrote
the email, but then I retested with 8EB and I corrected the email,
forgetting some 7t instead of 8e...
Anyway, if BTRFS would allow more than three super-block, in the 7TB
case, the super-block at 1TB would appeared
>
> Hugo.
>
--
gpg @keyserver.linux.it: Goffredo Baroncelli (kreijackATinwind.it>
Key fingerprint BBF5 1610 0B64 DAC6 5F7D 17B2 0EDA 9B37 8B82 E0B5
next prev parent reply other threads:[~2013-01-07 18:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-06 18:28 Btrfs: wipe all the superblock [redhat bugzilla 889888] Goffredo Baroncelli
2013-01-07 16:33 ` David Sterba
2013-01-07 18:20 ` Goffredo Baroncelli
2013-01-07 18:24 ` Hugo Mills
2013-01-07 18:33 ` Goffredo Baroncelli [this message]
2013-01-08 17:14 ` David Sterba
2013-01-08 15:48 ` Günter Gersdorf
2013-01-08 20:31 ` Goffredo Baroncelli
2013-01-09 8:09 ` Günter Gersdorf
2013-01-08 16:43 ` Karel Zak
2013-01-09 17:48 ` Goffredo Baroncelli
2013-01-09 18:10 ` Karel Zak
2013-01-08 18:01 ` Karel Zak
2013-01-08 20:09 ` Goffredo Baroncelli
2013-01-08 20:27 ` Chris Murphy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50EB14FB.3080002@tiscalinet.it \
--to=kreijack@tiscalinet.it \
--cc=chris.mason@fusionio.com \
--cc=dsterba@suse.cz \
--cc=hugo@carfax.org.uk \
--cc=kreijack@inwind.it \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=util-linux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox