From: Chris Mason <chris.mason@oracle.com>
To: Ahmed Kamal <email.ahmedkamal@googlemail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: crash when mounting
Date: Mon, 04 Aug 2008 08:47:22 -0400 [thread overview]
Message-ID: <1217854042.29139.41.camel@think.oraclecorp.com> (raw)
In-Reply-To: <3da3b5b40808021612q1ec112c2jae0769b0abdcceb5@mail.gmail.com>
On Sun, 2008-08-03 at 02:12 +0300, Ahmed Kamal wrote:
> Hi guys,
> I was playing on vmware with btrfs on complete disks /dev/sd{b,c,d,e}.
> Next I decided to use partitions, so I created /dev/sd{b,c,d,e}1 and
> used those, worked fine! Afterward, I mistakenly re-ran an old command
> on the full disk ( mount -t btrfs -o subvol=. /dev/sdb /mnt/ ) notice
> this is sdb not sdb1, and I got this spectacular kernel freeze. Let me
> know if that's some bug.
It would be nice if we didn't oops, there is clearly some hardening to
do in the failure paths for corrupt filesystems.
-chris
next prev parent reply other threads:[~2008-08-04 12:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-02 23:12 crash when mounting Ahmed Kamal
2008-08-04 12:47 ` Chris Mason [this message]
2008-08-04 12:59 ` Ahmed Kamal
2008-08-04 13:08 ` Chris Mason
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=1217854042.29139.41.camel@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=email.ahmedkamal@googlemail.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