From: "René Vangsgaard" <rene.vangsgaard@gmail.com>
To: Jan Schmidt <list.btrfs@jan-o-sch.net>
Cc: cwillu <cwillu@cwillu.com>, "Ken D'Ambrosio" <ken@jots.org>,
linux-btrfs@vger.kernel.org
Subject: Re: mount errors
Date: Tue, 22 Nov 2011 14:24:54 +0000 [thread overview]
Message-ID: <CAPWZyXZkdnaXJhEWW81LuaEHtMDEQgMBfOKGZCu8y_cMF1JQAA@mail.gmail.com> (raw)
In-Reply-To: <4ECBAA17.2070404@jan-o-sch.net>
I did a reboot, and now I am trying to recover from a disk with no
partition table. Currently gpart has been running for 30 mins - stupid
me for not printing the partition table.
I did nothing more than executing "make" and "make install" in ./btrs-p=
rogs/.
On 22 November 2011 13:56, Jan Schmidt <list.btrfs@jan-o-sch.net> wrote=
:
> On 22.11.2011 14:26, Ren=C3=A9 Vangsgaard wrote:
>> I got the build working by changing -lpthread to -pthread in the gcc=
call:
>>
>> gcc -pthread -g -O0 -o btrfs btrfs.o btrfs_cmds.o scrub.o ctree.o
>> disk-io.o radix-tree.o extent-tree.o print-tree.o root-tree.o
>> dir-item.o file-item.o inode-item.o inode-map.o crc32c.o rbtree.o
>> extent-cache.o extent_io.o volumes.o utils.o btrfs-list.o btrfslabel=
=2Eo
>> =C2=A0-luuid
>>
>> Using -lpthread gave a build error. I will now reboot and have a loo=
k...
>
> We've already queued a fix for that, it's just not pushed out yet.
> -Jan
>
--
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
next prev parent reply other threads:[~2011-11-22 14:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-19 13:01 mount errors René Vangsgaard
2011-11-21 16:27 ` Ken D'Ambrosio
2011-11-21 23:29 ` René Vangsgaard
2011-11-22 4:55 ` cwillu
2011-11-22 13:01 ` René Vangsgaard
2011-11-22 13:06 ` cwillu
2011-11-22 13:26 ` René Vangsgaard
2011-11-22 13:56 ` Jan Schmidt
2011-11-22 14:24 ` René Vangsgaard [this message]
2011-11-24 23:04 ` René Vangsgaard
2011-11-21 23:32 ` René Vangsgaard
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=CAPWZyXZkdnaXJhEWW81LuaEHtMDEQgMBfOKGZCu8y_cMF1JQAA@mail.gmail.com \
--to=rene.vangsgaard@gmail.com \
--cc=cwillu@cwillu.com \
--cc=ken@jots.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=list.btrfs@jan-o-sch.net \
/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).