linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* btrfs: failed to read chunk tree on vde1 (f18 anaconda crash)
@ 2013-01-19 22:53 Reartes Guillermo
  2013-01-20 13:22 ` Hugo Mills
  0 siblings, 1 reply; 3+ messages in thread
From: Reartes Guillermo @ 2013-01-19 22:53 UTC (permalink / raw)
  To: linux-btrfs

Hi,

I reported a bug to anaconda (rhbz 901905), but it might be btfs related.

Anaconda does this:

18:49:10,317 INFO program: Running... mkfs.btrfs --data=single
--label=fedora /dev/vdb1 /dev/vdc1 /dev/vdd1 /dev/vde1
18:49:10,742 INFO program:
18:49:10,746 INFO program: WARNING! - Btrfs Btrfs v0.19 IS EXPERIMENTAL
18:49:10,746 INFO program: WARNING! - see http://btrfs.wiki.kernel.org
before using
18:49:10,748 INFO program:
18:49:10,749 INFO program: SMALL VOLUME: forcing mixed metadata/data groups
18:49:10,750 INFO program: Created a data/metadata chunk of size 8388608
18:49:10,750 INFO program: adding device /dev/vdc1 id 2
18:49:10,751 INFO program: adding device /dev/vdd1 id 3
18:49:10,752 INFO program: adding device /dev/vde1 id 4
18:49:10,752 INFO program: fs created label fedora on /dev/vdb1
18:49:10,753 INFO program:      nodesize 4096 leafsize 4096 sectorsize
4096 size 2.93GB
18:49:10,754 INFO program: Btrfs Btrfs v0.19
18:49:10,987 INFO program: Running... udevadm settle --timeout=300
18:49:11,007 INFO program: Running... udevadm settle --timeout=300
18:49:11,036 INFO program: Running... udevadm settle --timeout=300
18:49:11,070 INFO program: Running... udevadm settle --timeout=300
21:49:11,121 INFO program: Running... /bin/mount -n -t btrfs -o
defaults /dev/vdb1 /tmp/btrfs-tmp.5205bBZQ
21:49:11,135 ERR program: mount: wrong fs type, bad option, bad
superblock on /dev/vdb1,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail or so

In the syslog file this is shown:

21:49:10,371 INFO kernel:[  435.624404] device label fedora devid 1
transid 3 /dev/vdb1
21:49:10,371 INFO kernel:[  435.624720] device label fedora devid 1
transid 3 /dev/vdb1
21:49:10,385 INFO kernel:[  435.638653] device label fedora devid 1
transid 3 /dev/vdb1
21:49:10,396 INFO kernel:[  435.649839] device label fedora devid 2
transid 3 /dev/vdc1
21:49:10,404 INFO kernel:[  435.657442] device label fedora devid 3
transid 3 /dev/vdd1
21:49:10,434 INFO kernel:[  435.687677] device label fedora devid 4
transid 3 /dev/vde1
21:49:10,746 INFO kernel:[  435.999309] device label fedora devid 1
transid 4 /dev/vdb1
21:49:10,918 INFO kernel:[  436.171992] device label fedora devid 3
transid 4 /dev/vdd1
21:49:10,925 INFO kernel:[  436.178937] device label fedora devid 3
transid 4 /dev/vdd1
21:49:10,928 INFO kernel:[  436.181545] device label fedora devid 4
transid 4 /dev/vde1
21:49:10,929 INFO kernel:[  436.182475] device label fedora devid 1
transid 4 /dev/vdc1
21:49:10,930 INFO kernel:[  436.183409] device label fedora devid 4
transid 4 /dev/vde1
21:49:10,932 INFO kernel:[  436.185171] device label fedora devid 1
transid 4 /dev/vdc1
21:49:10,971 INFO kernel:[  436.224843] device label fedora devid 1
transid 4 /dev/vdb1
21:49:11,130 INFO kernel:[  436.383110] device label fedora devid 1
transid 4 /dev/vdb1
21:49:11,133 INFO kernel:[  436.386297] btrfs: disk space caching is enabled
21:49:11,133 WARNING kernel:[  436.386697] btrfs: failed to read chunk
tree on vde1
21:49:11,134 WARNING kernel:[  436.387183] btrfs: open_ctree failed

I booted again and did both the mk.btrfs and the mount manually and i
got the same error.

Is it a known issue?

Thanks in advance.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: btrfs: failed to read chunk tree on vde1 (f18 anaconda crash)
  2013-01-19 22:53 btrfs: failed to read chunk tree on vde1 (f18 anaconda crash) Reartes Guillermo
@ 2013-01-20 13:22 ` Hugo Mills
  2013-01-21 22:44   ` Reartes Guillermo
  0 siblings, 1 reply; 3+ messages in thread
From: Hugo Mills @ 2013-01-20 13:22 UTC (permalink / raw)
  To: Reartes Guillermo; +Cc: linux-btrfs

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

On Sat, Jan 19, 2013 at 07:53:08PM -0300, Reartes Guillermo wrote:
> Hi,
> 
> I reported a bug to anaconda (rhbz 901905), but it might be btfs related.
> 
> Anaconda does this:
> 
> 18:49:10,317 INFO program: Running... mkfs.btrfs --data=single
> --label=fedora /dev/vdb1 /dev/vdc1 /dev/vdd1 /dev/vde1
> 18:49:10,742 INFO program:
> 18:49:10,746 INFO program: WARNING! - Btrfs Btrfs v0.19 IS EXPERIMENTAL
> 18:49:10,746 INFO program: WARNING! - see http://btrfs.wiki.kernel.org
> before using
> 18:49:10,748 INFO program:
> 18:49:10,749 INFO program: SMALL VOLUME: forcing mixed metadata/data groups
> 18:49:10,750 INFO program: Created a data/metadata chunk of size 8388608
> 18:49:10,750 INFO program: adding device /dev/vdc1 id 2
> 18:49:10,751 INFO program: adding device /dev/vdd1 id 3
> 18:49:10,752 INFO program: adding device /dev/vde1 id 4
> 18:49:10,752 INFO program: fs created label fedora on /dev/vdb1

   Out of interest, how big are these devices?

   Hugo.

[snip]
> I booted again and did both the mk.btrfs and the mount manually and i
> got the same error.
> 
> Is it a known issue?

-- 
=== 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 believe in free will because we have no choice. ---        

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: btrfs: failed to read chunk tree on vde1 (f18 anaconda crash)
  2013-01-20 13:22 ` Hugo Mills
