All of lore.kernel.org
 help / color / mirror / Atom feed
From: Goffredo Baroncelli <kreijack@gmail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: Chris Murphy <lists@colorremedies.com>,
	"linux-btrfs@vger.kernel.org list" <linux-btrfs@vger.kernel.org>
Subject: Re: BUG btrfs fi show displays stale btrfs volume
Date: Sun, 06 Jan 2013 18:20:45 +0100	[thread overview]
Message-ID: <50E9B26D.3030900@gmail.com> (raw)
In-Reply-To: <50E9A5D1.4050704@inwind.it>





On 01/06/2013 05:26 PM, Goffredo Baroncelli wrote:
> Hi Chris
[...]
> 
> I will start to update the wiki; then I will give a look to wipefs to
> improve it.

Hello I updated the wiki page:


https://btrfs.wiki.kernel.org/index.php/Problem_FAQ#What_if_I_don.27t_have_wipefs_at_hand.3F
-----
 What if I don't have wipefs at hand?

There are three superblocks: the first one is located at 64K, the second
one at 64M, the third one at 256GB. The following lines reset the magic
string on all the three superblocks

# dd if=/dev/zero bs=1 count=8 of=/dev/sda seek=$((64*1024+64))
# dd if=/dev/zero bs=1 count=8 of=/dev/sda seek=$((64*1024*1024+64))
# dd if=/dev/zero bs=1 count=8 of=/dev/sda seek=$((256*1024*1024*1024+64))

If you want to restore the superblocks magic string,

# echo "_BHRfS_M" | dd bs=1 count=8 of=/dev/sda seek=$((64*1024+64))
# echo "_BHRfS_M" | dd bs=1 count=8 of=/dev/sda seek=$((64*1024*1024+64))
# echo "_BHRfS_M" | dd bs=1 count=8 of=/dev/sda
seek=$((256*1024*1024*1024+64))
------

> 
> BR
> G.Baroncelli


-- 
gpg @keyserver.linux.it: Goffredo Baroncelli (kreijackATinwind.it>
Key fingerprint BBF5 1610 0B64 DAC6 5F7D  17B2 0EDA 9B37 8B82 E0B5

      reply	other threads:[~2013-01-06 17:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-05 23:21 BUG btrfs fi show displays stale btrfs volume Chris Murphy
2013-01-06 16:26 ` Goffredo Baroncelli
2013-01-06 17:20   ` Goffredo Baroncelli [this message]

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=50E9B26D.3030900@gmail.com \
    --to=kreijack@gmail.com \
    --cc=kreijack@inwind.it \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lists@colorremedies.com \
    /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 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.