From: Josef Bacik <josef@redhat.com>
To: Victor Roetman <victory747@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: OOPS when subvol=xxx where xxx does not exist
Date: Thu, 13 May 2010 14:00:05 -0400 [thread overview]
Message-ID: <20100513180005.GG27011@dhcp231-156.rdu.redhat.com> (raw)
In-Reply-To: <4BEBE180.9080705@gmail.com>
On Thu, May 13, 2010 at 07:24:48PM +0800, Victor Roetman wrote:
> I am running 2.6.34-rc5, testing was done with a 4G thumb drive.
>
> # mkfs.btrfs /dev/sdd1
>
> WARNING! - Btrfs v0.19-16-g075587c IS EXPERIMENTAL
> WARNING! - see http://btrfs.wiki.kernel.org before using
>
> fs created label (null) on /dev/sdd1
> nodesize 4096 leafsize 4096 sectorsize 4096 size 3.73GB
> Btrfs v0.19-16-g075587c
>
> # mkdir one
> # mkdir two
> # mount /dev/sdd1 one
> # mount /dev/sdd1 two -o subvol=xxx
> mount: /dev/sdd1 is not a valid block device
> # umount one
Thanks for this, I just posted a patch to fix the problem.
Josef
prev parent reply other threads:[~2010-05-13 18:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-13 11:24 OOPS when subvol=xxx where xxx does not exist Victor Roetman
2010-05-13 18:00 ` Josef Bacik [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=20100513180005.GG27011@dhcp231-156.rdu.redhat.com \
--to=josef@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=victory747@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).