@ 2013-01-21 22:44   ` Reartes Guillermo
  0 siblings, 0 replies; 3+ messages in thread
From: Reartes Guillermo @ 2013-01-21 22:44 UTC (permalink / raw)
  To: Hugo Mills, Reartes Guillermo, linux-btrfs

Thanks for asking, but in the end it was not btrfs related at all.

Virt-Manager failed to issue a warning (for yet unknown reasons) and a
single hard disk image was being accessed as two
different devices...

I spent quite a bit of time until i found it. (normally, virt-manager
prevents this)

Cheers.


On Sun, Jan 20, 2013 at 10:22 AM, Hugo Mills <hugo@carfax.org.uk> wrote:
> On Sat, Jan 19, 2013 at 07:53:08PM -0300, Reartes Guillermo wrote:
>> Hi,
>>
>> I reported a bug to anaconda (rhbz 901905), but it might be btfs related.
>>
>> Anaconda does this:
>>
>> 18:49:10,317 INFO program: Running... mkfs.btrfs --data=single
>> --label=fedora /dev/vdb1 /dev/vdc1 /dev/vdd1 /dev/vde1
>> 18:49:10,742 INFO program:
>> 18:49:10,746 INFO program: WARNING! - Btrfs Btrfs v0.19 IS EXPERIMENTAL
>> 18:49:10,746 INFO program: WARNING! - see http://btrfs.wiki.kernel.org
>> before using
>> 18:49:10,748 INFO program:
>> 18:49:10,749 INFO program: SMALL VOLUME: forcing mixed metadata/data groups
>> 18:49:10,750 INFO program: Created a data/metadata chunk of size 8388608
>> 18:49:10,750 INFO program: adding device /dev/vdc1 id 2
>> 18:49:10,751 INFO program: adding device /dev/vdd1 id 3
>> 18:49:10,752 INFO program: adding device /dev/vde1 id 4
>> 18:49:10,752 INFO program: fs created label fedora on /dev/vdb1
>
>    Out of interest, how big are these devices?
>
>    Hugo.
>
> [snip]
>> I booted again and did both the mk.btrfs and the mount manually and i
>> got the same error.
>>
>> Is it a known issue?
>
> --
> === 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 believe in free will because we have no choice. ---

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2013-01-21 22:44 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-01-19 22:53 btrfs: failed to read chunk tree on vde1 (f18 anaconda crash) Reartes Guillermo
2013-01-20 13:22 ` Hugo Mills
2013-01-21 22:44   ` Reartes Guillermo

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).