btrfs: open_ctree failed

btrfs: open_ctree failed

[Yulin, Denis]

Hi all,=C2=A0just=C2=A0apologize for=C2=A0my English.
In=C2=A0a=C2=A0nice,=C2=A0warm evening,=C2=A0turn off the=C2=A0electric=
ity,=C2=A0and=C2=A0my router=C2=A0with
btrfs on root,=C2=A0broke=C2=A0..
I removed the image of a partition (10G), I will now rearrange the
system is probably on ext4 ..

Start the discussion -=C2=A0http://www.linux.org.ru/forum/general/64658=
51
OS=C2=A0during the fall=C2=A0- Debian=C2=A06 (2.6.39=C2=A0kernel=C2=A0f=
rom=C2=A0sid),=C2=A0mounted
filesystem=C2=A0with parameters=C2=A0compression=3Dlzo
btfs-progs v0.19 from git.
btrfs-show - all ok;
=46S is the LVM;

root@sysresccd /root % mount -t btrfs -o compress=3Dlzo /dev/mapper/nas=
-root /re
mount: wrong fs type, bad option, bad superblock on /dev/mapper/nas-roo=
t,
=C2=A0 =C2=A0 =C2=A0 =C2=A0missing codepage or helper program, or other=
 error
=C2=A0 =C2=A0 =C2=A0 =C2=A0In some cases useful info is found in syslog=
 - try
