linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hugo Mills <hugo@carfax.org.uk>
To: kathleen.hodge@emc.com
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs w/ckd
Date: Thu, 2 Jun 2011 20:59:56 +0100	[thread overview]
Message-ID: <20110602195956.GC8002@carfax.org.uk> (raw)
In-Reply-To: <47C68B986D117D40A7E109AE2FC85C291128DB4A12@MX01A.corp.emc.com>

[-- Attachment #1: Type: text/plain, Size: 1638 bytes --]

On Thu, Jun 02, 2011 at 03:45:07PM -0400, kathleen.hodge@emc.com wrote:
> Hello,
> I'm trying to use mod3 ckds which are already RAID10 protection. (most of the doc I'm looking at uses fba instead of ckd, so I didn't know if this was a limitation)
> I'm addressing the head device and able to use these devices with no problem as ext3.  I've been reading that cache may remember that it used to be ext3, so I detached and reattached, but get the same result when trying to mount after formatting.
> 
> I use the following to make the file system after I've attached, varied online, formated and partitioned (also tried without the journaling switch).
> mke2fs -j -t btrfs /dev/dasdbj1

   Quoting the man page for that command:

"mke2fs  is used to create an ext2, ext3, or ext4 filesystem, [...]"

The -t option specifies which of ext2, ext3, and ext4 to create.  I'm
surprised it did anything at all given a type of "btrfs"...

   You probably wanted mkfs.btrfs instead:

# mkfs.btrfs -d single -m single /dev/dasdbj1

> Then the mount command:
> mount -t btrfs /dev/dasdbj1 /home/sdasd/d01
> mount: /dev/dasdbj1: can't read superblock

   If it created an ext2/3/4 filesystem, I'm not entirely surprised
that it can't find a btrfs superblock there. :)

   Hugo.

-- 
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
  PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
  --- We teach people management skills by examining characters in ---   
            Shakespeare.  You could look at Claudius's crisis            
                   management techniques, for example.                   

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 190 bytes --]

  reply	other threads:[~2011-06-02 19:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-02 19:45 btrfs w/ckd kathleen.hodge
2011-06-02 19:59 ` Hugo Mills [this message]
     [not found]   ` <47C68B986D117D40A7E109AE2FC85C291128DB4A33@MX01A.corp.emc.com>
2011-06-02 20:43     ` Hugo Mills

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=20110602195956.GC8002@carfax.org.uk \
    --to=hugo@carfax.org.uk \
    --cc=kathleen.hodge@emc.com \
    --cc=linux-btrfs@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;
as well as URLs for NNTP newsgroup(s).