From: Nageswara R Sastry <rnsastry@linux.vnet.ibm.com>
To: Liu Bo <liubo2009@cn.fujitsu.com>
Cc: linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
chris.mason@oracle.com, kamalesh@linux.vnet.ibm.com
Subject: Re: [BUG] Kernel Bug at fs/btrfs/volumes.c:3638
Date: Mon, 27 Feb 2012 11:26:28 +0530 [thread overview]
Message-ID: <4F4B1B0C.4040100@linux.vnet.ibm.com> (raw)
In-Reply-To: <4F487BB5.1060706@cn.fujitsu.com>
On =E0=B0=AB=E0=B0=BF=E0=B0=AC=E0=B1=8D=E0=B0=B0=E0=B0=B5=E0=B0=B0=E0=B0=
=BF 25 =E0=B0=B6=E0=B0=A8=E0=B0=BF=E0=B0=B5=E0=B0=BE=E0=B0=B0=E0=B0=82 =
2012 =E0=B0=89. 11:42, Liu Bo wrote:
> Hi, I guess you're mounting a quite small partition. Given that this=20
> oops is in such an early stage, could you please show 1) your=20
> mkfs.btrfs options and 2) the log of "btrfs-debug-tree /dev/loop0"?=20
> thanks, liubo
Here are the steps with options,
1. dd if=3D/dev/zero of=3D<filename.img> bs=3D1M count=3D16
2. mkfs.btrfs <filename.img>
3. Corrupt the <filename.img> using 'mangle'
4. mount -t btrfs -o loop <filename.img> <mount point>
5. # btrfs-debug-tree <filename.img>
Couldn't map the block 3221392384
Couldn't read chunk root
unable to open <filename.img>
# btrfs-debug-tree /dev/loop0
Couldn't map the block 3221392384
Couldn't read chunk root
unable to open /dev/loop0
Regards,
R.Nageswara Sastry
--
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
WARNING: multiple messages have this Message-ID (diff)
From: Nageswara R Sastry <rnsastry@linux.vnet.ibm.com>
To: Liu Bo <liubo2009@cn.fujitsu.com>
Cc: linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
chris.mason@oracle.com, kamalesh@linux.vnet.ibm.com
Subject: Re: [BUG] Kernel Bug at fs/btrfs/volumes.c:3638
Date: Mon, 27 Feb 2012 11:26:28 +0530 [thread overview]
Message-ID: <4F4B1B0C.4040100@linux.vnet.ibm.com> (raw)
In-Reply-To: <4F487BB5.1060706@cn.fujitsu.com>
On ఫిబ్రవరి 25 శనివారం 2012 ఉ. 11:42, Liu Bo wrote:
> Hi, I guess you're mounting a quite small partition. Given that this
> oops is in such an early stage, could you please show 1) your
> mkfs.btrfs options and 2) the log of "btrfs-debug-tree /dev/loop0"?
> thanks, liubo
Here are the steps with options,
1. dd if=/dev/zero of=<filename.img> bs=1M count=16
2. mkfs.btrfs <filename.img>
3. Corrupt the <filename.img> using 'mangle'
4. mount -t btrfs -o loop <filename.img> <mount point>
5. # btrfs-debug-tree <filename.img>
Couldn't map the block 3221392384
Couldn't read chunk root
unable to open <filename.img>
# btrfs-debug-tree /dev/loop0
Couldn't map the block 3221392384
Couldn't read chunk root
unable to open /dev/loop0
Regards,
R.Nageswara Sastry
next prev parent reply other threads:[~2012-02-27 5:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-24 10:41 [BUG] Kernel Bug at fs/btrfs/volumes.c:3638 Nageswara R Sastry
2012-02-25 6:12 ` Liu Bo
2012-02-27 5:56 ` Nageswara R Sastry [this message]
2012-02-27 5:56 ` Nageswara R Sastry
2012-02-27 4:42 ` Jérôme Carretero
2012-02-27 14:52 ` David Sterba
2012-02-27 14:52 ` David Sterba
2012-03-01 0:27 ` David Sterba
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=4F4B1B0C.4040100@linux.vnet.ibm.com \
--to=rnsastry@linux.vnet.ibm.com \
--cc=chris.mason@oracle.com \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liubo2009@cn.fujitsu.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.