=C2=A0 =C2=A0 =C2=A0 =C2=A0dmesg | tail =C2=A0or so
root@sysresccd /root % dmesg | tail
[ 3821.972350] parent transid verify failed on 3807195136 wanted 5412 f=
ound 5414
[ 3821.972364] parent transid verify failed on 3807195136 wanted 5412 f=
ound 5414
[ 3821.979182] btrfs: open_ctree failed
[ 6298.660270] device label root devid 1 transid 12174 /dev/mapper/nas-=
root
[ 6298.660657] btrfs: use lzo compression
[ 6298.662878] parent transid verify failed on 3807195136 wanted 5412 f=
ound 5414
[ 6298.663321] parent transid verify failed on 3807195136 wanted 5412 f=
ound 5414
[ 6298.663584] parent transid verify failed on 3807195136 wanted 5412 f=
ound 5414
[ 6298.663595] parent transid verify failed on 3807195136 wanted 5412 f=
ound 5414
[ 6298.669180] btrfs: open_ctree failed
root@sysresccd /root % btrfsck /dev/nas/root
parent transid verify failed on 3807195136 wanted 5412 found 5414
parent transid verify failed on 3807195136 wanted 5412 found 5414
parent transid verify failed on 3807195136 wanted 5412 found 5414
btrfsck: disk-io.c:416: find_and_setup_root: Assertion `!(!root->node)'=
 failed.
zsh: abort =C2=A0 =C2=A0 =C2=A0btrfsck /dev/nas/root
--
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

Re: btrfs: open_ctree failed

[Samuel Just]

Looks like it, cross posting to linux-btrfs.
-Sam

On Mon, Dec 12, 2011 at 7:20 PM, Matt Weil <mweil@genome.wustl.edu> wro=
te:
>
> another butter bug?
>
>> btrfs: open_ctree failed
>> ------------[ cut here ]------------
>> WARNING: at fs/btrfs/inode.c:2194 btrfs_orphan_commit_root+0xb0/0xc0
>> [btrfs]()
>> Hardware name: ProLiant DL380 G5
>> Modules linked in: btrfs zlib_deflate nfsd exportfs autofs4 nfs lock=
d
>> fscache auth_rpcgss nfs_acl sunrpc bonding ipv6 dm_mirror dm_region_=
hash
>> dm_log ipmi_si ipmi_msghandler hpilo pcspkr serio_raw sg iTCO_wdt
>> iTCO_vendor_support i5k_amb i5000_edac edac_core bnx2 shpchp ext4 mb=
cache
>> jbd2 sr_mod cdrom pata_acpi ata_generic ata_piix hpsa cciss radeon t=
tm
>> drm_kms_helper drm hwmon i2c_algo_bit i2c_core dm_mod [last unloaded=
:
>> speedstep_lib]
>> Pid: 42, comm: kworker/4:1 Not tainted 3.0.8 #3
>> Call Trace:
>> =C2=A0[<ffffffff8105ff5f>] warn_slowpath_common+0x7f/0xc0
>> =C2=A0[<ffffffff8105ffba>] warn_slowpath_null+0x1a/0x20
>> =C2=A0[<ffffffffa04c8250>] btrfs_orphan_commit_root+0xb0/0xc0 [btrfs=
]
>> =C2=A0[<ffffffffa04c3845>] commit_fs_roots+0xc5/0x1b0 [btrfs]
>> =C2=A0[<ffffffffa04c48fe>] btrfs_commit_transaction+0x40e/0x850 [btr=
fs]
>> =C2=A0[<ffffffff8104cd80>] ? __dequeue_entity+0x30/0x50
>> =C2=A0[<ffffffff81082670>] ? wake_up_bit+0x40/0x40
>> =C2=A0[<ffffffffa04c5010>] ? btrfs_end_transaction+0x20/0x20 [btrfs]
>> =C2=A0[<ffffffffa04c502f>] do_async_commit+0x1f/0x30 [btrfs]
>> =C2=A0[<ffffffff8107b9d1>] process_one_work+0x131/0x450
>> =C2=A0[<ffffffff8107d57c>] worker_thread+0x17c/0x3c0
>> =C2=A0[<ffffffff8107d400>] ? manage_workers+0x220/0x220
>> =C2=A0[<ffffffff81081ff6>] kthread+0x96/0xa0
>> =C2=A0[<ffffffff814e3f04>] kernel_thread_helper+0x4/0x10
>> =C2=A0[<ffffffff81081f60>] ? kthread_worker_fn+0x1a0/0x1a0
>> =C2=A0[<ffffffff814e3f00>] ? gs_change+0x13/0x13
>> ---[ end trace ed99a1a191db74aa ]---
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel"=
 in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at =C2=A0http://vger.kernel.org/majordomo-info.ht=
ml
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" i=
n
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: btrfs: open_ctree failed

[Not Zippy]

Was working this morning and my kernel crashed. Unfortunately one of
my two btrfs partitions would not mount after rebooting, this is the
error log:
[ 1518.147030] device label MediaNew devid 1 transid 28844 /dev/sdc3
[ 1518.147364] btrfs: enabling auto defrag
[ 1518.147372] btrfs: use lzo compression
[ 1518.632469] parent transid verify failed on 498530500608 wanted
26696 found 27535
[ 1518.632707] parent transid verify failed on 498530500608 wanted
26696 found 27535
[ 1518.640263] parent transid verify failed on 498530500608 wanted
26696 found 27535
[ 1518.640279] parent transid verify failed on 498530500608 wanted
26696 found 27535
[ 1518.660243] btrfs: open_ctree failed

Tried btrfsck after a lot of messages got:
...
leaf parent key incorrect 563096514560
Unable to find block group for 0
btrfsck: extent-tree.c:284: find_search_start: Assertion `!(1)' failed.

My kernel 3.0.0-16-generic, any hope for this ? Or is he dead jim ? I
don't have any snapshots of the partition.

Thoughts ?
thanks

Re: btrfs: open_ctree failed

[Hugo Mills]

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

