From: Eric Sandeen <sandeen@redhat.com>
To: vgrvelu <vgrajan2005@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: hi
Date: Tue, 24 Sep 2013 19:48:29 -0500 [thread overview]
Message-ID: <524232DD.60202@redhat.com> (raw)
In-Reply-To: <CALe5Emw4u1g2XPet5goM5V3YFbb4isqA4OTecR9RxnD7gxZr7g@mail.gmail.com>
On 9/24/13 6:39 PM, vgrvelu wrote:
> hi
>
> I created btrfs file system on one of sda partition. when I mount
> with mount -t /dev/sda17 /btrfs,
# mount -t /dev/sda17 /btrfs?
That doesn't work. Maybe you meant :
# mount -t btrfs /dev/sda17 /btrfs ?
> it is failing with wrong fs type bad option. when i see the dmesg,
> mount command is searching for ext3, ext2 filesystem on sda17. but
> not btrfs.
> even in the man page of mount, btrfs is not mentioned as supported
> file system type.
>
> Please help me to solve this issue.
does your kernel support btrfs? Sounds like maybe not.
To load it in case it's a module:
# modprobe btrfs
then see if the kernel even knows what btrfs is, either via the
module, or due to being built into the kernel image already:
# grep btrfs /proc/filesystems
The first cmd might fail if it's built into the kernel, but if that's
the reason, the 2nd one should find btrfs in /proc/filesystems...
If not, you need a kernel that supports btrfs.
-Eric
> thanks
> rajan
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2013-09-25 0:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-24 23:39 hi vgrvelu
2013-09-24 23:56 ` hi Chris Murphy
2013-09-25 13:00 ` hi vgrvelu
2013-09-25 13:51 ` hi Wang Shilong
2013-09-25 15:29 ` hi Eric Sandeen
2013-09-25 0:48 ` Eric Sandeen [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-04-12 12:58 Hi Stevenson, Marjorie
2015-10-19 19:23 Hi Judith Guest
2011-10-28 11:06 Hi lisa hedstrand
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=524232DD.60202@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=vgrajan2005@gmail.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 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).