On Mon, Mar 26, 2012 at 02:40:24PM -0700, Not Zippy wrote:
> Was working this morning and my kernel crashed. Unfortunately one of
> my two btrfs partitions would not mount after rebooting, this is the
> error log:
> [ 1518.147030] device label MediaNew devid 1 transid 28844 /dev/sdc3
> [ 1518.147364] btrfs: enabling auto defrag
> [ 1518.147372] btrfs: use lzo compression
> [ 1518.632469] parent transid verify failed on 498530500608 wanted
> 26696 found 27535
> [ 1518.632707] parent transid verify failed on 498530500608 wanted
> 26696 found 27535
> [ 1518.640263] parent transid verify failed on 498530500608 wanted
> 26696 found 27535
> [ 1518.640279] parent transid verify failed on 498530500608 wanted
> 26696 found 27535
> [ 1518.660243] btrfs: open_ctree failed
> 
> Tried btrfsck after a lot of messages got:
> ...
> leaf parent key incorrect 563096514560
> Unable to find block group for 0
> btrfsck: extent-tree.c:284: find_search_start: Assertion `!(1)' failed.

   btrfsck doesn't fix anything. It just checks the FS and tells you
that there's something wrong (which it just did). If you're feeling
very very brave, there's the "dangerdonteveruse" branch of the
btrfs-progs tools in cmason's git, which might fix things.
Alternatively, it might fuck up your filesystem so badly there's no
way you can retrieve any remaining data from it. Your choice.

> My kernel 3.0.0-16-generic, any hope for this ? Or is he dead jim ? I
            ^^^^^ Old, old, old. It's a bit late now, but you should
                  really keep up with the latest kernels. That should help
				  minimise this kind of event.

> don't have any snapshots of the partition.

   btrfs snapshots wouldn't help here. LVM snapshots would, of course.

   There's a restore tool that may allow you to copy off any data
that's not backed up (you *do* have backups, right? for an
experimental filesystem?). See the wiki at [1].

   Hugo.

[1] http://btrfs.ipv5.de/index.php?title=Restore

-- 
=== 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
    --- "I will not be pushed,  filed, stamped, indexed, briefed, ---    
               debriefed or numbered.  My life is my own."               

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

Re: btrfs: open_ctree failed

[Not Zippy]

Hugo
I did try the dangerdonteveruse branch and thats the error btrfsck
--repair gave me. Looks like the btrfs-restore command may work
(thanks!). And yes I do have backups for the important data - I had
some other data on there which would need to be d/l again..

I don't dabble that much with the kernel - this is a straight ubuntu
which I regularly do their updates - Can I advance the kernel beyond ?
If your recommending this I will definitely look into it (since I dont
want a repeat of this to occur) Does this article describe the update
well enough ? http://www.upubuntu.com/2012/03/how-to-install-linux-33-k=
ernel-in.html

Thanks for the help
Nz

>
> =A0 btrfsck doesn't fix anything. It just checks the FS and tells you
> that there's something wrong (which it just did). If you're feeling
> very very brave, there's the "dangerdonteveruse" branch of the
> btrfs-progs tools in cmason's git, which might fix things.
> Alternatively, it might fuck up your filesystem so badly there's no
> way you can retrieve any remaining data from it. Your choice.
>
>> My kernel 3.0.0-16-generic, any hope for this ? Or is he dead jim ? =
I
> =A0 =A0 =A0 =A0 =A0 =A0^^^^^ Old, old, old. It's a bit late now, but =
you should
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0really keep up with the latest ker=
nels. That should help
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0mi=
nimise this kind of event.
>
>> don't have any snapshots of the partition.
>
> =A0 btrfs snapshots wouldn't help here. LVM snapshots would, of cours=
e.
>
> =A0 There's a restore tool that may allow you to copy off any data
> that's not backed up (you *do* have backups, right? for an
> experimental filesystem?). See the wiki at [1].
>
> =A0 Hugo.
>
> [1] http://btrfs.ipv5.de/index.php?title=3DRestore
>
> --
> =3D=3D=3D Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.=
org.uk =3D=3D=3D
> =A0PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org=
=2Euk
> =A0 =A0--- "I will not be pushed, =A0filed, stamped, indexed, briefed=
, ---
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 debriefed or numbered. =A0My life is my o=
wn."
--
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

Re: btrfs: open_ctree failed

[Hugo Mills]

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

On Mon, Mar 26, 2012 at 03:36:13PM -0700, Not Zippy wrote:
> Hugo
> I did try the dangerdonteveruse branch and thats the error btrfsck
> --repair gave me.

   Oooh, a brave one, I see. ;)

> Looks like the btrfs-restore command may work (thanks!). And yes I
> do have backups for the important data - I had some other data on
> there which would need to be d/l again..

   Excellent. We don't need to set the hounds onto you, then.

> I don't dabble that much with the kernel - this is a straight ubuntu
> which I regularly do their updates - Can I advance the kernel beyond ?

   Yes, there's a PPA[1] for it (documented in the "Getting Started"
page on the btrfs wiki at [2]).

[1] http://kernel.ubuntu.com/~kernel-ppa/mainline/
[2] http://btrfs.ipv5.de/index.php?title=Getting_started#Ubuntu_Linux

> If your recommending this I will definitely look into it (since I dont
> want a repeat of this to occur) Does this article describe the update
> well enough ? http://www.upubuntu.com/2012/03/how-to-install-linux-33-kernel-in.html

   I'm not 100% sure -- I don't run Ubuntu on very many machines. You
will probably need to add the PPA to your /etc/apt/sources.list file.
I'm not sure exactly which URL you need, though. I'd guess that
Googling for "Ubuntu Kernel PPA" will get you the relevant
instructions. (Or just download the .deb manually from the URL above
and intall with dpkg -i).

   I'd definitely recommend running as recent a kernel as you can --
either the last released (3.3 in this case), or the latest -rc (still
also 3.3 right now, but going up to 3.4-rc1 in a few days' time). Both
should be available in the kernel PPA.

   Hugo.

-- 
=== 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
    --- There is no dark side to the Moon, really. As a matter of ---    
                          fact,  it's all dark.                          

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

Re: btrfs: open_ctree failed

[Chris Samuel]

On 27/03/12 09:47, Hugo Mills wrote:

>    I'd definitely recommend running as recent a kernel as you can --
> either the last released (3.3 in this case)

I'm not sure I'd recommend 3.3; there were a number of reports of a
regression regarding preamture ENOSPC in that code which was bisected to
a particular change but I didn't see any evidence of it being fixed in
3.3 (only 2 unrelated fixes were merged after rc6, where this problem
was confirmed).

 https://lkml.org/lkml/2012/3/9/624

I'm currently running 3.2.13 from the Ubuntu site here:

 http://kernel.ubuntu.com/~kernel-ppa/mainline/

I just download the deb via Lynx and install it with dpkg -i $PACKAGE.

cheers,
Chris
-- 
 Chris Samuel  :  http://www.csamuel.org/  :  Melbourne, VIC

Re: btrfs: open_ctree failed

[Not Zippy]

One entire subvolume was restored. But there were 4 subvolumes on that
partition. Is there a way to specify/force the restore of a different
subvolume ?

find-root seems to only find a single root.

thanks

On Mon, Mar 26, 2012 at 3:47 PM, Hugo Mills <hugo@carfax.org.uk> wrote:
> On Mon, Mar 26, 2012 at 03:36:13PM -0700, Not Zippy wrote:
>> Hugo
>> I did try the dangerdonteveruse branch and thats the error btrfsck
>> --repair gave me.
>
> =A0 Oooh, a brave one, I see. ;)
>
>> Looks like the btrfs-restore command may work (thanks!). And yes I
>> do have backups for the important data - I had some other data on
>> there which would need to be d/l again..
>
> =A0 Excellent. We don't need to set the hounds onto you, then.
>
>> I don't dabble that much with the kernel - this is a straight ubuntu
>> which I regularly do their updates - Can I advance the kernel beyond=
 ?
>
> =A0 Yes, there's a PPA[1] for it (documented in the "Getting Started"
> page on the btrfs wiki at [2]).
>
> [1] http://kernel.ubuntu.com/~kernel-ppa/mainline/
> [2] http://btrfs.ipv5.de/index.php?title=3DGetting_started#Ubuntu_Lin=
ux
>
--
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

Re: btrfs: open_ctree failed

[Hugo Mills]

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

On Tue, Mar 27, 2012 at 05:58:17AM -0700, Not Zippy wrote:
> One entire subvolume was restored. But there were 4 subvolumes on that
> partition. Is there a way to specify/force the restore of a different
> subvolume ?
> 
> find-root seems to only find a single root.

   There is only a single root tree, so that's understandable. If you
have a look at the documentation for restore[1], it mentions (right
near the bottom of the page) that -r will allow you to select an
alternative subvolume to recover from.

   Hugo.

[1] http://btrfs.ipv5.de/index.php?title=Restore

> thanks
> 
> On Mon, Mar 26, 2012 at 3:47 PM, Hugo Mills <hugo@carfax.org.uk> wrote:
> > On Mon, Mar 26, 2012 at 03:36:13PM -0700, Not Zippy wrote:
> >> Hugo
> >> I did try the dangerdonteveruse branch and thats the error btrfsck
> >> --repair gave me.
> >
> >   Oooh, a brave one, I see. ;)
> >
> >> Looks like the btrfs-restore command may work (thanks!). And yes I
> >> do have backups for the important data - I had some other data on
> >> there which would need to be d/l again..
> >
> >   Excellent. We don't need to set the hounds onto you, then.
> >
> >> I don't dabble that much with the kernel - this is a straight ubuntu
> >> which I regularly do their updates - Can I advance the kernel beyond ?
> >
> >   Yes, there's a PPA[1] for it (documented in the "Getting Started"
> > page on the btrfs wiki at [2]).
> >
> > [1] http://kernel.ubuntu.com/~kernel-ppa/mainline/
> > [2] http://btrfs.ipv5.de/index.php?title=Getting_started#Ubuntu_Linux
> >

-- 
=== 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
   --- The enemy have elected for Death by Powerpoint. That's what ---   
                         they shall get.  -- gdb                         

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

Re: btrfs: open_ctree failed

[Not Zippy]

I had found that note on the restore but my restore.c does not allow
that flag (it is also missing the "m" flag as well), I used the branch
dangerousdonteveruse on
https://git.kernel.org/?p=3Dlinux/kernel/git/mason/btrfs-progs.git I
switched to the master branch to see if there was a difference but it
does not appear to be any different. (I did find a btrfs-progs on
git-hub which appears to have those flags, but i thought the best to
use would be on git.kernel. )

Assuming I can locate the correct restore.c, is there a some other
software to determine the object id of the subvolume ?  the root
object id was 5

thanks
Nz

On Tue, Mar 27, 2012 at 6:02 AM, Hugo Mills <hugo@carfax.org.uk> wrote:
> On Tue, Mar 27, 2012 at 05:58:17AM -0700, Not Zippy wrote:
>> One entire subvolume was restored. But there were 4 subvolumes on th=
at
>> partition. Is there a way to specify/force the restore of a differen=
t
>> subvolume ?
>>
>> find-root seems to only find a single root.
>
> =A0 There is only a single root tree, so that's understandable. If yo=
u
> have a look at the documentation for restore[1], it mentions (right
> near the bottom of the page) that -r will allow you to select an
> alternative subvolume to recover from.
>
--
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

Re: btrfs: open_ctree failed

[Not Zippy]

Thought I would let you know I did get things figured out. I used
btrfs-progs from github
https://github.com/josefbacik/btrfs-progs

I also used the findroot function from there which generated more
possibilities for the root objectid.
By pluging in the guesses from findroot into -r objectid for the
restore I was able to access the data from my subvolumes.

thanks
Nz

On Tue, Mar 27, 2012 at 8:21 AM, Not Zippy <notzippy@gmail.com> wrote:
> I had found that note on the restore but my restore.c does not allow
> that flag (it is also missing the "m" flag as well), I used the branc=
h
> dangerousdonteveruse on
> https://git.kernel.org/?p=3Dlinux/kernel/git/mason/btrfs-progs.git I
> switched to the master branch to see if there was a difference but it
> does not appear to be any different. (I did find a btrfs-progs on
> git-hub which appears to have those flags, but i thought the best to
> use would be on git.kernel. )
>
> Assuming I can locate the correct restore.c, is there a some other
> software to determine the object id of the subvolume ? =A0the root
> object id was 5
>
> thanks
> Nz
>
> On Tue, Mar 27, 2012 at 6:02 AM, Hugo Mills <hugo@carfax.org.uk> wrot=
e:
>> On Tue, Mar 27, 2012 at 05:58:17AM -0700, Not Zippy wrote:
>>> One entire subvolume was restored. But there were 4 subvolumes on t=
hat
>>> partition. Is there a way to specify/force the restore of a differe=
nt
>>> subvolume ?
>>>
>>> find-root seems to only find a single root.
>>
>> =A0 There is only a single root tree, so that's understandable. If y=
ou
>> have a look at the documentation for restore[1], it mentions (right
>> near the bottom of the page) that -r will allow you to select an
>> alternative subvolume to recover from.
>>
--
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